@tchambers@kbin.social
@tchambers@kbin.social avatar

tchambers

@tchambers@kbin.social

Technologist, writer, admin of indieweb.social. Fascinated by how new politics impacts technology and vice versa.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

A case for preemptively defederating with Threads (kbin.social)

With Meta beginning to test federation, there's a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don't...

FaceDeer,
@FaceDeer@kbin.social avatar

I came to the Threadiverse because Reddit was closing its APIs and building the walls higher around its garden.

I will be supremely disappointed if the Threadiverse collectively turns around and does the same thing.

Instances should be defederated when they do something harmful. Preemptively defederating is counterproductive, it gives Meta no incentive to do things right.

ernest,
@ernest@kbin.social avatar

Wow ;) I'm incredibly lucky to have come across people like you. The authors of those posts are actually right - managing /kbin is a significant challenge nowadays. It requires extensive knowledge and experience to keep it under control. But also I've never hidden that fact - the information about it is placed at the very top of the repository's readme ;) However, as I mentioned, a lot is changing very quickly https://kbin.social/m/RedditMigration/t/122333/Fediverse-won-t-replace-Reddit-as-long-as-Lemmy-is-the#entry-comment-478779. And we're all working hard on it, to improve and automate as many things as possible. Thanks to all of you, I believe I can face it head-on, and together we can create a better place. Better internet. Not just this instance, but cooperation between platforms is the key here.

Unfortunately, there are delays occurring again - I've decided that smooth website operation will be the priority this time. There are approximately 450k tasks waiting in the queue, and everything will be handled, but it will take some time. Today, we're also conducting final tests of the new infrastructure. It's taking a while because we're documenting templates that can later be used by others to create their own instances. I hope these are the last issues we have to endure ;)

Thanks for everything.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • meta
  • Macbeth
  • All magazines