[Krisando]

> The idea is to have a view built by the connections people on your instance make. The view from tech.lgbt is different from the view from photog.social, and that's a feature.

I looked at: a) https://mstdn.social/tags/opensource b) https://tech.lgbt/tags/opensource c) https://photog.social/tags/opensource

They look completely identical, the feature isn't working.

I'm sceptical it's even an intended feature as much as just the overall result of the protocol design not putting too much thought into it.

> Smaller nodes can subscribe to relays if they find it too limiting.

I looked into it, that's actually a better solution than the old one I was aware of which involved a bot account automatically subscribing to different accounts across the fediverse. It's my understanding that needs to be explicitly configured by a Mastodon administrator for a subscription though, out of the hands of the user.

This still isn't particularly user friendly and I still think this is a terrible user experience, particularly when comments like these appear:

>>>> Hashtags play a huge role on Mastodon - discover people by following hashtags

>>> I'm probably twiddling the wrong buttons or something but whenever I've clicked on a Fediverse hashtag, it's always just been the hashtag on the originating server. Is there a way to get a wider view that I've missed?

[zimpenfish]

If I look at [1] whilst logged in to that instance, I do get a slightly different (first couple of pages have a few more posts, then it starts diverging) view than from [2] where I am not logged in. Also slight difference from [3] in that posts from, e.g., @[e-mail] are not there but are in [1] and [2].

[1] https://octodon.social/tags/opensource

[2] https://tech.lgbt/tags/opensource

[3] https://photog.social/tags/opensource

[Kye]

They were just two random examples. As a server's connections build, it'll inevitably reach a point where it sees most/all of the network and it's no longer distinguishable.