Help needed: if you know what you’re doing with Shelly devices, we can’t get switching working with the physical switch. Digital is all good, but physical isn’t changing state. Suggestions?
Further, we’ve got the same problem with both Shelly units so I’d be surprised if both were faulty as suggested in this thread (similar symptoms): shelly-support.eu/forum/index.ph…
Fixed! Not my work (licensed electrician only), but this is the end result and it works *perfectly*!
It’s beautiful 😢
This is precisely what I was after: digital and physical controls perfectly complimenting each other with neither suffering in the presence of the other. Will share a more full rundown of the room once work is complete but for now, the Shelly 1 just rocks 😎
For those asking, the explanation from the electrician was: “Moved the LED on the Zen [light switch] from the load side of the manual switch into the output on the Shelly”
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The Pornhub story regarding age verification shows just how hard privacy-preserving identifying verification is. Even when everyone agrees on the sentiment (nobody is saying kids should have access to porn), there’s no consensus on the execution. 404media.co/pornhub-is-now…
It took me a few seconds to VPN into Texas and capture these screens. It takes someone in Texas a few seconds to VPN into California and *not* see these screens! It costs a few bucks a month for a good VPN with loads of exit nodes around the world, placing you where you want.
I suspect that factored into Pornhub’s decision - the knowledge that they can satisfy a state law whilst not posing any real barrier to paying customers. If someone is willing to pay for porn, surely they’re willing to pay a lot less for a VPN to access it?
Was confused whilst doing my live stream just now why there was a sudden spike in DB usage on @haveibeenpwned. Turns out it was related to *dropping* this constraint:
ALTER TABLE [dbo].[Domain] ADD CONSTRAINT [CHK_DomainName_Pattern] CHECK (([dbo].[IsDomainValid]([DomainName])=(1)))
We'd decided a constraint that calls a function on every insert of a new domain was unnecessary; all it did was validate that the string adhered to the correct pattern, but because we controlled the upstream code, we could do that before it even hit the DB.
Hi folks, yes, I'm aware of this. I've been in communication with the Internet Archive over the last few days re the data breach, didn't know the site was defaced until people started flagging it with me just now. More soon.
This was a very uncomfortable breach to process for reasons that should be obvious from @josephfcox's article. Let me add some more "colour" based on what I found:
Ostensibly, the service enables you to create an AI "companion" (which, based on the data, is almost always a "girlfriend"), by describing how you'd like them to appear and behave:
Another cool little @Cloudflare thing that snuck out recently is this very simple security.txt creator:
It's a simple form-based configuration that takes the basics of a security.txt file in the following interface:
Because @cloudflare sits in the middle of the traffic, they can then intercept requests to the appropriate path and serve up the file. Here's one I just created: troyhuntsucks.com/.well-known/se…