if your response to seeing any antizionist Jew is to call them a token, that's so shitty. Jews can have their own opinions. the sages wrote a whole 20 volume book of arguments, and now you expect Jews to toe a party line to be valid? Jews can even argue with G-d, what authority do you think you or the state of Israel really have?
Once you start running community "safety" tools, you invite public discourse. If you can't receive criticism without claiming to be a victim of harassment, then you aren't capable of running those tools. True community safety tools should be run without hierarchy and without restriction for those who can contribute.
You can't be both cop and victim. Ask yourself why you're bleeding out patreon supporters and why people are more and more hesitant to support your project. You can only cry wolf so much before people notice you're the wolf.
@sun_eat3r to be fair most black people think he's a twat, like on Bluesky and Twitter they make fun of him and use him as an example of why fedi sucks.
today's TME discourse is basically "transfemmes need to shut up and make space for the real victims of transmisogyny, which is everyone who isn't a transfemme"
So, I wrote the first thing for Balormo's backend tonight. I wanted to do dice rolls, or really RNG (random number generation) broadly, and in this case I wrote the simplest form of it in the TTRPG space: rolling XdY, take the sum.
I did not write an FE for this yet. That's because I want to discuss the way I designed it. Now would be the time to refactor things or change around how it's structured. This is backend proof of concept phase.
For the time being, you can use curl to try it out once you have an account on dev.iddqd.social:
curl -X POST "https://dev.iddqd.social/api/v1/statuses"
-H "Authorization: Bearer REDACTED"
-H "Content-Type: multipart/form-data"
-F "status=Rolling CON for AD&D 2e style"
-F "source=Pleroma FE"
-F "visibility=public"
-F "content_type=text/plain"
-F "balormo[rng][system]=dice_sum"
-F "balormo[rng][denomination]=6"
-F "balormo[rng][quantity]=3"
Unfortunately, Soapbox and Pleroma seem to drop the balormo object in federation. However, quite fortunately, it delivers the Object URL, which does retain that information:
The way I wrote this is you just add more fields to the /api/v1/statuses endpoint and give it extra fields. In this case, the system field can be changed and the pattern matching will pick up on the right one and then generate dice rolls etc in the right fashion. For example, I might write a Shadowrun dice roller that rolls d6s given only a pool value and re-rolls 6s until you don't get anymore.
The reason to bake this into the protocol is so that you can manage the data better and change the way it's displayed in the future. The appended roll text to the status will be put in a <div> with a class on it that's invisible for the FE.
Thoughts on how to improve this before I move on to the FE?