1,898 karma · joined February 27, 2019
Second: Just because the snow stops falling doesn't mean the problem goes away. The snow can take a couple of weeks to melt (essentially until the next rain, or a hot enough day), so stopping and waiting for nature to resolve the situation on its own would shut down the city for a month or so every year.
"Note that while pulls from ECR Public do work from outside AWS, they are rate limited if not authenticated with an Amazon account, and you should generally use the Docker Hub addresses if you are pulling from outside AWS. Please see the ECR Public quotas documentation for more about how limits work with ECR Public.
If you are an AWS customer, pulling Docker Official Images from ECR Public offers several advantages. ECR Public is replicated across all AWS regions, so pulls are local to the region you pull from. This helps ensure lower latency for requests and ensures that all your resources are in the same failure zone, which is the recommended architectural pattern."
Another is that there aren't many European companies that are internationally dominant. Customers and partners get banned from Booking.com (a Dutch company), so there's that.
I don't know what happens to sites that are collecting links to videos that were not made by the site author, because clearly the author can't modify other people's videos and can't rehost them without violating copyright. But a human judge wouldn't be fooled by it in this case :)
Also note: the law requires captions, not Hebrew captions. The captions must match the spoken language in the video.
Israel did not invent its own accessibility standard. The law simply enforces "Israeli Standard 5568", which is a PDF that links to WCAG 2.0 with a short figure that changes certain compliance levels (e.g. captions are classified as Level AA instead of Level A).
https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#qr-medi...
Failure F8 seems relevant to the loophole: https://www.w3.org/WAI/WCAG21/Techniques/failures/F8.html
1. Super easy to use actions & internal UIs, that allow end-users to run things without following Confluence rituals/SOPs. So many things that used to be "ask an engineer to do this when they have time" are now just buttons or interactive screens. But engineering still has control: anything that can can an incident or that is hard to reverse, Airplane automated the approval workflow so that a qualified person can approve it - whether it's a task or a button in an internal UI. Also, several scheduled runbooks/workflows that we could have set up a system to run - but why do that (+ maintain it forever) if it takes 20 minutes to configure in Airplane?
2. Cannot introduce more risk than it reduced (because we _did_ have risk from people doing these things by following written procedures). Everything gets logged, critical things are reported as Datadog events + Slack messages, our tasks and UIs exist in multiple environments (and go through source control) so we can test them like real software. All tasks run on _our_ infrastructure, using our IAM roles (which we've worked with Airplane to get to their minimal form, where they can't touch anything non-Airplane'y - and they changed the default installation to match, so if you start using Airplane you'll benefit from that too) and security groups (which reach dedicated load balancer listeners that can validate the requests). We have set permissions to be as strict as Airplane allows, connected to Google Workspace user groups (and so audited regularly).
Obviously whenever doing Build vs Buy: we could have built this. We could have also soldered our servers' circuitry on our own. But if someone needs something quick to automate their work, it takes less than an hour to set it up from scratch now and it's all straightforward.
> Yes, thank you for making my argument for me?
Agreement isn't "making your argument for you". It is agreeing with your opinion. When discussing things with people, you often agree with things that they say - hopefully.
(I never used IPFS.)