Somehow, though, people invest more and more resources into making both more real at the same time lol
'Cause trying to build AGI is speeding up the warning xD
Somehow, though, people invest more and more resources into making both more real at the same time lol
'Cause trying to build AGI is speeding up the warning xD
There are folks form KDE who are trying to implement the Plasma Bigscreen solution: https://plasma-bigscreen.org/. Seems promising to me :)
Though, I'd still recommend to use an external device to avoid breaking the TV OS up ;)
I love trams. So nice way of getting around!
The web ui with integration of email ecosystem for all those things are one of core selling points of https://sr.ht/
I'd say this list is not about moving towards FLOSS, but more about breaking up with Google services. Some replacements are betters, some worse, but definitely in each column there is at least one non-floss application 🤔
I've been following the software forge federation some time ago, and didn't feel to pick up even when it was discusssed initially. It is a neat idea on high-level, though it requires forges to implement it, which has a risk of not picking up (just look at how much iterations of social media federation protocols was there, until ActivityPub arose).
On the other hand, all of the forges are based on a distributed technology out of the box: git
. Most of the "modern days" comforts there are, are just built on top, and there are different ways to approach it.
As an example, you can send patches directly to the author in email. Is heavily implemented and suggested by https://sr.ht/ (1) — a software forge, which focuses on building a federated workflow by using email for communication (which is federated by design). This way, you can create "Pull Requests" without having account on the forge — all you need to do is just submit a patch. Author is very vocal about supporting it (2), and provides quite useful guides to learn (3), (4)
Generally, I'd say that e-mail is the only federative implementation you can get so far :)
TBH, when I visited Athens, it felt like the most car-centric capital I've ever visited in my life (haven't been to US though). Fascinating comparison to be :)
Oooh, thanks, looks neat!
I presume that their employers just had terms that essentially gave the whole IP to the employer. And GPL is conflicting that, especially if they were producing the code using employers equipment, which essentially makes all the code to belong to employer. At the same time, GPL maintains the IP on the author of the code.
Not a lawyer, though I heard that some far-eastern companies have copied the US policymaking, which allows full separation of IP from the author.