Category Archives: code

adabox 004 project in mind

playing with the prototyping breadboard and some parts from the adabox004 , a few mp3’s, good ol’ IFTTT and lightweight Arduino code.

It will be a variation of John Park‘s project here

I’ll be tossing in a little IR remote to fire off sounds I want to hear, and a potentiometer to control volume.  If I get antsy, I may add a battery pack for portability over the micro usb cable. It could be fun to hide it around the house and drive the cats crazy with phone or remote- activated sounds.

Code under the cut.

Continue reading adabox 004 project in mind

adblock help

A website is telling me to disable AdBlock before it will show content

Modified on: Fri, 13 May, 2016 at 1:45 PM


More and more websites display a message asking you to disable AdBlock to be able to access the website’s contents (e.g., videos or articles). If it’s a site you enjoy and visit frequently, you might consider subscribing to it, which will eliminate the ads on the site while supporting the content provider.

If you’d rather not see any ads, try this instead.

Subscribe to the Adblock Warning Removal and Anti-Adblock Killer filter lists

  1. Click the AdBlock button and select Options.
  2. On the FILTER LISTS tab, click update now.
  3. Enable the Adblock Warning Removal list.
  4. Visit reek’s website and subscribe to the AakList (Anti-Adblock Killer filter list).

Create a custom filter for the site

  1. In AdBlock’s options on the CUSTOMIZE tab, next to Manually edit your filters click Edit.
  2. In the text box type: @@||example.com$elemhide
    For example, to create a filter for twitch.tv, type @@||twitch.tv$elemhide
  3. Click Save and reload the page.

If these steps don’t seem to make any difference, you can also try installing the Anti-AdBlock Killer userscript.

Report the website

If nothing you’ve tried has helped, the website needs to be reported to the filter list maintainers. Please report the issue to the filter list that matches the language of the website:

  • For English websites, please report the issue to EasyList.
  • You can find the contact information for other filter lists in our Knowledge Base.

You can also report the website to Anti-AdBlock Killer in situations where the issue can’t be worked around with AdBlock filters.

Bonus tip

We found a nice article on how to bypass websites that block AdBlock (e.g., Forbes.com). This method, which incorporates some of the steps we suggested above, also works on Hulu.com and ComedyCentral.com (according to the comments, at least; YMMV).

Have you disabled AdBlock but the site still asks you to disable your ad blocker?

This usually happens when the site is poorly written. Basically, it’s a bug in the code the site uses to check for ad blockers. Because of that, it affects all ad blockers, not just AdBlock.

If you absolutely need to use the site, try removing your ad blocker entirely. If that doesn’t help, there is nothing we or you can do to get around this. You can try notifying the site administrators if a contact is listed in the page footer, or just wait for them to figure it out and fix the bug.

QUICK COOL QUERY FROM PAUL!

<cfprocessingdirective suppresswhitespace="yes">
<cfinclude template="/includes/hep/header.cfm" />
<a name="content" id="content"></a>
<div id="pagecontents">
<cfoutput><h1>#page_title#</h1>
<cfif #page_subtitle# neq ""><h2>#page_subtitle#</h2></cfif></cfoutput>

<cfdirectory action=”list” directory=”#expandpath(“.”)#” name=”digests” filter=”he*.cfm”>

<cfset issues = querynew(“issuemo,issueday,issueyear,file”,”integer,integer,integer,varchar”)>
<cfoutput query=”digests”>
<cfset prename = listfirst(replace(name,”he”,””),”.”)>
<cfset month = left(prename,2)>
<cfset day = mid(prename,3,2)>
<cfset year = right(prename,2)>
<cfset queryaddrow(issues)>
<cfset querySetCell(issues, “issuemo”, month)>
<cfset querySetCell(issues, “issueday”, day)>
<cfset querySetCell(issues, “issueyear”, year)>
<cfset querySetCell(issues, “file”, name)>
</cfoutput>

<cfquery name=”showissues” dbtype=”query”>
SELECT issuemo, issueday, issueyear, file
FROM issues
ORDER BY issueyear DESC, issuemo DESC, issueday
</cfquery>

<cfoutput query=”showissues” group=”issueyear”>
<h2>20#issueyear#</h2>
<cfoutput group=”issuemo”>
<h3>#MonthAsString(issuemo)#</h3>
<ul>
<cfoutput>
<cfset filename = issuemo & “/” & issueday & “/” & issueyear>
<li><a href=”#file#”>#dateformat(filename,”mmmm dd, yyyy”)#</a></li>
</cfoutput>
</ul>
</cfoutput>
</cfoutput>

