Lol. The knee-jerk contrarianism online really gets under my skin, especially when it's towards experts.

Like yeah, sometimes experts are wrong or systems don't behave as expected. But framing that as some sort of erudite insight really bugs me.

"I hope the recovery system works!" doesn't need to be rewritten as "Mmm yes. But what these engineers haven't considered is the possibility that they are wrong".

In a meme? Never.

Crowd extensions are already pretty common with traditional VFX techniques.

I worked in Hollywood editorial for a bit and, IMO, the producers are playing up the AI stuff so that said stuff can be given to the writers and actors as a "victory" instead of the real spectres in the room:

• streaming residuals need to get the same payout and transparency as home video and syndication did

• streaming numbers need to be made available to creators to facilitate the above.

• the 'mini-room' system that totally disconnects writers from the productions they are writing for needs to be broken down.

Definitely a case of "task failed successfully" though, because we cultivate those planets -- making their continued survival all but ensured.

Agreed, I grew up in a very conservative area and was pretty homophobic when I started college.

"They can do whatever they want, just don't ask me to like it" was an important stepping stone towards "oh shit, love is love" and finally actually listening to the experience of gay people.

A lot (all) nuclear accidents also occurred with older reactor designs.

Traditional nuclear reactors were designed in such a way that they required management to keep the reaction from running away. The reaction itself was self-sustaining and therefore the had to be actively moderated to stay inside safe conditions. If something broke, or was mis-managed, the reaction had a chance of continuing to grow out of control. That's called a melt-down.

As an imperfect analogy, older reactors were water towers. The machinery is keeping the water in an unstable state, and a failure means it comes crashing down to earth

Newer reactrs are designed so they they require active management to keep the reaction going. The reaction isn't self-sustaining, and requires outside power to maintain. If something breaks or is mismanaged, the reaction stops and the whole thing shuts down. That means they can't melt down.

As an imperfect analogy, newer reactors are water pumps. If power is interrupted nothing breaks catastrophically, water just stops moving.

Console exclusives are anti consumer and it should be illegal for console makers to offer any incentive to developers -- including studios they own -- to make a game exclusive.

Thank you for coming to my Ted Talk

As much as I think he could have handled the transition a little more gracefully, it's good to see an open source maintainer recognizing when they are no longer making their life better by working on a project.

So many open source devs burn themselves out by continuing to work on projects that no longer spark joy out of a sense of obligation.

This also should be a reminder to the community NOT to harass devs if a project is making choices you don't agree with. The reason most maintainers contribute to open source is the hope that people will like and use their software. Getting messages that indicate people don't like their work and won't use their software is the quickest way to kill someone's enthusiasm for their little corner of FOSS.

I think I have a bead on what you're saying now.

I can't really say I agree that gently supporting someone to explore a side of themselves they are coming to grips with is the same as advocating for the eradication of trans people...

I'm curious if you have examples given that seems pretty against what I've seen of Beehaw so far.

Not saying you're wrong, it's just not something I've seen yet.

Although this user is kinda huffing their own farts, I think they are speaking to something that needs to get solved in the long term.

If you make an account on an instance, create a bunch of posts and comments, then your instance makes a choice you totally disagree with... It's easy for everyone to say just leave and find another instance, but leaving that history and effort behind kinda sucks. Even if you're not at the mercy of an instance's admins, your account is.

Lemmy/Kbin really need a mechanism to migrate an account so users are totally free to find their own home, and client apps need a way to transparently mix content from different accounts so you can join two instances that have de-federated from each other. Again, it's easy to say you just need to make an account on each, but the UX of doing so is terrible.

IDK, the creator of that instance just started it as a little side project. I don't get the sense they ever really expected for it to blow up or were trying to make it a "main instance".

If anything this is just a reminder that instances aren't nodes in the same service. They will all have their own culture, goals and philosophy.