Have a lot of custom/personal emojis and want to keep track of them? lemmy-emojis just got support for that! (It's exactly as janky as the rest of the extension.) Btw, if you only want to use the extention to keep track of your own emojis and don't want to have emojis from some lemmy instance, clearing the domain setting (and turning off "update automatically," since it is unnecessary) will let you do that

Don't know what lemmy-emojis is? It's for you, the non-hexbear that want's to use hexbear's emojis. Or if you want to use dbzer0's, or some third instance. It let's you do that.

ⓘ This user is suspected of being a cat. Please report any suspicious behavior.

you are viewing a single comment's thread
view the rest of the comments

[–] edie@lemmy.encryptionin.space 3 points 15 hours ago* (last edited 13 hours ago) (1 children)

The problem is figuring out how to display it. Fetching the list and changing it's structure (which was necessary in my extension) is pretty easy. Storing stuff too. Personal emojis could potentially just be a list hard-coded into the script... But getting it displayed... that's not quite as easy. If I knew how to do it I might take a shot.

Edit: that thing where you start out looking at the code for an AO3 y/n userscript and end up reading smut...

ⓘ This user is suspected of being a cat. Please report any suspicious behavior.

[–] Trying2KnowMyself@hexbear.net 2 points 3 hours ago

Some general thoughts after poking around at it a bit + prior userscripts experience:

userscripts modify the page, so displaying it would mean inserting it somewhere on the site rather than having an extension button to show it - that leaves two possible routes: replace the emoji picker on input boxes, or throw it somewhere common like the site header
if options are not hard coded, they would similarly need to be rendered somewhere to support config changes - hard coded would be an easier starting point to get the rest of it working
throwing it somewhere common is probably easier, because the general approach I’ve seen/used previously is that you create a promise that loops trying to select a known element with a setTimeout some number of times, and appends/prepends the desired element to the container it finds
getting it to replace the built in picker would probably require first using that approach to attach event listeners to reply buttons and then using the events to trigger the replacement behaviour when someone starts to comment + additional handling for the create post page
best practice for userscripts is to restrict the URLs they run on - something that potentially runs on your bank website is much more concerning than something that only runs on one site, but it’d be difficult to limit it appropriately enough while still listing/supporting most instances
some userscripts will also intercept network calls by overriding methods on XMLHttpRequest.prototype and attaching load event listeners when the path matches, though I’ve mostly seen/used this in the context of wanting to capture the results to do other things with them - if that or similar could instead be used to augment the emojis response, then that could allow additional data to be added to the existing picker without replacing it

I’ll probably take another look at things later, but figured I’d share my thoughts so far.