jdev - 2026-02-10

Is XEP-0503 actually used anywhere at this point?

it's not clear to me how I would even tell that a node is a space

no, currently that service is unavailable

> rewriting history is generally frowned upon by nerds like us xD i think editing is fine as long as you can show edit history. i dislike apps eating the original version or allowing deletion without a trace ↺

(i.e. the client should at least show _This message was retracted._) ✏

> Ease of implementation especially in the pre mam world singpolyma, would you wager that its safe to edit older messages nowadays? ↺

jjj333_p (any pronouns): it's still pretty confusing; and for someone on a non-MAM client like Profanity, it'd show up as a new message out of sequence

would it make sense to try to fallback it somehow? like ive seen imessage do `Corrected "original message" to "new message".` on older iphones

ive not recently looked at the spec (im getting ready for class/work, dont have much time) so i dont know how reasonable that is

The body of the edit message _is_ the new version of the message, so a traditional fallback wouldn't work

but a client could at least tell the user that it's supposed to be an edit

> The body of the edit message _is_ the new version of the message, so a traditional fallback wouldn't work i was wondering if you could use the fallback ranges to remove a portion though ↺

in theory, but that would mean that existing clients would include that text in the edited message

hm true

make a new xep 🧌

>> Ease of implementation especially in the pre mam world > singpolyma, would you wager that its safe to edit older messages nowadays? My apps all all the user to do it so that shows you my wager ↺

My new apps also store edit history