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 probably would. However it has become increasingly obvious that the flaws with solutions so far have been in the organisation. Not so much the particular hardware or software. If I'm going to buy something I'd like some hope that it'll be there in 5 or 10 or 20 years. So please if you go serious with this, look into worker-owned organizations because I'm tired of dodging profit-maximizing traps and pretend-non-profit landmines. If the people building and supporting the thing aren't the ones deciding what to do with the revenue and profit, you're the only one doing it and you're going to make mistakes that will hurt them and us. And then you become a landmine to dodge.
These are great points, and I fully agree. I'd be interested in knowing what kind of license or corporate structure or contract would give you confidence that the organization is worth investing in. I could put all the software out with a really strong Affero license so that you've got the source code, but I get the impression that you, like me, want more than that. Corporations like Mondragon are interesting to me, and I'm aware of a few different tech cooperative organizations. I'm not confident that a cooperative structure alone is enough. Yes, it helps avoid the company taking VC money, shooting for the moon, failing, and then selling everything that's not clearly legally radioactive. But it doesn't protect you against more insidious forces like the founders selling to private capital and adjusting the EULA every few months until they have the right to sell off your baby photos.
I've been batting around the idea of creating a compliment to the "end-user license agreement" - the "originating company license agreement". Something like a poison pill that forces the company to pay out to customers in the event of a data breach, sale of customer data, or other events that a would-be acquirer may think is worth it for them.
I'm just not sure yet what kinds of controls would be strong enough to convince people who have been burned by this sort of thing in the past. What do you think?
Purely on the product side, if I decide to buy it, I wouldn't buy it for myself. I'd buy it for friends and family who are not that tech literate. Either to make my life easier to give them self-hosted services, or ideally for themselves to be able to do so. I want this product to be a non-shitty, open source "Synology," from a firm I can trist to support it for a very long time. Doesn't have to have that form factor. And I'm totally fine with an ongoing subscription. I'd like to be able to say - hey friend, buy this from ACME Co-op and sign up for their support plan. Follow the wizard and you'll have Immich, Nextcloud, etc. A support plan might include external cloud HTTP proxy with authentication and SSL that makes access trivial. Similar to how Home Assistant's subscription (Nabu Casa) works. It could also include a cloud backup. Perhaps at a different subscription rate.