panoptic

If I’m reading the protocol right, it’s probably larger instances that will avoid more duplication, since:

1. There’s a higher chance they’re going to have more communities shared among users (for really tiny instances you’re probably going to get a lot of overlap since those people likely have interconnected interests, but I expect that would fall off quickly, but then converge at scale).
2. The larger number of users will mean they ‘use’ more of the content they’re pulling down (I can’t read all of a highly active community in a day, but 1000 people together checking through the day might ‘use’ it all).

I’m not sure I see where you see caching fitting in.
I am surprised I don’t see some kind of lower resolution digest concept in the protocol (which might be what you’re looking for)

That’s what they’re saying.

Essentially - if someone from the small instance subscribes to a community that has a ton of data (huge post volume, images, whatever), the small instance needs to pull data over from the larger instance. At some point there may be communities that are so large small instances can’t pull them in without tanking.

^^^ This

Source:
https://kbin.social/m/kbinMeta/t/12719/Why-are-you-not-seeing-as-many-posts-from-Lemmy

Hey, we’ll always have narwals baconing at midnight

No idea - but I actually think the Fediverse concept maps to Reddit way better than it has other social networks so I could see some iteration of this really catching on over time.

For something like Twitter, the whole value proposition is “one big universal conversation” and the federated stuff gets in the way of that a little bit, but Reddit has always been a federation of communities (who occasionally fight, join together, cross post, etc) - that maps really well to this stuff.