Linux

RSS. It's still around but slowly dying out. I feel like it only gets added to new websites because the programmers like it.

IPv6. Lack of IPv4 addresses it's a problem, specially in poorer countries. But still lots of servers and ISPs don't support it natively. And what is worse. Lots of sysadmins don't want to learn it.

Markdown. Its only in tech-spaces that its preferred, but it should be used everywhere. You can even write full books and academic papers in markdown (maybe with only a few extensions like latex / mathjax).

Instead, in a lot of fields, people are passing around variants of microsoft word documents with weird formatting and no standardization around headings, quotes, and comments.

Unified Push.

Unbelievable that we have to rely on Google and co for sth as essential as push messages! Even among the open source community, the adoption is surprisingly limited.

IPv6

I mean, why the hell is IPv4 still a thing??

• IPv6, needed for modern Internet not to collapse, would make many other important things easier. Easier to become an ISP, to selfhost, to build P2P networks, etc.
• GNU Taler, a payment protocol just look at it go: https://101010.pl/@didek/111934952208145427, or just imagine building a payment terminal of a Raspberry Pi
• Matrix, to unify chat, conference and calling apps
• some self-arranging darknet protocol becoming a norm like I2P, GNUNet or Yggdrasil, so we could have a backup when mass Internet blockage happen

Do Not Track

Such a simple solution for the cookie banner issue. But it prevented websites from tricking users into allowing them to gather their data, so it had to go.

RSS (RDF Site Summary or Really Simple Syndication) It is in use a fair amount, but it is usually buried. Many people don't know it exists and because of that I am afraid it will one day go away.

I find it a great simple way to stay up to date across multiple web sites the way I want to (on my terms, not theirs) By the way, it works on Lemmy to :)

odf/odt/ods

.md

SimpleX

Matrix

OpenPGP

Last, certainly not least... ActivityPub

XMPP

IOT devices shouldn't connect to wifi. ZWave or zigbee is much better suited to IOT stuff, but it seems to mostly get adopted in very limited, locked down proprietary shit like Hue Lights.

LaTeX. As someone in academia, I absolutely love it. It has some issues like package incompatibility, but it's far far better than anything else I've used. It's basically ubiquitous in academia, and I wish it were the case everywhere else as well.

Matrix... it's on such a good path I can't complain. Adoption could be faster but it's alright.

I2p, although I have no idea if the lack of adoption has not a very good reason.

• Communication: Matrix
• Browsing: I2P
• Communities: ActivityPub / Mastodon
• Software Forge: Fogejo + ForgeFed
• OS: Linux
• Money: Monero

Since they meet at least one of,
if not all of the following:

• Decentralized / Federated
• Sensorship resistant
• Privacy respecting
• Open source

QUIC

I wish Microsoft Office would use the .odf standard by default. Or, failing that, it'd implement its own published .docx specification correctly, so other office suites can be compatible.

I2P. Current protocols should go through it

Remember SOAP? Remember XML-RPC? Remember CORBA?

Those were not very good.

XMPP.

peer to peer, i would be happier thitking that every time i open somo application, i'm helping it, like i2p

Others have said already, but XMPP and RSS. Also, nobody mentioned NNTP yet.

I wish everything was accessible by NNTP and we had better NNTP clients. NNTP is like RSS but for forums (so, Lemmy, Reddit, or anything where you could reply to posts). Download for offline reading, read in your client, define your own formatting, sorting, filtering, your client, your rules.

If Lemmy was accessible via NNTP, I could just download all posts and comments I'm interested in and reply to them without any connection, and my replies would get synced with the server later when I connect to WiFi or something.

https://editorconfig.org/

XMPP

RFC 2549 is such an important improvement over RFC 1149. Everyone should adopt the updated standard.

Honestly, IRC was a very functional, easy, free, low-resource and privacy friendly chat protocol and I don't really see why it got left behind. If you wanted image/ file support that could really be implemented client and/or server side.

I wish people used email for chat more. SMTP is actually a pretty great protocol for real time communication. People think of it as this old slow protocol, but that’s mostly because the big email providers make it slow. Gmail, by default, waits ten seconds before it even tries to send your message to the recipient’s server. And even then, most of them do a ridiculous amount of processing on your messages that it usually takes several seconds from the time it receives a message to the time it shows up in your account.

There’s a project called Delta Chat that makes email look and act like a chat app. If you have a competent email service, I think it’s better than texting. It doesn’t stomp on the images you send like SMS and Facebook do, everyone has it unlike all the proprietary services, and you can run your own server for it that interacts with everyone else’s servers.

Unfortunately, Google, Microsoft, etc all block you if you try to run your own server “to protect against spam”. Really, I’m convinced that’s just anticompetitive behavior. The fewer players are allowed to enter the email market, the less competition Gmail and Outlook will have.

As much as I like ProtonMail too, unfortunately their encryption models prevents it from working with Delta Chat. I’d love to see Proton make a compatible chat app that works with their service.

I made an email service called Port87 that I’m working on making compatible with Delta chat too. I’d love to see people using email the way it was originally meant to be used, to talk to each other, without being controlled by big businesses.