A lesser known Mastodon pro tip:
Uncategorized
32
Posts
12
Posters
2
Views
-
A lesser known Mastodon pro tip:
Want to mute a conversation, but the mute conversation button isn't appearing on the post?
The only way you can mute a conversation is on a post you have made in the conversation.
But the secret part - Say you want to mute it without actually participating in the conversation:
Reply to a post, set the visibility to "Private Mention", remove everyone's username from the post. Post it.
Then you can click "mute conversation" on THAT post, and it silently mutes you from the conversation.
@JessTheUnstill I thought if you take out all the usernames it stops being part of that conversation? Good to know
-
Now it allows you to mute conversation
jesstheunstill@infosec.exchange the inability to mute someone else's conversation seems to arbitrary. Maybe there's a technical reason behind it but there needn't be...
-
A lesser known Mastodon pro tip:
Want to mute a conversation, but the mute conversation button isn't appearing on the post?
The only way you can mute a conversation is on a post you have made in the conversation.
But the secret part - Say you want to mute it without actually participating in the conversation:
Reply to a post, set the visibility to "Private Mention", remove everyone's username from the post. Post it.
Then you can click "mute conversation" on THAT post, and it silently mutes you from the conversation.
@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? 🤔
-
A lesser known Mastodon pro tip:
Want to mute a conversation, but the mute conversation button isn't appearing on the post?
The only way you can mute a conversation is on a post you have made in the conversation.
But the secret part - Say you want to mute it without actually participating in the conversation:
Reply to a post, set the visibility to "Private Mention", remove everyone's username from the post. Post it.
Then you can click "mute conversation" on THAT post, and it silently mutes you from the conversation.
Is there some reason these steps cannot be automated, and exposed as a single control in the UI?
-
@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@infosec.exchange oh my god, using a poll as a hack for snoozing is genius
-
@julian thank you, I don't think I came up with it originally
-
RE: https://mastodon.social/@aslakr/109789888503839904
@julian @JessTheUnstill Muting/following conversation and sub-conversation (threads) is one of the things I miss from usenet.
-
Is there some reason these steps cannot be automated, and exposed as a single control in the UI?
@8r3n7 a 3rd party client could probably automate some sort of hidden meta-post, but no idea how fragile that might end up being. And yeah, Mastodon devs could build something to fix it, but I don't think it's on their roadmap anytime soon.
-
@julian @JessTheUnstill After a brief dive into the mastodon API documentation, it seems to be a protocol limitation indeed. You (or rather your client program) do not get to see the conversation ID until you join that conversation, so until then, you do not have the correct piece of information to request muting of that conversation.
Some references:
https://docs.joinmastodon.org/methods/timelines/#home
https://docs.joinmastodon.org/methods/conversations/#get -
A lesser known Mastodon pro tip:
Want to mute a conversation, but the mute conversation button isn't appearing on the post?
The only way you can mute a conversation is on a post you have made in the conversation.
But the secret part - Say you want to mute it without actually participating in the conversation:
Reply to a post, set the visibility to "Private Mention", remove everyone's username from the post. Post it.
Then you can click "mute conversation" on THAT post, and it silently mutes you from 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. -
@julian @JessTheUnstill After a brief dive into the mastodon API documentation, it seems to be a protocol limitation indeed. You (or rather your client program) do not get to see the conversation ID until you join that conversation, so until then, you do not have the correct piece of information to request muting of that conversation.
Some references:
https://docs.joinmastodon.org/methods/timelines/#home
https://docs.joinmastodon.org/methods/conversations/#getticho@mas.to hey, I sort of disagree. While the protocol itself doesn't contain topic level information, it can be inferred from context.
This is how NodeBB achieves it. It also sends contextual information so it's explicitly available as well.
-
undefined oblomov@sociale.network shared this topic
-
A lesser known Mastodon pro tip:
Want to mute a conversation, but the mute conversation button isn't appearing on the post?
The only way you can mute a conversation is on a post you have made in the conversation.
But the secret part - Say you want to mute it without actually participating in the conversation:
Reply to a post, set the visibility to "Private Mention", remove everyone's username from the post. Post it.
Then you can click "mute conversation" on THAT post, and it silently mutes you from the conversation.
@JessTheUnstill this is an exceptionally useful tip. It's also grotesque that it would be needed in the first place.
-
@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 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.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@aru when people start upgrading and other people say "nooo not yet!!!" 😆
-
@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
-
TIL about this wonderful post written about GNOME when they turned 25
GNOME started in Aug 15 1997
Whether you use GNOME actively or you use components of it {often without knowing it } the Open Source GUI landscape would look very different without the massive contribution of GNOME.
For me GNOME is very valuable.
I use critical components of GNOME in the different desktop environments I work with.
The Gnome components give my desktop environments consistency across the different GUI platforms I use.
Without those components my DEs would look and function dull, since the programmers of those environments would have to invent the wheel themselves time and time again
Thank you GNOME programmers
Keep on hacking...
-
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. 😛
