Open jesopo opened 1 year ago
I've been implementing this in my clients with the network operator stuff already in the protocol.
on second thoughts, I think I'd prefer to do it on a message-by-message basis. staff don't really want a badge on 24/7
Would a message-by-message thing be the same as the oper
tag in https://github.com/ircv3/ircv3-specifications/pull/494?
A message-per-message tag wouldn't allow clients to display an indicator outside of a message context (for instance, on a user info page). The information would get out-of-date until the staff sends a new message visible to the client.
The network operator in the current spec can be toggled on/off as desired.
I'd intend the visual indication to be shown on the message, not the user
consider this to how, on reddit, you can select whether you're speaking as a user or a mod
and, as for the oper tag, maybe libera just needs to start sending that to users... scratch that, can't easily turn it on and off without deopering
How is this any different to ircv3/ircv3-specifications#494?
The draft/oper
tag spec says it is added "to messages sent by a user who is currently an IRC operator". That doesn't seem to allow the intent expressed by @jesopo, to have this annotation attached only on-demand by the user speaking, a la reddit's "speaking as a mod" function that badges only specific comments when the user posting them chooses to do so.
i guess this is sort of a verified checkmark. no idea how I'd go about implementing this, other than
metadata
once we finish it.primary intended usecases is clearly visually denoting services bots and network staff in a way you cannot impersonate.