Yes, encrypted (otherwise what’s the point? 😄). I’ll admit I haven’t tried the PGP version yet. How’s client support? For OMEMO it’s pretty lackluster, from what I’ve heard not much different for PGP?

In any case, perfect forward secrecy is definitely a good thing / strength, but I’d like a way to re-encrypt messages from an old device, just as an example, during the setup process; or a standardized way to export all history; or just something beyond “either use worse or no encryption, or loose access to your history eventually”.

I unfortunately wouldn’t call it solved. I host XMPP and Matrix, (and a STUN/TURN server, and a Livekit server for the modern matrix calls…), and nothing is perfect.

Prosody is really great because it’s so no-nonsense. It doesn’t hog resources or choke up like matrix servers do if you suggest to them that maybe they could deliver this text message? :3 Oh, no, it’s “hold for 2 weeks despite the recipient being online” again? Ok…

But XMPP is still incredibly hard to recommend for me, because

1. no way to read old chats on new devices, which honestly is close to a deal-breaker for many people, myself inclided. And
2. apart from maybe monocles on android, the clients just suck ass. They’re bad. Their UI/UX is stuck 20 years ago, and that does matter.

Hence why I still mostly use Matrix… Even though it’s such a stupid, stupid protocol.

I’m a bit confused. “Decive-level parental controls” have been touted on Lemmy whenever anything age-gating-related has come up on the service side.

Now here they are. And you don’t need to scan your face, it seems. “You’ve had this account for a long time” or “you have a credit card” seem to be pretty sane unlock methods, using data Apple already has from you.

No, \* is being put as a hash of a password, originally precisely because that would mean no actual hash (over any input) ever matches it.

Ah. Thanks for the correction. The intro + where I originally learned this from made me overreact a bit, it seems.

Ah. Thanks for the correction. The intro + where I originally learned this from made me overreact a bit, it seems.

Ah. Thanks for the correction. The intro + where I originally learned this from made me overreact a bit, it seems.

Yeah fair, sorry about that. The intro + where I originally learned this from made me overreact a bit, it seems.

Ah. Thanks for the correction. The intro + where I originally learned this from made me overreact a bit, it seems.

Remember, password-auth off is the problematic setting.

NO! Exactly the opposite, that is the problem. Key-only is a prerequisite for this.

Edit: see also, the first thing that pops up under the link.

I was wrong, see below.

NO! Exactly the opposite, that is the problem. Key-only is a prerequisite for this.

Edit: see also, the first thing that pops up under the link.

I was wrong, see below.

It’s also not real. It’s legislative clickbait.

1. this is a joke of a law meant to generate headlines and nothing else; congrats on biting.

2. how dare you imply the GDPR is bad. It might just be the best consumer protection law ever put to paper, certainly in the digital space. It has massive positive impact on the privacy of EU citizens, and even beyond. All the shitty things associated with GDPR - namely, annoying cookie banners - are not mandated by GDPR, they are malicious compliance from companies furious they can no longer steal your data without telling you. And even then: incredibly small price to pay.

Jellyfin on the open internet is FINE.

I’m hosting my own 🤷🏼‍♀️

Have been for some years actually. Has been great so far. E2E isn’t really a thing with emails anyways, unless you do PGP encryption and signing, which you should be able to do with any half-competent client, including when hosting your own.

Idk. I get it’s not for everyone.

I didn’t read the article

- prole(@lemmy.blahaj.zone)

Oh SHIT yes, I hadn’t even considered using this for my own purposes.

“Some practical notes”

Looks inside

Three slop in a trenchcoat