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
No down vote from me, but surely by now you know how people feel about crypto.
At any rate, I don't think an immutable ledger is desirable for speech (what's the point of moderation), perhaps more something like torrent would be preferable. And, as someone else mentioned, relay software already exists.
Who said anything about immutable ledger? I was talking about signing updates so it can be verified when relayed through untrusted third parties.
So if lemmy.world sends an update to lemmy.selfhosted.guy and then lemmy.anotherselfhosted.guy federates with lemmy.world, lemmy.world can then say "Hey, here's my public key, lemmy.selfhosted.guy have a copy of my data and is willing to be delegated to, you can get the data from him" and then lemmy.world doesn't have to distribute it's changes to everyone itself, but maybe just update 5-10 hosts. And the number of relays will scale with the network.
And thanks to the data being signed, you can trust the updates from lemmy.selfhosted.guy being from lemmy.world and not been tampered with, keeping lemmy.world as the authority of the data, even if you don't trust lemmy.selfhosted.guy.
Edit: This would also mean all the small self hosted instances will boost the network instead of threatening to overload it.
My bad, I thought you meant the other crypto (as did everyone else, presumably). I know cryptography was first, but I think it's safe to say that that abbreviation has been irrevocably tainted.
yeah, I'm slowly starting to realize that. That a few misunderstood, I could see that. If you're new to things you've probably only heard in connection to cryptocurrencies. But everyone misunderstanding? It's really shocking. Especially since the context should have made it obvious.
As developer we have crypto libraries. Crypto systems. Crypto layers. Crypto functions.. And so on.
Crypto is cryptography. Cryptocurrencies are just a small thing, using cryptography. To have that "take over" the crypto word completely is as unnerving as waking up one day and mentioning to someone you washed your face this morning and they respond "What, like, the screen?" and then discover everyone only thinking of facebook, even with the context.
I'm sorry, I'm rambling. It's just so unbelievable to me to have this happen in a forum focusing on self hosting services. Where crypto should (hopefully) be daily bread and butter.
It happens. Remember the original meaning of the word hacker, versus its public perception? You can hang on to the original meaning and have an extra hurdle in communication, or you can accept it and move on by being more specific.
At any rate, I think public/private keys are already being used by Lemmy for authentication on the way you propose.