Gregory's ServerOh! And I was meant to be attending a Belle & Sebastian gig tonight. I canceled those tickets for I could fly to SF.
So far, I reckon Alan's acquisition of Twitter has cost me close to £190.
Wonder if he's good for the money?
|
59 comments
@Edent Excellent project. You might have seen, but there's also this feature request for better 🧵 handling: https://github.com/mastodon/mastodon/issues/8615  Cor! That @katebevan is good for engagement! Look at all those conversations she's kicked off! Indeed, how could they be? That means that ID of a reply is different depending on where you see it. So the ID of this post is: But when you see it on your server, it might appear as: The #MastodonAPI copes with this really well. But it is a mite confusing to get one's head around. @Edent I think @ostephens means that because you use the CW effectively as a subject line, some clients when they expand the CW-ed post will hide the CW itself and therefore the subject of your post. (Whereas some will expand the post but leave the warning in place, still readable. I've tried a few clients so far and seen both behaviours.) @benjamineskola @ostephens Oh, that's interesting. I mostly use the web interface. I don't think there's a right or wrong answer. @Edent @ostephens It looks like the official iOS client treats it as a toggle: either the CW text is displayed or the rest of the post is displayed. But Metatext treats it like a “below the fold” thing with expanding and collapsing. And tooot displays both the CW and the body of the post with no separator because I’ve configured it to always expand CWs. Think you’re right that there’s not really one way that will always work best for every client. @benjamineskola @Edent that’s right. Which means it would work better for users of the iOS client if you were to include the information that is currently only in the CW at the start of the toot as well. Otoh it might be the impetus for me to try out an alternative client! @Edent I ran into this recently: https://todon.nl/@benjamineskola/109341966082818336 I had assumed that an ID of a post on another server is effectively scoped to that server, so when I look for your post on my server it's `your.server/1234` which is different from `my.server/1234`. This is *not* the optimal way to view a Mastodon conversation - but it gives you an idea of what it looks like as a tree. Here you can see all the conversation threads - and which instances people are replying from. I can now read Mastodon conversations as proper threads on the command-line. Just as nature intended! Some pretty simple #Python code which uses the #MastodonAPI. All #OpenSource at https://codeberg.org/edent/Mastodon_Tools Blog coming soon 😃   @Edent looks great! hot tip: use Textualize Rich Py package to color code those threads and message parts a bit. Make it cyberpunk hardcore! 😂  @Edent Let's just add a mastodon backend to neomutt so you can do it in style.  @Edent Next step: add local feeds to MARC ( https://en.m.wikipedia.org/wiki/MARC_(archive)#:~:text=MARC%20(Mailing%20list%20ARChive)%20is,volunteers%20led%20by%20Hank%20Leininger. ) and make searchable? @5SpeedFun I'm wary of archiving someone else's content without their permission. @Edent If the software exists, you know someone will do it....I mean I'd be surprised if someone doesn't, even if it's just <secret agency> of "democractic/free" country. I wonder if this is something instances should prohibit in their rules? @dutchengineer it is *so* much friendlier than Twitter's. @Edent@mastodon.socialUsenet used/uses (past tense offensive to some) a message id that is supposedly globally unique when a message is peered. Dunno if that's a valid comparison though. |
One of the #MastodonAPI projects I'm working on is a better way to view long & complex threads.
You may have seen me build something similar for the other site a while ago - demo at https://shkspr.mobi/blog/2021/09/augmented-reality-twitter-conversations/ - so I'm hoping I can do something similarly interesting.
Main limitation is getting *all* of the conversation threads. It looks like the context API isn't paginated. But I might be being thick.