You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is recent but it seems like a good idea: ambassador.
You should read the description to understand what it's doing, but basically it would promote the most fav'd toots from our instance and allow remote instances to follow it in order to seed their instances with interesting content. This is a proposed fix to the problem of followbots.
Anybody see any problem with this approach? If we want to install it, it looks like I'd have to be the one to do it since it runs server-side.
The text was updated successfully, but these errors were encountered:
I think that's a great idea!
Maybe we could also link it's profile from about or more page (continuing from #7) so that people can get some feeling of this instance before they join?
I really like the idea of ambassador bots. New users and users on other instances can see the best of 🎺 ☕ I also would like to see other instances installing one, so it becomes common for users to check an instance's ambassador handle for good stuff.
I'm a bit concerned that only one instance seems to actually be using an ambassador bot. Also it's third-party code running directly against the database. Gonna hold off for now. I hope the core Mastodon project adds local timelines.
This project is recent but it seems like a good idea: ambassador.
You should read the description to understand what it's doing, but basically it would promote the most fav'd toots from our instance and allow remote instances to follow it in order to seed their instances with interesting content. This is a proposed fix to the problem of followbots.
Anybody see any problem with this approach? If we want to install it, it looks like I'd have to be the one to do it since it runs server-side.
The text was updated successfully, but these errors were encountered: