@Nougat It doesn’t prevent them now, as they can just easily crawl all of your posts on here because you are posting on a *public instance*. Defederating from them does nothing to make your public content private.
@ninboy No, it doesn’t make my public content private, but it would display my content alongside everything else that a threads user would see, which would make Meta’s product more attractive to threads users. Increased threads userbase means increased ad revenue. Speaking of which, I’m now thinking about how content I created, not on a Meta-operated site, would be (as federation by default intends) displayed next to Meta advertising on their instance. My ability to prevent me-sourced content from reaching Meta’s instance prevents me-sourced content from displaying next to advertisement I don’t want it to be displayed next to.
@Nougat that makes sense, thanks for elaborating on your points. I guess as soon as we put any content out there we can’t prevent screenshots going viral on any context.
@ninboy Sure, you’re not going to close that “analog hole,” but in a case like that, the audience is aware that the content isn’t from the site they’re on. Me- (and you- and everyone-)sourced content appearing on a Meta site as though it was Meta content would carry some things to have real concerns about.
Of course, this is all really new(ish), so it’s possible that a future internet audience will have a better awareness of how federation works, and bring that understanding with them while they browse. On the other hand, have you seen people?
Tangent: You tagged me in your original reply, which made me wonder why, and if I should do the same thing. Checking your username, I see you’re on from mastodon.social, and here I am via kbin.social. I think this is my first real interplatform conversation like that, and I think it’s really cool.
@Nougat It doesn’t prevent them now, as they can just easily crawl all of your posts on here because you are posting on a *public instance*. Defederating from them does nothing to make your public content private.
@ninboy No, it doesn’t make my public content private, but it would display my content alongside everything else that a threads user would see, which would make Meta’s product more attractive to threads users. Increased threads userbase means increased ad revenue. Speaking of which, I’m now thinking about how content I created, not on a Meta-operated site, would be (as federation by default intends) displayed next to Meta advertising on their instance. My ability to prevent me-sourced content from reaching Meta’s instance prevents me-sourced content from displaying next to advertisement I don’t want it to be displayed next to.
@Nougat that makes sense, thanks for elaborating on your points. I guess as soon as we put any content out there we can’t prevent screenshots going viral on any context.
@ninboy Sure, you’re not going to close that “analog hole,” but in a case like that, the audience is aware that the content isn’t from the site they’re on. Me- (and you- and everyone-)sourced content appearing on a Meta site as though it was Meta content would carry some things to have real concerns about.
Of course, this is all really new(ish), so it’s possible that a future internet audience will have a better awareness of how federation works, and bring that understanding with them while they browse. On the other hand, have you seen people?
Tangent: You tagged me in your original reply, which made me wonder why, and if I should do the same thing. Checking your username, I see you’re on from mastodon.social, and here I am via kbin.social. I think this is my first real interplatform conversation like that, and I think it’s really cool.