mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

14K
active users

#noarchive

0 posts0 participants0 posts today
Replied in thread

@ken_fallon @hpr @methoddan @Edent @webmink @perloid @garythewilliams

The chat about "grabbing comments" at the start is quite interesting. I don't know if you know already, but it is common for people who don't want their comments archived to have #noarchive (or #noindex, or #norobots) in their bio. Nothing is a surefire protection, since what they want is not very coherent (they kind of want you to read their mind) - but accounting for that tag at least gives people an opt-out.

Continued thread

What do the "#NoArchive #NoIndex #NoSearch #NoBridge" hashtags do?
These are all special hashtags intended to control the behavior of certain 3rd party tools that integrate with fedi.

- NoArchive requests that the profile and posts should not be included by fedi archive services.
- NoIndex and NoSearch request that the profile and posts should not be indexed by any cross-fedi full-text search applications.
- NoBridge requests that the profile and posts be excluded from any cross-network bridges, like bots that mirror posts between Fedi and BlueSky.

These all come with a caveat, which is that only
good-faith actors will respect them. You are welcome and encouraged to include them on your own profile, if desired, but be aware that some shady services will just ignore the hashtags.

Continued thread

To be clear, the need for #nobot, #noarchive, #noindex, and #nobridge was not born out of some single discrete event. This happened in four separate events. This has been a recurring problem on Fedi at least four times I know of. And I'm sure there's plenty of other bots out there I don't know about that I would have to opt-out of in the same way (if they bothered to let you).

And it should be abundantly clear that there is no respect for GDPR, privacy, boundaries, or anything but a modicum of shame in any of these actions.

Not that it has ever been any different online. Go look up robots.txt. This situation has not ever been any different.

Welcome to the Internet, y'all.

#Introduction

Hello, my name is Cal, and I pretend to be a robot cat on the Internet. As far as you know, I'm *just* pretending.

I joined at the recommendation of LRR so everything that happens here is entirely their fault. /joke

Some hashtags to make me more searchable: #Yorkshire #ScienceWitch #Furry #Technophile #RetroGaming #Nintendo2DS #Nintendo3DS #PS2 #PS3 #RSD #TransRights #NotOnDiscord #AutoDelete #NoArchive #NoIndex #NoSearch #NoAI #NoBridge #NoScrape #NoQuote

cont., 2/2

For example, these discussions on FEP c118 here:

https://socialhub.activitypub.rocks/t/fep-c118-content-licensing-support/2903/14__

# FEP-c118: Content licensing support
## Summary
Currently, popular Fediverse software does very little to establish the legal status of posts. Controversy over indexing and scraping the Fediverse is common. The hope is that providing a legal framework to express the desires of users as to how their content may be re-used might bring order to this debate.
https://codeberg.org/fediverse/fep/src/branch/main/feps/fep-c118.md

4. If you don't want your posts being easily accessible on the instances you federate with, why not make the posts followers only in the first place? I'd love to know the history behind folks thinking that public posting and a
#noindex or #noarchive hashtag was ever sufficient on the #Fediverse.

Folks with the institutional memory of these things, please step up and tell the history. Every admin has the right to defederate from whoever they want, but to do so on the basis of a
#Mastoverse -centric denialism & rewriting of the history of search & indexing on the Fediverse should be called out.

Respecting a federated post's no-index settings or even account level settings would be really cool but is currently impossible across the
#Fediverse.

Oh and wait until I tell you about how
#ContentWarnings aren't reliably reproducible across the fediverse either. Another day..

#fullsearch #Universeodon #ActivityPub #Misskey #Calckey, #Foundkey #Pleroma #Akkoma #Friendica #Hubzilla #Streams #FEP #FediverseSafety #FediblockMeta #meta #FediblockDiscussion #nosearch #fullTextSearch
SocialHub · FEP-c118: Content licensing supportThis is a (quite) question of #openweb vs #closedweb The Fediverse worked/s because it is #4opens at a protocol and #UX implementation, it’s a #openweb project, this is a good thing. Yes, the is a history of well worded “white lies” about privacy and safety that have helped to change social behavers. A kinda not bad thing. One of the #4opens is #opendata, every post has a URL, the is no encryption at all, in this all “privacy” is based on trust, a good thing. I agree with the need for #openli...
Replied in thread

@atomicpoet Just searched a post I made yesterday on there and it showed up.

I have all of the available common flags for opting out of indexes on my accounts (#noindex, #nobot, #noarchive, #nosearch in bio, and account marked to not be indexed in settings)

Seems like it ignores all of them, and the only opt out they offer is a link to the post privacy section of the Mastodon docs.

Public posts are public, and should be expected to be permanent, but still seems condescending.

[clip]
Threadstodon
This is just how we name these sorts of things now.

Paste a mastodon url that begins a thread here and we'll roll it into something presentable
Respects noindex (Mastodon user preference), #noindex, #nobot, #noarchive tags in bio.

I intend for this to be a tool to share toots in a way that's presentable to a wider audience outside of Mastodon and that's it. 100% tracker free. Every toot is linked back to its source....
[/clip]
threadstodon.io/

threadstodon.ioThreadstodonUnthread a series of status updates (aka toots) posted to Mastodon.

@djlena there's no exploitation happening at all. everything collected by whatever scraper this is is publicly available. it obviously doesn't respect hashtags like #NoBot / #NoSearch / #NoArchive but that's par for the course

it's annoying for sure but scrapers scrape every site on the Web. this is not a purely mastodon issue and you shouldn't frame it as such.

Privacy Hashtags: as users and interest in the #Fediverse grows, so do various bots, scrapers, and potential new search utilities

Vetting is done by admins via hashtag-Fediblock, but also various posts I have seen suggest using 'opt-out' hashtags in your Bio / profile

#NoBot - no interaction / scraping by bot accounts
#NoArchive - no crawling / archiving
#NoIndex / #NoSearch - do not include posts in search engine results

Of course bad-actors may ignore them (hence Fediblock), but good players should honor them

Hope this helps folks 💫