It's awesome! I'm running this since years without any problems.
Don't know myself as I have no use case for that setup, but it is a well known setup since several years. If teh performance was bad it wouldn't be recommended as an alternative as often.
JBOD via mergerfs and snapraid on top for parity is a possible solution.
Take a look at https://www.reddit.com/r/usenet/wiki/indexers/ for starters
That's the thing, you'd have to connect to the seedbox via VPN anyways.
I'm using usenet anyway, always have, always will ;-)
Is there a way to get and pay seedboxes anonymously? Otherwise the feds could "just" get your information from them. Like with every VPN service you got to trust the the service and their confidentiality (not keeping logs etc) I guess?
Relevant part from the blog post:
What are we doing differently in Firefox? WebRequest
One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.
Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.
Same here, started about the same time. Sadly the crashes aren't catched and logged...other crashes appear under settings > about Firefox> crashes.
It's not even site related - after restarting firefox the sites load as expected.
"dosen't belive"
But lowercase "linux" marked as wrongly spelled is a problem. Priorities.
Thanks, but I already know how to switch DNS and tried that with different DNS resolvers. Flushed DNS caches, too. I'm out of ideas and don't care anymore (well...that last one is a lie 😄)
I don't even use cloudfare's 1.1.1.1 but get into that captcha loop anyway. Worked for some weeks but since about 1 week it's all captcha and no bueno. I have given up.
Interesting! I experience this bug on my windows machine every now and then but wasn't bothered too much with it. Nice to get some background info on that.
Why should it have a GB cap? It's just a way to use your web browser as a torrent client I stead of using a native windows/linux app.
Ja, du verstehst es falsch.
Aus dem Artikel:
Störerhaftung – bis dato
Bei dieser handelt es sich um einen bis dato bestehenden Schutz vor kostenpflichtigen Abmahnungen zugunsten der Betreiber offener Drahtlosnetzwerke.
Bedeutet: wenn du als Betreiber eines Cafés deinen Gästen einen WLAN-Zugang anbietest, die Gäste dann Filme/Spiele/sonstwas per BitTorrent ziehen (und hochladen), furht dir IP zunächst einmal zum Betreiber/Café. Die Abmahnanwälte können aber durch die aktuelle Regelung zur Störerhaftung nicht den Anbieter des WLAN-Zugangs (Betreiber des Cafés) in Anspruch nehmen. Dieser kann vielmehr auf die Gäste verweisen, er selbst ist hinsichtlich Schadensersatz etc. raus. Dass das WLAN hier verschlüsselt sein wird, ist vollkommen irrelevant, da niemand vor dem Café hockt und versucht den Traffic mit zuschneiden. Die Abmahnindustrie nutzt vielmehr angepasste Torrent clients um die IP Adressen der am jeweiligen Torrent beteiligten clients abzugreifen. Dann wird damit jeweils Anzeige gegen unbekannt wegen des strafrechtlich relevanten Urheberrechtsverstoßes gestellt und nach einigen Wochen über die Akteneinsicht die Anschrift des zum fraglichen Zeitpunkt Inhabers der IP Adresse geholt. Dorthin gehen den die bekannten Abmahnungen raus.
Dieses Vorgehen wäre wieder möglich, wenn die aktuelle Regelung zur Störerhaftung nicht beibehalten würde.
Nicht vergessen, eine mögliche Lösung hier zu posten :)
Ah, nice, will try that out. I guess the success rate depends on the way the sites filte email addresses.
Thanks for the reply!
That's something I'm doing too. I wish there was a nicer way though.
Thanks for the reply!
So, a lot of websites filter out known trash mail domains and won't allow any of their email addresses for sign up. I don't see that Simplelogin or Addy can circumvent that (beside using a custom domain which however will be linked to your name via the registrar).
How do you manage websites with such restrictions?
Even if they were - do you really want to trust them that they found every single piece of the rootkit and that there's not something sleeping undetected, loading stuff and running the rootkit again? Do you really want to trust that pc with online banking, email logins and other stuff?