And just like DEI teams, ethics teams will be easy to cut back on if a company runs into economic trouble.

Sure, no argument there. There’s a choice to be made between “post the second story as a comment to the first one” and “post the second story a a separate topic”. I’m in favor of the first approach to keep discussion in one spot, but it’s not something I feel super-strongly about.

Avoiding dupes is, I think, an important one. We’ve had multiple instances on Beehaw of the same story showing up more than once. If you try to post a duplicate link, Lemmy will let you know (by showing the previous copies to you as crossposts). It’s harder to make sure you’re not posting the second or third story from a different source on the same topic. Perhaps we can just encourage people to search before posting.

I’d like the rules to at least ask people to add an image description in their original post. https://beehaw.org/post/686974 would be good to link to here.

And given the nature of many posts in the news, I think it would be good for this community to remind people to be(e) nice in their discussions.

Clearly someone needs to figure out how to get an old Furby to interact with a new Furby.

(Of course, someone has already done ChatGPT + Furby)

I’m pretty sure that discovering a new isotope while working on your MS guarantees that you’ll get the degree.

In my opinion it’s unreasonable to think anything can truly be deleted in a federated system. Even if the official codebase is updated to do complete deletion & overwrite, it’s impossible to prevent some bad actor from federating in a fork that just ignores deletion requests.

Seems sensible to just not post anything that you don’t want to be available for the lifetime of the internet.