nickw444 (u/nickw444)

nickw444 commented on Chrome 68 will mark all HTTP sites as “not secure” security.googleblog.com/2... · Posted by u/el_duderino

jasonkester · 8 years ago

Terrible news.

So much work for so many people to update so many old websites that will see absolutely zero benefit from serving content via ssl.

I have an old travel blogging site with a few hundred thousand posts in read only mode. Thinking about how much work it was to upgrade my other sites to https, chase down and work around every http request in the code base, purchase and install certs for silly things like cloudfront that you wouldn't think would suck away two days of your life.

I'll probably just let the site die in July. It doesn't make money, so it's going to be a tough decision whether to dump thousands of dollars of otherwise billable time into upgrading it to accommodate google's silly whim.

nickw444 · 8 years ago

You could always consider a free service like Cloudflare which can sit in front of your site and serve the site via SSL to your customers. Yes, it's still unencrypted between CF and your site, however it would resolve the poor "insecure" UX.

As a bonus, CF also has functionality that can re-write http uri's to https.

nickw444 commented on Slack is down status.slack.com/2017-10/... · Posted by u/peterlk

nickw444 · 8 years ago

Even their status page is occasionally coughing up 500's...

nickw444 commented on Reverse Engineering a 433MHz Motorised Blind RF Protocol nickwhyte.com/post/2017/r... · Posted by u/wolframio

j45 · 9 years ago

Nice write up! I wanted to do this in my place and have one less reason not to

nickw444 · 9 years ago

Thanks, feel free to hit me up on Twitter (@nickw444) if you happen to have any questions :)

nickw444 commented on Reverse Engineering a 433MHz Motorised Blind RF Protocol nickwhyte.com/post/2017/r... · Posted by u/wolframio

ReverseCold · 9 years ago

This guy did it the hard way, I automated my lights in a similar way with simple command line tools (./listen <pin> to get code and ./send <pin> to send.)

See here: https://home-assistant.io/

nickw444 · 9 years ago

Hey there, I'm actually the author of the linked post. Yes whilst you're right about doing this the hard way, this wasn't really what I was wanting to do.

In the post I actually outlined that I had actually captured enough data from a handful of remotes that I could have replayed these captures to control the blinds (and I even had a rig set up to do this).

But that's not what I wanted to do. I was interested in working out what was happening with these remotes and being able to generate as many arbitrary remote codes as I wanted.

Going the step further to reverse engineer the protocol is something I did as a learning (and fun and challenging) exercise. I've definitely picked up skills through this process that I can apply in similar projects later down the track.