Oct 25, 2026, 11:24 AMShould it work with Pixelfed too?
It says "follow requested". My server is on 0.15.2, so the newest Pixelfed version.
At the moment there is no possibility to add a relay, https://github.com/pixelfed/pixelfed/issues/4472 was closed by @shlee - not sure if it's still planned or not. I'm also not sure, if I would add tag.push for all #PUNKdotPHOTOS users or not.
Oct 25, 2026, 11:24 AMWhat I would love to see, @evan, that I can subscribe my posts just to specific tag.push bots.
E.g. I would love that only my posts with #foo are reposted by #foo@tag.push but not the #dontrepostthisone.
Can you point me to the github issues and I will add a feature request...
Thx
Oct 25, 2026, 11:27 AM
Oct 25, 2026, 12:49 PMOct 25, 2026, 12:49 PMOct 25, 2026, 6:09 PMOct 25, 2026, 3:36 PM@joergi one way is to just post things Quiet Public.
Oct 25, 2026, 6:12 PM@evan
I can't follow this. Why this would help?
Oct 25, 2026, 6:44 PM@joergi tags.pub doesn't boost posts that are Quiet Public. So, it would work for sharing some posts and not others, but it wouldn't work for sharing only specific tags in the same post.
Oct 25, 2026, 7:37 PM@evan
But that's not what I ment.
My idea is:
Instead of the (@)_follow(@)tag.push I would love to have a
(@)_subscribe(@)tags.pub
First follow, then subscribe with PM for specific hashtags
"(@)_subscribe(@)tags.pub subscribe #foo #abc #xyz"
(Or one PM for each hashtag, maybe easier)
Unsubscribe with PM
"(@)_subscribe(@)tags.pub unsubscribe #foo
"(@)_subscribe(@)tags.pub list"
For a list of all subscription
1/3
Oct 25, 2026, 7:37 PMEspecially for those where the server has the relay function, but people don't like every post to be reposted by the bot-army it would help.
Because sometimes you want a topic to be reposted. But not everything. And posting everything quiet public (which would be unlisted), just because of these bots, is not what I want (and as I read in discussions, not others).
So this would give the users more control over their posts, and not the full control to the admins.
2/3
Oct 25, 2026, 7:37 PM@evan
As I said: happy to make a proper feature request, if you are interested.
(I found the github repo)
3/3
Oct 25, 2026, 7:58 PM@joergi great, please do.
Oct 25, 2026, 8:00 PM@joergi i think what you're saying is, you have an allowlist of tags that the bots are able to boost, but otherwise they don't boost?
Oct 25, 2026, 8:01 PMOct 25, 2026, 8:01 PM@joergi and just turn off tags.pub entirely.
Oct 25, 2026, 8:47 PM@evan
That's the point. I'm maybe happy with special hashtags being pushed.
But I don't want every hashtag to be reposted.
But as always, 2 people, 2 opinions. 5 people, 5 opinions.
Oct 25, 2026, 9:02 PM@joergi That sounds reasonable. I think private messages are a great way to set those variables. I'd probably also eventually have a Web UI for the configuration, too, but doing it through PMs is probably fine to start.
Oct 25, 2026, 9:05 PM@joergi I think having two levels of settings, site-wide and per-tag, makes sense.
site-wide default: "allow" or "deny". If a tag doesn't have a value, use this.
per-tag override: "allow" or "deny". This overrides the site-wide default. If it's the same as the site-wide default, it doesn't matter.
So, maybe you'd do something like this:
PM tags.pub "set permission deny" (this sets the permissions off by default)
PM linux at tags.pub "set permission allow" (overrides default)
Oct 25, 2026, 9:06 PM@joergi Or you could do something like this:
PM tags.pub "set permission allow" (this sets the permissions on by default)
PM nsfw at tags.pub "set permission deny" (overrides default)
PM mh at tags.pub "set permission deny" (overrides default)
Oct 25, 2026, 9:14 PM@evan
Something like that.
I personally would still prefer to actively subscribe/allow different hashtags, instead of the unsubscribe/disallow.
I really wanted to have only specific one reposted. Not all.
But I guess, both way it would work.
Oct 25, 2026, 8:45 PM@evan
I use [@]punk[@]fedigroups.social for many of my punk.photos posts. But sometimes you forget it to mention and so on. So having this done by a tags.pub without adding works better (for me).
Oct 25, 2026, 8:40 PM@evan
If you wanna call it allow list, I would call it subscribed for special hashtags.
But the meaning is more or less the same.
Also if a relay is on a server activated, an "unsubscribe all" would be good. Without blocking the complete user.
Even I do like tags.pub, I understand everyone who is unhappy about being pushed because of their server admin signed in.
Consent is important but also hard, if their admin decides differently.
I will write the FR in the next days
Oct 25, 2026, 8:51 PM@joergi We already have a couple of ways to opt out entirely.
I think it'd be interesting to have per-user allowlists and denylists, though. "Only boost my content when it has these tags: A B C D E" or "Always boost my content unless it has these tags: U V W X Y Z".
I think the way I'd do that is by turning the whole service on and off, then turning individual tags on and off.
PMs is a good interface, but I'll probably build a UI for it too.
Oct 25, 2026, 9:10 PM@evan
Ui is definitely a good idea, but it's also way more complicated to implement.
Other question: is there a list of all hashtags which are reposted, ordered by the number of accounts who follows?
Haven't seen something like that on the website.
And how many % of the tags.pub bots have less then 10 followers?