Conversation

Notices

1. Embed this notice
   Neo-Rodneyite: Yap Szn ✍🏿📖 (jalcine@todon.eu)'s status on Monday, 06-Oct-2025 09:26:49 JST Neo-Rodneyite: Yap Szn ✍🏿📖

   I don't like that you can deactivate an account for a short period but you can't do that here. A little annoying. It'd be a boolean flag and some materialized views, no?

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Monday, 06-Oct-2025 09:26:47 JST infinite love ⴳ

     in reply to

     @jalcine of course you could just settle for a local-only deactivation, and accept that remote servers will continue to show your profile and posts unaware. i think there might be an issue about this for mastodon at least

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 06-Oct-2025 09:26:47 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh @jalcine there are probably ways to do it that don't require 100+ pieces of software to learn your new flag.

     I'd probably change the account name and description to "[Suspended]" and make new properties for the former name and description and so on.

     So software that wants that info can get it, but everyone else sees a clear indication that the account is shut down.

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Monday, 06-Oct-2025 09:26:48 JST infinite love ⴳ

     in reply to

     @jalcine a boolean flag is the easy part. the hard part is getting 100 softwares to understand the boolean flag and 30,000 servers to update :-)

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 06-Oct-2025 09:27:37 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh @jalcine in general, I think making changes to your protocols that work for existing software is a good architectural goal.

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Monday, 06-Oct-2025 10:27:08 JST infinite love ⴳ

     in reply to

     • Evan Prodromou

     @evan @jalcine that doesn't hide existing posts, though. the goal is to make things not show up during the deactivation window. in a system where everyone fetches from one origin, this is easy. in a system where each origin maintains its own state, this becomes a state synchronization problem.

     bluesky can do it easily because their "one origin" for most people is bsky.app, which 99.99% of people use as opposed to something like deer.social which lets you ignore flags.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 06-Oct-2025 10:27:08 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh @jalcine Updates, change the addressing? That seems straightforward.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 06-Oct-2025 10:35:03 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh @jalcine It's an interesting question!

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Monday, 06-Oct-2025 10:35:04 JST infinite love ⴳ

     in reply to

     • Evan Prodromou

     @evan @jalcine i don't think sending tens of millions of Update activities is reasonable for a temporary deactivation (followed by a second batch of tens of millions of Update activities). that's not a ridiculous number, btw -- you can reach it with 100,000 posts and 100 peered servers.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 06-Oct-2025 10:39:53 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh @jalcine I don't like the idea of the visibility of content being dependent on the state of the actor.