I’ve been in Lemmy for a month and I’m quite enjoy using the service.
However, after the mass migration on both Reddit and Twitter, I feel like the services are now significantly slower than they used to be. So I’m wondering whether I should have some kind of personal CDN/relay service for “caching” information especially medias or just create a new instace and federated to public Lemmy instance?
FYI, I have a private OpenVPN served on DO and 1L “server” that run Proxmox for existing services to my home. Should be okay to have a Nginx reverse proxy, right?
Or use crypto. Generate keypairs, sign updates. Add support for delegating updates to other instances.
Maybe add support for having instances getting data to indicate if they’re willing to relay update data to others, and have main instance refer to them for a certain time period, say… 6 hours maybe?
Relay willingness would depend on instance config and load, ideally.
Edit: any reason I’m getting down votes? If there is a problem with the approach, at least leave a comment.
Edit2: Crypto as in CRYPTOGRAPHY! Which has been shortened to crypto since long before bitcoin was invented. If this was some non-tech forum I could understand, but a community about self hosting and no one seems to be making the obvious connection? Wow. And you guys host stuff, that’s just scary.
You thought I was talking about cryptocurrencies? Really? You read that, saw crypto, public/private keys, signing data, and thought “He’s talking about cryptocurrencies, and surely not cryptography!” ??
Seriously? Wow… I sincerely hope you’re not hosting anything public, and if you do, consider shutting it down and step away from the server until you have a bit more technical insight.
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.
