HN user

echoangle

4,560 karma
Posts2
Comments2,099
View on HN

Also even if it would work (which it very much doesn't), whether it "hurts the original publisher" is actually literally one of the criteria for considering something fair use or not. Look it up.

I don’t know why you’re repeating the stuff I just wrote like I didn’t. My point is that this is only relevant for the fair use defense and not copyright in general.

Here’s what I said:

The “does it hurt the original publisher” is a test for fair use BTW, just because you hurt the sales of someone doesn’t necessarily make it copyright infringement. That is only relevant if you try to defend using fair use (and it’s only part of the test that’s used to decide fair use).

similarly, as has been shown (by numerous publishers and authors), LLMs are capable of producing nearly-verbatim versions of the texts they have been trained on, to a well enough quality that most people won't be able to notice the difference.

If that is true, you have a legal claim and can sue them. I doubt that’s true in the general case though.

The “does it hurt the original publisher” is a test for fair use BTW, just because you hurt the sales of someone doesn’t necessarily make it copyright infringement. That is only relevant if you try to defend using fair use (and it’s only part of the test that’s used to decide fair use).

That’s some really obnoxious writing, somehow even worse than the usual AI spam (although this also reads like co-written by AI). Here’s the cleaned up version:

I built 160+ micro calculator tools across finance, math, health, fitness and more. I did the keyword research after and the data genuinely surprised me. There were 3,600 keywords total across the calculator hub. The estimated traffic potential is 341 million per month. The average keyword difficulty is 33. 1,784 of all the keywords sit at an easy KD of under 30. That means that 50% of the entire set have low competition. Small boring tools with exact match domains are one of the most underrated SEO plays.

I guess congrats to the author for saving 30 seconds by leaving out half of the words that can technically be inferred.

And how would you validate that? Which arbitrary cutoff do you find reasonable?

And if your app crashes on an input like that, you should pick a different date Library or stop and rethink your coding skills.

I don’t think people are criticizing the MAXINT thing. The problem is that IDs are already reused when you create 10 rows, delete 5 and then make a new one. Normal DB engines just keep counting afaik so the new ID will still be one that has never been used before.

Every year, speculation articles appear with people guessing winners (for the Pulitzer and National Book Award and Booker in particular) based on absolutely irrelevant factors like whether an entirely different jury liked this author’s last book five years ago, or whether this book was on other juries’ lists for other prizes. Any article that gets people talking about books is a great thing, but the speculation part is, I hate to say it, useless.

How is that irrelevant? I don’t think the idea is that the previous information causes the book to be chosen next, but it should be an indicator that the book is good.

Just like a student writing a good exam isn’t irrelevant when deciding the next grade, even though the good grade itself doesn’t cause another good grade. But it still influences the expectation.

The normal ROWID selection algorithm described above will generate monotonically increasing unique ROWIDs as long as you never use the maximum ROWID value and you never delete the entry in the table with the largest ROWID. If you ever delete rows or if you ever create a row with the maximum possible ROWID, then ROWIDs from previously deleted rows might be reused when creating new rows and newly created ROWIDs might not be in strictly ascending order.

I disagree. Surely the newsworthiness of vulnerability writeup is a mix of the relevance and article quality.

You could submit a vulnerability report about an internal tool no HN user could ever be affected by and people could find it really interesting, and you could submit an article about a vulnerability that’s really bad and only people that really care about the affected project would be interested.

Edit: removed some irrelevant stuff because I misread the comment