http://heavy.com/news/2017/10/michael-christopher-estes-asheville-airport-bomber-suspect/
A 46-year-old man is facing federal charges accusing him of leaving a jar filled with explosives at a North Carolina airport as part of a war he pledged to fight on U.S. soil.
Michael Christopher Estes was arrested October 7 and charged with attempted malicious use of explosive materials and unlawful possession of explosive materials in an airport, according to a criminal complaint unsealed Tuesday.
The improvised explosive device, or IED, was found inside a jar at the Asheville Regional Airport about 7 a.m. on October 6, the FBI said in the complaint. Bomb technicians from the Asheville Police Department rendered the device safe. The baggage claim and lobby area of the airport were evacuated and shut down for about 2 hours. No one was injured.
also at USA Today and The Independent
(Score: 0) by Anonymous Coward on Monday October 16 2017, @01:15AM (1 child)
Are you using a proxy such that other people's sins are getting you in dutch?
Being routed through a company server?
"Our systems have detected unusual traffic from your computer network."
If you're not using a proxy (which will tar you with the same brush they use to tar other, miscreant, users of that proxy) then I suggest that you straighten up, fly right, and quit doing whatever got you on their shit list.
N.B. Whenever I've seen that message, it was because I had tried to narrow down a search, lost track of what I had already tried, and repeated the -same- search multiple times.
(Taking my browser offline and doing a drag & drop to a new tab now alerts me to repeats that are already in cache; if it's actually new, just go back online and hit Reload.)
Back a while, they used to bitch if I included site: in too many searches; they got over that nonsense.
...and, worst case for me, the message has gone away in a few hours.
...and, if you do JavaScript and don't block images, there has been a CAPTCHA associated with that when that message came up for me.
(It's been a long while since I encountered this stuff.)
.
...and when a page won't work for me (I typically block scripts and CSS), a proxy that almost always works just fine is archive.li [archive.li]
...also available as archive.is|archive.eu|archive.fo.
They run all that stuff on their machines and deliver the result.
Very nice.
Here's your first one, on the house.
http://archive.li/yQhBD#selection-745.0-745.10 [archive.li]
I wish you would instead pick a pertinent, credible page from the search results
When it suits my purpose, I do that.
In this case, it doesn't.
-- OriginalOwner_ [soylentnews.org]
(Score: 0) by Anonymous Coward on Monday November 13 2017, @12:50AM
Thanks for the response. I do use a proxy; when Google offers me a captcha and I solve it, sometimes all I get for my trouble is a 403 error page. With Google Translate, that happens consistently. For a long time (around a year), archive.{li | fo | is} was on CloudFlare and it also had a captcha.