Linux

48340 readers

430 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r

247

Which communication protocol or open standard in software do you wish was more common or used more? (lemmy.ml)

submitted 7 months ago* (last edited 7 months ago) by cyclohexane@lemmy.ml to c/linux@lemmy.ml

342 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] x3i@kbin.social 72 points 7 months ago (2 children)

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.

[–] technom@programming.dev 32 points 7 months ago (1 children)

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.

[–] kevincox@lemmy.ml 0 points 7 months ago

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.