SyrupThinker

This seems excessive, the author outright admits that LLMs were used, but some of your critiques can just as well be explained by a lack of familiarity with certain expressions or terminology.

For example, (software/e) fuses are a common thing spoken about in the context of Android custom roms and rooting, typically re rollbacks. The term is used as such in the XDA thread the article links to in the same paragraph.

"not getting the memo" and "something being the best television in years" are also two very common expressions. Both are used beyond literal notes or TV.

This blunt bashing of phrases makes me (and surely others) not want to share thoughts on the internet. Because apparently trying to not sound like a textbook, or in some cases even trying to write proper English, gets you labeled as LLM.

Does this really discourage the LLM-assisted writers more than those that would use these specific phrases naturally? I doubt it, the former will probably just obfuscate it.

You realize this was intended as a joke, because a base assumption in that comment was, in a very specific and not that relevant way, incorrect, right? The "oops" and the parenthetical was intended to give it away.

Oops, in Germany the kitchen is usually the tenants responsibility. Does that mean we should lose our heating privileges instead? (I'm sure some landlords would love that)

Depends on how you frame it, the employee still owns the work in the sense that they are the copyright holder. But the employer is granted exclusive usage rights to the work, so you wouldn't have the rights to license it to someone else as is encouraged in the article.

That would be relevant, for example, when the company goes defunct, and no one else holds any usage rights for the work. Then you'd regain those usage rights.

That of course is iffy to make use of because you'd need to be sure that you are considered the exclusive author, and that no one else acquired these exclusive usage rights.

This is more likely referring to the VM disk image the feature allocates, which would have little to do with Electron.

At the very least it did result in plenty of services that previously didn't allow one to delete accounts to add that option. For other cases writing a strongly worded email did the trick, unfortunate that Nikola did not have as much success with it.

> The search fails where the accept-language was wrong far dominate the numbers over the search fails where the accept-language was ignored.

Wouldn't this imply that "regular" users are running their OS and/or browser in a language they do not want to use for search? This seems unlikely to me, or is there some systematic reason that results in this being the case?

FWIW the decision-makers at Google (and some other companies) should just learn what the Accept-Language header is for.

I wonder if this suffers from the same issue as 3 Pro, that it frequently "thinks" for a long time about date incongruity, insisting that it is 2024, and that information it receives must be incorrect or hypothetical.

Just avoiding/fixing that would probably speed up a good chunk of my own queries.

No, I just dislike ad-hoc insulting people for superficial things, because the focus was on the photos, not the article. I realize the irony of my previous comment, so apologies for that.

Ignoring the actual proposal or user, just looking at karma is probably a pretty terrible metric. High karma accounts tend to just interact more frequently, for long periods of time. Often with less nuanced takes, that just play into what is likely to be popular within a thread. Having a Userscript that just places the karma and comment count next to a username is pretty eye opening.

Please tell me you are not running a NodeJS release that hasn't been supported for at least 3 years...

Optional chaining was added in v14 (2020), and it sure looks like that is the issue here.