æʃliŋ, purrepurrocessor @aescling@cat.family

@amy -bonk-

@coriander when the

when the elfstrogen

@coriander elfstrogenated

@Packbat oh wait no i furgot, custom emoji are always tagged in a post by the backend (statuses are serialized to the client alongside the info necessary to replace all custom emojim with their assoicated images), so there is definitely a step where you have all the emojim that the status have available to check, so making sure you do this right should be easy

@Packbat custom emoji are really just :single_words_between_colons: so the only maybe tricky part is making sure the instance actually has an emojo fur any instance of a :single_word_between_colons: (you don't want to allow such text to pass through otherwise, you know?)

@Packbat i am assuming doing such a check is easy ofc but i can't imagine it wouldn't be

@Packbat yeah you'd just add a validation step in PostStatusService.call and the logic fur that---while i couldn't write right now off the top of my head---should be pretty simple. you might need a unicode/emoji library

if you look at fur example, PostStatusService.validate_media!, invoked at line 43, defined here, it just throws Mastodon::ValidationErrors (implicitly forcing post creation to fail) as required; you'd just do a check fur whether there’s a non-emoji and throw as needed

@Packbat i am near certain it would be simple to patch mastodon (upstream or not) to maintain such a restriction

@jinxies what's the diffurence tbh

@monorail nice.

@chr unselect is honestly such a pawerful option though

@wallhackio i can really allow that if you want.................

@wallhackio this is configurable by setting environment variables; i can make it even larger here if you wanted

i cannot guarantee that all remote instances or mastodon-compatible clients will actually see every poll option, however

@coriander @amy lmao

@wallhackio @alyssa lmao