181
submitted 2 days ago by [email protected] to c/[email protected]

The future is community-hosted


Related Hacker News thread:

top 50 comments
sorted by: hot top new old
[-] [email protected] 5 points 19 hours ago

Companies like Amazon have been playing dirty with Digital Rights Management (DRM) since the Internet's inception.

False. They came along after the fact and sullied the waters, then lobbied to make it illegal to tinker with the DRM locks, then got richer than God.

[-] [email protected] 27 points 1 day ago* (last edited 1 day ago)

Lol. So we trust local governments and communities now?

Has anyone ever worked with them IT wise?

I do so in four different EU countries and know people who do in the US and Canada. And...well...there is a reason local governments often went towards the cloud services. Do people think Joe Admin in Bumfucknowhere can operate what basically becomes a MiniDC? And who controls that?

Sorry. Either go "host at home" and only fuck up things for oneself. Or do it properly with a proper DC. Colocate if you want. But that? I know it sounds appealing, especially for someone entering selfhosting (like the author did a few weeks ago). But there is a reason hosting is a business once it comes to other peoples data.

[-] [email protected] 3 points 1 day ago

I can easily host vaultwarden, trillium, docker-mailserver, jellyfin, borgbackup and syncthing instances for my 5 neighbours. Everyone who's even slightly good with computers can do that for their neighbours. That's what I think when I hear "community". Not online fandoms.

[-] [email protected] 4 points 1 day ago

Yeah. And I am sure you won't do anything bad.

But we all know how many that will not be the case. There were countless cases of school IT staff being malicious, of healthcare IT staff being malicious. Do you think that won't be happening regularly on a small community scale? And that goes both ways: What happens when your neighbour suddenly accuses you of stealing passwords from you?

Don't get me wrong - I am also providing services to my friends and family. But I absolutely do refuse to do so for any vital or financially debilitating services (which I consider vaultwarden for example). And I am seeing large issues with promoting this model as a solution - which need to be addressed.

[-] [email protected] 2 points 23 hours ago

I trust my neighbour more than I trust Big Tech.
With Big Tech we know full well they'll completely legally, ethically and anonymously harvest us, profile us, manipulate us, encircle us and enslave us in their digital slaughter house. I'll take my chances with 10 million community organizers and the occasionnal small time crook instead of the certainty of a Big Tech Panopticon Mega Dystopia

[-] [email protected] 1 points 22 hours ago

Yeah,big US tech is cancer - but I am fortunate enough to not live in the US and there are enough mid size companies that fall under reasonable laws and governmental oversight (in the good way,not the bad way) that I can choose from. People always seem to think it's "selfhost or big tech" but there is a shitton of solutions between them.

Mailbox.org, Infomaniak(but I would be cautious on them due to the changing legal framework), posteo,Mullvad,Photoprism,Passbolt,Hetzner Storage Space,Ionos, Deepl, etc. are all a sane middle ground for most people and

I much rather have people do that than fall into the arms of their neighbourhood asshole (and let's face it,there are a lot of difficult characters in IT). Because first of all it's people's lives who are at stake - You can wait for the first creep who will use access to his neighbours photos (Immich,Photoprism,etc.) for some uncanny purposes. Who will use the WiFi&Device passwords saved to get access to someones CCTV system to spy on his neighbours. Etc. Etc. And, and this is as much of an issue,it will only take a few of these people to drive people away from all open source products, right back into BigTech.

Lastly: It's okay,that you see it that way. But people need to be informed that these are the risks. If you would take those risks (and don't think from an IT role but from your neighbours perspective here), go for it. I wouldn't, we can absolutely agree to disagree. And I don't think many would once someone tells them the truth: "Yeah, BigTech can absolutely access your files and possibly your passwords with enough efforts. If you let Joe over here host your files and passwords he can,but BigTech can't." I am not sure how people would decide.

[-] [email protected] 6 points 1 day ago

Something that's always given me trouble is sharing my music.

If I hear a cool song and want to send it to a friend I have to go to YouTube.

And many of my friends send me Spotify tracks. The share feature of Navidrome has been incredible for this.

I can send them a link and have a listen party with them and then erase the link when were done.

