How Subscribing Helps Federate

I recently setup a new Lemmy instance and was surprised when my feed was mostly empty. I've since learned that a key part of Lemmy's federation is based on a user from your instance subscribing to communities on other instances. Only then, will your instance pull in posts from the subscribed community to your "All" feed.

This means that subscribing to new communities is especially important if you're on a young Lemmy instance since it helps to build out everyone's feed on that instance.

I've found discovering new communities to subscribe to on other instances can be difficult. To help me search for new communities I may be interested in, I tried aggregating as much of the Lemmy fediverse together into a single feed by subscribing to the widest range of Lemmy communities possible. This offers a Lemmy feed that's kind of like reddit.com/r/all. If it's interesting to anyone else, you can find the instance here: https://lemmy.directory.

Hopefully this offers another way to find new communities to subscribe to on other instances.

Here's a better description of my understanding on how Lemmy federates communities and why you might be interested in checking out lemmy.directory: https://lemmy.directory/post/34207.

Hope this helps ease the orientation to how Lemmy federation and communities work.

Krusty,
@Krusty@feddit.it avatar

I think you forgot to follow feddit.it

PriorProject,

This offers a Lemmy feed that's kind of like reddit.com/r/all. If it's interesting to anyone else, you can find the instance here: https://lemmy.directory.

You might want to update your instance link to be https://lemmy.directory/home/data_type/Post/listing_type/All/sort/Active/page/1. Ironically, it defaults to the local feed which is... empty. You could probably make nginx rewrite the homepage to be the all feed as well so the simple/nice url does what you want.

You might also want to add a section to your post writeup about federation load and why Lemmy doesn't do this by default. In a world where Lemmy is very successful and there are lots of instances (many thousands) that subscribe to all communities like you're doing...

  • An instance hosting lots of niche/unpopular communities is going to be sending thousands of copies of every post/comment off to instances where no one is going to read them. The federated network is small right now, and federation replication load is not a big issue... but the way it remains a non-issue as the network grows is for communities to replicate only when users on an instance are interested in them.
  • Each instance would have to handle the replication and storage of the entire lemmyverse. I don't know if that's a meaningful workload yet... but again... part of what keeps single-user instances viable in the future as the network grows is ensuring that they only have to fetch and store content that their user is interested in.

Very cool project though. Having an "all" instance sounds like a great service for discoverability. I'd also be interested to see a writeup from you about the hosting requirements. Does it take a lot of CPU/ram/disk to receive the full lemmyverse right now, or is it trivial? Your performance profile could be an interesting leading indicator of replication load as the network grows.

kiwi,

You might want to update your instance link to be https://lemmy.directory/home/data_type/Post/listing_type/All/sort/Active/page/1

Thanks for the tip, I updated the link! And I'll work on drafting some more text about the implications of subscribing to everything.

An instance hosting lots of niche/unpopular communities is going to be sending thousands of copies of every post/comment off to instances where no one is going to read them.

The rate a small instance would need to send off copies would be tied to the frequency of posts to the community, right? I'm interested in aggregating the lemmyverse, but wouldn't want to overburden other instances in doing so. Although, honestly, I'm more worried about overburdening my own trying. Were you suggesting that it might be rude to subscribe to a community just for discoverability?

So far the hosting requirements seem moderate, although I'd image if more people browse the feed the CPU and database reads will spike. I'll keep an eye on them. I'm not sure if this project is feasible/needed yet, but I thought it might be interesting to try. And if ever help, then I'd imagine during the start of a bunch of new instances.

GuyDudeman,
@GuyDudeman@lemmy.ml avatar

Hey there... do you not have sign-ups enabled on Lemmy.directory?

PriorProject,

The rate a small instance would need to send off copies would be tied to the frequency of posts to the community, right?

I believe it would be frequency_of_posts * number_of_instances_with_users_that_subscribe. Accounting of course for the idea that lots of small niche communities could... in aggregate... still be a lot of posts even if individually they aren't that busy.

I’m interested in aggregating the lemmyverse, but wouldn’t want to overburden other instances in doing so. Although, honestly, I’m more worried about overburdening my own trying. Were you suggesting that it might be rude to subscribe to a community just for discoverability?

No, I don't think you're likely to cause problems for other servers and I think it's a cool project. But "why is it so hard to discover communities" in lemmy is a common theme that armchair federated protocol designers try to solve on their first day after signing up for lemmy. New users might see your instance, and start pestering devs to say...

"Make subscribe-all the default, see lemmy.directory does it, why don't all instances automatically subscribe to all communities on all instances they federate with."

You already have such a nice and nearly comprehensive explanation of what you're doing. My suggestion is that it might be even nicer to anticipate this misguided extrapolation of your work and discuss why lemmy limits federation by default, why what you're doing is a bit different, and why even though it's reasonable for an instance or two to do mass discovery like this... it's almost certainly a bad idea for the entire network to behave that way.

matthieu_xyz,
@matthieu_xyz@piaille.fr avatar

@PriorProject

I think that’s almost inevitable. Almost all mid-sized lemmy instances will have a copy of almost all mid-sized lemmy communities.

Lemmy is a very different beast compared to mastodon. Of course not everyone is following everyone on mastodon, but if you have an even slightly diverse userbase, they’ll subscribe to a lot of different communities and your instance will have a lot of traffic very quickly. Hosting lemmy is going to be challenging.

PriorProject,

Lemmy is a very different beast compared to mastodon.

Yeah, this is an interesting point. I'm inclined to think that there will be niche communities that in aggregate make a bunch of posts, and that most servers might not have a subscriber for. But yeah, every medium size server is going to have to fetch every big community. Big machines can sling a lot of text, but maybe it does get wild and selective replication doesn't help.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • lemmy@lemmy.ml
  • GTA5RPClips
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • tacticalgear
  • cubers
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • osvaldo12
  • ngwrru68w68
  • kavyap
  • InstantRegret
  • JUstTest
  • everett
  • Durango
  • cisconetworking
  • khanakhh
  • ethstaker
  • tester
  • anitta
  • Leos
  • normalnudes
  • modclub
  • megavids
  • provamag3
  • lostlight
  • All magazines
    •