Damn! Any word on the cause?

I will!

Thank you!

Let me go into more detail. Don't use the same browser for clearnet and tor. Never do this.

It's best to clear the data from whatever browser you use for tor every time you start it. The tor browser does this on it's own. It would be easy enough to correlate you via left-over browser data.

You should really be using the tor browser unless you have a specific need to not.

Don't use javascript unless you really need it. That can expose you. Not only that, but who wants to run untrusted code? This will break some sites.

Don't mix your lives. Your bank account should never be accessed over tor. Nor your facebook, twitter or whatever else. Unless that's the only way you ever access it. Think political bloggers in some less than free countries. It depends on your case use. But, never login with the same account on both networks.

Yes, but be smart about it.

I maintain my own link list [here]. I check every link on it once a week. I'm actually updating it right now as I type this comment, actually, so it's especially fresh.

Yes it's fine. Just make sure your browser turns off headers, or, you are using the tor browser. The security risk comes from the fact that some websites request the headers of what ever other tabs you happen to have open. Turning off header requests in firefox should solve this.

yes, fuck the government

Perfectly safe. I do it all the time.

v2

they seem to made the switch because the last place they could use to do bitcoin exchanges finally blocked tor.

niggers?

don't use it, use claws mail

based

Thanks!

~$ torsocks curl -s https://check.torproject.org/ | grep Congratulations.
 Congratulations. This browser is configured to use Tor.
 Congratulations. This browser is configured to use Tor.

Still no go in Thunderbird with setting up the proxy. I'll dig into it more, because I think that's the ticket. The TorBirdy plugin is outdated and has been for a while, which is what seems to be used previously. I may boot up in Tails or something similar to see if the issue persists.

the primary requirement for an exit node that no one tells you about:

balls of steel.

Has anyone ever been arrested or held legally liable for running an exit node (in a modern country, like the US/CA/UK/Etc)?

I've thought about running one as well since my server provider is okay with it as long as I handle the abuse complaints which is basically copy/pasting a cookie cutter response on how it's an exit-node and not possible to tell the origin of whatever it is the complaint is about.

the primary requirement for an exit node that no one tells you about:

balls of steel.

Oh cool that's even better it's backed by the torproject. I'll check it out!

For a terminal based Tor monitor, look no further than nyx: https://nyx.torproject.org/

Ok cool thanks. I just wanted to see network charts basically. I will look into those.

Per https://community.torproject.org/relay/relays-requirements/

A <40 Mbit/s non-exit relay should have at least 512 MB of RAM available.
A non-exit relay faster than 40 Mbit/s should have at least 1 GB of RAM.
On an exit relay we recommend at least 1.5 GB of RAM per tor instance.

Not sure about the control panel to manage it, but that'd add overhead to the RAM requirement. Hopefully someone will correct me if I'm wrong, but I'm pretty sure it's "set it and forget it". What are you wanting to do with a control panel? See network graphs and stats and stuff? Observium or Librenms will collect pretty much any server related stat that you could ever need. Those will chart and graph things like CPU, RAM, Disk IO, Network Graphs, uptime, etc all over time. From very recent to multiple years if you keep it running long enough.

That's basically it, all those request clogs up them internet pipes.

Regular sites often use CDN's (server networks to share the load), and a clearnet solution would have one server sort out illegitimate requests and serve CAPTCHA's while a different server that doesn't see any of the unwanted traffic host the site.

Is this a problem solvable through certificates? Like you hide the certificates behind a captcha and revoke certificates of misbehaving users.

Oh okay I guess that makes a bit more sense. I always thought a DDOS attack had to have a specific port or webpage as a target. But I don't know how one would be sent through the tor network and I dont even really know how they're sent through the regular internet other than it's just a bunch of requests from different locations.

From my understanding, the CAPTCHA is a very low intensity operation that barely takes any server load, while logging in ot registration or making purchases or even browsing like a script would do repeatedly to complete a DDoS attack. Having a CAPTCHA effectively prevents scripts from doing these high intensity operations multiple times per second.

For clear web sites this is an awful approach, but since you can’t really block IPs on Tor, it’s the best and most effective tool market owners have.