<!—
<h2>2015</h2>
<h3>August</h3>
<ul>
<li><a href=”/livability/he_digest/he082715.cfm”>August 27, 2015</a> <cfoutput>#newtag(“n”,”8/27/2015″)#</cfoutput></li>
<li><a href=”/livability/he_digest/he081315.cfm”>August 13, 2015</a></li>
</ul>
<h3>July</h3>
<ul>
<li><a href=”/livability/he_digest/he073015.cfm”>July 30, 2015</a></li>
<li><a href=”/livability/he_digest/he071615.cfm”>July 16, 2015</a></li>
<li><a href=”/livability/he_digest/he070215.cfm”>July 2, 2015</a></li>
</ul>
<h3>June</h3>
<ul>
<li><a href=”/livability/he_digest/he061815.cfm”>June 18, 2015</a></li>
</ul>
<h3>May</h3>
<ul>
<li><a href=”/livability/he_digest/he052115.cfm”>May 21, 2015</a></li>
<li><a href=”/livability/he_digest/he050715.cfm”>May 07, 2015</a></li>
</ul>
<h3>April</h3>
<ul>
<li><a href=”/livability/he_digest/he042315.cfm”>April 23, 2015</a></li>
<li><a href=”/livability/he_digest/he040915.cfm”>April 9, 2015</a></li>
</ul>
<h3>March</h3>
<ul>
<li><a href=”/livability/he_digest/he032615.cfm”>March 26, 2015</a></li>
<li><a href=”/livability/he_digest/he031215.cfm”>March 12, 2015</a></li>
</ul>
<h3>February</h3>
<ul>
<li><a href=”/livability/he_digest/he022615.cfm”>February 26, 2015</a></li>
<li><a href=”/livability/he_digest/he021215.cfm”>February 12, 2015</a></li>
</ul>
<h3>January</h3>
<ul>
<li><a href=”/livability/he_digest/he012915.cfm”>January 29, 2015</a></li>
<li><a href=”/livability/he_digest/he012215.cfm”>January 22, 2015</a></li>
<li><a href=”/livability/he_digest/he011515.cfm”>January 15, 2015</a></li>
<li><a href=”/livability/he_digest/he010815.cfm”>January 8, 2015</a></li>
<li><a href=”/livability/he_digest/he010115.cfm”>January 1, 2015</a></li>
</ul>
<h2>2014</h2>
<h3>December</h3>
<ul>
<li><a href=”/livability/he_digest/he121814.cfm”>December 18, 2014</a></li>
<li><a href=”/livability/he_digest/he121114.cfm”>December 11, 2014</a></li>
<li><a href=”/livability/he_digest/he120514.cfm”>December 5, 2014</a></li>
</ul>
<h3>November</h3>
<ul>
<li><a href=”/livability/he_digest/he112014.cfm”>November 20, 2014</a></li>
<li><a href=”/livability/he_digest/he111314.cfm”>November 13, 2014</a></li>
<li><a href=”/livability/he_digest/he110614.cfm”>November 6, 2014</a></li>
</ul>
<h3>October</h3>
<ul>
<li><a href=”/livability/he_digest/he103014.cfm”>October 30, 2014</a></li>
<li><a href=”/livability/he_digest/he102314.cfm”>October 23, 2014</a></li>
<li><a href=”/livability/he_digest/he101614.cfm”>October 16, 2014</a></li>
<li><a href=”/livability/he_digest/he100914.cfm”>October 9, 2014</a></li>
<li><a href=”/livability/he_digest/he100214.cfm”>October 2, 2014</a></li>
</ul>
<h3>September</h3>
<ul>
<li><a href=”/livability/he_digest/he092514.cfm”>September 25, 2014</a></li>
<li><a href=”/livability/he_digest/he091814.cfm”>September 18, 2014</a></li>
<li><a href=”/livability/he_digest/he091114.cfm”>September 11, 2014</a></li>
<li><a href=”/livability/he_digest/he090414.cfm”>September 4, 2014</a></li>
</ul>
<h3>August</h3>
<ul>
<li><a href=”/livability/he_digest/he082814.cfm”>August 28, 2014</a></li>
<li><a href=”/livability/he_digest/he082114.cfm”>August 21, 2014</a></li>
<li><a href=”/livability/he_digest/he081414.cfm”>August 14, 2014</a></li>
<li><a href=”/livability/he_digest/he080714.cfm”>August 7, 2014</a></li>
</ul>
<h3>July</h3>
<ul>
<li><a href=”he073114.cfm”>July 31, 2014</a></li>
<li><a href=”he072414.cfm”>July 24, 2014</a></li>
<li><a href=”he071714.cfm”>July 17, 2014</a></li>
<li><a href=”he071014.cfm”>July 10, 2014</a></li>
<li><a href=”he070314.cfm”>July 3, 2014</a></li>
</ul>
<h3>June</h3>
<ul>
<li><a href=”he062614.cfm”>June 26, 2014</a></li>
<li><a href=”he061914.cfm”>June 19, 2014</a></li>
<li><a href=”he061214.cfm”>June 12, 2014</a></li>
<li><a href=”he060514.cfm”>June 5, 2014</a></li>
</ul>
<h3>May</h3>
<ul>

