Programming

17024 readers

291 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

220

Which protocol or open standard do you like or wish was more popular? (lemmy.ml)

submitted 2 weeks ago* (last edited 2 weeks ago) by cyclohexane@lemmy.ml to c/programming@programming.dev

272 comments fedilink hide all child comments

There are a couple I have in mind. Like many techies, I am a huge fan of RSS for content distribution and XMPP for federated communication.

The really niche one I like is S-expressions as a data format and configuration in place of json, yaml, toml, etc.

I am a big fan of Plaintext formats, although I wish markdown had a few more features like tables.

you are viewing a single comment's thread
view the rest of the comments

[–] SirEDCaLot@lemmy.today 1 points 5 days ago (1 children)

Xmpp definitely wins in privacy. What is there to privacy more than message content and metadata? Matrix definitely fails the second one, and is E2E still an issue for public groups? I don’t remember if they fixed that.

XMPP being a protocol built for extensibility means it will be hard for it not to keep up with times.

Okay so how does modern XMPP protect this? When I last used XMPP, some (not all) clients supported OTR-IM, a protocol for end to end encryption. And there wasn't a function for server stored chat history (either encrypted or plaintext).
Have these issues been fixed?

[–] ambitiousslab@lemmy.ml 1 points 2 days ago* (last edited 2 days ago)

It's not perfect yet, but it's much, much better than the old days.

OMEMO is supported by every major client, and they interoperate successfully. Unfortunately, most clients are stuck with an older version of the OMEMO spec. It's not ideal, but it doesn't cause any practical issue, unless you use Kaidan or UWPX, which only support the latest version.

All popular clients and servers support retrieving chat history now too.

In practice, I've been using it for several months to chat with friends and family, and haven't had any issues.