in reply to AJ Sadauskas

The media in this post is not displayed to visitors. To view it, please go to the original post.

in reply to Droppie [infosec] 🐨 ​

@Friendly Koala @Marek πŸ‡¦πŸ‡ΊπŸ‡©πŸ‡ͺ Hi again Marek, hope you're well. I more or less stopped using my new account here as per my "final" post to you about the hashtags difficulty several weeks ago. Tonight though, as per this thread, i wondered if there might now be reason to hope anew.

Would you be kind enough pls, when you have time, to review this thread & advise me your thoughts, wrt your server? Thx.

cc: @Droppie [infosec] 🐨 ​ @AJ Sadauskas @FollowBackBot

in reply to Marek πŸ‡¦πŸ‡ΊπŸ‡©πŸ‡ͺ

@Marek πŸ‡¦πŸ‡ΊπŸ‡©πŸ‡ͺ @FollowBackBot @Friendly Koala @AJ Sadauskas yes i did, but i posted the pic of the resultant page, above... here it is again... i dunno what to do with this page once there.

i suppose my main question here for you is -- how do you feel about any of your instance users, eg me, using this new possibility, wrt your server resources?

cc: @Droppie [infosec] 🐨 ​

in reply to AJ Sadauskas

"If someone puts up a post using that hashtag, and no-one on your instance follows that person or anyone who shares it, it won't appear in your feed."

That's not true. I can follow a hashtag without following the person who uses it.
When following a hashtag I get all posts containing that hashtag.
social.growyourown.services/@F…

This entry was edited (2 days ago)
in reply to planeguy

I think we need to mitigate against centralization there.

One way is to have multiple tag servers. tags.pub exists; so does Fedibuzz and tagpump.app. Other services like surf.social or channel.org use aggregated channels with multiple tags, actors, and other inputs, but they're in the same vein.

I'd love love love to see someone take the code we've made and deploy another server, 3, 5, or 7. I'd be happy to help with that process.

This entry was edited (2 days ago)
⇧