eupraxia

Sure, but broadly reducing red meat consumption is a pretty good idea for a lot of reasons. I think you're acknowledging this re: factory beef farms, but I think it's important to call out and also to note that a like 80% plant-based diet can be nutritionally complete, not ridiculously expensive, and more sustainable.

Hmm... usually I prefer push-in 😇

Gotta say I'm glad we can be and date any genders we like these days with much milder pushback (on average) than used to be the case. Really does help zoomers be a lot healthier imo, even if we've got other issues in the internet age.

That's been my experience with GPT - every answer Is a hallucination to some extent, so nearly every answer I receive is inaccurate in some ways. However, the same applies if I was asking a human colleague unfamiliar with a particular system to help me debug something - their answers will be quite inaccurate too, but I'm not expecting them to be accurate, just to have helpful suggestions of things to try.

I still prefer the human colleague in most situations, but if that's not possible or convenient GPT sometimes at least gets me on the right path.

they had to change the motto because it got too cumbersome to set up the drum machines when they wanted to say AUDIOOOOOOOOOOOOOOOOOOO [synth riffage] VIIIDEO DISCOOOOOOOOOO

ooh I fell in love with Taking Water by Billy Strings a day or two ago and it's been in my head since

While this is true to an extent, from experience this line of thinking has its limits and is very easy to misapply. On the one hand, yes you can tell people their ideas do not gel with the vision of the project, and sometimes that's the right call. And sometimes doing this a lot is best for the project.

On the other hand, even if a majority of the work is coming from one person, not only does your community learn your project, they also spend time contributing to it, fixing bugs, and helping other people. I feel it's only to a project's benefit to honor them and take difficult suggestions seriously, and get to the root of why those suggestions are coming up. Otherwise you risk pissing off your contributors, who I feel have the right to be annoyed at you and maybe post evangelion themed vent blog posts if you consistently shut down contributors' needs and fail to adapt to what your users actually want out of your software. And forking, while freeing and playing to the idea of freedom of choice, also splits your userbase and contributors and makes both parties worse off. It really depends on the project, but it pays to maintain buy-in and trust from people who care enough to meaningfully contribute to your project.

bark-to-text, of course!

Ironically this is one of those things that's easier to deal with in a poly context - your partner isn't your one and only so if they're ace and you're not, you're allowed to get those needs met elsewhere and still have a loving romantic relationship with them.

I've attempted to do public-facing technical support for a game and dear Christ you're spot on. I love people for wanting to engage with something I've spent a substantial part of my life putting together and trying to make it run okay, and am sympathetic to people feeling frustrated when technical issues prevent them from fully enjoying an early access game. Early on when the community was small I had a great time shitposting with the players, but once we hit release the environment turned toxic pretty much overnight as the community suddenly grew.

But like, none of them know how hard we crunched to get even a playable version of the game out, nevermind one that's playable on the lowest of netbook specs. None of em know how complicated the system is that's breaking preventing them from logging in, that that's not actually my area of expertise and that I'm just feeding them information from the matchmaking team who are all freaking the fuck out because this is the first time we've tested this shit at scale. None of them know that we were getting squeezed by our publisher, who wanted us to do a progression wipe that we didn't want ourselves, but like they control if the game gets shipped at all so... not really a choice there. And we can't admit any of this because accusations of incompetence come out pretty early, tend to stick around, and leave devs very little room to make bad decisions (which happens a lot!)

And like, being trans now on top of that? Hell no, I'm never touching a public server again if I can help it. Slurs and mistrust were already flying before, I can't throw myself in front of that bus again. I'm gonna miss it because I cared a lot about connecting with people playing the game and for a while found a lot of joy in responding to bugs and fixing individual system issues and integrating into the community. And there were some amazing people who were great to talk to that I really missed when I left. But the inherent abuse that comes with that gets so overwhelming and it drained my desire to even work on games at all for quite a while.

To be fair, Bluesky does have "blocklists" maintained by other users that you can opt into, and quite a few popular ones exist with active maintainers who take and act on reports pretty quickly. So you still can delegate moderation responsibilities. One advantage to this is that you can opt into a few blocklists based on what you personally want to block - separate lists exist for hateful bigots, crypto pushers, and so on. I gave it a shot out of curiosity and haven't run into any issues yet, but that's just me.

I still prefer Mastodon for broader AP integration, and I think blocklists aren't discoverable enough outside of word of mouth, but I am curious to see how that turns out for Bluesky. Certainly an improvement over Xitter imo.

I forgor 💀