Twitter
Celebrating a family day, 10 years since we met our daughter. Unbelievable how fast it goes.
Twitter
Tonight, Charleston City Council unanimously approved the attached resolution I introduced following Charlottesvill…
Twitter
False equivalence. FB is not the sole arbiter of ideas; many choose not to use it. My ISP *is* the sole path to the…
Twitter
Today is the 2 year anniversary of bringing Iria home from @OregonHumane. She still can’t ever get enough pettings…
Twitter
@grepory As it turns out, you can still deploy with Capistrano and have good practices and be far better off than d…
Scuttlebutt SSB
Historically, sea-slang for gossip - a scuttlebutt is basically a watercooler on a ship. Scuttlebutt is a decent(ralised) secure gossip platform.
Twitter
RT @bbchase: I have some thoughts about why news orgs are finding that people won’t read long articles…
Test from shell script if remote TCP port is open - Stack Overflow
It's easy enough to do with the -z and -w TIMEOUToptions to nc, but not all systems have ncinstalled. If you have a recent enough version of bash, this will work: # Connection successful: $ timeout 1 bash -c 'cat < /dev/null > /dev/tcp/google.com/80' $ echo $? 0 # Connection failure prior to the timeout $ timeout 1 bash -c 'cat < /dev/null > /dev/tcp/sfsfdfdff.com/80' bash: sfsfdfdff.com: Name or service not known bash: /dev/tcp/sfsfdfdff.com/80: Invalid argument $ echo $? 1 # Connection not established by the timeout $ timeout 1 bash -c 'cat < /dev/null > /dev/tcp/google.com/81' $ echo $? 124 What's happening here is that timeout will run the subcommand and kill it if it doesn't exit within the specified timeout (1 second in the above example). In this case bash is the subcommand and uses its special /dev/tcp handling to try and open a connection to the server and port specified. If bash can open the connection within the timeout, cat will just close it immediately (since it's reading from /dev/null) and exit with a status code of 0 which will propagate through bash and then timeout. If bash gets a connection failure prior to the specified timeout, then bashwill exit with an exit code of 1 which timeout will also return. And if bash isn't able to establish a connection and the specified timeout expires, then timeout will kill bash and exit with a status of 124.
Twitter
This is exactly right. Benefits, plus challenges that (faced rightly) bring deeper benefits.
Twitter
@ralphm @iNPUTmice I know, I don't say that it happened over night. In Germany we also lost gmx and web.de. Overall…
Twitter
Basically every reason I resist AMP. Making a fast and clean experience is time much better spent.
Twitter
RT @aliranger29: It seems fitting that, with the #TrumpCare debate raging, I got this bill in the mail today from Ethan's most recen…
Twitter
Today I Learned: You can extract the Windows key from a machine under Linux. $ sudo strings /sys/firmware/acpi/tabl…
Twitter
hey nonprofit #opensource communities how about supporting your fellow #opensource communities like @matrixdotorg i…

List of feeds:

pinboard: last checked Tue 22 Aug 2017 12:00:02 AM EDT (3517 posts; 3 new)

flickr: last checked Tue 22 Aug 2017 12:00:02 AM EDT (48 posts)

youtube: feed not found (10 posts)

libre.fm: last checked Tue 22 Aug 2017 12:00:03 AM EDT (0 posts)