I could see walking through a debug session document with a junior dev to guide them on how to debug classes of issues better. Or if they're running into a bug and ask for your help, you could write out the first few debugging steps and let them take it from there. That might be easier to understand than "I'd check service X and see if it's processing Y like it should or just passing it on to Z". Having a defined way to explain how to debug an issue could be useful

that looks like a console

Not just looks, but provides the UX of a console. So you buy it, plug it up, log in, and immediately start playing. Even consoles don't provide that streamlined UX anymore, but ppl want all the benefits console used to provide with all the benefits PC gaming provides now. But the key part is the PC benefits don't get in the way of the ease of it. You don't have to install or administer a linux distro, you don't have to twiddle settings for every game (unless you want to), etc

This issue has been noted since mastodon was initially release > 7 years ago. It has also been filed multiple times over the years, indicating that previous small "fixes" for it haven't fully fixed the issue.

Harvesting the dataset isn't the problem. Using copyrighted work in a paid product is the problem. Individuals could still train their own models for personal use

yes exactly what sneezycat said. I was being sarcastic and pointing out that Manifest V3 was always a crackdown on ad blocking and nothing else.

It's funny how this comes after Chrome's switch to Manifest V3, which makes ad blocking not possible on Chrome and was purely for security reasons and not for disabling ad blockers. Now that Chrome users can't block ads on the first-party site, they're going after third-party clients. Such coincidental timing.

There's no way Mozilla is replacing Google as the default, so what are they actually announcing here? I didn't read any actual results thats happening. Are they just adding Qwant as an option in the search engine settings?

These "Aerocarts" will be pulled down the runway by the lead plane just like a recreational glider. They'll lift off more or less together with the lead plane, then stay on the rope throughout the cruise phase of flight, autonomously surfing the lead plane's wake for minimal drag and optimal lift

Super disagree. A community at the protocol level can have just as much character as a community at the network level, but without most of the drawbacks. The "instance as community" idea was always a poor substitute for actual Groups. The community shouldn't be a server that users are bound to; it should be a Group that has access controls and private memberships (if desired). The moderators get all the same benefits of maintaining a limited community with their own rules, but users aren't beholden to petty drama via instance blocks or defederation.

The article also points out that there were people who ate the raw sushi with no adverse affects, so mentioning "their established toxicity" seems like it would be just as misleading.

"Morels are more likely to cause intestinal distress if eaten raw, although even raw, they can be tolerated by some people," the agency wrote. Morels should be cooked before eating, as cooking can destroy bacterial contaminants. "For that matter, all mushrooms, wild or cultivated, should be cooked to release their full nutritional value because chitin in their cell walls otherwise inhibits digestion," the USDA writes.

The article mentions multiple times that cooked mushrooms are safer than raw ones.

But public posts federating across the network isn't an "experience". It's the basic functionality of the network.