Show HN: Hacker News bot that automated archive finding and commenting (github.com)
Hi everyone,
I build this bot to automate the process of going to wayback machine (or archive.ph) to find the archive link for posts with articles that have subscription blocks
The idea was to have this run on a server and then I wouldn’t have this daily annoyance, the bot was banned, so its not currently active, but I still wanted to show it off and get some feedback
Disclaimer : HN doesn't allow bots, so please don’t use this to run your own HN bot.
28 comments
[ 2.0 ms ] story [ 74.0 ms ] threadOccasionally there are gems.
hnflagflyer.com
Someone said "nothing was known about X until $date" or words to that effect and I replied with two sources, available online, that spoke about X prior to the date and that it was from my own recollection that I knew the sources existed. The incorrect comment stands and I got the usual "your comment was not complete enough for us". Every now and again I'll post something, especially when there are no responses and I have a source to share -- but I've taken to messaging the OP now instead.
Maybe it's all chaff, but I'm curious to find out.
I like the Slashdot way of having scoring and a slider so you can see it all if you want, and the "boosts" they do so you can see humorous stuff even if others want to see serious stuff. User-level filtering makes much more sense to me.
Also, if you want to tell mods something, email it because @dang doesn't automatically summon a dang.
Dang has actually written a response to OP a few days ago, saying essentially that he understands the intention is good, and that this sort of automation is at odds with the core philosophy of HN existing to promote curiosity and interesting conversation between human beings. When a post is popular enough, the community tends to organically post the un-paywall links, making the bot unnecessary.
Imagine having machine-automated archive link posts on every NYT and WaPo submission, it would be annoying and the early comment count would become meaningless noise, not even indicating that some person found it interesting enough to dig up the archive links for.
I was on the fence, but this is the compelling argument against, IMO.
This argument I understand, because as @dang said - while this bot would enhance the HN experience, once the Floodgates are allowed to open, it will have unintended consequences and lead to a worse HN experience
> this sort of automation is at odds with the core philosophy of HN existing to promote curiosity and interesting conversation between human beings.
I don't agree with that statement. Enabling easier access to the articles that are being discussed, would allow more people to participate and enhance the conversation
> it would be annoying and the early comment count would become meaningless noise
Maybe, but (a) Whats the impact of a single comment? (b) you could always prevent the bot from commenting the archive link on posts with less than N points or N comments.
That being said, I think the first point @dang made is a strong argument against the bot
Whenever there's an access issue, someone posts a workaround. The argument for making an exception for some bot has to be stronger than 'takes something that isn't broken and fixes it so it's clunkier and noisier'. The entire premise that it's 'enabling easier access' just not well-supported by what one can easily see by reading HN threads.
It is easy to automate this using a forward proxy. I use one on a loopback address. The way I have it set up, I add a given domain to a text file, reload,^1 and from then on, the proxy will rewrite the URLs using that domain to point to archive.org or whatever.
I have never encountered an archive.ph URL on HN where the site proxied, purportedly to avoid a "subscription block",^2 was not accessible without using the archive.ph URL. For example, sometimes the issue is simply that Javascript needs to be disabled, or one needs to use an AMP URL without Javascript. (The later looks great in a text-only browsersuch as links.) Whereas submissions for articles on sites that are password-protected, e.g., ft.com, rarely or never have archive.ph URLs.
This notion of "bots" is a never-ending source of amusement.
Everyone thinks they know what a "bot" is, but IMO that term alone tells us next to nothing. For example, one can write scripts, here using Python, that are disrespectful of server resources or whatever "rules" are in place and, as a result, get "banned". One can also write scripts that are respectful of server resources and any rules and never get banned. Automation is not per se "bots" and "bots" are not per se "bad". Computers and automation are everywhere. We do not label all automation using the internet as "bots". Whether something is "good" or "bad" depends on what a script is doing and, sometimes, who is using it.^3
I have been using automation for reading HN for over 10 years. Yes, it is possible to get banned but it depends on what a script does. The HN software does have limitations and one has to learn to work within those constraints.
1. Something like
2. IMO a true "subscription" would require a password. That is, non-subscribers would not have access to the content. Why do sites make content avaiable to to non-subscribers. Is it only to try to attract new subscribers. The site is gathering data about computer users and serving advertising. The site operator profits from the traffic from non-subscribers. If a site operator wants to make content only accesible to sucbscribers it can make that content password-protected. If the operator chooses not to use password protection then she may have a difficult time convincing a court the content published was not public. Annoying people with Javascript is not access control.3. Corporations performing telemetry and remotely installing and running "updates", automatically, without explicit consent on computers that do not belong to them generally do not get labeled as "bots". Whereas using automation to "subscribe" to "tech" company websites that aim to collect data about users in order to target advertising might be labeled as "bots" in a perjorative sense, if one is in the business of online advertising.
This sounds super useful to me. Would you be able to point me to some resources to set up a workflow for something similar?
To redirect to the most recent archive.org capture, I use a date in the distant future such as 203001234567890. This will automatically redirect to the latest capture.
To redirect to the earliest archive.org capture, I use 1. This will automatically redirect to the earliest capture. If I want to all requests for example.org files to retrieve from archive.org instead of example.org, I do something like 1. https://www.haproxy.org for documentation.Correction: FT was wrong example
I had forgotten ft.com like many other sites sends the plain text of the article to non-subscribers. It can be read in the page HTML. There is no way for non-subscribers to "opt-out" of receiving the article text when they follow ("click") a URL for a FT article.
It is in fact common to find archive.ph URLs for ft.com submissions.
Here is short program to make reading the article in the ft.com HTML page easier. It discards everything but the article text and replaces "\n" with newline.
Everything on that site that triggers a page-scrape is behind Google's ReCAPTCHA. And they've got the threshhold set at "hyper-aggressive" -- way above any other non-email-sending site I know of. It's the one site that I still get hit with a captcha from every time (excluding direct links to already-archived pages -- those don't seem to trigger the captcha).