HN user
You don't believe Team Cherry's prior sales of Hollow Knight would reach the bar noted in the docs you linked?
Aside, your second point is incorrect. The SteamDB folks have a public write up on analysis of the preload system: https://steamdb.info/blog/steam-download-system/
I don't mean to support or refuse the author's main points or analysis, but you might like to know that the Chrome team is currently working towards shipping the Topics API. I have strong opinions about it but I will try not to editorialize.
My high-level understanding is that they're going to run an ML model over your browsing history (locally on your device) to build a list of "topics" that you care about. Sites you browse can use the Topics API to pull a set of these interests from the browser to show you "relevant" ads. Mozilla has taken a negative position against this standard.
In my experience with modest specifications, you can source servers from tier 1 vendors (Dell, HPE, etc) with 5 years of support for less than a 1 year commitment for the roughly equivalent AWS or GCE instances (without prepayment).
The monthly opex to house and power and cool those servers isn't _negligible_, but if you're doing back of napkin math comparing MRCs to Cloud you can just deduct the costs from their bandwidth charges that have been marked up 10,000%
Most of the stuff that makes the distribution different from Debian Testing is tightly coupled with Google's internal infrastructure and generally uninteresting (or unuseful) to users writ large. Just run Debian!
There's a reasonably good FAA sponsored app to help drone owners with this problem: https://www.faa.gov/uas/recreational_fliers/where_can_i_fly/...
Based on the pictured bezel, it looks like they've got three rows 3.5" 14TB SATA drives up front in 14th generation carriers. Best guess would be something like an R740XD2 which has 26 total drive bays per 2U.
Nobody at Google has a need to raise a ticket with some ops group in Bengaluru to partition a Kafka topic, renew a certificate, bridge two VPCs, or any of that type of thing.
Except when your team wanted to initially onboard with GOOPS and your request sat in Buganizer for 2 weeks waiting for someone to triage. Uh oh — we're turning down this service next quarter, you will need to go start this onboarding process again with its replacement.
Or when you needed quota in a cell where your product area didn't have Flex. Maybe you can set up a VC with your PARM? Does next week work for your launch plan? Hopefully they can do something for you!
Or when your logs access request sat in GUTS for a month because both of the approvers were on vacation and no, there's not an escalation path.
Or when you needed to change a firewall rule for a project your team inherited which for some reason runs on GCE. Make sure you bring your Ariane link when you open your request. Have ISE reviewed your code? No? ISE currently have a quarter-long backlog, so we're not sure we can grant your firewall exception.
None of these examples are contrived; the weight of the operational bureaucracy is staggering. It may well be that this stuff is felt more on the SRE/Security side around production launches than on the SWE side for experimentation or iterative development, but I struggle with the idea that Google is nimble.
I'm curious about what specific thing is signaling to you that your Steam password has been cracked. (I assume you mean brute forced?)
It's significantly more likely that you've been keylogged or phished if attackers are actually accessing your Steam account with passwords of that complexity.
Email access is required for self-service account recovery, but there are plenty of other documented methods:
https://support.steampowered.com/kb_article.php?ref=5421-QTF...
Historically at Google the exceptions fell into one of a few buckets:
* You used a modified client or client proxy (this was done for e.g. SSH)
* You used a remote-desktop protocol to remote into a machine with direct network access to the service
* The service got a wholesale exemption and was allowed through the firewall with ordinary IP ACLs
(descending order of impressiveness wrt the BeyondCorp philosophy and whitepaper)
Some of this is discussed in the "Non-HTTP Protocols" section of this paper: https://www.usenix.org/system/files/login/articles/login_win...
This is likely aimed at $device_manufacturer that wants to put a cellular modem into their device for remote telemetry (uploading a tiny payload every 24 hours for the lifetime on the device). There's a lot of attention in the docs towards "fleets" — they aren't expecting you to just buy one.
The specific rules for key sales are covered here: https://partner.steamgames.com/doc/features/keys#3
Do you have a make/model or link for the valve? I went all-in on Z-Wave and am similarly interested in controlling drip-lines.
Sharing without comment: https://twitter.com/GenePark/status/1196488999524802562
Depending on how much stock you put into the Steam Hardware Survey, it's worth noting that Nvidia still controls 74% of the market relative to AMD's 15%: https://store.steampowered.com/hwsurvey/videocard/
I also feel like graphics cards are one of those weird things that command a lot of brand loyalty, so it's probably going to take more than near-performance-parity to move the needle.
The cost of the Lidar hardware was down to $7,500 well over a year ago and may have come down even more in the intervening time: http://www.businessinsider.com/googles-waymo-reduces-lidar-c...
The iPhone 5C could be attacked this way because it didn't contain the Secure Enclave that shipped as part of the A7 chip. Attacks on devices with the A7 (or newer chips) would be novel.
The document shows in great detail that Kalanick and Levandowski were already working together closely before work on the truck even began.
2016-01-26 - Levandowski's last day at Google
2016-02-22 - iMessage chatter directly between Levandowski and Kalanick about poaching more Google employees
That certainly paints the "acquisition" of Ottomotto in August 2016 in a different light, no? It's also shown in the document that Levandowski was meeting with Kalanick and other Uber execs as early as June 2015, though it's harder to divine what was happening at that time.
Cloning? Nest has been shipping their basic outdoor camera since 2016 (which itself is not exactly innovative). The Ring device appears to have hit the market two months ago.
Agreed on the point that the deployment is only going to get easier over time.
Also individual Googlers who want to open source their work without going through the copyright assignment paperwork.
A lot of the projects bearing that disclaimer are passion projects done 100% outside of work hours.
Google's model allows SSH to "internal machines" over a set of relays that apply the same machine authentication and trust tier logic that's laid out in the papers.
So your workflow would still be supported, and it would likely be more secure than exposing SSH traffic to the internet at large.
The actual framing is WebSockets over TLS once the session is established and the latency is no worse than SSH over VPN practically speaking.
The protocol also supports session resumption in case your connection to the relays is briefly interrupted, but client support is buggy so it's been disabled for years (with few complaints)
The workaround functions by opening the privileged socket and re-executing the binary as an unprivileged user with access to the filehandle. Any background goroutines would exit with the privileged parent.
Also: please don't spawn goroutines during init(). There's generally a better time and place, and in the event that you justifiably need a package-level background routine you can spawn it on demand with a sync.Once.
There's a simple-ish workaround for the privileged port issue if you can't just use CAP_NET_ADMIN: http://play.golang.org/p/dXBizm4xl3
The namespace issues are unfortunately a lot tougher to address.
We're going to make sure that the Secure Shell app for Chrome, in one form or another, continues to be usable on Chrome OS.
(I'm one of the current maintainers and we're already all over this transition)
That's not a correct interpretation either; it's noted in the linked article that GCE uses a proprietary VMM instead of QEMU which itself was "ripped out" of the standard KVM+QEMU arrangement.
I probably would have chosen gentler phrasing.
I've never had a LinkedIn account, and I've opted out of receiving "<Person> wants you to join their professional network on LinkedIn!" emails, and yet I somehow manage to get 2-3 messages from LinkedIn per month.
https://twitter.com/darylginn/status/590664399041519617 rings true.
Driving from my friend's studio 3rd floor walk-up near AT&T Park to Mountain View convinced me that drive is crazy.
That's analogous to visiting Carlsbad from your place in PB. I mean, except that Carlsbad is worth visiting ;-)
The norm seems to be living and working in the city unless you're attached to a large megacorp with a fleet of shuttles, or else you end up on Caltrain.
I used to commute on the trolley from La Mesa to Downtown and it was great. But if you don't live on one of the trolley lines, SD public transit is dreadful!
I spent years between a few healthcare startups, and I feel like there is a strong scene not only for Biotech but also in Communications and Defense. Speaking somewhat from experience: I feel like the problem is that the companies in those spaces are giant, lumbering, unappealing employers for young people. It's really hard to pitch an energetic new grad on writing Java for SAIC or Qualcomm.
Biotech stands to be an exception, but despite a strong presence by a medium-large number of companies, there just didn't seem to be enough jobs.
As a San Diego native who relocated to the Bay about five years ago: the income difference scales up faster than the rent difference. I've put away a lot of savings on that margin.
Now if your intent is to own a home, well, that's another story altogether. I'm generally priced out of even the cheapest areas.