<li><a href=”he052914.cfm”>May 29, 2014</a></li>
<li><a href=”he052214.cfm”>May 22, 2014</a></li>
<li><a href=”he051514.cfm”>May 15, 2014</a></li>
<li><a href=”he050814.cfm”>May 8, 2014</a></li>
<li><a href=”he050114.cfm”>May 1, 2014</a></li>
</ul>
<h3>April</h3>
<ul>
<li><a href=”he042414.cfm”>April 24, 2014</a></li>
<li><a href=”he041714.cfm”>April 17, 2014</a></li>
<li><a href=”he041014.cfm”>April 10, 2014</a></li>
<li><a href=”he040314.cfm”>April 3, 2014</a></li>
</ul>—>
</div></div>
<cfinclude template=”/includes/moddate.txt” />
<cfinclude template=”/includes/hep/footer.cfm” />
</cfprocessingdirective>

ACTIVE SHOOTER AWARENESS / Newton / etc

SLEEPING BEAUTY (1959) – SILENCE!

Sleeping Beauty (1959)

You folks on the bus, on the phone at 5:30am… Shaddap, willya? Or at least, pipe down some?

ACTIVE SHOOTER AWARENESS

Sent to me (my office), on how to respond to an active shooter after the events in Paris last Friday. It is surprising that this wasn’t sent out when there was a supposed shooter in the Navy Yard last summer?

This video, recently produced by the Houston Mayor’s Office of Public Safety and Homeland Security, dramatizes an active shooter incident in the workplace. Its purpose is to educate the public on how to respond during such an incident. Warning: The initial sequence in this video may be disturbing.
The U.S. Department of Homeland Security (DHS) defines an active shooter as an individual actively engaged in killing or attempting to kill people in a confined and populated area; in most cases, active shooters use firearm(s) and there is no pattern to their selection of victims.”  
Active shooter situations are unpredictable and evolve quickly. Typically, the immediate deployment of law enforcement is required to stop the shooting and mitigate harm to victims.  Since active shooter situations are often over within minutes, before law enforcement arrives on the scene, individuals must be both mentally and physically prepared to deal with an active shooter situation.
Your actions can make a difference for your safety and survival. Be aware and be prepared.
HOW TO RESPOND WHEN AN ACTIVE SHOOTER IS IN YOUR VICINITY
 
If you are to ever find yourself in the middle of an active shooter event, quickly determine the most reasonable way to protect your own life.  Remember that employees are likely to follow the lead of managers during an active shooter situation.  The plan doesn’t have to be complicated. You have three options that can make a difference: Run. Hide. Fight.
In preference and priority order, there are three general options or responses when one is confronted by an active shooter situation:
 
1. Run (First preference and priority)
  • Have an escape route and plan in mind
  • Leave your belongings behind
  • Keep your hands visible
 
2. Hide (Second preference and priority)
  • Hide in an area out of the shooter’s view
  • Block entry to your hiding place and lock the doors
  • Hide behind furniture if possible
  • Silence your cell phone
 
3. Fight (Third preference and priority)
  • If confronted directly and as a last resort when your life is in imminent danger
  • Attempt to incapacitate the shooter
  • Act with physical aggression, throw items and improvising weapons
Call 911 when it is safe to do so.
Information you should provide to the 911 operator or law enforcement includes:
  • Your location
  • Location of the active shooter
  • Number of shooters
  • Physical description of shooters
  • Number and type of weapons held by shooters
  • Number of potential victims at the location
 
Attempt a quick accounting of workers.
  • Given the nature of an active shooter incident, employees may or may not use designated assembly or muster locations
  • Supervisors should attempt a quick accounting of worker and building visitors as soon as feasible and a more detailed accounting toward or at the end of the incident
 
