flyt
flyt on Hacker News
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.
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.
Posted by
flyt on Sunday August 04, 2019 @01:33PM
from the washingtonpost.com dept.
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.
IPv6 is provably faster, especially for mobile clients. iOS 9/10 also prefer it and the App Store has begun requiring apps to work on full v6 stacks, meaning any end points in AWS will require 6to4 somewhere.
This is a massively important release, and is basically a complete reboot of the SNS SMS product. Before it was limited to something for your backend services to send messages to service administrators, but now it's a fully featured Twilio-like SMS gateway.
Anybody sending 2FA or other SMS messages should give this a look.
It doesn't do any good to point the finger at your vendors when your service goes down; that data isn't useful for your customers. Never forget the lesson of
http://www.whoownsmyavailability.com/
us-east-1 and us-west-2 pricing is locked to each other. Typically the power differences are related to the cost of power and transit/peering, not the capital of building the facilities.
Northern Virginia and Oregon have (generally) cheap power and cheap connectivity to anywhere in the world, with plenty of peering opportunities. In a developing country or with more expensive infrastructure (Mumbai, Tokyo) costs will be higher to get power and pull in fiber to peering locations with enough capacity to supply a provider of Amazon's size.
Unfollowing is just as easy as following. If somebody chooses to follow an account that ultimately posts too many ads then they can quickly and painlessly unfollow.
The grey area is sponsored content that doesn't identify itself as such and is incredibly common on celebrity twitter/IG accounts. As long as the relationship is clearly identified (and not with an #ad hashtag buried in a pile of other hashtags) I think it's ok.
All publications of a certain size pre-write obits. This isn't unique to the Times.
No, and this isn't what Facebook did internally. "Lockdown" was more of a way of thinking about the problem and cover for working longer hours rather than literally locking the doors to prevent people from going home.
I will. My system runs lots of closed source code already.
Hi Sneak! As you're no doubt aware, people change over the years. They learn from mistakes, improve how they live their lives, and become better over time.
Companies tend to be the same way, learning along the way and maturing, especially when it comes to business processes and risk-related parts of the business.
It's entirely possible that the Dropbox of 2016 isn't like the Dropbox of five years ago in many concrete ways. For example, they could have hired new people, improved testing and release processes, and become more serious about engineering discipline.
Many startups early-on make dumb mistakes and go on to great success and professionalization, but we should have both empathy and forgiveness for them in the long term. Dropbox has recently demonstrated a focused attention on large scale, challenging engineering projects (building a replacement for S3 in-house from scratch, writing kernel extensions, etc) and a reasonable observer might conclude that they've learned from the mistakes of 2011.
It doesn't send any personal data back to WhatsApp/Facebook, all it needs to work is a phone number.
It hasn't even launched yet; won't be out until later this Summer.
I doubt it. The sharing models and overall experience of Snapchat sharing and Twitter are radically different and this doesn't change it in a meaningful way.
I downvoted your comment but please keep in mind that Facebook is a large company that needs to lobby the federal government on a variety of issues, which necessitates a presence in DC.
Also, the Secret Service employs some of the smartest and most capable people in the federal government. Any company is lucky to hire ex-USSS agents.
Using these two points as evidence that humanity collectively has "no privacy" is not only false on the surface but dishonest when closely examined. There are valid critiques of both the US Government's use of the Internet and, separately, Facebook, but these two are not intellectually honest.
To the contrary, pushing back dinner is a savvy way to serve less meals. Most employees need to get home to family or other obligations. If the food is served at 6PM then many will eat and leave, which negates the benefits of employees staying later. Serving at 7PM means serving only those that can stay later, which is likely a smaller group.