Hey, a month ago I would have simply pressde the button and not thought too much about it. Now the situation looks completely different. I have bookmarked all the discussions I came across, and next week I will read every single post to have a complete picture. I owe you that.
However, we need to think about additional privacy features, as priorities have drastically changed in recent weeks, and I will have to carefully consider that. Now that I have dealt with infrastructure issues, I will focus on the most important matters.
My worry that many articles are going to have a biased take on the situation, or be coming from Mastodon etc. where things don’t map up 1:1.
My perspective:
I moderate a medium-sized magazine here on Kbin (@Disneyland, about 264 subscribers here and a couple dozen elsewhere on the fediverse). You can’t moderate a magazine from another instance, nor can you redirect a magazine somewhere else. This means I effectively must use Kbin.social, especially since I also mod the /r/Disneyland subreddit and have been redirecting people to our magazine for a month now.
I personally would like to see Threads here, if only because @disneyparks would be a nice fit to have automatically included in our microblog tab. I can’t go to another instance that supports Threads because again - moderators on Kbin can’t be from different instances. And besides - me being on another instance doesn’t stop the fact that I couldn’t have content from Threads automatically added here. So my options are basically “deal with it” or “abandon the community here”.
It really sucks that there is a way that could make my magazine better by including actual official Disney sources in our Disney-themed magazine, but some people are afraid of EEE they are trying to keep that from everyone. I’d rather federate with Threads and allow users to individually block the domain if they desire.
If EEE is the worry, fight them at the “extend” step, not the “embrace” one.
If mountains of spam is the worry - people have to manually follow people from other instances for those posts to federate to Kbin, so not every single account will magically pop up here on Kbin. It’ll be accounts that people on Kbin have followed; a small chunk.
Vice-versa, Threads is full of casual users who don’t know much about the fediverse. Any Threads users interacting on Kbin are those who understand the fediverse and go out of their way to subscribe to Kbin magazines from Threads. We know from past history that these are going to be a minority; even within the fediverse, Mastodon is huge (and tech-savvy) but we see very few Mastodon folks posting to Kbin threads.
If “Facebook is sucking up all my data” is the worry, they could do that anyway. The fediverse is open and public; they can easily set up a “shadow instance” that federates everywhere and slurps everything. They don’t need Threads for that.
If people just don’t want to see Threads users at all, making the block button defederate on the account level would be wonderful. If people choose to block Threads, then Threads users couldn’t see them and vice versa. People who see Threads as a potential useful resource (myself, for the magazine I mod) would still be able to have that content in the community here on Kbin. Everyone’s happy.
While I absolutely appreciate the commitment, you do not owe us that. You don’t owe us anything really.
If you want to have a discussion, I suggest maybe you could make a thread where it’s discussed officially, rather than you having to go through everything that has been written all over the place. We owe that to you. :)
Hey, a month ago I would have simply pressde the button and not thought too much about it. Now the situation looks completely different. I have bookmarked all the discussions I came across, and next week I will read every single post to have a complete picture. I owe you that.
However, we need to think about additional privacy features, as priorities have drastically changed in recent weeks, and I will have to carefully consider that. Now that I have dealt with infrastructure issues, I will focus on the most important matters.
My worry that many articles are going to have a biased take on the situation, or be coming from Mastodon etc. where things don’t map up 1:1.
My perspective:
I moderate a medium-sized magazine here on Kbin (@Disneyland, about 264 subscribers here and a couple dozen elsewhere on the fediverse). You can’t moderate a magazine from another instance, nor can you redirect a magazine somewhere else. This means I effectively must use Kbin.social, especially since I also mod the /r/Disneyland subreddit and have been redirecting people to our magazine for a month now.
I personally would like to see Threads here, if only because @disneyparks would be a nice fit to have automatically included in our microblog tab. I can’t go to another instance that supports Threads because again - moderators on Kbin can’t be from different instances. And besides - me being on another instance doesn’t stop the fact that I couldn’t have content from Threads automatically added here. So my options are basically “deal with it” or “abandon the community here”.
It really sucks that there is a way that could make my magazine better by including actual official Disney sources in our Disney-themed magazine, but some people are afraid of EEE they are trying to keep that from everyone. I’d rather federate with Threads and allow users to individually block the domain if they desire.
If EEE is the worry, fight them at the “extend” step, not the “embrace” one.
If mountains of spam is the worry - people have to manually follow people from other instances for those posts to federate to Kbin, so not every single account will magically pop up here on Kbin. It’ll be accounts that people on Kbin have followed; a small chunk.
Vice-versa, Threads is full of casual users who don’t know much about the fediverse. Any Threads users interacting on Kbin are those who understand the fediverse and go out of their way to subscribe to Kbin magazines from Threads. We know from past history that these are going to be a minority; even within the fediverse, Mastodon is huge (and tech-savvy) but we see very few Mastodon folks posting to Kbin threads.
If “Facebook is sucking up all my data” is the worry, they could do that anyway. The fediverse is open and public; they can easily set up a “shadow instance” that federates everywhere and slurps everything. They don’t need Threads for that.
If people just don’t want to see Threads users at all, making the block button defederate on the account level would be wonderful. If people choose to block Threads, then Threads users couldn’t see them and vice versa. People who see Threads as a potential useful resource (myself, for the magazine I mod) would still be able to have that content in the community here on Kbin. Everyone’s happy.
Thoughtful consideration is the most I could have hoped for. Thanks Ernest, keep being awesome :)
While I absolutely appreciate the commitment, you do not owe us that. You don’t owe us anything really.
If you want to have a discussion, I suggest maybe you could make a thread where it’s discussed officially, rather than you having to go through everything that has been written all over the place. We owe that to you. :)