A lesser known Mastodon pro tip:
Uncategorized
32
Posts
12
Posters
2
Views
-
@julian While in general, I agree, you could implement some sort of heuristics, there is one huge difference - a NodeBB server is centralized and sees everything. With Mastodon, half of the posts in a conversation might not be visible to you, either because of being outright blocked, or the post simply not hitting your instance because of where the participants post from.
Any heuristic based on unrelated metadata would be inaccurate at best, but more often than not outright misleading.
@julian This could theoretically be solved by simply adding the conversation id to each Status object in the timeline (and likely also any other post-like object that your client is receiving), but someone familiar with the entire protocol would need to look at this change, since it might bring compatibility issues. 🤷
-
@julian This could theoretically be solved by simply adding the conversation id to each Status object in the timeline (and likely also any other post-like object that your client is receiving), but someone familiar with the entire protocol would need to look at this change, since it might bring compatibility issues. 🤷
@ticho @julian An important thing to remember with AP is that the AP protocol itself is pretty loose. Mastodon is one particular implementation of it, and doesn't even absolutely comply with the spec. Hence why some of the other server softwares have more features or slight incompatibility with Mastodon. So I'd be more inclined to believe that the oddities of conversation threading are in the Mastodon implementation rather than the AP spec itself.
Yes, some pendantry, but it means fixing it is down to one development team, not all Fediverse implementations.
-
@ticho @julian An important thing to remember with AP is that the AP protocol itself is pretty loose. Mastodon is one particular implementation of it, and doesn't even absolutely comply with the spec. Hence why some of the other server softwares have more features or slight incompatibility with Mastodon. So I'd be more inclined to believe that the oddities of conversation threading are in the Mastodon implementation rather than the AP spec itself.
Yes, some pendantry, but it means fixing it is down to one development team, not all Fediverse implementations.
@JessTheUnstill @julian Indeed. I started my earlier dive with AP docs, only to realize that they're too generic for what I'm looking for, and that I'm better off digging through Mastodon docs specifically to find details about timelines and conversations. :)
-
@JessTheUnstill I thought if you take out all the usernames it stops being part of that conversation? Good to know
@xanna no, the conversation ID is part of the post because you initiated it from a reply. The usernames just indicate who is allowed to see the post
-
@JessTheUnstill I do something similar to this, instead I add a poll to remind me of the post in X days. I wonder if it work with a mute? 🤔
@webhat wait, does a poll mute the conversation?
-
@JessTheUnstill
I know you're talking about the default web client, but for what it's worth, some clients do include this mute option.@xinit does it also give that option even in a conversation you've not commented on yet?
-
@xinit does it also give that option even in a conversation you've not commented on yet?
@xinit another question - if you mute it in fedilab, is the conversation still muted if you later go into a web UI or another device? Just curious how that's implemented.
-
@strypey Just checked Moshidon - you can mute from any post, but only in conversations you've posted in. Go try another post that you've not been in the conversation at all.
-
@webhat wait, does a poll mute the conversation?
@JessTheUnstill instead of muting it snoozes the conversation, however, combining it with a mute, won't create a timed mute. It's just muted outright
-
@JessTheUnstill @julian Indeed. I started my earlier dive with AP docs, only to realize that they're too generic for what I'm looking for, and that I'm better off digging through Mastodon docs specifically to find details about timelines and conversations. :)
ticho@mas.to jesstheunstill@infosec.exchange while I'm not working with the Mastodon team the folks at the ForumWG actually did start making inroads to solving this.
Latest Mastodon version should actually supply that conversation ID! It can even be resolved to retrieve all the replies in that entire thread.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@grahamperrin nice!
-
@francina1909 si, esatto
-
@shumann78
Oh Dio, vita da strega (Samantha) e strega per amore (Ginny) che cosa mi hai fatto ricordare 😍😍😍
-
@stefano_zan ne conosco solo 2 di questa lista
-
Person-focused:
― no boosts, no replies.
That's an example for @stefano alone. There are numerous other possibilities.
I should have thought of Fediwall a month ago, I had a mental block at the time:
-
@kristiana ahahahah vero. 😛
-
@francina1909
Ne ho un sacco e non saprei scegliere.
Le metto tutte (in ordine sparso). Scegliete voi! 😁
Il Prigioniero
Agente Speciale (The Avengers)
UFO
Spazio 1999
Thunderbird
Atrenti a Quei Due (The Persuaders)
Happy Days (oviusli!)
Mork e Mindy
The MonkeesSe poi contano gli sceneggiati italiani:
A Come Andromeda
Il Segno Del Comando
-
@clv0 I subscribed too.
