In reply to: https://activitypub.space/post/1683
In reply to: https://activitypub.space/post/1683
Friends, if you haven't already, it would be a big favour to me if you could enable tags.pub to boost your public tagged posts.
Just follow @_followback . It will follow you back, and when you make a post with a hashtag in it, the server will boost your post from the appropriate hashtag.
If you're interested in any topics, like @nokings , follow that account to get posts with that hashtag from across the Fediverse.
Let me know how it works for you!
@tchambers @joe great idea!
I think it's a really interesting question of how much of the Fediverse needs to be providing data to tags.pub.
I think this might be an interesting network science problem. I'll do some math and let you know!
@evan I read years ago that multi-word tags should be done in CamelCase, for the benefit of screenreaders. So when I take my posts, I'm careful to do so. It appears however that tags.pub lowercases all my tags.
I understand that it shouldn't create separate accounts for tags that vary only by capitalisation, but when creating a new account, why not preserve the capitalisation of the original tag?
@silverpill @liaizon Which, fine, all resources from other places need to be restricted to prevent DoS attacks anyway.
@rick have you started to figure out how to get quote posts working?
@liaizon @rick Probably very unlikely as long as the vocabulary isn't in Fedify: https://github.com/fedify-dev/fedify/issues/452 But now that the interaction policy vocab is in, it might not take too much longer.
New post: Can we have a more “social” media?
https://profpatsch.de/essays/a-more-social-media
On advertising, the Fediverse, and what a more human social web could look like.
Special mentions: @smallcircles, @phnt, @happy-programming
@Profpatsch You need to create a new signature because the request target is changing. It is a part of a signature base, so the initial signature becomes invalid when the client follows a redirect.
@Profpatsch @liaizon The guide recommends limiting the response size, to prevent DoS.
I also found this in your SECURITY.md:
@Profpatsch @Edent I see this is now merged, has it now been tested against how these new unicode actors will federate across to mastodon and other platforms that don't allow unicode usernames? cc @north