Conversation

Notices

1. Embed this notice
   Erin Kissane (kissane@mstdn.social)'s status on Friday, 21-Jul-2023 09:31:48 JST Erin Kissane

   • Dr. Johnathan Flowers

   But what is the actual PROBLEM with Mastodon?? Said one hundred dozen people over several months of threads here. So I wrote it up.

   It's too long, but we got bad doors, stilt-walking French shepherds, water bugs, a bunch of @shengokai quotations, What The Fuck Is Up With Bluesky, and more.

   https://erinkissane.com/the-affordance-loop

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 21-Jul-2023 09:54:53 JST Paul Cantrell

     in reply to

     @kissane
     This is magnificent. I’m just a few pages in, and it is already going on my permanent references list. Some of the best explanations I’ve heard of not one but •several• crucial ideas in human-centered design.

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Friday, 21-Jul-2023 17:29:12 JST Annika Backstrom

     in reply to

     @kissane The part about which replies you see isn't 100% accurate, but an accurate description of how that works would be longer than the current post, so 🤷♀️

   • Embed this notice
     Erin Kissane (kissane@mstdn.social)'s status on Friday, 21-Jul-2023 17:29:13 JST Erin Kissane

     in reply to

     I would bet actual money that I've got some nuance of Mastodon's functionality wrong in there so when you see that please do lmk. I thought about asking instance-running friends to preview it but I've taken up enough of their time this week.

   • Embed this notice
     old man and the cbowns (cbowns@xoxo.zone)'s status on Saturday, 22-Jul-2023 03:06:53 JST old man and the cbowns

     in reply to

     • Annika Backstrom

     @annika (I would 100% read a Painfully Accurate Description if there’s one out there or if you ever type it out; I am here for this nonsense)

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Saturday, 22-Jul-2023 03:19:57 JST Annika Backstrom

     in reply to

     • old man and the cbowns

     @cbowns ok so it's not THAT long, but people's eyes tend to glaze over. it boils down to: did your server have a *reason* to get the reply in question? let's say Alice makes a post and Bob replies. Reasons you would see the reply:

     1. Bob is on your server (post originated on your server)
     2. Alice is on your server (Bob's reply was directed at your server)
     3. Somebody on your server follows Bob (Bob's posts are sent to your server)

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Saturday, 22-Jul-2023 03:22:25 JST Annika Backstrom

     in reply to

     • old man and the cbowns

     @cbowns 4. Somebody on your server follows Carol, and Carol boosts Bob's reply (the reply shows up on Carol's timeline, which is sent to your server)
     5. Someone on your server visited the thread on any other server, and copied the origin URL into your server's search box (causing the reply to show up in your server's db and timelines)

     That's everything, off the top of my head.

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Saturday, 22-Jul-2023 03:24:35 JST Annika Backstrom

     in reply to

     • old man and the cbowns

     @cbowns Notably absent from the list of "reasons" is the simple fact that a reply was posted. If I'm on server A, looking at a post from Server B, and there is a reply from Server C, there is no implicit relationship between servers A and C. C doesn't necessarily even know A exists, or that anybody from A saw the post on B.