(Edit: To be clear, I’m not a current dev on this project)
I believe point 1 is custom behavior and point 2 is just a matter of adding a markdown rule but I’m not 100% sure. I believe the emojis repo has a normalized copy of each emoji that could theoretically be downloaded and used like a sticker pack by mobile app users or just uploaded manually, even elsewhere. But an actual sticker pack feature on the app would be a neat and fun feature. As for the thing about showing the legacy emojis to other servers, I’d imagine that involve regex ing every single comment ever sent with a custom list of hard coded emojis and URLs, which is kinda messy, especially for server-to-server federation endpoints
Yeah, good point about it being messy, and I also wonder about performance. But if the hexbear frontend is already doing this text replacement when generating the html, then it must already be a solved problem? Would need to crack open the code to see how it was implemented
(Edit: To be clear, I’m not a current dev on this project)
I believe point 1 is custom behavior and point 2 is just a matter of adding a markdown rule but I’m not 100% sure. I believe the emojis repo has a normalized copy of each emoji that could theoretically be downloaded and used like a sticker pack by mobile app users or just uploaded manually, even elsewhere. But an actual sticker pack feature on the app would be a neat and fun feature. As for the thing about showing the legacy emojis to other servers, I’d imagine that involve regex ing every single comment ever sent with a custom list of hard coded emojis and URLs, which is kinda messy, especially for server-to-server federation endpoints
Yeah, good point about it being messy, and I also wonder about performance. But if the hexbear frontend is already doing this text replacement when generating the html, then it must already be a solved problem? Would need to crack open the code to see how it was implemented
Should be part of the markdown renderer