Email or username:

Password:

Forgot your password?
Erin Kissane

It's not completely clear to me how various zones of the Fediverse distinguish "scraping" from "non-Mastodon ActivityPub services functioning according to spec in ways I didn't expect."

Given how frequently protocol behaviors act as ethical markers ("if you *can* do it, it's fine") this seems like a fruitful territory to try to map…

(I say this as someone who has myself been surprised more than once by AP implementations that put Fedi posts into unfamiliar-to-me contexts, don't eat me.)

21 comments
christa

@kissane I think about this a lot, especially given that each public post on mastodon is presented as an RSS feed (eg void.holdings/@christa.rss). it's a great question. my posts even acts differently than I expect within mastodon! what are the ethics around reading RSS feeds?

tachi

@christa @kissane wow.. I assumed when I locked down my instance that it disabled public rss but it did not. Now I'm hoping there is an option to lock that down to authed users as well :(

Derek Powazek 🐐

@kissane Given that the entire protocol copies things from server to server on purpose, the periodic freakouts about new services doing exactly that while others are applauded for "implementing the protocol" (which copies things by default) is so mystifying to me.

Derek Powazek 🐐

@kissane (I know, humans are complicated and trust is hard in distributed systems, etc.)

Erin Kissane

@fraying I think whenever I get confused by this stuff I get *really interested* because it's usually a sign that there are cultural norms being obscured by technical capacities. And of course I love that shit.

Derek Powazek 🐐

@kissane it definitely all means … something.

Stefan Bohacek

@fraying @kissane Something I brought up a few times today is this idea of having a robots.txt file for each of our social media profiles.

Much like a website that gets to decide who can access its publicly available content, some people would also like to exercise this level of control.

Luis Villa

@kissane in a discussion last week[1], someone explained a related vibe as "I used to create works, now I produce points in a corpus" and I've been thinking about that a lot as an efficient encapsulation of the current moment.

Among other things thoughts, I'm not aware of any protocol, or implementation, or legal supplement to a protocol, that has terminology or other mechanisms to capture that vibe.

[1] Maybe it was @CyberneticForests ?

Erin Kissane

@luis_in_brief @CyberneticForests

<whispervoice>I think protocols largely try to exclude vibes but they get through anyway, just in weird/uncanny ways</whispervoice>

Luis Villa

@kissane @CyberneticForests definitely agreed, though Fedi protocol more than most actively *includes* a loooooot of mid-20teens vibes (no QT, hostile to search, migrating names but not posts, etc.). How explicitly/implicitly those vibes are encoded varies a lot, though, which is of course the slippage you're (correctly!) so intrigued by.

Luis Villa

@kissane related to something I said to @polotek a few minutes ago, also: often vibes get layered into legal "protocols" (IP, TOUs, etc.) instead of the technical protocol, for a variety of reasons (some good, some less so).

Fedi/AP are rediscovering that, the hard way.

Eryk Salvaggio

Just published some of those thoughts from the CC panel today! ""This transition from β€œa thing I shared” to a data point to a dataset, and then to data infrastructure, has been a sour pill for those of us who shared our work online without foreseeing the future of AI models for labor displacement, surveillance, or other unsavory forms of automation." It's here: techpolicy.press/context-conse

@luis_in_brief @kissane

Mark T. Tomczak

@kissane Yes, agreed. This whole meta-topic probably requires a blog post.

... that blog post might very well be already written. I haven't made time to digest the whole thing, but I think privacy.thenexus.today/unsafe- touches on some of this.

(... I think the nut of the issue is "Protocol is behavior. If we want to be able to distinguish acceptable and unacceptable scraping, that has to be representable in the protocol; chasing every novel client and asking "Are you scraping me without my consent?" will not scale when "A node is allowed to scrape a subset of your node to clone topics and posts" is core to Mastodon's design).

@kissane Yes, agreed. This whole meta-topic probably requires a blog post.

... that blog post might very well be already written. I haven't made time to digest the whole thing, but I think privacy.thenexus.today/unsafe- touches on some of this.

(... I think the nut of the issue is "Protocol is behavior. If we want to be able to distinguish acceptable and unacceptable scraping, that has to be representable in the protocol; chasing every novel client and asking...

Erin Kissane

I think this formulation matches my own sense of why some things feel weird and others don't, and I'm really interested in pinning down what it is about some implementations that produce that impression.

(I think obviously it's more than one thing.)

tenforward.social/@noracodes/1

Erin Kissane

tx @noracodes fo permission to include this, tagging her here instead of above to reduce unintentional reply-bombing

Apple Annie :mstdn:

@kissane for me it is indeed the lack of linkbacks, the content is presented as being part of that platform, not part of a group of sites sharing a platform

Erin Kissane

@anniegreens Thank you!

The person representing Maven here said that the lack of linkbacks is unintentional, which makes me wonder about the effects of encountering half-built things. (We've seen this a few times just in the past few months.)

This is not a defense, just to be clear, just an open question.

Apple Annie :mstdn:

@kissane Yes, this is true. The last one was Content Nation, IIRC, and that person was attacked pretty harshly here. The project was still very much in development, but it wasn't apparent while perusing the site at the time.

Go Up