Which new Protocol or Standard are you most excited about?

[koulib@sh.itjust.works]

pretty much the title.

[hawgietonight@lemmy.world]

37.5 hour work week

[xavier@lemmy.ca]

The Solid protocol specification or anything similar (it doesn't have to be that specific protocol).

For example, registering to a website or service actually creates a local secure database/bucket/pod where that website/service organizes/sort/manipulates our data and stores all generated modified data/metadata within our local personnal server, every time we interact with that same external website/service it gets access to the database/bucket previously created. (Ideally) no personnal data should be stored on external servers/machines outside our control and without our explicit consent.

[justenoughducks@feddit.nl]

We have 38h in Belgium, but if you work 40, you get 12 extra full days of holiday during the year (what I do).

A 32 hour work week with no salary cut will never happen, but that would be a dream

[brisk@aussie.zone]

IndieWeb in general and the h-entry and WebMentions specifically.

Collectively they promise a highly personalised web experience that maintains ownership of your own content while encouraging socialisation across platforms, while avoiding the sustainability and scale limitations of activitypub.

I also want to see XMPP/OMEMO have a comeback.

[oceane@jlai.lu]

Hi, does it have any advantage over greping your RSS feeds for your blog's URL?

[oceane@jlai.lu]

It may happen through union development, and free software development, i.e. whatever form of permanent democracy you prefer.

25% of any population being able to democratically vote for a strike and fully enforce it will de facto become the main political force in the country.

[brisk@aussie.zone]

What is "it"? Webmentions? Webmentions can be sent from anywhere, not just places you're actively monitoring. They can be used for example to create a comments section on your blog which amalgamates comments from various syndication points.

That is, you post to your blog, you post a link to your blog post to twitter/Facebook/lemmy etc, and comments or replies from any of those can show up on your blog itself if you so choose.

[oceane@jlai.lu]

Alright, that's pretty cool, sorry – I thought it was a list of links automatically inserted in lieu of comments.

I've been trying to get into the IndieWeb for years, but I've been struggling to implement it. Doesn't it rely on a central server too? Can we use it in a fully e.g. decentralized or federated way – would it even make sense, or could we easily switch to another flagship server, as we did with the Freenode takeover?

Please feel no pressure to reply, I can do my own research ^_^

[mtw@lemmy.blahaj.zone]

Pipewire, Wayland, Matrix.

[droplet6585@lemmy.ml]

Fedora moving forward with UKIs, bootc and composefs

[swedneck@discuss.tchncs.de]

long-term it'd have to be https://libp2p.io/, if we can start embracing it then user-level networking will become so much easier and more sensible.
No more fucking around with port-forwarding and configuring stuff on your router, no more ddns services to ssh into your home desktop, just point your computer to a peer ID and it figures out how to establish a connection, even if you change networks or your only internet access is through bluetooth tethering to your phone's LTE.

[swedneck@discuss.tchncs.de]

My money is on IPFS, because it's so simple (like, in principle, obviously it's complex under the hood).
It's not fancy, it's basically a better version of torrent and only handles static data, but it does that really fucking well.
It takes any data you add to your node, splits it into small blocks, does a fancy hash of those blocks, and then builds a tree of pointers that point to pointers that point to the constituent blocks. This means that any identical blocks have the same address, and thus only need to be sent once! And the same goes for anything that ends up being identical in structure, it has the same address and only needs sending once, and if someone else sc

In effect it does the same thing that http or any other normal file transfer protocol does, but in a modern and fundamentally decentralized way. You don't care where the data comes from, you just request the ID from whatever nodes you can see, if they don't have it they forward the request to those they can see etc etc, if anyone has it they reply to you and start sending the data, and then you do some fancy math to verify that it's correct.