cassie 🐺

Best description of this I’ve read, thank you. It’s not a question about men directly, it’s a question about how women have to navigate a world with a small percentage of men that will hurt them given the opportunity.

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.

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.

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 heard there’s a holy yellow sky / Just make sure you close your eyes

Do you know who ate all the function candidates?

If it were up to me I’d be avoiding templates altogether. Sadly, I don’t get that choice with 3rd party code.

I love gcc but it can’t make nested template errors any less horrifying