It'd be nice to have this feature in more of the self hosted apps.

[-] [email protected] 1 points 17 hours ago

It looks like you can self host Navidrome.

[-] [email protected] 3 points 21 hours ago

Thank fuck I neither desired nor ever used Kindle. I used either my library app to read e-books or getting my booty from the high seas!

[-] [email protected] 10 points 1 day ago
[-] [email protected] 1 points 1 day ago

I would say the future is in pooling resources.

Like it happens with torrents. As one p2p protocol very successful.

Self-hosting not applications, but storage and uniform services. Let different user applications use the same pooled storage and services.

All services are ultimately storage, computation, relays, search&indexing and trackers. So if there's a way to contribute storage, computing resources, search and relay nodes by announcing them via trackers (suppose), then one can make any global networked application using that.

But I'm still thinking how can that even work. What I'm dreaming of is just year 2000 Internet (with FTP, e-mail, IRC, search engines), except simplified and made for machines, with the end result being represented to user by a local application. There should be some way to pay for resources in a uniform way, and reputation of resources (not too good if someone can make a storage service, collect payment, get a "store" request and then just take it offline), or it won't work.

And global cryptographic identities.

Not like Fediverse in the end, more like NOSTR.

[-] [email protected] 12 points 1 day ago
[-] [email protected] 1 points 1 day ago

The presence is P2W.

[-] [email protected] 17 points 1 day ago

If you do not have physical access, it is not yours. Trust absolutely no one.

[-] [email protected] 1 points 20 hours ago
[-] [email protected] 120 points 2 days ago

I agree with the premise that selfhosting is not something the layman can or want to do, but the assumption that self-hosters only host software that serve themselves is very, very dumb, and clearly comes from the mouth of someone who self-hosts out of hate for corporate services (same, though) and not for the love of selfhosting.

He complains that the software he uses can't handle multi-users, but that sounds like a skill issue to me. His solution is to make his government give him metered cloud services. What he actually wants is software that allows multi-users. What he wants, by extension, is federated services.

The bulk of users on the fediverse are on large, centrally/cloud hosted instances, but the vast majority of instances are self-hosted, and can talk to the centrally hosted instances, serving usually more than the 1 user who's hosting the instance in their attic.

The author conflates self-hosting with self-reliance, and I understand why, but it's wrong. If you're part of this community, you're probably not some off-gridder who wants nothing to do with society, self-isolating your way out of the problems we face. If you're reading this, you already know that we don't have to live on our own individual and isolated paradise islands to escape Big Tech. Federation is the future, but selfhosting is fundamental to that, and not everything can or should be federated. Selfhosting is also the future.

[-] [email protected] 14 points 2 days ago

That's an interesting point...

I'd like to share some (holiday) photos with my friends & family, so I can put those onto Pixelfed / Friendica / etc... I don't necesarily want to share all the photos...

And that's using the cloud.

Job Done. The self-hosting + federated cloud future is here!

Rejoice.

[-] [email protected] 1 points 1 day ago

I self host seafile server and use seafile app to sync taken photos on my iPhone to the server. Then you could (haven’t yet) setup a photo hosting service

load more comments (3 replies)
[-] [email protected] 13 points 1 day ago

I'd love to help community host stuff, but I'm terrified of someone posting cp to a server I have or getting breached.

[-] [email protected] 3 points 1 day ago

Zero-knowledge hosting solutions should help with that, but I'm unsure how the tech and UX has been going for that on FOSS as of yet.

[-] [email protected] 36 points 2 days ago

The authors approach to not owning anything digital was to attempt self hosting. But the authors reaction to the amount of work was that he shouldn’t own the “self-hosting”? He does not even realize that he’s back to not owning anything

[-] [email protected] 28 points 2 days ago

He proposes the cloud be owned by communities, so in a way by everyone. That's not the same everything being owned by private companies.

[-] [email protected] 17 points 2 days ago

In fact, that model (conceptually, though not technically) is how most fediverse software already work

[-] [email protected] 5 points 2 days ago* (last edited 2 days ago)

So is he insinuating that communities should have IT people who keep things running for everyone (like a digital librarian of sorts)?

