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 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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
IANAL. I originally interpreted the license.txt as: all of the source code is AGPL (see lines 234-235), some of the source is also Apache 2.0, and the binaries are MIT; plus a trademark notice and contact info for getting a commercial license. After rereading it, my only conclusion is that this is a dumpster fire of a license.txt, and can be reasonably read several different ways.
And, people have been asking them to clarify it and they just say, “no.”
They’re acting very suspiciously.
Agreed, very suspicious. I would feel safe assuming that I can use the code under AGPL, but I would hesitate to use it for anything other than personal hobby because it would not surprise me if they closed their github account and never released any more code.