Whether you're really passionate about RPC, MQTT, Matrix or wayland, tell us more about the protocols or open standards you have strong opinions on!
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.
Markdown is terrible as a standard because every parser works differently and when you try to standardize it (CommonMark, etc.), you find out that there are a bajillion edge cases, leading to an extremely bloated specification.
Have you read the CommonMark specification? It’s very complex for a language that’s supposed to be lightweight.
What's the alternative? We either have everything specified well, or we'll have a million slightly incompatible implementations. I'll take the big specification. At least it's not HTML5.
An alternative would be a language with a simpler syntax. Something like XML, but less verbose.
And then we'll be back to a hundred slightly incompatible versions. You need detailed specifications to avoid that. Why not stick to markdown?
Markdown is awesome, I agree! I did not realize you could extend markdown with anything other than html. The html extension is quite nice to do anything that markdown doesn't support natively, but I wish there was an easier way to extend markdown. Maybe the ones you listed are what I need.
Hedgedoc / hackmd support a good amount of extensions out of the box. I think typora and obsidias do also (but not open source).
odf/odt/ods
.md
SimpleX
Matrix
OpenPGP
Last, certainly not least... ActivityPub
Heads up for anyone (like me) who isn't already familiar with SimpleX, unfortunately its name makes it impossible to search for unless you already know what it is. I was only able to track it down after a couple frustrating minutes after I added "linux" into the search on a lark.
going based on preliminary understanding of this shit, it looks like it does all of the user handling on the client side explicitly, server side probably doesn't do anything of the significant sort.
Or at least to a degree that provides reasonable assurance that X person is different from Y person based on the messaging alone. Though your typing style is going to significantly influence it regardless of that.
probably not accurate, just what i gleaned in about 3 minutes.
- 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
I'm stupid, can you elaborate a little further about how ipv6 would make becoming an ISP easier?
There are no IPv4 addresses left. So you eather go IPv6-only, which would make many services not work. Or wait in a long queue to repurpose address spaces marked as depracated which would soon run out too. And then you put clients behind double or triple NAT doing having shitty service.
There's proctored private resale of IPv4.
A lot of orgs (mine included) are sitting on large chunks of IPs they don't need (we have a /16 and several /24s) because they adopted early, got an ASN and prefix assigned by ARIN, and their addressing scheme is now so disjointed and scattered that they can't sell off anything bigger than a /22, and that makes setting up BGP a pain. Juice ain't worth the squeeze.
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 :)
Honestly there is rarely a blog I want to follow that doesn't have it. I do think it would be great to have more readers using it so that it becomes more significant, but for my reading it is actually pretty great.
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.
Is it practical outside of academia? I heard the learning curve is kinda big
You're going off-topic from the OP question :-) But to answer your new question : I do not trust Matrix enough when it comes to privacy. I know that this link is old but still. https://disroot.org/en/blog/matrix-closure
Then again I do not trust Signal that much either but sometimes compromises need to be made to get things done. With XMPP the end user can host their own server if they wish to, without meta data going to a centralized point. And video calls via XMPP and Conversations were a pleasure to use when I used it during the Covid-19 pandemic.
- 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
i2p is pretty cool. One of the more interesting projects out there. Like tor, though i'm preferential to the weird ones.
there is also GNUNET which seems to be in perpetual development, perhaps one day that will see something interesting happen.
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.
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.
IRC is still in use by several open source projects, and it can be nice for quick and open public chatting for meeting people,and to ask questions.
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.
Probably it would be better to edit my comment, but I'll go with a reply to myself.
To all fans of RSS: there's this service called FeedBase that is essentially a RSS to NNTP gate. You add your RSS feed to that and it becomes a newsgroup on their server, and you can subscribe to it using any NNTP client. New articles appear as new posts in that newsgroup and you can post your own replies to them. So, you get RSS but with discussions or comments.
https://feedbase.org/
If you try this, let me know what RSS feeds you're reading, so we could read the articles together and have some discussion there!
P.S. This comment is not an ad. I genuinely love feedbase and use that myself.
i2p. It's sorta like Tor, but the way that every user is a node provides some advantages over Tor.
Also the user interface and builtin solutions for torrenting, hosting, address booking make it way more user friendly for people to start using I find.
