@stefan I thought there was a bot somewhere linking the most interacted posts but I can't find any such thing. @TrendingBot posts about hashtags and looks at mastodon.social only.
@DrHyde@metacpan@perl I have been following @tag@relay.fedi.buzz for a while to see #Perl hashtagged posts that don’t otherwise make it to my #Mastodon instance.
Unfortunately, last September’s Mastodon 4.2.0 release broke the underlying #FediBuzz service’s basic methodology (which was a questionable kludge.) The latter’s developer, @astro, has been trying to adapt and support more traditional #ActivityPub#relay operation. I don’t know how that’s progressed over the past several months.
How do you balance between a wide range of content and massive following (I'm at > 800) and handpicked timeline?
I know there are lists and there are relayServers (I'm operating a #GoToSocial instancen), but I still miss a lot of posts in the flood called timeline.
@st3fan I'm also running my #GoToSocial instance.
I follow hashtags via https://relay.fedi.buzz/ on an alt account so it populates my federated timeline with stuff I'm interested in. You can now either search for hashtags or create tabs on your main account.
#Fedibuzz relays can be followed like normal users, no relay support is needed. Example: @tag
Just found out you can donate tokens to fedi.buzz, it’s a great relay and giving a token is only for fetching public posts from the federated timeline! Consider donating here!: https://fedi.buzz/token/donate
11 days past the release of Mastodon four-twenty, #FediBuzz has a live streaming connection to only half the instances than before. The content rate is holding up but we still need more token donations: https://fedi.buzz/token/donate
… and to think, without #FediBuzz I would never have noticed the latest #rust drama. I sure hope there will be some sort of workaround before Mastodon 4.2 is out.
I like the whole "A #relay for #hashtags" thing, but apparently it was working in a broken way, which is about to be fixed.
The solution is "join more relays" but in my experience that's just "see more cruft" - I don't want to be connected to a firehose of posts (many of which are in languages I can't read) I want to be connected to my interests, and for me FediBuzz was a great solution to that problem.
Do you like #FediBuzz and would love for it to continue? I know, I'm in the same camp as you.
@astro made it possible for you to donate a token, and the page says
> We consume only the federated timeline. We don't even see boosts or replies. The permissions that we request shouldn't allow us to do anything else.
Unfortunately, that's misleading. I agree that the permissions “shouldn't allow them to do anything else", but the reality is that today, they do.
The token you're donating can read the private messages of the user that created the token.
So if you do so, make sure you trust @astro with access to your private messages and their ability to keep your token secure or create a token from an account where you don't have private messages.
If you regret donating the token, you can revoke it at /oauth/authorized_applications
I don't like the way #Mastodon devs are downplaying the importance that #FediBuzz has on small instances... but asking for tokens that can read private messages without disclosing it is wrong. And considering that the people that are aware of it are mostly admins, means that it's more likely they will have important messages on their accounts.
I've found #FediBuzz to be incredibly valuable for finding content from a small Mastodon instance.
A future update to Mastodon is going to break the way #FediBuzz has worked so far. It will need an API token to authenticate with each instance to see posts on the public timeline of that instance.
Luckily, you can help out by "donating" an API token for your instance, which will make sure your instance stays visible to #FediBuzz.
@jan It's in the #FediBuzz backend that consumes and provides this API. It makes me incredibly sad that I do not publish this openly but I am afraid multiple #FediBuzz instances would make things worse.
This is VERY bad news for users of small instances like myself.
I do understand the reasoning behind it, and I'm not sure there is a good alternative. But it sure feels a bit like a deja vu from the self hosted email days ...