Eli Grey
https://news.ycombinator.com/item?id=11625633 :frowning: We either need to reverse engineer the google.com internal JS API (used by https://www.google.com/#q=test) or resort to scraping HTML. Also, automated use will probably trigger CAPTCHAs as explained...
Yeah I second this. Trusted users should be able to !trust/!untrust other users. There would need to be 2 tiers of trust though (one that can't be removed with this...
Also managing the [twitter mappings](https://github.com/oftn/oftn-bot/blob/b3ae1cca290631a7bc154ba540ec366e1c22ea13/oftnbot.js#L508) could be a trusted action. `!twitter-alias eligrey ^EG`
Maybe Iexploder only supports 1 thread?
In the meantime we can hardcode in some ugly UA sniffing code and if we detect Firefox, only ever test up to 20 threads. If Core Estimator estimates exactly 20...
Sure, I'll probably accept any well-formatted pullreq adding that.
Have you contacted the developers of the affected browser extensions? They can potentially detect blob URIs and preempt their download manager behavior before breaking downloads.
Oh yeah I forgot that it doesn't use blob urls, sorry
I do not want to spend more of my CPU cycles performing prophylactic security for third parties, which should have been handled by those parties themselves.
@danoctavian It seems like your own https://github.com/danoctavian/bit-smuggler repo would also belong in this category. Interestingly, I don't see it on the list.