There are 3 issues with this:

1. This is a third-party project, not an official part of Bluesky. Bluesky was never meant to work with ActivityPub, that was a clear design choice. This is just a workaround.
2. It's opt-in, meaning most accounts will never get federated, because people just aren't aware that something like this exists. This especially applies to new users.
3. It relies on a centralized service, Bluesky and ActivityPub servers don't talk directly to each other, which would be required for true federation. Federation is always decentralized, this is the exact opposite.

I don't understand why anyone should use Bluesky with cheap hacks to attempt to fix Bluesky's poor design choices and or utter incompetence, if they could just use Mastodon and federate with the Fediverse over ActivityPub by default.

From a user perspective, Bluesky is just Mastodon with a recommendation algorithm. There is no other protocol required for this, everything could easily be done using ActivityPub exclusively. I will never care about Bluesky, since it tries to be the new Twitter, but the enshittification of Twitter began when they introduced their crappy algorithm, instead of just displaying tweets of accounts you follow in chronological order (like Mastodon does it).

For my fellow fish shell users: git log --graph --abbrev-commit --no-decorate --date=format:'%Y-%m-%d %H:%M:%S' --format=format:'%C(8)%>|(16)%h %C(7)%ad %C(8)%<(16,trunc)%an %C(auto)%d %>|(1)%s' --all

Well the reasons they provide im the modlog are absolutely ridiculous, it's mostly something like "Rule 1", "Rule 2" or something else absolutely stupid.

This is their stupid excuse. They could still implement ActiviyPub as a secondary federation protocol. (Bluesky <-> Bluesky via ATProto, Bluesky <-> Fediverse via ActivityPub). They decided against it. It's an intentional choice, and they're just making up excuses.

your emails aren't hidden from Google as much as you think.

You're wrong, Proton encrypts notifications before sending them to you through Google or Apple push services. The notification is then decrypted in the Proton client on your phone, and only then displayed to you.

Probably an unpopular opinion, but I've never seen the point of PWAs. I don't want a crappy website as an icon on my homescreen, I want a proper native app. If the app is privacy-invasive, I will either find a FOSS alternatives, or isolate it in a separate user profile.

The main reason I think they may need google services is the banking app. Mine will refuse to launch without google services installed.

That's true, I also need Play services for mine, but I have a special user profile for it.

No, this is specifically for DNS over UDP (Port 53). What you're looking for is just an HTTPS proxy. There is no difference between a DoH connection and any other HTTPS connection.

Blocking an instance in the user settings just hides communities from that instance in the community search. Defederating hides all communities, posts, comments and user from that instance. It's not implemented the same way, probably on purpose, because the Lemmy devs (who btw are the admins of Lemmy.ml and Lemmygrad.ml) know that half the Fediverse would just block them.

Hell no, fuck Bluesky. There is no reason not to adopt ActivityPub when trying to build an open, federated Twitter alternative. Except for power and control over the platform, its core protocol and ecosystem. Screw these guys, use Mastodon or anything on the Fediverse.

Tell me more about Beehaw, I know about the trouble with lemmy.ml and lemmygrad, but so far haven't heard anything about Beehaw.

They can recieve security updates if you use an alternative ROM such as Lineage or /e/OS.

They can only receive OS updates, but firmware updates are just as important for maintaining the security of a device. These can only be provided by the device manufacturer.

Can you please explain how e/OS/ is insecure?

Sure. It's based on the already insecure LineageOS, you can read more about that here: https://madaidans-insecurities.github.io/android.html#lineageos

On top of that, the /e/OS devs don't release updates in a timely manner, often taking 1-3 months to releases even simple but important Android Security Bulletin patches.

The new Element X is really great, but only available for iOS and Android. Unfortunately no desktop or web version.

I don't think Lemmy currently has notifications for moderation actions, but there are plans to add them: https://github.com/LemmyNet/lemmy/issues/4572

But this issue depends on other issues
https://github.com/LemmyNet/lemmy/issues/2441
https://github.com/LemmyNet/lemmy/issues/2444

If you use a Pixel, why don't you go with GrapheneOS? It is much more secure and private than LineageOS.

They're really overpriced though. Flashing GrapheneOS is really easy thanks to their Web-based installer, and there are countless tutorials on YouTube.

Pixels are great, but definitely make sure to install GrapheneOS to increase your privacy and security

Or, if you want an older phone, try a Pixel 3, 4 or 5

These are outdated and don't get security updates anymore, and thus shouldn't be used anymore. The Pixel 6a is supported until 2028, the Pixel 8 even gets 7 years of security updates (until 2030), the Pixel 8a and 9 are supported until 2031.

/e/OS (also known as Murena) is also a good ROM for privacy

/e/OS is unfortunately highly insecure and shouldn't be compared to GrapheneOS or recommended. Graphene is really the better choice here.

can suggest a Bootloader Unlock: Wall of Shame

Unfortunately it only mentions unlocking. Re-locking the bootloader is just as important, and strictly necessary for Android Verified Boot to work.

Google services shouldn't even be needed for the apps OP listed above. Instagram works just fine without Google services, just like Discord, Telegram and Steam. I don't know about GitHub, but there are FOSS alternatives for it on F-Droid. Spotify (xManager) also works just fine.

You can unlock the bootloader on OnePlus devices, but you can't re-lock it afterwards, permanently leaving your device in an insecure state. This is a really bad idea, and definitely shouldn't be recommended.

The S10 came out in 2019 and hasn't been supported by the manufacturer for a long time, it's not a good idea either.

And lastly, LineageOS itself is pretty insecure. It is much weaker than stock Android or even iOS. You can read more about this here: https://madaidans-insecurities.github.io/android.html#lineageos
or here: https://eylenburg.github.io/android_comparison.htm

It also has much worse app compatibility than GrapheneOS, because it doesn't use the official Google Play services binary (which GrapheneOS puts in a sandbox to restrict its access), except you install it as a system application, which kinda defeats the whole purpose of using a custom ROM in the first place. GrapheneOS is the easiest, best and most secure choice for degoogling.