Email or username:

Password:

Forgot your password?
All posts lnkr_'s posts Post Back to profile
Top-level
Marius DAVID

@lnkr_ I'll mention @bortzmeyer . He seems to like this kind of stuff.

8 May 2023 at 17:33 | Wall-to-wall | Open on mastodon.mariusdavid.fr
7 comments
lnkr_

@marius851000 @bortzmeyer Thanks, could really use some expertise on that.

Very hard to imagine how something like this could happen by accident without breaking the rest of the internet, but maybe there are some explanations after all, I just don't know what else to check.

8 May 2023 at 17:42 | Open on social.inex.rocks
Stéphane Bortzmeyer

@lnkr_ @marius851000 Two of the tested RIPE Atlas probes are at Silknet, two at Magticomas.
Also, when DNS resolvers lie for censorship,they typically return NXDOMAIN or localhost or the IP address of a Web site with warnings. I never saw SERVFAILs being returned.

9 May 2023 at 6:07 | Open on mastodon.gougere.fr
lnkr_

@bortzmeyer @marius851000

Me neither, that's one of the things that makes it even weirder

9 May 2023 at 6:36 | Open on social.inex.rocks
Stéphane Bortzmeyer

@marius851000 @lnkr_ There are ten RIPE Atlas probes in Georgia and not one of them exhibit this behaviour atlas.ripe.net/measurements/53 The "censored" names are fine for all.
RIPE Atlas probes' DNS resolvers may not be typical resolvers so more information is needed (output from dig, names/ASn of providers, etc).
Also, it may have been a temporary network glitch? Or, of course, a test for censorship.

#DNS #censorship #freedomOfSpeech

@marius851000 @lnkr_ There are ten RIPE Atlas probes in Georgia and not one of them exhibit this behaviour atlas.ripe.net/measurements/53 The "censored" names are fine for all.
RIPE Atlas probes' DNS resolvers may not be typical resolvers so more information is needed (output from dig, names/ASn of providers, etc).
Also, it may have been a temporary network glitch? Or, of course, a test for censorship.

9 May 2023 at 6:05 | Open on mastodon.gougere.fr
lnkr_

@bortzmeyer @marius851000

Genuine question - assuming that I wasn't tripping, and both the test I did yesterday and it's results there social.inex.rocks/@lnkr_/11033 were correct, with pretty much all of the ActivityPub server names resolve attempt fails being SERVFAIL, is there any plausible explanation as to how this could have happened because of some glitch or anything else that wasn't done intentionally?

9 May 2023 at 7:16 | Open on social.inex.rocks
Stéphane Bortzmeyer

@lnkr_ @marius851000 Did you test, at the same time, other names such as well-known services (facebook.com), reliable but not famous names (ietf.org), small under-the-radar fediverse instances (mastodon.gougere.fr)?

9 May 2023 at 7:42 | Open on mastodon.gougere.fr
lnkr_

@bortzmeyer @marius851000

There was 1000 AP instances, generally anything with more than 100 active users reported, including mastodon.gougere.fr too, versus the first 1000 names from OONI global raw.githubusercontent.com/citi which I guess can pass as a sort of a combination of well-known and reliable but not famous names.

Unfortunately, I have not saved responses for each of the domains, only overall stats, but now that I scrolled through OONI list I can say with reasonable certainty that those few percents on OONI list resolvance failures was definitely due to the fact that it also contains several ActivityPub instances.

I'll put together more representative lists for next time, but I believe it was already a statistically significant difference.

@bortzmeyer @marius851000

There was 1000 AP instances, generally anything with more than 100 active users reported, including mastodon.gougere.fr too, versus the first 1000 names from OONI global raw.githubusercontent.com/citi which I guess can pass as a sort of a combination of well-known and reliable but not famous names.

9 May 2023 at 8:41 | Open on social.inex.rocks
Go Up