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.
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
I'll be the heretic here, but so far as I know you are only required to make source available when you distribute binaries. And for that matter, it doesn't even have to be online just available upon request unless you're using a derivative GPL that added online access as a clause.
I highly doubt the users of a web interface are required to be given access to source. There are multiple GPL-licensed web servers (I am well aware Apache is not btw) and I've never seen one embed a code link on every page.
Tl;Dr: Lemmy does it, but I believe it's not required. Modify away if you so choose.
AGPL has a clause that basically says "network access counts as distribution". If you make modifications to a AGPL code which users can connect to, users should be able to have access to the source code with your changes.