maxgashkov

Still less expensive than NAT gateway though /s

This is correct: https://www.post.japanpost.jp/int/ead/index_en.html

I think they're still PaaS and not IaaS. So yes, you can build fully-fledged app with them if you're willing to change your engineering paradigm and not use any of the usual arbitrary computing workloads.

It has 'drag multiple' functionality -- you have to start dragging one icon and quickly tap on several others to grab them also. Personally I don't have the finger dexterity (or maybe understanding how this actually is supposed to work) to reliably perform the gesture, so I resort to dragging one at a time :(

Worked at one place for 16 years. Never been married, but now I know what a divorce feels like.

So yeah, fuck that family bullshit.

Large scale commuting adoption seems unlikely. Usually JR sells commuter passes at approximately 50% of price of daily roundtrips between destinations, for Nagoya-Tokyo on current shinkansen this will come to ~$2.5k/mo. No way this is going to be approved by companies even for middle management positions.

> In Japan, the traditional salaryman workweek is 6 days

It seems it's starting to change. Currently I'm leaving the company which indeed has 6 days work week (with the 6 hr Saturday) and literally every opening I'm seeing right now is 5d.

Maybe I'm biased though as I'm looking for jobs in IT companies or departments.

Zero Trust is not really applicable here. ZT is about not implicitly allowing someone elevated access just because they have access to network and requiring explicit grant based on the identity and other rules.

Fastly's downtime seems to be caused by an automatically generated config that got deployed in production as a result of change requested by a legitimate customer.

This happened to CF in its early days and I really doubt that ZT had anything to do with the fact that they do not have this kind of problem anymore. It's probably some sanity checks before they deploy updated lua scripts to their fleet of nginx's if anything.

It's a long standing tradition from older forms of chat software (IRC, ICQ and so on) and yes, it seems endemic to Russian speakers for some reason. I always explained it to myself that it saves time and also by the fact that to type ":)" in Russian kb layout you have to press Shift+6, Shift+0 compared to Shift+;, Shift+0 in US layout which seems a bit more cumbersome.

Anyway, this is going away as most of the younger generation just uses emoji instead.

Yes, I've read this. Unfortunately that's not enough if you have 3rd party themes or plugins installed.

Some commercially available themes do it during installation. I was surprised to find that also as this contradicts every instinct I have as a web developer.

While WP's ecosystem is nothing less than impressive, but I'm still in shock to this day, how cumbersome is site migration.

For me and I guess for many other engineers it's quite normal to develop a site locally (or at least on a staging non-public domain name) and then move it into production under the final name.

In Wordpress, the site name is baked in all over the place — in config, in database, in generated stylesheets and so on. In theory, this should not be like this (if you use barebones install w/o plugins), but then you buy a theme or some less-than-perfect plugin and boom, you need a separate plugin just to handle migration (which may or may not work 100% of the time).

APIs are not what's hard IMO. Creating a layer simulating S3 API is pretty straightforward.

Designing and implementing a highly available and resilient storage solution on-prem is much more harder task that will take 99% of time & budget to do properly compared to a compatibility layer.

My bank did that ~10 yrs ago, it was really neat, but unfortunately it does not scale well.

I do understand that, but there are services that are still billed for when ‘spun down’. To stop getting the bills they have to be terminated.

The solution seems to be to implement ‘emergency stop’ when whole account is put to pause but no state is purged. And then you’ll probably have a week or two to react and decide if you want larger bill, salvage the data or just terminate it all.

That’s extremely hard to design, at least with the current state of what AWS bills and does not bill.

Example: let’s assume you’ve set the cut-off budget too strict, spun off another shard for your stateful service (DB for example), it received and stored some data during the short window before some other service brought whole account over budget (i.e. paid egress crossed the threshold).

To bring VM and EBS charges to 0 (to implement your idea of ‘shut down everything’) AWS will have to delete production data.

While it may be OK when you’re experimenting, it’s really hard to tell in automated way.

So, to fully comply w/o risking losing customer data, AWS will have to stop charging for not running instances and inactive EBS volumes which most definitely bring on many kinds of abuse.

—

There may be some other way to do this, maybe mark some services expendable or not, so they are stopped in the event of overspend.

