KLISHDFSDF

wow! happy to hear that. May have to play around with it before I fully commit.

For those who may not know, bcachefs (bcachefs.org) was written by the same developer as bcache (wikipedia.org) - TIL! I was always confused when reading headlines about bcachefs but never looked into why someone might give their filesystem such a conflicting name. Now it makes sense. I've used bcache briefly and it worked really well for my use case. Anyone using bcachefs that can speak to their own experience? How does it compare to btrfs?

People need to (re)discover adblockers and alternative apps.

• Firefox+uBlock Origin takes care of nearly all ads on the web.
• NewPipe Lets you watch YouTube without ads (and lets you download videos).
• Pixelfed is like insta without the ads (or people, lets be honest, but you gotta be the change you want to see)
• Mastodon is twitter without ads
• Lemmy reddit without ads

We have the tools and technology, its just a matter of people making the move, but that's hard because of the network effect.

Because not only do you (the end user) have to go out of your way to get it, but you get spammed by Microsoft/Edge and Google/Chrome to install a "faster" and "more secure" browser. Additionally, on the mobile side, Apple is preventing all iPhone/iPad users from picking a real alternative browser that isn't just webkit re-skinned, putting half the population at a disadvantage and to their own corporate interests.

Good analogy, although I think it falls apart when we consider that SMS is a legacy messaging protocol (over 30 years old now) that is insecure, unreliable, doesn't work over the internet and lacks a ton of features considered mandatory on various other messaging platforms, etc. To compare SMS to any modern messenger is doing a disservice to the all the bells and whistles we've taken for granted in the age of modern messaging platforms.

Another example is FTP being dropped from Chrome and Firefox. Should Mozilla and Google have continued including support for that legacy protocol just because it's been there historically? Is it a bit more complicated for some users who need to use FTP? Probably, but they should be in the minority. Sometimes the best path forward is to deprecate legacy tech.

Arguing both sides at the same time isn’t helping you.

I'm not communicating effectively then. I'm mostly agreeing with you in terms of non-privacy features (things users generally care about) vs privacy features that can be subtle and more easily ignored. For example: It's immediately obvious when messaging a non-iMessage user if you want to initiate a game or some other proprietary feature that doesn't work over SMS that that specific feature doesn't work. It's not so obvious that the same message that can still be sent-received is not protected and in essence potentially viewable by multiple third parties unrelated in a 1-to-1 message. Hope that clears things up.

The same user isn’t both too uneducated to understand the differences and also savvy enough to manually manage insecure and secure messaging decisions.

It's about reducing the cognitive load in knowing what's secure vs what isn't. It's the reason "https" is the standard now and "http" is going away. General users can't be trusted to even look at a lock icon in a web browser to ensure their communications are secure, which is why Google will be getting rid of it in Chrome - their research shows only 11% of users understand what it means. With that knowledge, do you think the average person is going to understand what it means to have a minuscule lock icon (or a different chat color) in a messaging app?

Apple/Google Messages apps handle this transport layer decision for the user, and Signal used to do this too. It’s a basic requirement for mass appeal to users.

You're probably right about this, but it doesn't mean its not less secure for the end-user.

Fair point, but in the context of attempting to guarantee privacy to all your users, it's probably best to either separate SMS functionality into another app or was make it abundantly clear that messages via SMS can be intercepted. The majority of iPhone users have no idea what green vs blue means other than features aren't available. You have the same issue with people using SMS/RCS. They generally don't understand/know the difference.

Lastly, Signal/WhatsApp users are still able to communicate via more insecure methods, it's just a separate app, so there is no loss of communication just convenience.

for anyone wanting to avoid giving "X", formerly known as Twitter, any traffic, here it is.

tradition: ancestral peer pressure. fuuuug that

while it's definitely not just icing on the cake, they were definitely standing on the shoulders of giants.

X? Can we collectively decide to forever call it "X, formerly known as Twitter" just to piss him off?