anonymuse

Notes:

-------

- FEMA is moving to level 1.

- The DPA was last invoked during the cold war

- Links to FEMA [1] and Wikipedia [2]

- Doctors may now practice across state lines

- A 100 page plan has been recently published which references an 18 month cycle for the pandemic [3]

- There was a reference to a "significant proportion" of serious infection rates in the millennial generation based on early reports from India

Links:

-------

[1] https://www.fema.gov/defense-production-act-overview

[2] https://en.wikipedia.org/wiki/Defense_Production_Act

[3] https://int.nyt.com/data/documenthelper/6819-covid-19-respon...

More details on the proposal and discussion can be found in the merged pull request here:

https://github.com/cncf/toc/pull/38

and the voting here, in case you'd like to see into the decision making process that went into this:

https://lists.cncf.io/pipermail/cncf-toc/2017-October/001309...

There also a very interesting sub-discussion about bundling Notary and TUF together, an what the implications are for pairing image signing and package signing into a single request. While TUF can be seen as a next gen tool for signing groups of digital content, it's relationship at this point to Notary is yet to be solidified.

Another vote for the Goruck GR-1.

http://www.goruck.com/gr1-rucksack-black-/p/GEAR-000574

It's been through three rucks and has been my daily partner for three years now.

As a bike commuting New Yorker, I'm frequently carrying my whole life around plus laptop, and it's been perfect. It looks as new as the day I purchased it.

A truly buy it for life item.

Neat, I like organizational apps. Any https://taskwarrior.org/ users here comment on what they think of Tdo?

From the design goals outlined in the FAQ, it seems clear to me that Google expects there to be a great deal more bandwidth hungry devices in the home speaking first to each other, and then out to the WAN, in the near term.

Including Bluetooth, Weave, and Thread, along with up to 128 devices, gives me a rough sense of the scale of connected devices they anticipate in each home. Given that it also has a reasonable compute capabilities and cooling as one of the highlights, I think it's far to say that it could do a lot of processing on its own before reaching back home to the GOOG DCs.

One of my favorite parts of living in this (at-points) expensive, overcrowded, noisy, competitive, shallow, and brutal metropolis is the extensive walking culture that we share. My walk/bike commute to work could meander along the same main and side streets, with every one of the ~251 trips taken being uniquely constructed.

Furthermore, that ignores the wiggling route I enevitably travel, pushed left by a honking cab and similarly colored stoplight, or nudged right by the inevitable crowded side street filled with movie sets or construction vehicles.

Putting aside the health benefits of human-powered-travel, it's both a refreshing and invigorating way to spool up my mind on the way into the office, and also a way to decompress and release the day's aspirational steam that's best not blown out all at once, just inside your apartment.

I think it'll be quite interesting to see how the smaller players organize themselves around the multitude of cluster resource management tools emerging as a natural reaction to Kubernetes growing out of the work Google's done on Borg.

I am curious to see how long of a shake-out period will exist before there's either a de facto stack of "compute resource" tooling, or if there's always going to be a highly fragmented and diverse way to accomplish your goals. Just off the top of my head (and there's way more) I'm thinking about Tectonic[1], Mesosphere[2], Rocket [3], Kismatic [4] as a few examples.

As a technologist and a planner, it's been challenging to see far enough into the future to decide on what tools to devote myself to learning at this point. I do think we're certainly in a "post-public cloud" timeline where we're getting good enough (or will be in 6-12 months) at abstracting virtualization right up to a millimeter or two below the application layer of our stacks. How we choose to do so seems to be currently up in the air.

In my mind, this opens up the possibility of compute as a resource much wider than had previously been possible. We'll be less reliant upon Azure, AWS, and GCP's mixture os Paas and Iaas and much more interested in compute as a resource, likely from bare metal or private cloud providers.

I'm looking forward to the increased efficiency (both through compute power and cost) and security available in moving from a application-level virtualization to operating system-level virtualization.

[1] https://coreos.com/blog/announcing-tectonic/ [2] https://github.com/mesosphere [3] https://github.com/coreos/rkt [4] https://github.com/kismatic

Highly recommend checking out "Hack All The Things - 20 Devices in 45 Minutes" by CJ Heres & Amir Etemadieh & Mike Baker & Hans Nielsen. https://media.defcon.org/DEF%20CON%2022/DEF%20CON%2022%20vid...

This is the GTVhacker group that hacked the GoogleTV.

"Weaponizing Your Pets" with Gene Bransfield is definitely also worth checking out. "The War Kitteh and Denial of Service Dog."

https://media.defcon.org/DEF%20CON%2022/DEF%20CON%2022%20vid...

This is good, let's get this sort of hiccup out of the way before the predictably massive traffic from Black Friday and Cyber Monday.

What's everyone using to monitor external asset hosts? Is anyone dynamically switching between them, or failing back to local assets?

Anecdotally, our site is now loading quickly for me: http://canary.is/.

However, digging the Cloudfront name servers times out intermittently:

  $ dig +short @ns-666.awsdns-19.net cloudfront.net
  ;; connection timed out; no servers could be reached

AWS Status shows Cloudfront DNS issues, which is reflected in our page's assets not loading. Kinda makes me wish we were using something like https://github.com/etsy/cdncontrol/ but that's a fight for another day!

  <title type="text">Informational message: DNS Resolution      errors </title>

  <link>http://status.aws.amazon.com</link>

  <pubDate>Wed, 26 Nov 2014 17:00:39 PST</pubDate>
	   <guid>http://status.aws.amazon.com/#cloudfront_1417050039</guid>

  <description>We are currently investigating increased error   rates for DNS queries for CloudFront distributions.  </description>

Thanks for the feedback. I'll consider that in the future. It's probably naive to think drive-by-criticism can be constructive in this setting.

Really? I spent a small amount of time trying to craft a suggestion that I honestly felt would help this person do their job better. I can see how it could appear potentially condescending, but how are we able to give people constructive advice if there's an effort at a concise, polite response and it's perceived as obtuse?

Using words such as "recommend", "advice", "friendly" in my mind conveys only transparency. I would genuinely like to know how this email could be re-written in a more helpful tone. Or is any response doomed to snarkiness?