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!
TOML
I wish the protocol used by Hotline Client took off, it was basically Discord in the 90s with its support for announcement/news posts and file sharing
Also KDX. I was too young to use that, but tried and it’s cool. Sadly even FOSS clients are all dead and don’t build anymore. (I think I had limited success with patching one called Fidelio to build, but that was a few years ago and I can’t find any traces of that attempt.)
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.
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.
Holy cow, that’s neat as hell! Thanks for sharing!
Back in the day I was a big Usenet fan. What’s the modern solution to the spam issue? At the time, folk wisdom was that the demise was being caused by spam, and that due to the nature of the protocol it was somehwhat unsolveable.
I also wonder to what extent activity pub is the barrier to offline use? For reddit, the Slide client had offline reading and iirc posting. I have been disappointed it isn’t available for Lemmy. My guess has been it simply isn’t a priority for the devs. Maybe eventually we will get it.
I think it would be cool if RSS got put into Lemmy clients. Example you could make a unified inbox for all accounts by automatically getting the private RSS for incoming messages for all logged in accounts. I have manually set this up a couple of times but its tedious. Completely lacks smoothness when it comes to clicking a link, replying etc. But a client could add a little finesse to fix that.
True, Lemmy (and activitypub in general) could integrate RSS and also be accessible via NNTP.
Or at least add some functionality for offline reading/posting. It’s just not a priority for devs now.
About spam, most of spam was coming from Google groups and since Google unpeered from Usenet, there is no spam.
Content addressable protocols are better for asynchronous use. I’d like to see a proper bluesky atprotocol fork with “post lexicons” properly adapted for forums, they’re built on top of content addressing and public key based account IDs along with 3rd party moderation tooling support integrated and custom 3rd party feeds/views.
definitely some alternative internet mesh routing standart, just imagine if every device with wifi or ethernet could just extend the network without relying on an isp, yeah they could still serve as a fast backbone, but they just wouldn’t be needed and no disaster could really ever disrupt the whole internet again
honestly: activity pub, matrix, xmpp, markdown and soo many more probably. All of these would be able to solve our walled gardens problem, but the apps with a basically monopoly don’t have much of an incentivw to implement them
Why is that preferable over Matrix?
Matrix came 15 years after XMPP, so the question should be: why is Matrix preferable? Does it bring anything to the table, other than fragmentation?
I don’t believe that its existence causes more fragmentation than it remediates. https://news.ycombinator.com/item?id=36939482 explains why I consider Matrix fundamentally superior most (if not all) uses, although in practice it’s because the clients (Element and FluffyChat primarily) are cross-platform and support a generally uniform set of features, in comparison to the aged (but glorious) Pidgin, and its counterparts.
Your hackernews post and the fact you mention Pidgin shows that you haven’t used xmpp in the last 10 years. By the time Matrix was first released, xmpp had history sync.
Which is why I can’t wrap my head around why a second protocol with no features that didn’t already exist in XMPP took over.
I used it yesterday, via Pidgin. I’m
rokejulianlockhart@xmpp.jp. Why else would I have referenced it? Don’t tell me what I’ve done. That’s not a way to have productive conversations.Regardless, I can’t provide any more technical insight than that - I know solely that the clients provide so much more functionality that irrespective of the protocol, it’s better in practice. Fedora, openSUSE, the Bundeswehr, NATO, and Beeper - all chose Matrix over XMPP, not least partially because of Element (which they also all chose).
Yeah, my experience with Element and a Matrix.org account is that it’s sluggish. However, it’s been better at Beeper, so I’m uncertain whether it’s intrinsic to Matrix or merely Matrix.org and/or Element’s servers.
I’m really into CloudEvents because I love event-driven systems, and since events can come from, or be consumed by, so many different services, having a robust spec is super duper useful.
So what problem is this solving? What are some event-driven systems that need to interoperate? Seems like even if you have a common encapsulation method, you still need code to understand and deal with the message body. Just seems like an extra layer around a JSON blob.
There was a slight surge in popularity for I2P after the tor network experienced some downtime a couple years ago.
Anonymous lemmy, anonymous torrents, anonymous IPFS, anonymous eMule, anonymous streaming, anonymous source forges, anonymous chats, anonymous everything…
Imagine unbridled, anonymous, mainstream piracy, software development, sitehosting, communication, social media.
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.
Why should this be at the editor level? There should be a linter that applies all these stylistic formatting changes to all files automatically. If the developer’s own editing tools or personal workflow have a chance to introduce non-standard styles to the codebase, you have a deeper problem.
I want both. When I am typing code in my editor I want it to follow the styles of the project. Then when I run the linter/formatter it will fix the mistakes.
The last thing I want is to start a new
if foo {statement and the indent is half of the indent of the if above. That would be too distracting.Why should this be at the editor level?
Because for every programming language there’ll be people using text editors, but you’ll never succeed in even creating code formatters for them all.
The greatness in this project is in aiming low and making things better through simple achievable goals.
Fuck Unified Push. Just use the Web Push standard. https://www.rfc-editor.org/rfc/rfc8030
It is what is used for browser push messages, is already widely supported. Is compatible with existing push infrastructure and users and is end-to-end encrypted. IDK why Unified Push felt the need to create a new protocol when a perfectly good one already existed.
Although there is no “client side” spec. The Unified Push client side could be useful. But they should throw away their custom backend protocol and just use Web Push.
Nobody knows about unifiedpush. Last time I checked, their Linux dbus distributor also wasn’t ready. There has to be a unified push to get it adopted.
I don’t know about unifiedpush but I’m going to look into it now.
Using firebase for push notifications always seemed a little sketchy to me.
I’ve been playing with MQTT on meshtastic. I really hope LoRa and meshtastic continue to grow.
The more they grow, the busier the spectrum will be. I really hope it doesn’t grow too much.
Just enough to grow the network so we don’t need mqtt.
FHIR instead of all legacy standards. Also ISO IDMP to make referencing medicines way easier.
peer to peer, i would be happier thitking that every time i open somo application, i’m helping it, like i2p
Ever heard of IPFS? I really hope that will take off some time.
Unfortunately the reality of IPFS is that despite its huge funding it was poorly designed from the start and still to this day has much slower loading times then my I2pd instance (despite i2p transmiting messages through multiple encrypted proxies), to the point where the company working on the rust implementation determined it was so bad they had to scrap the whole thing to make something that actually worked. Not to mention that I managed to have my server taken over by some kind of malware by downloading a particular piece of content.
Thanks, that was an interesting read! I always felt IPFS wasn’t ready yet, but the value it tries to provide of being a file system, I’ve found no real alternative to. Very good to read that iroh is willing to look beyond the IPFS spec to provide its values with better performance. I hope it works out.
