becauseiam

Owning property or land in Japan does not give you right to reside within the country and you will still need to get some sort of visa in place in order to move in.

IPv6 is not a first-class protocol on AWS, but it is absolutely doable for most scenarios. It still requires having something of a dual-stack network in place (you definitely can't have a v6 only network of anything meaningful).

This kind of growth is starting to make me be concerned as a customer - app performance and latency have deteriated over time, and most importantly customer service has also changed. Scaling good customer service for an effectively free product whose revenue currently derives only from overdrafts and very minimal fees from over-use is going to be very challenging for a bank not yet profitable.

The Instagram account @shibuyameltdown has been covering people in Tokyo being passed out in public areas for a while now.

For me at least, doing an SMC and PRAM reset appeared to resolve the issue of the battery draining heavily during sleep.

Of course it's going to be underwhelming - the smartphone market is completely saturated, and the margins on technology advancements in the space are diminishing more and more over time. People are holding onto their devices for much longer these days and the mad rush to get the next best thing is waning. Personally I think this is a good thing as the market is reaching some sort of sustainable, stable ground and no longer in a huge "race to the bottom" as it were.

I agree - jQuery has done a lot to help inspire what querySelector and fetch are today (among many other things). The only cause for concern I have is what might frameworks in current vogue might do to influence standard APIs of the future.

Let me break down exactly why I think the language in what appears to be a lawyer-driven PR pot-bashing is so terrible, because if your plan was to go back to internal G+ with "someone on HN said a lawyer wrote it" little will probably change.

> Established GCP customers...

> Online customers with established payment history...

What exactly qualifies as being "established"? In the first example, additional stipulations around billing arrangements are imposed, but in the latter it remains unclear.

> ...review for flagged fraud accounts...

> ...event that fraud or account compromise activity is detected...

You gotta stop using the f-bomb like that. This piece is supposed to be a follow on to a story of a customer who apparently was conducting completely non-fraudulent activity within their account. Your copy should, like your culture, assume "innocent until proven guilty". Saying something is "flagged for fraud" in a PR piece breaks that rule.

> We will provide ways for customers to pre-verify their accounts with us if they desire...

Sounds very passive-aggressively optional. Nor does it tell me what I actually gain here, or even a hint of what might be involved for verification or how potentially simple or easy it may or may not be - do I need my counsel to post via registered service on company letterhead confirmation of my organisation's official trading details, or do I click an link in an email?

> There are also steps that customers can take to help us protect their accounts including...

The word "protect" is suitable if you were a bank, and you wanted to encourage customer behaviour to prevent them being victims to fraudsters. But you're not, so really this language is suggesting customers need to "protect" themselves from your algorithms and automated systems, which is kind of inappropriate to be saying.

> if you can encode it, of course

And here lies a really big issue I have with modern codec standardisation and development - it will be unfortunately many years to come until we see sufficient optimisations to make at a minimum realtime encode and decode of AV1 feasible. Ten years ago when Moore's law was actually a thing this can-kicking may have been acceptable but now I sincerely believe codec development needs to be more iterative, and to consider hardware optimisations (in particular, having even a HDL variant as part of reference codec) from the initial outset.

VVC I suspect will repeat history in many ways, by virtue of how these codec standards bodies operate.

BBC's Horizon covered this back in 2008 with an episode titled "How to kill a human being"[1] where the show aimed to find the most humane form of death penalty. When supporters of the death penalty were asked if they would consider using hypoxia they dismissed it, saying words to the effect of "so what if the condemned are in a bit of pain?"

[1] https://www.bbc.co.uk/programmes/b008rdyh

The WHOIS blackout has already started, I recently registered a domain with a non-European ccTLD, but with Gandi for the registrar. The WHOIS reads:

   Administrative Contact:
      Not displayed due to GDPR

46.137.0.0/17 which that address falls under is not part of the allocations for CloudFront infrastructure, but for EC2. I suspect their "CDN" is just EC2 instance(s), probably fronted by a load balancer.

It's not just patent holders who care. Harmonic sells products where a large portion of the cost is derived from licensing codecs like AVC and HEVC. One of their contribution encoders[1] has separate software licensing for a variety of subsampling ratios.

1: https://www.harmonicinc.com/media/2017/06/Harmonic_DS_ViBE-C...

> Did AWS forums start requiring an account for read access?

No but if you timed out from a session with your account through the console, you might see something about not being signed in. Clicking the "log out" button (or hosing cookies) should rectify it.