Goofed Home

@evan
#FediBuzz was always followable by users because there is just no technical difference.
@julian @mlanger

@julian @mlanger

This all brings in a firehose, which can be a lot of data to handle, especially if you're only interested in a few topics.

Fedibuzz has solved this really nicely, by having one relay per hashtag. So an admin can add a few hashtag relays for topics of interest to their users.

@evan
I would like to drink from your firehose
@julian @mlanger

@julian @mauvehed Try https://fedi.buzz/api/v1/timelines/tag/hiking

@julian @evan If I provided them, I would probably implement https://github.com/mastodon/fediverse_auxiliary_service_provider_specifications/blob/main/discovery/trends/v0.1/trends.md but haven't done so yet. Is that suitable for you? If so, I should do it soon.

@julian @evan I do trends for individual hashtags only. I fear that analyzing co-occurrency is going to use much more memory than I am allowed to use on our servers in the basement.

@astro @julian I think channel.org and Surf are doing this at a higher level.