myofficialaccount

joined 1 year ago
[–] [email protected] 3 points 11 months ago

It's awesome! I'm running this since years without any problems.

[–] [email protected] 0 points 11 months ago

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.

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (3 children)

JBOD via mergerfs and snapraid on top for parity is a possible solution.

[–] [email protected] 1 points 11 months ago (1 children)
[–] [email protected] 3 points 11 months ago (5 children)

That's the thing, you'd have to connect to the seedbox via VPN anyways.

I'm using usenet anyway, always have, always will ;⁠-⁠)

[–] [email protected] 6 points 11 months ago (9 children)

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?

[–] [email protected] 30 points 11 months ago

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.

[–] [email protected] 3 points 11 months ago

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.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

"dosen't belive"

But lowercase "linux" marked as wrongly spelled is a problem. Priorities.

[–] [email protected] 1 points 1 year ago

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 😄)

[–] [email protected] 2 points 1 year ago (2 children)

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.

[–] [email protected] 14 points 1 year ago

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.

view more: next ›