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!
i2p. It’s sorta like Tor, but the way that every user is a node provides some advantages over Tor.
so would you be able to run ipfs under i2p to have a secure and private ipfs?
Technically yes by rewriting ipfs’s code, but due to ipfs’s flaws you would be better off using something like freenet/hyphanet which has been designed for that purpose and has been successfully running since 2000, with the added benefit that the data is actually stored in the network by others instead of just by you (at least when you often request the data)
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.
A few years ago there was a Lemmy instance on I2P
was? so it’s not anymore?
Yea I think it shut down due to lack of users/interest. This was before Lemmy even had federation working, so much smaller community
Oh damn, I didn’t even know lemmy didn’t have federation at first
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.
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.
removed by mod
NBD (Network Block Device), it’s like a remote hard drive.
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.
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.
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.
I sincerely wish all of my messages were delivered to me by an owl holding a scroll.
XMPP
Why is that preferable over Matrix?
It’s kinda more resposive than Matrix for me.
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.
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
[email protected]. 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).
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.)
Many years ago I found Silc very interesting.
Dconf
FHIR instead of all legacy standards. Also ISO IDMP to make referencing medicines way easier.
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.
Isn’t Matter supposed to solve this issue?
There’s only one case I’ve found where Wi-Fi use seems acceptable in IoT: ESPHome. It’s open-source firmware for microcontrollers that makes DIY IoT sensors and controls accessible over LAN without phoning home to whatever remote server, without trying to make anything accessible over the Internet, and without breaking in any way if the device has no route to the Internet.
I still wouldn’t call Wi-Fi use ideal even there; mesh can help in larger homes and Z-Wave/Zigbee radios tend to be more power efficient, though ESP32 isn’t exactly suited for a battery-powered device that’s expected to run 24/7 regardless.
Yes but at least Hue (and IKEA and LIDL and many other brands’) lights work well with open Zigbee coordinators, like deconz and ZHA in Home Assistant.
I wish there were more Zigbee and Zwave and less WiFi IoT devices too. I don’t even have a Zwave coordinator because I never found anything I wanted with Zwave support.
Remember SOAP? Remember XML-RPC? Remember CORBA?
Those were not very good.
I had to do some soap integration last year and it feels like it only got worse with age.
I’ve worked with all of them and hate all with a passion. SOAP wasn’t bad in theory but lots of APIs and clients didn’t implement it properly.
IPFS I’m really glad things like nerdctl and guix support it, but I wish more things too advantage of the p2p filesystem.
Petals.Dev and hivemind ml P2P AI inference and training seem like the only true viable options to make foundational models that are owned soley by authoritarian government s and megacorps.
Matrix for federated general real time communication. (Not justs chat, video, images, but just data, with third room being on the cooler demos for what is possible)
Activity Pub for asynchronous communication between servers. The socialmedia aspect is obviously the focus and the most mature, but I’m also excited for things like Forgejo (Codeberg.org) and Gitlab’s support.
I am also excited for QUIC for increased privacy of metadata and reduction of network trips.
