I'm a "but..." because private accounts are kind of frustrating on Mastodon.
-
I'm a "but..." because private accounts are kind of frustrating on Mastodon. When you reply to a followers-only post on Mastodon, for example, the response is legible only to *your* followers, not the followers of the person you replied to. So, the conversation diminishes rapidly. This is a bug.
-
I'm a "but..." because private accounts are kind of frustrating on Mastodon. When you reply to a followers-only post on Mastodon, for example, the response is legible only to *your* followers, not the followers of the person you replied to. So, the conversation diminishes rapidly. This is a bug.
Second, there's an in-between kind of audience -- a set of people that I don't know personally, but that I trust some smart moderators have vetted. Bike lovers, Montreal Open Source fans, ActivityPub developers. Sometimes you want to talk to "people like us", vaguely defined. Facebook Groups work like this, for instance; well-managed mailing lists and chat groups work this way, too. My hope is that the work that we're doing for groups in the SocialCG will help with this: https://github.com/swicg/groups
-
Second, there's an in-between kind of audience -- a set of people that I don't know personally, but that I trust some smart moderators have vetted. Bike lovers, Montreal Open Source fans, ActivityPub developers. Sometimes you want to talk to "people like us", vaguely defined. Facebook Groups work like this, for instance; well-managed mailing lists and chat groups work this way, too. My hope is that the work that we're doing for groups in the SocialCG will help with this: https://github.com/swicg/groups
Finally, there's that extra step of end-to-end encryption (E2EE) that protects the content even from your (and their) server operator. I think the current work on bringing MLS to ActivityPub will help with that a lot. https://github.com/swicg/activitypub-e2ee
-
Finally, there's that extra step of end-to-end encryption (E2EE) that protects the content even from your (and their) server operator. I think the current work on bringing MLS to ActivityPub will help with that a lot. https://github.com/swicg/activitypub-e2ee
@evan So I think you need to think about audiences. Compare Bluesky. Mastodon launched very "closed" and Bluesky launched very "open". And Bluesky users all want *more* privacy features than they have, but the overall thing is Mastodon attracted a *very* privacy-conscious crowd and Bluesky less so. Which means I think some scraping-based features which are *entirely defensible*, and which Bluesky users would love, would find bad traction with the Mastodon userbase *specifically*. We self-sorted.
-
@evan So I think you need to think about audiences. Compare Bluesky. Mastodon launched very "closed" and Bluesky launched very "open". And Bluesky users all want *more* privacy features than they have, but the overall thing is Mastodon attracted a *very* privacy-conscious crowd and Bluesky less so. Which means I think some scraping-based features which are *entirely defensible*, and which Bluesky users would love, would find bad traction with the Mastodon userbase *specifically*. We self-sorted.
@evan Are the SocialCG "groups" different from the thing Lemmy is already using?
-
@evan So I think you need to think about audiences. Compare Bluesky. Mastodon launched very "closed" and Bluesky launched very "open". And Bluesky users all want *more* privacy features than they have, but the overall thing is Mastodon attracted a *very* privacy-conscious crowd and Bluesky less so. Which means I think some scraping-based features which are *entirely defensible*, and which Bluesky users would love, would find bad traction with the Mastodon userbase *specifically*. We self-sorted.
@mcc I don't understand your point. The whole thread is about avoiding scraping. I didn't say anything about adding scraping-based features.
-
@evan Are the SocialCG "groups" different from the thing Lemmy is already using?
@mcc yes.
-
@mcc I don't understand your point. The whole thread is about avoiding scraping. I didn't say anything about adding scraping-based features.
@evan @mcc the framing of the poll appears to suggest that the real question is whether to go with individualist solutions for scraping problems, or to condemn scraping practices more broadly (the latter being the fedi status quo right now)
this may or may not have been your intent, but it's how it comes off
-
@evan @mcc the framing of the poll appears to suggest that the real question is whether to go with individualist solutions for scraping problems, or to condemn scraping practices more broadly (the latter being the fedi status quo right now)
this may or may not have been your intent, but it's how it comes off
@ireneista @evan When I've seen such sentiments previously, I feel like I've seen it from people who want to make third-party apps that would require scraper-like behavior, and are thus chafing against the Mastoverse social norm that even public posts don't get scraped. I'm used enough to that being the bounds of discussion it didn't click for me that you (Evan) were talking about actual protocol extensions.
-
Finally, there's that extra step of end-to-end encryption (E2EE) that protects the content even from your (and their) server operator. I think the current work on bringing MLS to ActivityPub will help with that a lot. https://github.com/swicg/activitypub-e2ee
So, a couple of people asked if this poll was meant to keep people from arguing against scraping, indexing, and training on people's public data. Nothing of the kind.
-
So, a couple of people asked if this poll was meant to keep people from arguing against scraping, indexing, and training on people's public data. Nothing of the kind.
I think that developers in our community, who hold our values, are likely to be very amenable to this kind of argument. I think that making that point verbally can be really helpful.
-
I think that developers in our community, who hold our values, are likely to be very amenable to this kind of argument. I think that making that point verbally can be really helpful.
I also think advisory signals, like robots.txt and meta tags, or the indexable/discoverable flags on Mastodon accounts, can be helpful with compliant and friendly bots -- especially search engine or archiving bots.
-
I also think advisory signals, like robots.txt and meta tags, or the indexable/discoverable flags on Mastodon accounts, can be helpful with compliant and friendly bots -- especially search engine or archiving bots.
But I also think people are concerned about bots that aren't friendly or compliant -- for example, "dark" LLM training bots that ignore robots.txt and other signals. I don't think that arguing or signalling helps in those cases. Having a private account and posting followers-only does, though.
-
@ireneista @evan When I've seen such sentiments previously, I feel like I've seen it from people who want to make third-party apps that would require scraper-like behavior, and are thus chafing against the Mastoverse social norm that even public posts don't get scraped. I'm used enough to that being the bounds of discussion it didn't click for me that you (Evan) were talking about actual protocol extensions.
@mcc @ireneista Great. Thanks.