←back to thread

52 points JSLegendDev | 10 comments | | HN request time: 1.963s | source | bottom
Show context
ramiborni99 ◴[] No.41887000[source]
I love it! how did you make it, with plain javascript code? or with specific engine?
replies(1): >>41887031 #
1. defrost ◴[] No.41887031[source]
Are you training an AI @ Sendler.ai to make insipid low value comments on days old threads in order to astroturf this account for later boosting of your submissions?

I mean, it looks like that: https://news.ycombinator.com/threads?id=ramiborni99

but that's surely a mistake on my part?

replies(4): >>41917867 #>>41917988 #>>41918042 #>>41918192 #
2. wormlord ◴[] No.41917867[source]
Hey they're dogfooding.
3. mmcallister ◴[] No.41917988[source]
Given the answer to their question on how it's written is quite obvious in the provided link, I'd say if they are using an AI it doesn't appear to be parsing the content and maybe only the titles?
4. amazingamazing ◴[] No.41918042[source]
What’s the relevance of this comment? Why does it matter if it’s ai or not? Plenty of people only read titles
replies(2): >>41920424 #>>41927061 #
5. rexreed ◴[] No.41918192[source]
It's odd that the post shows as being only a few hours old, but the comments from ramiborni99 as 3 days old when viewed from the above link (here it shows not as old)? Similarly, your comment shows as a few minutes old, but showing as 3 days old when I view the threads from the above link... Very odd

@dang - what's going on with the timing on these comments and posts when viewed from the user thread link?

replies(2): >>41918732 #>>41920223 #
6. Wowfunhappy ◴[] No.41918732[source]
Usually this means the story is in the second-chance pool. I'm sure more information will come up if you search "second-chance pool", dang has posted about it before.

FYI `@dang` is a no-op. To contact dang send an email, he's quite responsive.

7. defrost ◴[] No.41920223[source]
As noted the story got second chanced.

The comment I made was (as of now) made three dayas ago, I addressed a brand new account that made a run of "cookie cutter" comments on older threads at the least active HN time (my peak reading time zone in Australia).

There are runs of such things, often much more obvious, "insincere" pretend engagement to bed a new account in prior to using it in a gang to promote | vote up other material.

HN likes a good signal to noise ratio and not cheap hype accounts.

I engaged in order to see if was being run by a human paying attention - I (an ordinary user) seem to have been given extraordinary ban abilities - I've [flag]'d a lot of obvious bot comments in past months and now anything I flag turns [dead] _immediately_.

Clearly I've been blessed with an extraordinary mini-mod super power and I prefer to exercise it with caution and check whether an account is bot or not before killing it.

This I'm leaving, there are eyeballs and attention which gets others to look at new accounts with fresh eyes and wider community involvement.

replies(1): >>41920330 #
8. rexreed ◴[] No.41920330{3}[source]
Ah - thanks for the heads up! Been on HN for 14+ yrs and first time I noticed that ;)
9. jbaber ◴[] No.41920424[source]
I mostly read comments :) I care very much that someone more attentive than me point out if a comment is machine generated.
10. kaeruct ◴[] No.41927061[source]
Nah, I think a lot of people read comments.

Personally sometimes I don't even read the article, I only read the comments