Because that takes time, effort, and money. Like a lot more than one would spend or need for just themselves/family/maybe a couple of friends.

Also, community-run self-hosting just seems like a bad idea from a privacy and legality standpoint. One pirate getting caught isn't usually so bad (usually a warning or small fine). But once you start distributing, then you're going from a kiddie pool of consequences into an ocean of consequences. We're talking massive fines and/or jail time.

Edit: I should clarify that I'm not talking about services here, but content itself.

[-] [email protected] 8 points 2 days ago

The point is that clouds aren't inherently bad, and actually come with a lot of important upsides; they've become bad because capital owns and exploits everything in our society, poisoning what should be a good idea. The author is arguing that while there's nothing fundamentally wrong with self-hosting, it's not really a solution, just a patch around the problem. Rather than seeking a kind of digital homesteading where our lives are reduced to isolated islands of whatever we personally can scratch from the land, we should be seeking a digital collectivism where communities, not exploitative corporations, own the digital landscape. Sieze the means of file-sharing, in effect.

load more comments (1 replies)
[-] [email protected] 21 points 1 day ago

Every city should host main public web servicies for its citizens, each one as an instance of a complex system, that's how anarchy works.

[-] [email protected] 2 points 1 day ago* (last edited 1 day ago)

That quickly becomes a tragedy of the commons. The city residents pay for it but how do you verify "citizenship"?

[-] [email protected] 3 points 1 day ago

If you mean citizenship as being associated to the city whose hosting services you are using, yhe power or water bill pointed at your name and residence should be able to do that. Now, if you want that plus anonimity, the only practical option I can think of for a city-wide physical campaign is some sort of GPG Signature Meetup ("signature party").

[-] [email protected] 2 points 1 day ago

yhe power or water bill pointed at your name and residence

Many people live in cities without owning their house. So they never see those bills. Renters are usually two levels away from the actual owner. Then there are all the people who live and work in cities but aren't official renters.

[-] [email protected] 1 points 20 hours ago

In the USA, most power bills are the tenants' responsibility. In the USA, virtually all internet connections are the tenants' responsibility.

The locality hosting the services could also pass a law requiring the tenants to either bear responsibilities for, or be included in, all utility related billing.

A lot of arguments in this thread seem to be ignoring this as a solution to the legitimate problems they're raising.

[-] [email protected] 1 points 1 day ago

If every city has the same then why would you even want to?

[-] [email protected] 1 points 1 day ago

It would have to be a national mandate that is available in every city or everyone would use the free service from one city but not vote to raise the taxes in their city to pay for their own.

If it's a national mandate, then might as well make it a national service.

[-] [email protected] 14 points 1 day ago

Hi! This is what I'm trying to do with tucson.social. Wish the city would get back to me. I don't want to own/operate Tucson.social alone perpetually. Lol.

It would allow me to expand to a lot more community services outside of social media, chat, and Meetup platforms.

There's dozens of us! Dozens!

[-] [email protected] 3 points 1 day ago

This is really cool. And I would say a good replacement for current cloud setups. Since it's unreasonable to expect everyone to self-host. Although I think this could only really be a cost saving measure since there are already services like protondrive that offer end 2 end encryption. And I would probably trust the reliability of proton drive over the community hosting my stuff.

[-] [email protected] 21 points 2 days ago

Instead of building our own clouds, I want us to own the cloud. Keep all of the great parts about this feat of technical infrastructure, but put it in the hands of the people rather than corporations. I'm talking publicly funded, accessible, at cost cloud-services.

I worry that quickly this will follow this path:

  • Someone has to pay for it, so it becomes like an HOA of compute. (A Compute Owners Association, perhaps) Everyone contributes, everyone pays their shares
  • Now there’s a group making decisions… and they can impose rules voted upon by the group. Not everyone will like that, causing schisms.
  • Economies of scale: COA’s get large enough to be more mini-corps and less communal. Now you’re starting to see “subscription fees” no differently than many cloud providers, just with more “ownership and self regulation”
  • The people running these find that it takes a lot of work and need a salary. They also want to get hosted somewhere better than someone’s house, so they look for colocation facilities and worry about HA and DR.
  • They keep growing and draw the ire of companies for hosting copies of licensed resources. Ownership (which this article says we don’t have anyway) is hard to prove, and lawsuits start flying. The COA has to protect itself, so it starts having to police what’s stored on it. And now it’s no better than what it replaced.
