git commit -m "$(curl -s programmerexcuses.com | sed -n '/ >/{s/ ] >//g;p}')"
git commit -m "$(curl -s programmerexcuses.com | sed -n '//{s/]*>//g;p}')"21–30 of 69 posts
git commit -m "$(curl -s programmerexcuses.com | sed -n '/ >/{s/ ] >//g;p}')"
git commit -m "$(curl -s programmerexcuses.com | sed -n '//{s/]*>//g;p}')"That's an interesting webpage. it has a hidden google ads-field in an iframe. I'm not web-savy enough to fully understand how it works. The "click me as often as you can" contents for sure generate a lot of clicks. genius!
Here's the first one that might make sense that showed up on my refresh: "It worked yesterday"
UPDATE: Must be Ad Block blocking it.
That's an interesting webpage. it has a hidden google ads-field in an iframe. I'm not web-savy enough to fully understand how it works. The "click me as often as you can" contents for sure generate a lot of clicks. genius!
I see my GET request for show_ads.js is failing. So perhaps that nonloading javascript is suppose to make it appear but it's non working at the moment... Now, which excuses from the site would apply here? Here's the first one that might make sense that showed up on my refresh: "It worked yesterday" UPDATE: Must be Ad Block blocking it.
Earlier quoted context omitted.
I see my GET request for show_ads.js is failing. So perhaps that nonloading javascript is suppose to make it appear but it's non working at the moment... Now, which excuses from the site would apply here? Here's the first one that might make sense that showed up on my refresh: "It worked yesterday" UPDATE: Must be Ad Block blocking it.
Are you using Adblock or similar software?
On one reload I got a standard internal server error message. Next reload it was gone. If that was on purpose, it is a nice touch.
On one reload I got a standard internal server error message. Next reload it was gone. If that was on purpose, it is a nice touch.
I got this twice and I went to go look at the response to see if it was actually a 200 implying that it was purposeful, but once I loaded up the dev console to see the headers I couldn't reproduce.
Status comes back as 500 not 200.
http://www.pigdog.org/auto/mr_bads_list/shortcolumn/1914.htm...