flyt

Sign up and just add another user to your account. Their limits are soft and they probably won’t bother you if all you have is an extra user. Tailscale is fair and flexible this way.

The M2 MBA has MagSafe too.

AWS best practices is to use AWS SSO, which accomplishes this same effect but without any long-lived local credentials. It works really well.

This is correct. Mark never used Harvard servers for Facebook.

This is a store open 11am-6pm Monday through Friday, located in a middle of nowhere office park. No random walk-ins will be happening since this isn’t at all near an established retail district where people wander around.

It’s a “tech demo/test” for future stores that may be built but the only “customers” will be Facebook employees.

Oh, but they are. The average westerner (in the US, at least) is a $400 unexpected bill away from bankruptcy.

Also, Musk was not a founder of Tesla.

semiphemeral.com

Unions need more than a Discord to organize. They may need to compensate union leadership for time taken to organize away from their work duties, pay for events, pay for mailers and other communications infrastructure, and of course pay for professionals like labor lawyers.

No union will have much luck performing collective bargaining against Amazon without working alongside experienced lawyers.

These costs don't have to be huge, but they aren't zero.

Then don't travel to Taiwan for a few months.

Amazon in Seattle is a large enough org that they can "beta test" something like this with 10k+ employees that don't work on anything related to it, and get basically the same feedback as opening to the public.

Tell the CloudFront team to support adding custom HTTP headers to client responses (not the currently supported headers added to the origin requests), such as HSTS. CloudFlare and others already support this.

This is really something that needs to be setup/supported at the CloudFront layer (as CloudFlare and other CDNs already do) instead of S3. The danger is that somebody sets an HSTS or other security-related header on their bucket and breaks access for all other customers inadvertently for their customers that fetch from the S3 domain.

It seems unlikely considering their acquisition and later shutdown of Parse.