35
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Jul 2023
35 points (100.0% liked)
Selfhosted
40152 readers
461 users here now
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 posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
founded 1 year ago
MODERATORS
Eh i dont fully agree but acknowledge there’s space to disagree. It may not be open source in the way that “its GNU-Linux not Linux”; its not copyleft or “Open Source” but it is open source-lowercase o/s. The source code is available, its accessible under a license that allows you to see it and use it in your own projects, with some restrictions — just like the other main open source licenses do, only to a different degree. There is software licensed under Creative Commons noncommercial licenses, eg, even though CC advises against it. The reasoj I’m posting it on this community though is because it’s self hostable more than it’s open sourceness or lack thereof, though.
Open source is an industry term, the code is NOT open, it's available. I can read it. I cannot use it in anything that might net some profit in the future. "open-source" is defined by the OSI here: https://opensource.org/osd/.
The definition of open source is very tightly linked to the OSI, and has a very specific set of properties. One of those properties is that non-commercial clauses are strictly against open source. Many people misuse the phrase "open source" when talking about non-commercial licensed works, but the plurality of people using it wrong doesn't make them not wrong.
Making things source-available that weren't previously is very much a good thing. I'm all for it. What's not okay is claiming that something will be or is open source and then using a non-commercial license. It's using the reputation of open source to evoke an intuitive feeling of what the license is while slipping in clauses that kneecap the benefits of open source, and the more people that do this, the more the public's understanding of open source gets muddied.
The benefits of open source are not just that you can self-host it, but that you can use it to make your own software. Releasing with a non-commercial license means that basically nobody will work on this outside of the Owlbear Rodeo team, nobody will fork it and make their own maintained version, and it will die with the company. It means there won't be nearly as much community work on plugins or a plugin system, and the software will be worse off for it.
The Owlbear Rodeo team claimed they were going to open source version 1.0.
They lied.
Don't make excuses for them.
The scary part about this is that it kinda does. The more people use the term wrong, the more widely accepted the new definition will be - we see it happen with language all the time. I personally hate it, but I think it does highlight the importance of standing against it and ensuring people don't just accept the "new definition".
Totally fair. I'll update the OP.