We're a small export shop based in Japan. It's becoming increasingly difficult to find containers to ship even to APAC region. 'Difficult' = not just expensive, I'm talking we're not able to get on the ship period, no matter how much we'll pay.

So, for us service is deteriorating because we're not able to fulfill obligations and lose money. For our customers service is deteriorating, because they are not able to buy goods that will be delivered in a timely fashion.

This goes on for 3-4 months now, and this is definitely a problem, even if it doesn't look so from outside.

For fucks sake it still requires the phone to recognize the fact that you're wearing the mask to allow AW unlock—and good luck if the mask isn't the one Apple trained this shit on or lighting conditions are not optimal.

I do want to look the manager who decided that in the eye. What serious attack vector is this supposed to close? Somebody sawing your hand off and unlocking your phone? You have much bigger problems then.

It seems that this process will be incredibly stateful in the encoder component.

Most of codecs targeted at low bandwidth for mobile streaming track scene changes and if you make chunks in a naive way (split via I-frame borders and encode 'em independent of each other), when reassembled final video will look choppy due to broken scene change relations.

So after encoding each chunk you will have to carefully save relevant parts of encoder state and reuse it for the next chunk. Seems doable, but tricky to get right?

5.1. No keyboard shortcuts. Not even for a 'New Note': https://github.com/standardnotes/forum/issues/1119

The refund process is not automatic either, be prepared for a back-and-forth with customer support if you want to cancel a subscription.

It seems to me that author of the article implies that Cloudflare treats Workers' IPs as having much higher reputation (threat score in CF's terms) than any other IP on the Internet by default. This allows worker to bypass bot protection as it does not trigger at all or only when zone is configured to trigger on all requests (under attack mode).

Could you comment on that?

Yep, gonna stay on that sweet 5.14.23 till the end of times.

Don't get me started on hCaptcha! I've spent good 5 minutes yesterday trying to guess what the 'boat' is and is not according to its moderators.

> Can pure DNS site filtering really work these days? I have to imagine more and more of the internet is behind cloudflare / cloudfront / etc, and you probably can't block/grant access to a single site without catching a bunch of unrelated ones as well.

You're thinking about IP filtering. When site is behind Cloudflare/Cloudfront/... it _may_ share an IP with some other site, but it will most probably have a distinct DNS name that can be filtered upon during DNS resolution.

pi-hole/nextdns do this quite successfully for adblocking on network layer.

You're subjected to this on any edition and on any hardware, no matter the price. There are deferment options, yes, but now way to disable rebooting for update when they run out.

Why not? Lawful aspect aside, Apple states the conditions in their ToS upon which the app will be accepted and will stay available in their ecosystem.

It may seem unfair and counterintuitive, but I suspect that there is non-zero portion of Apple users that happily subscribe to this model.

What we're discussing here has strong political flavor, but this isn't the only case of Apple censoring Telegram's content. For example, all even remotely pornographic channels have been banned in native Telegram apps on iOS for years. Somehow Durov is silent about this (probably because you can't score some cheap publicity over defense of pornography).

His double standards aside: parent buying his child an iPhone is probably much happier due to this policy than not.

Yeah, but those channels are for effectively doxxing LEA workers in Belarus (and people affiliated with them).

While sympathetic to the protest movement there I'm feeling really conflicted in regards to its contents and if channels for coordination of bullying should be accepted on any platform, whatever the reason.

I'm not a parent but all practices described in the article infuriate me as well. I'm not sure why should I try to deduce if the next app I will install uses any of them -- and you don't even need to lock down APIs to prevent this.

All you need is a simple 'complain' function in App Store that will trigger a review by human with following expulsion of offending app (and probably the developer account too).

Disabling JS is a conscious decision. Using wheelchair is not — you cannot just flip a switch and walk once your spine is fucked.

> I want the government to act like a government.

That's a valid point, but: the US will probably require membership cancellations to not suck eventually. EU will too, maybe even earlier then US.

Japan? Not likely. Here the enterprise is king and individual is not a priority.

Russia? I don't even want to begin with this one.

And that's only 2 localities I had experiences living in, Apple & App Store probably operates in dozens of completely different jurisdictions, brining more or less the same rules everywhere.