myofficialaccount

Mit Voyager (App ) läuft’s bei mir auf Android seit gestern Abend/Nacht wieder problemlos. Vorher würde ich auch ständig ausgeloggt, jetzt nicht mehr.

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?

Ohne jetzt nachgelesen zu haben: klingt doch schonmal gut! (Warum nicht gleich so?)

Insbesondere die Lockerung und Klarstellung beim Eigenbau sind gut, inkl. Hinweis auf die getrocknete Menge. Unklar ist mir da nur, aber wann das Produkt als getrocknet angesehen wird…das könnte dann im Einzelfall auch wieder Zank geben.

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.