Post Avu2PtwObmx2W6sxI8 by buttplugio@buttplug.zone
(DIR) More posts by buttplugio@buttplug.zone
(DIR) Post #Avu2PsQoDk5fpr6DQ0 by buttplugio@buttplug.zone
2025-07-07T19:28:49Z
0 likes, 0 repeats
Wanna make random people on github mad?Deny them access to their penis tube pressure regulator.(There are valid reasons it's difficult to support the powerblow in @buttplugio but that don't stop people from posting like we owe them)https://github.com/buttplugio/buttplug/issues/578
(DIR) Post #Avu2PtwObmx2W6sxI8 by buttplugio@buttplug.zone
2025-07-07T21:24:04Z
1 likes, 0 repeats
Thanks to the powerblow situation, I have just created a new type of edging:Pull Request EdgingWho knew you could use github as a BDSM power play platform
(DIR) Post #Avu2oUcbsiFjEMMBfs by icedquinn@blob.cat
2025-07-07T21:47:52.262808Z
0 likes, 0 repeats
> there's no good fit for mapping the powerblow's commands to the current Buttplug commandweirdly reminds me of how CLAP handles versioning and sent 🧠off on a voyage about "just make something that works for this one thing now" placed behind a vendor specific URI and then come up with some careful common standard when there's enough real usage to do so.:neocat_googly: was gonna write a CLAP book once actually but ADHD out of it
(DIR) Post #Avu3gRJoNXkwciHuHA by Alex@boymilk.cafe
2025-07-07T21:57:38.024832Z
0 likes, 0 repeats
This isn't even a new type of edging, I've experienced it already, some FUCKING ASSHOLE opened a halfassed pull request to implement my favorite mtg card in the open source online client for it then never bothered to finish it so now he's in perpetual limbo because no one else is willing to touch a card someone's already started working on and is probably never going to actually be usable
(DIR) Post #Avu442Nckd5wECK6pk by icedquinn@blob.cat
2025-07-07T22:01:53.479608Z
0 likes, 0 repeats
@Alex I think a stalebot is acceptable for this situation. With the caveat that a CSR comes by and prods rather than it getting robo closed.Ive had to come back and close some of my own bug reports because nobody cared to follow up, but it has actually been fixed at some point, and it's a nicer overall vibe to be like "does anyone still have this problem" than, well, the alternatives.
(DIR) Post #Avu601c1rZk0b5H9Zw by Alex@boymilk.cafe
2025-07-07T22:23:34.986896Z
1 likes, 0 repeats
the issue with any fan made mtg client is that mtg releases new shit almost monthly, so if something isn't implemented right away, it just gets stuck on the eternal backlog of never ever being implemented. the release schedule is just so obscenely fast paced that no one can keep up with it, there's no time to finish implementing a set from two months ago when the set from last month is still a buggy mess that needs a tonne of patches before it's ready to publish and work on the current month's set hasn't even started and they're already starting previews of next month's set and what do you mean there's stuff from three years ago that still isn't in?
(DIR) Post #Avu6Hzcvz2NteUGbeS by icedquinn@blob.cat
2025-07-07T22:26:49.296208Z
0 likes, 0 repeats
@Alex i don't envy anyone who tries to support that game. i've taken a few skims over what goes in to that and its probably on par with trying to write a web browser :blabcat: i mean wotc has programmers who somehow do. i'm not sure if this is powered by indians + capital, or a genuinely clever solution with use of effects tracking and model based coding.
(DIR) Post #Avu7KK2LAgJ5U8pCvQ by icedquinn@blob.cat
2025-07-07T22:38:27.297150Z
0 likes, 0 repeats
@Alex i think my conclusion was you would have to use some horrible tag & model & maybe even a query engine of some kind in order for the problem to be tractable at all.i didn't try this but it would probably be worth an entire book if i did :blabcat:
(DIR) Post #AvuECG7kXBnyiESPho by Alex@boymilk.cafe
2025-07-07T23:55:26.160101Z
0 likes, 0 repeats
yeah it seems like an absolute nightmare. volume of product has only been going up, too, making it even worse. no idea how they even manage to keep arena running.