jdev - 2023-06-16

About Message Moderation

there is a paragraph about MAM Tomestones

and i wonder why would that be important for me as client?

what can i not do if i simply drop all tombstones?

is it just so i can show the user that something was moderated?

i think its ok to show the user something was moderated if he already saw the message maybe

but if we talk about messages that the user did not even see, thats the case when i receive a tombstone via MAM .. how useful is it to tell someone that something was moderated

Yes, it's so you have the option to show that something was moderated

I like this because otherwise you get a history full of people reacting to something that isn't there

but it is not there

you can not show to what they reacted ..

but yeah .. i just wonder if a spammer spams your channel

and moderator removes all

and you show the user still 50 messages but all "moderated" ..

You can show they reacted to "something worth moderating"

What do you do with messages locally when they are moderated?

set a flag that they are moderated

So I would suggest creating an otherwise empty message entry with the moderated flag already set.

with content that gets moderated after i downloaded it, i can at least show the user what was moderated if he wishes

but with tombstones, its just ok someone moderated something

yup

but yeah .. maybe i should do it like that

Zash if i have you here, the occupant-id thing is independent of anon setting for muc right?

in prosody?

No please tell me for all server implementations in the world :D

yes, for prosody

independent, yes

ok great, i hope nobody gets a horrible idea and does it only for anon mucs

is the XEP silent or unclear?

If 20 messages are moderated in a row, it would be great if the client would just show one message, telling that once or something

pretty sure you also get a second message with the moderation action itself

in the (far) future with a fastening collation ready database schema, we could probably do fancier things

like show moderated original messages to moderators

but now it's just overwritten

im really scared about collation

i hope this does not break all assumptions

i definitly would not do it for something like retraction or moderation

its so rare events in the grand scheme of things, that it makes more work than gain

my thought was essentially that each message would need its own archive, per type of thing

stuff like chatstates / markers, are a much better target

so [user@host][store][stanza-id][class][number]

hm can this be efficiently queried via MAM then? if you have multiple tables (archives) i guess?

We only have two tables right now, one for key-value stuff (most account data) and one for _ordered_ key-value stuff (archives, offline messages, pep items)

i think i found something problematic

https://xmpp.org/extensions/xep-0425.html

if occupant-id is supported

it is included in the tombstone <moderated> element

so i guess to id the occupant who moderated the message

the same occupant-id is not included in the <moderated> element if you receive it from the MUC live

and because the moderated live message comes from the bare room jid

i guess the server would not include *any* occupant-id

not even outside of the <moderated> element

oversight?

Is there a place where MUC log retention time is exposed?

I don't think so

Could be done easily enough I guess? Somewhere in disco just like other config options? As an "unsigned int or infinite"?

seconds or days?

https://en.wikipedia.org/wiki/ISO_8601#Durations is a thing, but I don't think we use it anywhere

Seconds I guess, but whatever people want really ✏