Sorunome
Sorunome
mx-puppet-bridge now supports sending these
> What about adding a mandatory level of pack indirection ? > > `im.ponies.room_emotes` would only contains something like: > > ``` > { > "packs": ["im.ponies.room_emotes.mypack1", "im.ponies.room_emotes.mypack2"] > }...
> how hard would it be to add versioning and uuids to emoji packs > like for example if i'm in a room with a sticker pack that matches the...
> and i don't see how any of this is affected by it being in a room or a user account `emote_rooms` is where you say that you want emotes...
Like, maybe the uuid and versioning stuff could be added in a separate msc building onto this - the goal of this was to keep things as simple as possible
> state events have timestamps right, so you could just use the newest state event instead of bothering with version numbers origin_server_ts can't be trusted and can easily be forged...
> oh you could just put a modified tag in then with like unixtime or something In a federated system there is no one true timesource. That is a mathematically...
Changed the format from ``` { "short": { ":emote:": "mxc://blah/blubb" } } ``` to ``` { "emoticons": { ":emote": { "url": "mxc://blah/blubb" } } } ```
Updated the MSC to 1. include stickers (`usage` parameter) 2. change shortcodes from `:emote:` to `emote`, the client can wrap in `:` or `()` or whatever it wants to 3....
Added now to also suggest image packs in claimed parents (`m.space.parent`)