Interesting, I like it. I do think the cards need rounded corners, and I wonder how it would look if the background for that dialog was purple. It might also make sense to remove the collapse…
Oh, dang. I had to clean up a bunch of spam profiles but removed some inactive accounts too. I didn't realize uploads would get dropped too.
leading-none clips letters than hang down, like g
Numbered posts won't be reliable because events can always get backdated or republished. We should just change this to [link icon] permalink or something.
You can do pushToMapKey(byRoom, h, event)
Or even const byRoom = groupBy(e => getTagValue("h", e.tags))
This seems like it would vary. Why not sort lexically by room name?
Similar to how chat replies work, let's prepend the compose input with a quote of the event the user clicked reply on.
I feel like we should not replace state, but I'm not sure.
This actually changes how threads work and doesn't follow the spec. Replies must always refer to the root kind 11, not the comments. Replies to comments should be done the same way as chat replies — use q and embed the parent in the quote reply. This matches how old forums used to work too.
Also, let's do base/nevent. We can then rely on goToEvent in routes.ts. This will be easier for other clients to parse as well if they want to.