Conversation

Notices

1. Embed this notice
   pinkdrunkenelephants (pinkdrunkenelephants@mastodon.social)'s status on Thursday, 25-Apr-2024 14:08:16 JST pinkdrunkenelephants

   So I want to leave .social for a better server that doesn't federate with Threads, but the ones on the fedipact website either actually do federate with Threads anyway (looking at you mas.to) or they're invite-only. :(

   #mastodon #fedipact

   • Embed this notice
     pinkdrunkenelephants (pinkdrunkenelephants@mastodon.social)'s status on Thursday, 25-Apr-2024 14:30:09 JST pinkdrunkenelephants

     • trumpet@mas.to
     • Tokyo Outsider (337ppm)

     @tokyo_0 @trumpet I signed up for an account there and the other users warned me that's what was going on. I deleted my mas.to account promptly afterwards. 🤷

   • Embed this notice
     pinkdrunkenelephants (pinkdrunkenelephants@mastodon.social)'s status on Thursday, 25-Apr-2024 14:34:08 JST pinkdrunkenelephants

     • trumpet@mas.to
     • Tokyo Outsider (337ppm)

     @tokyo_0 @trumpet 🤷 Even if I was, it probably wouldn't be a good idea to use an instance where people were doing that anyway. I found another instance that banned Threads though, and if approved I likely will move my account there in the next few days.

   • Embed this notice
     Mad A. Argon :qurio: (madargon@is-a.cat)'s status on Thursday, 25-Apr-2024 18:38:37 JST Mad A. Argon :qurio:

     • trumpet@mas.to
     • Tokyo Outsider (337ppm)

     @tokyo_0 @pinkdrunkenelephants @trumpet I saw posts related to this. Initially mas.to blocked Threads but later changed this to limited. And lists could be not updated after this :/

     Tokyo Outsider (337ppm) repeated this.
   • Embed this notice
     trumpet@mas.to (trumpet@mas.to)'s status on Thursday, 25-Apr-2024 18:50:19 JST trumpet@mas.to

     in reply to

     • Mad A. Argon :qurio:
     • Tokyo Outsider (337ppm)

     @madargon @tokyo_0 @pinkdrunkenelephants Hello there! mas.to still currently blocks Threads. We’ve posted about how we could theoretically move to limiting with Authorized Fetch enabled and per-user blocks in place, but we haven’t changed anything so far.

   • Embed this notice
     trumpet@mas.to (trumpet@mas.to)'s status on Thursday, 25-Apr-2024 19:13:32 JST trumpet@mas.to

     • Tokyo Outsider (337ppm)

     @tokyo_0 Thread here: https://mas.to/@trumpet/112212159528724033

   • Embed this notice
     trumpet@mas.to (trumpet@mas.to)'s status on Thursday, 25-Apr-2024 19:27:40 JST trumpet@mas.to

     • Tokyo Outsider (337ppm)

     @tokyo_0 What I posted is a proposal that I think might be the best compromise to protect those who don't want to interact with Threads, while allowing those who do the ability to connect. Still looking into the technical aspects of it.

   • Embed this notice
     trumpet@mas.to (trumpet@mas.to)'s status on Saturday, 27-Apr-2024 17:34:57 JST trumpet@mas.to

     • Tokyo Outsider (337ppm)

     @tokyo_0 Definitely thought of that approach too, the only thing is I thought it might be a little messy. But an option!