Conversation

Notices

1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Friday, 05-Jul-2019 13:02:48 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:
   if your pitch is essentially "we should make __________ work like user blocks on Mastodon" please take it somewhere else. i'm not interested in building software which lies to the people who installed it.
   1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Friday, 05-Jul-2019 13:15:19 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:

      in reply to
      "lies to the people who installed it," you ask?
      
      yeah. if you get blocked on Mastodon, it starts doing some pretty strange stuff: namely, the software starts lying to you, the admin of the software, about the existence of the account which blocked you.
      
      and the justification is "if they disappear, the target won't know they've been blocked."
      
      which is of course complete nonsense, because:
      
      - they don't actually disapppear
      
      - Mastodon starts throwing fake server errors when you try to discover the user, read profile data, etc.
      
      this is just a bad design that has the opposite effect of what is intended. let blocks just unsubscribe the user and forbid resubscription. that's behaviour that actually makes sense. trying to emulate the behaviour of platforms where the strategy only works because there's a single server involved doesn't make any damn sense.