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?

You are viewing a single thread.
View all comments
29 points

You definitely could, but it’s not really sustainable.

Worst case scenario: if everybody does this, and there’s 50.000 subscribers on a certain community, then that community will have to update 50.000 other servers whenever one user leaves a single message or vote.

Sure, your own server wouldn’t have a hard time, but it every popular server (with lots of subscribers) would. It would either take a long time for you to receive their updates, or you wouldn’t get them at all.

The best thing you can do, is join a medium size server: it won’t be as overloaded as a big server, and wouldn’t cause as much strain on the fediverse as a personal server.

permalink
report
reply
2 points

I would think that updating 50.000 Lemmy instances would have a similar performance effect of 50.000 Lemmy users browsing one instance. In that case instance with one user won’t benefit the Fedeverse, but shouldn’t be an issue either.

permalink
report
parent
reply
4 points

I would think that updating 50.000 Lemmy instances would have a similar performance effect of 50.000 Lemmy users browsing one instance.

Only if the users are browsing All their watched communities 24/7. Otherwise they would only be producing load when they’re interacting with Lemmy.

permalink
report
parent
reply
1 point

Do you think the Fediverse would scale to a 1:1000 instance to user ratio?

permalink
report
parent
reply
13 points

I can say with full confidence that I have absolutely no idea.

I’ve heard this idea thrown around before, so I take no credit for it: One way to circumvent the issue would be to have actual relay nodes. As in: nodes that don’t hold contents or users themselves, but just “broadcast” incoming messages to several instances, so that the source instances don’t have to. This would of course have its own drawbacks and limitations, but it would alleviate the bottleneck.

I’m sure some kind of solution will be found though. Call me optimistic, but I think the lemmi/binniverse has a bright future ahead of it. I, for one, have burned my reddit bridges.

permalink
report
parent
reply
1 point
*

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.

https://www.cryptoisnotcryptocurrency.com/

permalink
report
parent
reply
10 points

@sab @eleitl There are ActivityPub relays already: https://github.com/brodi1/activitypub-relays

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 3.4K

    Monthly active users

  • 3.4K

    Posts

  • 77K

    Comments