I haven't owned a keychain for many years now. After renovating our house, we installed a Yale Doorman. It's the best $300 investment I've done that I can think of:
- Don't have to carry a keychain at all anymore
- I can give strangers (think AirBnb, or cleaners) time-bound access codes
- I can remotely unlock/lock the door for someone if they need immediate access
- Kids can get home without a key - Kids losing their key not a worry anymore
- Work office is keyless too (xlock)
- We always keep a small 9V battery outside in case the battery goes flat
It was after a painful deadlock situation that we initially retro-fitted an electronic lock into the old front door which we carried over to the new door once we renovated the entire floor.
I've always been tempted/curious to adopt a sort keyless of approach. I dislike carrying keys...and have had to carry (what to me feels like too many) keys always throughout my life. But without really researching the option you referenced, i have fears about failure modes for this type of keyless kock. For example...
* If/When the battery dies, does the lock default to locked setting? I assume so, but how annoying would this be?
* Being a privacy nut, does the lock come with a pre-determined code, or can you generate your own? I assume you should be able to create your own, but figuried I'd ask.
Instead of answering my questions, if you have an online reference that you might have used to decide going this route, would be great if you could share. Thanks!
> * If/When the battery dies, does the lock default to locked setting? I assume so, but how annoying would this be?
Typically, the home locks are just actuated mechanical locks. So the lock will stay in whatever state it was when the battery died. If you want to get into commercial-grade locks, there are magnetic locks that can be configured to fail open or close on power loss.
Anyway, the battery is not a big deal. I have a Kwikset lock with a ZigBee module, it runs on 4 AAA batteries. I switched to Li-ion rechargables several years ago, and they last for about 6 months between recharges with moderate door use. It's even longer if the lock is not used often.
And the lock starts beeping annoyingly after opening/closing when the batteries get down to 30%, giving you plenty of time to replace them.
> * Being a privacy nut, does the lock come with a pre-determined code, or can you generate your own?
You always can set your own combinations. And there are biometric locks.
The Yale x Nest was my entry but after a few years a few complaints.
It auto locks after each use but no confirmation the door was closed and secured correctly.
The Yale mentioned above will gladly auto-lock with the door still open and it will report as locked in the app. Not to bad if you know you closed the door but by just looking in the app someone might have left it open and it "locked" itself.
It will say it wouldn't lock, if say the door was partially closed and the bolt couldn't move.
I'm assuming another component needs to be in the door well to detect the bolt.
Anyone know any consumer level smart devices that do this?
The Yale Doorman has two metal dots on the outside you can push a 9v battery against to power it. So if battery runs out, you can power it from outside temporarily to get in.
I found an approach that I liked was a mechanical combination lock — all the advantages of digital combination locks (can set temp codes, change codes, no need for keys etc.), except for the remote activation, but I never have to worry about batteries or power.
I bought a house with an electronic front door lock. One day a few months later I used the wrong code (a few times I guess) and I got fully locked out. I don't subscribe to the $60/month service that could have remotely reset the system so I had to get a locksmith to break me in.
After that I replaced it with a plain old mechanical lock. Never again touching any smart home crap.
I'm sure I didn't use the wrong code three times, something must have happened the 2nd/3rd times like a key didn't get pressed hard enough to register. But regardless, the lesson is there's a bunch of possible failure scenarios you won't think of.
>"All women are whores. Sorry to break it to you." -Kyle Benzel, Sept 28, 2022, Hacker News, https://news.ycombinator.com/item?id=33010046 (log in or create an HN account, and set showdead=true to view the evidence)
That's exactly why I directly quoted and linked to your own highly inappropriate and inaccurate words, that you posted here on Hacker News. There's no denying that you wrote them, it's on your permanent record.
So explain exactly what you meant when you wrote "All women are whores. Sorry to break it to you."
It's appropriate for me to quote your own words back to you and ask you about them, which is my right, because you viciously and personally insulted my mother, as well as your own mother too, and also four billion other women, including trans women, because they are truly women too.
As misogynistic, bigoted, idiotic, inappropriate, hateful, distasteful, and false as your own words and actions are, you might believe you have the right to call your own mother a whore because you of all people would know, but certainly not all other women, and definitely not here.
You should keep your attacks and accusations a private family matter, and get family counseling for your mental illness, instead of inappropriately airing your problems here publicly on Hacker News for all to read, no matter how "sorry to break it to you" you insincerely claim to be. If you meant that non-apology apology, you wouldn't have posted anything -- it just proves mens rea, your awareness that your actions were wrong.
And you should be sorry you posted it in the first place, so you owe all women a sincere public apology for what you insincerely publicly said.
Why did you call my mother and your mother and all other women whores in public, and do you apologize?
> get counseling for your mental illness, instead of inappropriately airing your problems here publicly on Hacker News for all to read
You should take your own advice. His comment from over two years ago may have been unpleasant, but you hectoring him for it now, apropos of nothing, is downright creepy and indicates an unbalanced mental state.
I have considered this route, especially with NFC keys becoming more widespread (ie, unlock door with Apple Watch). But ultimately my number keypad lock works just fine.
If I do upgrade, possibly use the system from Ubiquiti since I already have most of their equipment
From a technical point, you are absolutely correct. From a developer heavy business, it's a little more complicated.
If Rust had a good full-fledged web framework, it would enable more developers to justify why the business should use Rust. The culprit is that it would require a heavy education budget, but it would in turn enable the business to allow using Rust for other parts of the business which could benefit from Rust, e.g. middleware, small components, CLIs and systems programming in general.
Having a little bit of Python here, a little bit of Go there and a bit of Java elsewhere can become chaotic. There is a huge benefit for a small company to only have 1 programming language everyone agrees on using.
If your goal is to use just one language then why wouldn’t you pick JavaScript (likely Typescript), C# with Blazor, Go with templates or basically anything on the JVM? Rust is a bad general purpose language in my opinion, and its performance isn’t actually good enough compared to C# to really justify the added headaches. I say this as someone who really, really, doesn’t like C# by the way.
If your goal is easy web development, Django, Ruby on Rails and Laravel are frankly going be extremely hard to beat. I prefer Go with templates, but that’s still much worse than those options.
Here's a concrete scenario for you:
Say you are in a team of 10 developers with a huge codebase that has accumulated over 5+ years. If you're new in the team, and you need to understand when a specific HTTP header is sent, or just snoop the value in the payload you otherwise wouldn't be able to see.
Just learned about Kubed here, but I’m a longtime user of k9s and I’m keen to try out Kubed to see how it compares. It will be interesting to see if there are any workflow benefits to be gained from Kubed.
Grepping at at runtime, if you can call it that, is also very powerful. If you have a binary, either your company or a third party one, but don't have the source code easily available, I have used the `strings` program from GNU binutils which shows tokens in binary code, e.g. hardcoded URLs, credentials and so on. It can also be useful for analyzing certain things in memory.
There has been a lot of good mentions so far for permanent solutions on storing secrets securely..
On the other end, I'll chip in on https://onetimesecret.com/ for quickly sharing a secret. It will only allow the consumer to view the secret once, after that, the secret is no longer available. You can also set up One Time Secret with your company domain (self-hosted, I presume)
As author of SemanticDiff, I am obviously a bit biased. But Wilfred, the author of difftastic, found the analysis to be "pretty even-handed" [1], so I think it should be somewhat fair.
Good reflections. It kind of remind me of the big data era where everything needed to revolve around big data.
However, what happened is that it became apparent that not everything needs to be big data. Business needs will shine through as they always have and dictate what is truly important.
I'm not afraid of the wave of gen AI. Think of it as the new power tool that just came out that everyone's currently talking about. You'll add it to your toolbox because you don't want to be obsolete. It'll blend into everything else once the hype wave is over.
reply