[-] [email protected] 1 points 1 day ago

Wouldn't a zero-knowledge hosting solution (you provide hosting, but you can't see what's into it past a stream of binary) help with that?

[-] [email protected] 12 points 2 days ago

so did the author spent a bunch of money while excited about sticking it to companies upon discovering a company is not your friend. didn't enjoy the work of maintaining the services or have any friends to share them with. then dreamed up federated services so someone would do all that continuing maintenance for them? am i the weird one here for only putting effort into services i have other users for or actually enjoy doing?

[-] [email protected] 5 points 1 day ago

I didn't get the vibe that he didn't enjoy it. More that he figures that a typical person wouldn't enjoy it. And that I would agree with.

load more comments (1 replies)
[-] [email protected] 15 points 2 days ago

The LinkedIn-styled writing here is hard for me to get through, but I think the general gist is that for profit platforms are easier to onboard which I agree with. This line stands out:

And what do we get in return? A worse experience than cloud-based services.

I have to disagree somewhat, it's a different experience that is absolutely more difficult in many ways, but for those of us who value privacy, control over our data, and don't like ads, the trade-off is worth it. Also it goes without saying that the usability of selfhosted apps has exploded in the past few years and it will likely become less and less of an issue.

[-] [email protected] 12 points 2 days ago

Its funny to say a worse experience because I can confidently say that all the services ive replaced are equal or better than their corporate counterparts. And sometimes better by 10x

[-] [email protected] 4 points 1 day ago

I never wonder, is "X" is on jellyfin? Yes, good. No, give me 5.

[-] [email protected] 11 points 2 days ago

No, you could never buy books on Amazon, only rent them. Calibre with DeDRM plugin was a poor way to liberate them, given that formatting in libre formats was often worse than the original.

I stopped doing that and ingnored the Kindle ecosystem in general. I tried a Kobe reader with .epub books from diverse sources but I mostly use tablets (LineageOS and GrapheneOS) to consume content these days. The reader apps are not that great there, sadly.

load more comments (8 replies)
[-] [email protected] 7 points 2 days ago

E2E usually suffers from the same thing HTTP does: the MITM might not be able to read what you're saying, but they know who you're saying it to, and they may know in what context. This is a lot of information that can be used in profiling.

So you end up with systems like SimpleX, where everyone has a different UID for every contact, but that has its own problems, as anyone who's used systems like that are aware. We haven't really solved making that a good user experience for messaging; I don't see it translating to broader social media any time soon.

Nostr has some really good specs and tooling that neatly addresses these topics, including great cryptography support, signing, ad-hoc IDs, and an entirely voluntary simple naming lookup; it doesn't exactly solve zooko's triangle, but it provides a toolset sufficient to mix and match characteristics for whatever your threat model is. Sadly, Nostr is utterly dominated by the crypto crowd (and is associated with some controversial personalities), and even if you're not cryptocurrency-hostile, it's a really dull echo chamber with little other content that has prevented people who might otherwise build interesting platforms in it from doing so.

Mastodon was around for ages before (the in practice centralized) Bluesky; why did it take Bluesky to open a mass exodus from X?

This is a hard problem to solve. Throwing E2E at it doesn't make it easier; it's just tossing a buzzword in.

[-] [email protected] 8 points 2 days ago* (last edited 2 days ago)

I agree that we need to find a way to make this communal rather than individualistic, but government backing isn't that. It would be nice if that happened and all, but with a thesis like that it feels like it's missing the mark calling state-hosting "community ". How do we make self-hosted services something that can serve at the level of the community? Like a load balancing reverse proxy that points to the servers those in the community can host and everyone invites their friends and neighbours.

load more comments
view more: next ›
this post was submitted on 25 Jul 2025
181 points (100.0% liked)

Selfhosted

49825 readers
278 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS