#nobots
12 posts · Last used Sep 02
I just got my first report as an admin that made me break down crying.
Background: I action a lot of reports. Most are spam bots, scammers, NCII accounts, some bigots, etc.
I'm used to seeing hate speech, shitty hot-takes, and a ton of nonconsensual porn, but this temporarily broke me.
A "Gaza News" bot, scraping X, and posting unblurred, un-CW'd images of mutilated kids—just a wall of horrible atrocities.
I hate everything about this.
#FreeGaza #FuckTwitter #NoBots
Hey, Evan, this shit isn't okay. You and your bots don't have permission to share my communities outside of Fedi (or at all).
Again, I didn't even know you were doing this, because you *didn't ask*—you just assumed you had the right.
I know I blocked you and defederated all your projects already, so maybe one of your friends or bots can let you know you should delete these (and any other @alice@lgbtqia.space, @AltAfterDark@masto.thefword.club, @alice_watson@infosec.exchange, @alice@masto.thefword.club, and @alice_watson@mastodon.social posts).
#ConsentMatters #NoBots #NoTagsPub
tags.pubをリレーに追加して、テストしています。
tags.pubは、基本的な仕組みはハッシュタグリレーと同じで、リレーとして公開投稿を受け取って、ハッシュタグ付き投稿を希望者に配送するサーバです。
特定のハッシュタグつき投稿を受け取りたい人は、tags.pubのハッシュタグに対応するアカウントをフォローすると、tags.pubに届いた該当ハッシュタグ付き投稿がブーストされてきます。(Announceアクティビティなのですが、リノートとかリピートとか実装毎に機能の名前が異なります)
Social Web Foundationの設置しているサービスで、グローバルなハッシュタグフォローを実現する取り組みの一つです。
https://socialwebfoundation.org/2026/03/17/introducing-tags-pub/
https://tags.pub/
基本的に昔からハッシュタグリレーでやっていることと同じですが、リレー参加サーバに自動配送はせず、ユーザーのフォローベースで配送される点が異なります。
利用者は、自分のプロフィールの説明文の中に #NoTagsPub を記載したり、もう少し広い範囲で #NoBots や #NoBot を指定するとこの仕組みで配送されなくなります。
#fedibird #fedibird_info [参照]
Replying to
@mxk@hachyderm.io #NoBots like this? Or does it have to be #NoBot? I've also seen both. Along with #NoBridge, #NoIndex, and a few others...plus the new ones Evan mentioned today.
Also, that's not how consent works. I shouldn't need to defend myself from your lack of boundaries.
But I guess I just need to add the #NoBots pack to my purse along with the Rohypnol test kits, mace, and other things I'm supposed to carry to keep guys from violating my boundaries.
Replying to
@alice@lgbtqia.space
I'd seen the tags.pub bot before, and hadn't thought about it at the time. I read Evan's post and opted for the "extreme" option of blocking the domain. That seemed the most logical option. Imagine if all the different bots required different hashtags to opt out.
#nobots #botgoaway #noindex #nobotno #stopitbot #BotNo #NoTagBot #robotstop #NOTHANKS #stopindex #nobotscrape #noscraping #ignorethis #noindexno #donotscrape #donotindex
No room for bio.
@evan@cosocial.ca
Replying to
@alice@lgbtqia.space in my experience even tagging #NoBots or #NoBot gets ignored by most bot accounts anyways. I've vented at several before just reporting and blocking them.
"Add this tag to your profile to opt out of our shitty service" is *not* a valid way to run your bot/app/etc.
#NoBots #NoBot #NoTagsBot #HalfMyBioIsGoingToEndUpBeingOptOutsForYourShitServices #FuckBots
Boosted by @tchambers@indieweb.social
Replying to on hackers.pub
Hackers' Pub is now integrated with tags.pub. What this means is that public posts with hashtags will automatically be relayed to tags.pub, reaching a wider audience. Of course, if you have the #NoTagsPub, #NoBot, or #NoBots tag on your bio, your posts will not be relayed to tags.pub.
Cc: @evan@cosocial.ca #TagsPub
Boosted by @tchambers@indieweb.social
Hashtag discovery in the Fediverse is limited by which servers yours knows about. tags.pub, a global hashtag server by the Social Web Foundation, fills that gap. It collects public posts and redistributes them by hashtag, so your content reaches people across the network. It works out of the box on WordPress.com. Self-hosted sites can connect by adding a relay in the ActivityPub settings. The project is open source, privacy-conscious, and respects opt-outs.
Replying to
cc @evan@cosocial.ca relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.
#NoBots #nobot #fedi22 #NoTagsPub #Botiquette
Replying to on vault37.xyz
@chad@vault37.xyz For what it is worth, the dev of that AI timeline tool says it now supports several ways to stop it.
Zeitgeist now:
You've seen all posts