Hacker Newsnew | past | comments | ask | show | jobs | submit | SyrupThinker's commentslogin

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.


No, its AI. But your standard of required proof cannot be met. You can always point to any particular example and say, oh a human could say that. Yes, one odd phrasing could be attributed to that. Multiple per paragraph, and it's no longer a viable explanation. How much LLM text do you actually consume on the daily?


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)


You know how laws are made? There's this big building where rational people discuss the options. If they don't get it right, the people can vote them out. Of course stupid laws are occasionally passed, but also it's possible (easy, in fact) to write a reasonable law to say you cannot rent property that is either too hot or too cold.


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.


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.


This, the vm bundle which reappears after you delete it. They say it's For Cowork and Claude Code, but if you don't use Cowork or CC sandboxing, it has no value. Considering I'm always finding things to delete on apples anaemic 512gb because I run out of space.


Well Electron includes Chromium. Maybe that pulls the 4GB model as well… not sure if it is Chrome only.


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.


Frequently, but not always, I can reproduce such bugs using Epiphany [1] or other WebKit based browsers.

That's at least somewhat cheaper when it works.

[1]: https://webkit.org/downloads/


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


They know. They also know that almost no regular users know what it is, what it's for, or how to configure it. The search fails where the accept-language was wrong far dominate the numbers over the search fails where the accept-language was ignored.


> 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?


Browsers tend to default to an Accept-Language of en-US, and most users do not know how to change it.

As a result, Google learned early on (and numbers continue to suggest it is the case that) an Accept-Language of specifically en-US really means "The user has not chosen a language; fall back to a heuristic."


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.


Omg, it was so frustrating to say:

Summarize recent working arxiv url

And then it tells me the date is from the future and it simply refuses to fetch the URL.


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.


I have a userscript to actually hide my own karma because I always think it is useless but your point is good actually. But also I think that karma/comment ratio is better than absolute karma. It has its own problems but it is just better. And I would ask if you can share the userscript.

And to bring this back to the original arxiv topic. I think reputation system is going to face problems with some people outside CS lack of enough technical abilities. It also introduce biases in that you would endorse people who you like for other reasons. Actually some of the problems are solved and you would need careful proposal. But the change for publishing scheme needs push from institutions and funding agencies. Authors don't oppose changes but you have a lobby of the parasitic publishing cartel that will oppose these changes.


Yes, HN should probably publish karma divided by #comments. Or at least show both numbers.


(an added complication is that posting articles also increases karma)


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.


Brand new, clean install of npm.

Poor code + doc hygiene is the problem here.


The question is which version of node, not npm.


It doesn't matter. The install was broken as was written. That's poor hygiene.


It does matter.


Why yes, you're right, poor code hygiene and poor documentation hygiene does matter. We finally agree.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: