Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
They would likely have to rewrite the linux kernel right? I've never heard of a single project being granted taking the kernel private. If they were going to do that they would find it easier to rebase back on FreeBSD. They just switched to linux and invested a ton into the switch. The switch already cost them a bunch of users and dissent, the current narrative is causing more.
There will be forks of all the current code either way.
I would be more worried about the cheap Chinese hardware people are using that utilizes the linux kernel and other code that doesn't contribute back to the project or release their code.
Yeah, no, they couldn't do it to the kernel. But that's not really the interesting part of their product. It's all the software that they as a company hold the copyright to. If they solely hold copyright on all their own code or if they have permission to relicense from their contributors, they can take any or all of their products closed source, and when I say "their products" I specifically mean the things they as a company produce, which they built on top of open source projects that they don't control.
Agreed. But anything that is released as open source will still exist even if they move to closed source. So another group can take that code and continue to develop it as a new project.
True, but unless that new group is willing to step up and invest in physical device production to directly compete, I don't think it's going to be the same. The type of people buying a dedicated NAS with a custom OS are looking for as close to a plug and play solution ad they can get. They're less inclined to reinstall the OS on their new NAS, and the market is probably going to favor the now proprietary version TrueNAS sells, especially if they take steps to make it difficult to replace the OS on their devices.
I believe this doesn't apply to the Linux kernel. I mean there is a lot of products that include a Linux kernel and runs proprietary code on top.
I'm not really certain about the legalities, but IIRC it has to do with Linux being licensed under GPLv2 instead of GPLv3(?)