this post was submitted on 02 Jul 2023
22 points (95.8% liked)

Selfhosted

46172 readers
410 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
22
Suggestion for "relay" Lemmy instance for personal use? (lemmy.world)
submitted 2 years ago by itpcc@lemmy.world to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

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 comment's thread
view the rest of the comments
[–] sab@lemmy.world 6 points 2 years ago (2 children)

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.

[–] FenTiger@mastodon.social 4 points 2 years ago (1 children)

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

[–] sab@lemmy.world 1 points 2 years ago

Good to know, thanks!

[–] theterrasque@infosec.pub 0 points 2 years ago

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.