@mer honestly if I was building my own I’d see if I could just use switches instead of triggers and have it register as going to 100% pressed immediately; I’m not playing racing games or whatever anyway and in the ones I like the triggers are just pointless delays to whatever action is bound there :akko_wtf:
@mer I’m used to the xbox layout :akko_shrug: And I’m not sure if I want to get into DIY, it’s just that my current pad is starting to shit itself while I’m playing dark souls and I’m massively overthinking getting a replacement.
I could buy an used Thrustmaster eSwap for the price of a new Xbox controller; I usually prefer to buy new things and use them until they break (and if it’s used I don’t know how badly was it treated by the previous owner), but this one has replaceable parts, so if a stick breaks or something it’s not the end of the world.
Unfortunately, from what I read online it looks like it’s not supported on anything other than Windows; meanwhile Xbox controllers work fine on Linux and Mac.
It continues to amaze me that if you want something to work on a non-Windows platform then hardware made by Microsoft is usually a safer bet :cirno_for_reals:
How hard would it be to just buy the Thrustmaster sticks, some mechanical switches, 3d print the chassis, and hack together my own controller with blackjack and hookers :ablobfoxhyper:
@nyoom@Arcana@icedquinn I unironically think that the tolkien bot and the trump bot are better conversation partners than some of the people on this fedded verse, and I think the first one is just a markov chain :cirno_for_reals:
QBE seems a lot more understandable https://c9x.me/compile/doc/il.html Though it’s a bummer that there aren’t any atomic and vector instructions (?) It’s not like I need any of that right now, but it bugs me that if I start with QBE I’m going to hit a ceiling sooner or later. Maybe it would be easy to move to LLVM later since it’s also SSA, or maybe even contribute some code to QBE myself? I don’t have anything to test the risc64 backend though.
I should probably start actually doing something instead of screwing around and poring over possibilities.
@mer@Ukko@40@bl00d I admit I don’t have any experience, but I’m not sure why would anyone expect any sex differences in the first place? It doesn’t seem to work like that with nonhuman animals, unless I’m an unrefined pleb who can’t tell the difference.
@bl00d@Ukko@40 ah right, that was a different thread than the one with mer, that was on my previous instance and bl00d wasn't involved, I mixed it up as I posted the same ellen degeneres salami article.
@eris@winter Eh, centralized services have some benefits. They can have blocks (not just mutes) that work without being published to third parties, thorough deletion of posts, private posts that won't be automatically converted to public by someone, for better ir worse also control API access, etc. Of course, that depends on the admins not being malicious or incompetent, but at least there's fewer of them (though in any case screenshots exist).
ActivityPub bugs me in that for a users who aren't tech savvy it's hard to tell which features are actually enforced, which are at best speed bumps for a dedicated attacker, and what are just customs created by yelling loudly. People may click "block" not understanding that by necessity (well, I delibrately disabled it on my server, but I don't think it's a popular choice) it sends a `Block` activity to the recipients server which may do with that whatever it wants. Or get horrified when they find out soneone runs a ConvertNonDirectToPublic MRF.
And even before malice there's always plenty of bugs, like deletes not federating properly, blocks not working on dotsocial sometimes where it's probably not on purpose, etc.
I think there are tradeoffs, and while I ultimately prefer fedi, it's not nice when people shill decentralized services without mentioning any of those, and also throw schadenfreude parties when centralized ones like Cohost fold.