Looks to me like a bunch of satirical rhetoric aimed at yet another fedi character who cannot for the life of them just communicate and resolve conflicts normally. Have you tried not being a faggot?
That's basically my policy, but be warned apparently a supposed Eris alt here trying to just start a conversation with Moon was enough to get us defederated from SP.C, be warned tranny jannyism knows no bounds and this could happn to you. Of course, my suggestion would be to change nothing.
the real reason Graf wouldn't recommend it is he's wanted KF.cc defedded for AGES (due to how they make his podcast race paypigs eternally mald) and yet couldn't just because the optics of cutting out the next largest instance on this side of the fedi would've affirmed every negative opinion people have of the way this FtM nigga does things
when I add emoji to the json, I go and insert the emoji into a post and then copy and paste the rendered emoji into the json as represented in our list
Web standard only for now with this set up. Customs can be accomplished through further tinkering with the source but I haven't done it myself and won't because I think it sorta just edges towards feature bloat and could harm some compatibility with other instances.
Ah, you're doing what I did before when I made sloppy one-off adjustments, which is browsing the CSS that's minified in the built version of Soapbox on your server. It's possible to change things there but it won't persist through updates. What you need to do is basically fork the repo of the Soapbox version you use, find the file I posted and make the same adjustments to it in the source, and then build from the branch you committed your edits to yourself. There's instructions for building Soapbox manually for production in the readme, but later or whenever I'm free I can walk you through it more thoroughly if it's confusing. I needed one of my guys to help me make sense of it since I had little experience with node/yarn/etc. myself.
just get your admin to make this one weird change to the emoji selector CSS (values of course can be fiddled with to determine things like row length) and you too can have this power
should work on pretty much any version of soapbox I think since this stuff has been the same across versions--for instance, our current fork is using the old 2.0 version since we need to fix a lot of other stuff to make 3.0 not retarded (or we'll just backport 3.0 stuff like edits to 2.0 lol)
The changes just control the CSS related to the emojis reaction selector to let you fit many more emojis nicely, however to set the emojis within, you do it from the soapbox config json (which can be accessed via the "Soapbox config" link on the lower right of the soapbox UI on desktop to do it in-client) and just manually add them there.
someone said they were having QP visibility issues from certain other pleroma instances (as in, even the MRF replacement text/link wasn't being done right), testing to see what's going on and if maybe it's a new bit of hostile de-featurization from the trannies working on base pleroma or w/e