Hobestly, I can respect that. They seem to be fairly open about the motivations of that decision and who it's targeted it without devolving into vague fluffy corporate speech too much. You can sense the author was a bit pissed by the reactions.
And I do agree that many of the reactions to the news seemed overblown and I think the actions make sense from their point of view without being super shady, even if it still has some negative repercussions for the open source world as well.
fr0g
joined 1 year ago
Get your facts straight! I'm not a lemmy ludite, I'm a kbin krazy!
That being said, the whole heat thing does seem to be a thing, even if it's much less significant than the CO² heating effect and not a super big deal yet.
Isn't that just a further recipe for disaster? Isn't that just additional energy that will turn into heat sooner or later and heat up the planet?
If I'm not mistaken regulat solar is one of the few energy sources that doesn't have that problem and there's plenty sun to go around, so how is this helping anyone? (I guess it might have some applications in space?)
Yes, it's different. Self-hosting means you set up a running version of kbin (or whatever) on your own server. All the different domains you see (lemmy.ml, beehaw.org, lemmy.world, kbin.social, fedia.io etc etc) are on their own servers. Theoretically you could also set up a version where you are the sole user even.
There are some minor things. Accessing communities on your own is probably more efficient in terms of server load. A community from your instance can never get cut off from you due to defederation.
But those are honestly just very minor things.
Even most of the Linux apps use Shazam or similar for the backend. Most everything you will find in that area has some proprietary components and I can imagine that being hard to avoid for something that has to interface with licensed content (the music)
How does installing packages or configuring software work, if system files can't be changed?
On reboot. You install your changes into a separate part of the filesystem that's not running and then "switch parts" on next boot. Different distros do this differently. Vanilla OS has an AB system which basically works like Android does it, openSUSE uses btrfs snapshots and Fedora also uses btrfs I think but they got a more complex layering system on top.
I get that there's a security benefit just in that malware can't change system files -- but that is achieved by proper permission management on traditional systems too.
Is it though? All it takes is a misconfiguration or exploit to bypass it, so having several layers of protection isn't a bad thing and how any reasonably secure system works. And having parts of your system predetermined as read only is a comparably tough nut to crack.
No, the API isn't ready yet. But that isn't stopping some people
https://tech.lgbt/@hariette/110545151572492176
Not really. The real life thing is carefully guided process with serious obligations in which the professionally trained and educated judge is still the main arbiter. The jury is segmented to a very specific part of the process with a clear protocol for a reason.
What you're asking for is giving every Xth rando a police badge because law enforcement is understaffed.
I think it might be worth exploring making them more bean-shaped as opposed to the more ball-shaped appearance they have now.
I don't think there is a difference of opinion? RedHat only offering source code to paying customers (and devs) is completely legal and in line with the GPL license. But maybe there's something more to it that I missed.