@t@hexa.ninja looks like the "@" was already added upstream, reverted on my branch now. thanks!😄

@synace@blog.synace.com about the "@" it was a small regression that was introduced while adding support for vanity/webfinger domains support 😅

@t@hexa.ninja Thoughts on some of my tweaks?❓😇

@synace@blog.synace.com for the emoji picker, it won't make it upstream as we try to keep the JS usage as minimal as possible.

And for the "with replies" section, if more people ask for it, maybe it can be an option at some point, but for now you're the first person that wanted it.

@t@hexa.ninja Yeah, I didn't anticipate anything being merged upstream, just curious if you wanted me to put together a cleaner branch of anything to do so. The emoji picker is so-so, but I wanted to be able to plop in unicode emoji quickly rather than image based emoji. I'd really prefer a live markdown editor with preview and autocompletion of :smile: when typing.

@t@hexa.ninja Has anyone put in a ticket to support @t in the replys to a current thread. Or, even on a new post with a particular markdown format, unless that's already a thing? It's feeling pretty comfortable here now. Thanks for the software!

@synace@blog.synace.com I think it makes sense for a single-user instance to always use the full handle, and when you reply/or click mention the handles are pre-filled. So I don't think it's a big deal.

And thanks!

@t@hexa.ninja Gotcha. My concern was that when my notes show up on other instances, they wouldn't be clickable/linked if I just used the username portion. Obviously, there'd be an issue with the current implementation of just parsing the username from the raw post content, and it'd require context to know which user to link to, (in the case of duplicates for example). So, some markdown style syntax sugar would be needed, e.g. something like:

  [@t](@t@hexa.ninja)

~Cheers