Proposal: non-notifying mentions #118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Here's an idea - being able to mention user without notifying them while also avoiding cumbersome to/cc/bcc fields:
use
@!for mentions, i.e.@!hj@post.ebin.clubsupported software/versions will convert it to mention link with class "silent" while unsupported version just leave it as plaintext, avoiding accidental notifications
@lambadalambda @feld @lanodan what do you think of this?
Not entirely sure on this one… like what would be the use case? Soft-untagging from a thread maybe?
Also would probably be messy in terms of federation due to normalization comparable to our Transmogrifier, like reminds me of how weird Friendica's CCs can get.
And on the negative social side, I guess it would be as bad as pasting the URL of the account?
It would be useful in DMs to not accidentally inviting third party into the thread
Ah, pretty different from how I understood it, so mention but doesn't do a CC/BCC?
And could be neat but syntax wise it seems like an easy typo away from making a normal mention (fine for a CC/BCC, nasty for DMs).
Yes. Proposed syntax is such that if you intended to write a non-mention on unsupported backend (I.e. someone on mastodon trying to copy it) it would not end up mentioning and just end up with plain text
We do have this setting under :instance
I think this approach is less intuitive and it's hard to learn and easy to forget whether this option is enabled or not, plus not usea-configurable. It also adds confusion to receiving user if they are on instance that doesn't support it or has it disabled.
Overall custom syntax seem less dangerous and more intuitive.
I don't think it works to prevent accidental mentions. It's already possible to prevent mentioning a user by simply not adding an @ in front of the name. Similarly, a user would have to explicitly remember the @! syntax, it would do nothing to prevent them from accidentally mentioning someone because they use the same @ syntax they always use.
hmm, i think you're right
I think being able to generate a link to a user without mentioning them or pasting long url would still be beneficial. Over time people might learn how to use it when they see others use it.
Either way, I just think it would nice to have, not a priority. Feel free to dismiss it.
It is possible to achieve that effect by using the
tooption, see https://docs.pleroma.social/backend/development/API/differences_in_mastoapi_responses/#post-apiv1statuses, although that needs some serious frontend support.I think having
to:field is intrusive in context of micro-blogging, less compatible and confusing for mastodon and other front-end users.Having custom syntax is less intrusive - just remember new syntax, just like it would be with gropus - just use
!bankyAs for compatibility, here's a flow for both cases
to:field orsafe_dm_mentions@!syntax@!syntaxOr:
@!syntax@!syntaxGood point.
How hard would it be to implement it? We could run a experiment and if people complain we'll just remove it