When law enforcement arrives:
  • Remain calm and follow instructions
  • Put down any items in your hands (i.e., bags, jackets)
  • Raise hands and spread fingers
  • Keep hands visible at all times
  • Avoid quick movements toward officers such as holding on to them for safety
  • Avoid pointing, screaming or yelling
  • Do not stop to ask officers for help or direction when evacuating
The active shooter incident will be a dynamic situation that evolves rapidly and demands immediate response from law enforcement to terminate the life-threatening situation. The immediate response of the first patrolmen or officer on scene is to take aggressive action to find and stop the shooter(s). Rescue efforts will be delayed until the danger can be either mitigated or eliminated.
Weapons Prohibition – Possession or use of firearms and other dangerous weapons on a federally owned or leased facility, including grounds, parking lots and buildings, is illegal as stated in 18 USC  Chapter 44, Section 930 (a) and (b).  Violators are subject to fine and/or imprisonment for periods up to five (5) years.

[private post] SECURITY AWARENESS, POST PARIS EVENT ON FRIDAY

FHWA HQ Employees and Contractors:

The following information is being forwarded to you for your situational awareness.

We would also like to highlight some information about the DOT Alert system discussed below.  If you are not aware, this system will give you the ability to not only receive information like this on your work emails, but it will give you the option to receive important emergency messages and alerts such as this on any personal phone or email you elect to register to receive them on.  Unfortunately we have identified an issue with the directory that will prevent a problem for a very small number of employees to register.  We have identified the fix and it should be rectified by the end of the week.  If you have problems registering in the system or have any other questions regarding the FHWA Transportation Security Program please feel free to contact Mr. Jeff King at 202-366-5280 or by email at jeffrey.king@dot.gov

DHS to Increase Security at Federal Facilities

On Monday, November 16, 2015, the Department of Homeland Security announced that security will be stepped up at federal buildings in the wake of last week’s terrorist attacks in Paris.  These precautionary measures are to safeguard U.S. Government personnel, facilities, and visitors to those facilities.  The Federal Protective Service (FPS) has been directed to enhance its presence and security at various U.S. Government buildings in Washington DC and other cities around the country.

At this time, there are no immediate or specific threats, nor any actionable information indicating a credible threat to any DOT facility or personnel.

The OST Office of Security (M-40) and Office of Intelligence, Security and Emergency Preparedness (S-60) is closely monitoring this situation and will provide updates as circumstances warrant.

DOT has an Alert system that allows employees and contractors to self-register your personal contact information to receive information from DOT during an emergency, even if you are not in the office.  Registration is entirely voluntary and the information provided will be used for DOT Alert notifications only. To register visit the DOT Alerts Portal.

If you haven’t completed the annual Active Shooter training in TMS, please do so.  Click here for additional information on How to Respond to an Active Shooter.

Finally, we remind all DOT employees to remain vigilant and exercise a heightened state of awareness and report any suspicious activities to FPS, local law enforcement or to building security.

If you observe people acting suspiciously, be prepared to answer the following questions when reporting suspicious activity:

  1. WHAT is happening?
  2. WHO is doing it?
  3. WHERE is it taking place?
  4. WHEN did you observe it?
  5. WHY are you suspicious?

If you SEE Something, SAY Something!

Emergency Phone Numbers

DOT Headquarters (SEFC):                                 202-366-0333 or 202-366-0337

FAA Headquarters (10A):                                    202-267-8829

FAA Headquarters (10B):                                    202-267-0326

FPS (Nationwide):                                                  1-877-437-7411

Local Law Enforcement:                                       911 (check your local listing)

If you have any questions or require any guidance on these increased measures, please contact David Stackleather, Associate Director, Physical and Technical Security, Office of Security, at (202) 366-9090, or via david.stackleather@dot.gov .

A Secure DOT Requires Everyone’s Vigilance!

 

 

Newton this Morning. That’s my breakfast companion.

Snapchat-2667800010668077238.mp4

Newton this Morning. That’s my breakfast companion.

from Scott von Berg @ Google+ http://bit.ly/1QMHyWG
via IFTTT

https://code.visualstudio.com/updates/v0_3_0 (Visual Studio is now open source – https://news.ycombinator.com/item?id=10588264)
smortaz 40 minutes ago

We’ve been asked this by a few people, so I figured this is a good place to respond:
Will PTVS (Python Tools for Visual Studio) come to VSCode?
The answer is YES! This will be a major focus next year. Expect full intellisense, debugging, profiling, pkg mgmt, unit test, virtual env, multiple interpreter, Jupyter, etc. support.
Disc: Python/R/Jupyter team lead

https://www.visualstudio.com/features/python-vs

Welcome to my wall scrawls.