Feedback Technical Grievances

Did we just shit ourselves again?
 
Where are these FOSS lists maintained?
 
yep, connection timed out on clearnet 100% of the time. Elliot must be extra made. I bet we actually found his consent accident victim.

tracepath still seems to get through, for what it's worth.
 
OK, .net is working, slowly, but tor and .st are buggered.

Null fell asleep on the keyboard, again...

edit: tor is back.
 
This looks concerning.
Clearnet crapped out.
TOR fine.
Redlines.jpg
 
  • Agree
  • Like
Reactions: Vecr and JoshPlz
Where are these FOSS lists maintained?
There's a whole category on GitHub:

Yes they're called blocklists instead of blacklists now, which should be the first red flag.

Here's an example of a major one:

Note for example that they have a "fakenews" blocklist. But if you browse the list, it includes several ordinary right-wing news sites. While some are of low quality, they're still not "fake" in the sense of being clickbait pretending to be a news site.

You can also find lists specifically for blocking "hate" and the like.
 
im having no issues on net
It's weird as fuck because I'm on .net right now.
Maybe the bullshit with that Cogent fag sticking his nose in is causing routing problems.
I don't know shit about how the Internet works sadly.
I was having problems connecting ting to clearnet and switched to TOR but the clearnet seems to be working again fine for now.
 
  • Like
Reactions: Asian tech support
Yes, I'm on .net on tor, but on clearnet it seems to be fucked again. tracepath to 195.3.223.98 is failing. I guess my ISP (plusnet), or its upstream, has decided to nuke the routes again.
 
.net and .st seems to be blocked by both of my shitty ISPs in my shithole country since I can only access both sites by using a VPN set on the US.

Does anybody has the terminal command and tools to confirm this block? I'm going to yell at my ISPs and I want to have as much evidence of the block as I can.

EDIT: Or like the above poster said, it could be the upstreams. Which seems the most likely culprit right now.
 
.net connected immediately through polish VPN, United States, Netherlands and UK are not connecting. Not sure what that's all about, but it's not consistent with DDoS. I'm guessing Elliot is pulling out the big guns and girl talking into the early hours since his thread escalated.
 
.net connected immediately through polish VPN, United States, Netherlands and UK are not connecting. Not sure what that's all about, but it's not consistent with DDoS. I'm guessing Elliot is pulling out the big guns and girl talking into the early hours since his thread escalated.
I live in American and .net works fine, maybe it's a regional block?
 
I haven't had any issues from the USA. Two of the .net IPs (31.133.0.112 and 2001:67c:2044:c141:0:1:5527:1) showed widespread failures on ping.pe, but the other two were mostly working, and the two failing ones were taken out of rotation maybe a couple of hours ago. It appears that .st has only been using the two working ones all along.

So it may be regional.
 
  • Agree
Reactions: JoshPlz
Back