I actually did. The previous owner could not open it because the front panel got disconnected from the electronics at the inside and he didn't bother to look further.
I always loved Todoist but wanted a Kanban board to organise my day and week. So I created https://kanban.ist as an alternative client that lets me do this. It’s stateless and talks to the Todoist API directly, meaning tasks stay secret. Todoist released their “Boards” feature a few years after this but they only allow you to create a Kanban board for a single project, which didn’t work for me.
Australia has strict KYC and AML laws that means many financial institutions and fintech businesses will request drivers licences and passports as a part of user registration. This may well be common all over the world but I’ve had to upload a photo of my drivers licence to one service or another twice in the last month.
Some bars also take a photo of your driving license, I found that very weird but didnt say anything because I didnt want to cause any fuss going with a group.
This happens at a lot of places in Las Vegas, too. I don’t give any business to places I can’t prove my age, walk in, and pay with cash without a record being made of my whereabouts.
The real issue I find is that your data is being handed off immediately by the bar to a third party provider, with whom you have no business relationship. The moment you hand over your ID, the bar is uploading it, and now the data is entirely out of your control. They could publish your home address (if you’re foolish enough to have the location where you sleep on your ID card, which is effectively public record) and you’d have no recourse whatsoever against them when people show up at your house, or at your hotel while on holiday (because the hotel bar published/leaked a name+location+timestamp).
At the least, it’s a major privacy violation; at the most it’s a physical safety issue.
Make a fuss. That shit’s absolutely over the line. Take the whole group somewhere else.
From my POV as a former bouncer turned software developer, causing a fuss (assuming you mean in the moment) isn't the right move.
If you blow up and start yelling at the bouncer (who will get fired if he doesn't scan your ID), you're taking it out on someone who can't change the policy, and you're going to sully the entire evening for the rest of your group. Contact management, absolutely, but causing a fuss at the scene is less than effective.
And there is a flipside to the physical safety issue - there were two stabbings (and countless other attacks) in the club I worked at, and we were able to positively ID the attackers within ~30 minutes of the incident, which led to their arrest hours later.
Violating the privacy of 100% of patrons, putting them ALL at risk, to be able to catch the small percentage of violent people is not an acceptable trade-off, whether the group is 100 people or all of society. This is why we have the presumption of innocence and the 4th amendment. Private businesses can act otherwise, but they’re douchebags if they do so.
Showing ID doesn’t make anyone safer; indeed your bar violated everyone’s privacy and on multiple occasions someone STILL got stabbed. Worst of all options. It makes everyone less safe.
Privacy is a basic right.
Don’t give a single dime to organizations that act otherwise.
Why can't this just be centralized? upload KYC once and that one service verifies to other companies that you're legit, compared to uploading KYC to 33 different websites.
Correct. It’s not always this simple though, you also need an IAM profile that the EC2 instance can assume with the required permissions. Depending on how you configure your NAT Instance/Gateway, you may also need to whitelist the ssm service.
It might be unrelated but this page was mentioned in a fairly highly upvoted comment on a recent top story here. Dan Bornstein is also a relatively well known engineer.
I agree and just want to add IAM to the list of AWS Lock In services. We provisions environments almost entirely using Config-as-code tools (packer, ansible, terraform) and generally have a good blueprint for what an environment looks like and the parts I’ve had the hardest time thinking about migrating to another cloud provider is all the IAM rules that magically give hosts/services the ability to talk to other services.
I'm not sure about GCP, but Azure does offer role-based access[1] which gives you similar resource authentication magic to what IAM provides. The definition formats[2] even look fairly close to their IAM equivalents.
It's used in combination with Azure Active Directory, so the modality isn't 1:1 with AWS. But Managed Identities[3] is a feature that's rolling out across Azure which simplifies the model a bit, since it negates the need to create service principles in AAD beforehand.
IAM is simply one of AWS's killer features. It's just a service that's so good it differentiates itself from the competition. Lock-in based on quality is not the sort of lock-in that I'm most worried about, because it's very clear what I'm getting in return for it. The alternative to using IAM to begin with would be to commit to work comparable in scope to that required to migrate away from it in the future.
