TiffyBelle

Truthfully, nothing changed from my perspective. I mostly use some sports subs, a couple of technical subs, and book subs and they’ve fully gone back to how they were and seem as active as they were. Many mods in those subs received backlash after re-opening for even protesting at all, since many users didn’t know or care about the issue to begin with.

The Simpsons isn’t just an animated sitcom. It’s a documentary about the future:

Separate seems smart. Interacting from Lemmy to Mastodon and vice-versa isn’t exactly the most user friendly experience, since neither platform was really built with those type of interactions in mind.

Perhaps in future it’ll be more seamless.

The thing that makes /r/NoSleep good is the authors. Would be nice if more of the authors there were aware of Lemmy and posted here too.

They are not secure, as it states when you try to DM someone:

This is the same as any other DM service on any site that isn’t end-to-end encrypted, which are the majority. Nothing sensitive should ever be shared via DM.

This is a good take, imo.

I never understood the privacy concerns. Well, I do insofar as it’s safe to assume Meta is privacy-hostile. But many seem to think using Mastodon/Lemmy/etc. are some how “private” corners of the internet when they’re anything but. It is very trivial for someone to access public data on fediverse sites as you’ve pointed out, and if they want that data they’re going to get it.

The beauty of the fediverse is that we can choose who we trust with our core data, such as sign-up details, IP addresses, etc. Signing up to the Threads instance/app would be a disaster from a privacy perspective, but just treating them like any other server and taking advantage of the increased engagement from the content their large instance will post will likely increase content available on the fediverse and engagement across the board. Any decision to defederate with their instance(s) should purely be based on content and nothing more, imo. From a cross-server perspective, they’re no different than any other large instance.

In the ArkenFox zip there’s a updater.bat (Windows) or updater.sh (Linux) script which will pull the latest user.js. I do run this periodically as FF settings will for sure evolve over time with new versions, absolutely.

You could probably schedule these with a task scheduler/cron if you wanted.

I use ArkenFox as a base for a hardened version of FF. It’s not really designed to be used verbatim as that would leave the web in a fairly unusable state, at least for most users. I use a fair few overrides because on my daily browser I want it to be able to use DRM content, be able to login to my bank, etc. For me I see it as a really solid foundation, after which I can intentionally pick and choose what functionality to enable at my own risk rather than have bad defaults thrust upon me by the browser vendor.

I personally don’t concern myself that heavily with attempting to defend my daily browser’s fingerprint. With the default ArkenFox implementation, ResistFingerprinting in FF is enabled and that’s the best you can do, but it also breaks a few things on purpose which impacts functionality. I personally have RF off and use the CanvasBlocker extension to defend against naïve fingerprinting scripts, but that’s a choice users have to make.

If I were that concerned about being fingerprinted by advanced scripts, I’d be using the Mullvad Browser or TOR. Those are really the only effective way to “blend in” to a crowd. Most any browsers people use as their one for daily use that aren’t either of those will be fingerprintable and identifiable by an adversary determined enough, so investing too much time in worrying about a daily browser’s fingerprint beyond defending against naïve scripts isn’t worth that much time investment, imo.

You’re just mad that you weren’t invited.