A problem many have realized is that there are many /tech, /gaming etc. communities in different instances/servers. There is already https://fediverse.observer/ , so I think it wouldn’t be too hard to make a service that periodically roams the fediverse, checks for example the last 100,000 submissions of each (or top 100 active servers or something) server/instance, and gets info on all the communities/subs involved. Users could search communities, and if they write “gaming” they would get a list of all the active /gaming communities and info about them: subscriping users, total submissions, instance location (geographical) etc.

This could be used to find suitable /gaming communities for your needs.

A desireable future feature for both kbin and Lemmy would be to find and subscribe to multiple communities with the same name from the fediverse, and manage them to a single feed if the user so desires.

Ideas, thoughts?

    • mmaramara@kbin.socialOP
      0·
      1 year ago

      Yeah, I see others pointed out lemmyverse.net . I think separation between Lemmy instances and other Fediverse (ActivityPub) instances is arbitrary and creates needless fragmentation. So yeah I’m gonna have to check out Lemmyverse but I meant the whole Fediverse.

      • JonEFive@kbin.social
        1·
        1 year ago

        It isn’t “arbitrary” though. ActivityPub is just a baseline protocol that supports interoperability. Apps like Lemmy and Kbin build upon that framework, but also implement their own unique features and interfaces.

        There’s definitely value to being able to specifically search for Lemmy instances or things coming from Lemmy as much as any other fediverse app. But to your point, that could be handled through a filter on a much larger whatever set of data.

  • box464@kbin.social
    1·
    1 year ago

    What I’m looking for is lists or collections that I can create or the admin of the instance creates that combines common topics into a digest of subs. Then I just browse one digest on a topic rather than having to go through each separately.

    Having Kbin and Lemmy instances use a common catalog of topic identifiers so they can be easily coalesced would be helpful, too.