noenzyme

Same thing happened to Costco a few weeks ago. Maybe the same company behind both. From http://www.costcophotocenter.com/

===

As a result of recent reports suggesting that there may have been a security compromise of the third party vendor that hosts Costcophotocenter.com, we are temporarily suspending access to the site. We take the security of our members’ data seriously, which is why we are taking this precautionary step. This decision does not affect any other Costco website or our in-store operations, including in-store photo centers.

This situation is affecting multiple online photo sites. We are diligently working to determine when we can re-enable the site, but in all likelihood that will not occur until the middle of August. We will update this statement when we have more information.

I think a cool derivative work would be to see today's HN but filtered to only see activity of people who joined before you.

https://youtu.be/mL9AFkJJAq0?t=27m30s if you want to see the actual demo...

Experience Report: We just went through the decision to build as a monolith or via microservices. The original decision was to go with microservices as the rest of our systems are designed that way.

As the time pressure mounted the microservices that communicated naturally combined. The driving force was just the cycle time. Testing and deploying microservices took longer. Mind you, not minutes vs hours. Just a few extra minutes makes a difference if you do it often enough.

One decision that give us confidence we will be able to split the system back out again was to use the stuartsierra/component library. By using DI we can be fairly confident we don't build dependencies we aren't aware of. We simply substitute a client that talks over the network in for the one that does the calculation locally.

We are still in the stabilization zone but have already started to split out services. Code velocity is the driving force for the splitting. Certain components are well understood and fairly robust other still young and poorly understood. We want to limit our ability to accidentally screw up something we have already gotten right. So the components that haven't changed in a while get spun out.

We would then have come full circle. Robots/AI remove jobs, which causes basic income legislation to take root, which cause people to stop working the jobs the Robots/AI took away in the first place!

Actually the basic income creates new business models. If you can't take care of yourself you can sign up with a company that takes your basic income and provides 3 hots, a cot and an allowance. Can't image it will be the nicest accomidations but it will be there if you need it...

There is an underlying premise that only the US will have a basic income. If robots/AI do most of the labor there is no (long term) reason why all countries can't offer basic income to their citizens.

Here is a simple idea. Make it known that our top election issue is removing the NSA's (and others) tentacles from our daily lives. In addition we, the tech elite, will freely help candidates who share point of view and refuse to work with those that don't.

The last election showed how important IT systems are. And while it may take a few election cycles we can certainly use that to our advantage.

Thoughts?

Sweet, I need something like this.

Freakin awesome.

Anyone know the password to watch to old videos?