Just because, I’m gunna try to blog daily again. Obviously, I’m cheating, loading multiple blogs in at once and having them post automagically, but still. Something for every day. Even if it’s something short like this!
Bodies are stupid. Soon, I’m going to have surgery on my foot, because apparently nails sometimes curl and cut into the nailbed. This is pleasant… \s
Watching all the remixes is so cool. It’s amazing what humans are capable of
Apparently, cetirizine hydrochloride, the root chemical in a lot of common antihistamines has, this year, developed a new side effect for me. Absolute, stunning, crippling exhaustion. So. I’ve yet to try loradatine this year, but now I’m kinda scared. Gunna have to try it on a weekend, when getting crippling exhaustion doesn’t matter. Till then, yay for itchy eyes and running nose.
Annoyingly, I did something neat with Magento the other week, and meant to post about it here. I forget what it was now though :/ When you’re doing an average of 20-30 support tickets a day, these things just vanish from the head. Note to self: Write a draft in the meantime.
Setup a ProjectZomboid server for a friend. It’s running pretty well. One thing that I did run into, it seems it eats system entropy. That’s fine on a hardware server, but commonly on Virtual Machines (like the one I run most things on), entropy starvation is a thing. When that happens, the PZ server takes a very long time to start, as it’s gathering sufficient entropy for something. A quick fix is to install an entropy generator. Currently using “haveged”. Not sure how secure that is; but it’s better than everything requiring secure random numbers choking. Anyone have any preferences for entropy generation on a VM?
I signed up for the closed-beta of let’s encrypt earlier, so this blog is now encrypted. So far, so good. I’d quite like to use the SSL certificate it provides in my Jabber server, but I’d need to automate renewal.. and it’s not *quite* there yet.
Let’s Encrypt’ll hit open beta soon. Looks like the only feasible way HTTPs will be supported widespread. Even with domain validated SSLs, ssls cost too much at the moment, and are too much of a hassle.
Osomount bicycle handlebar smartphone mount
I want this bad lol
Is three performing a Man In The Middle SSL attack/proxy on my mobile hotspot?
Well hello NSA & GCHQ lol.
Funnily enough after searching Google for this issue and then retrying I don’t get some asshat trying to proxy my SSL connection. Or if they are they have a ‘genuine’ root certificate from a valid CA.
So, here’s something that’s been coming to mind of late, especially with the recent death of Leonard Nimoy.
Our digital lives varnish after our death. Oh, don’t get me wrong, they’ll last a little longer than our deaths — the server this blog is hosted on for example will stay running. However, it won’t get maintained, that’s what I do, so over time it’ll get hacked, or will break. My brother might take over maintaining it for a while, but in the end, the words and thoughts stored here (some hidden from public view) will vanish.
Archive.org is great, it’ll keep a copy of these words for posterity.. but who’ll ever read them?
I’m not sure if I’m morbid at the moment, or it’s just depression talking, but this all feels so.. transient. These words won’t have the lasting power of those stored on a book, in the end they’re stored on media that’ll die a lot faster than a book degrades, stored correctly. Not to mention, they’re stored in a particularly complex format, that isn’t human readable in any way without the right filter and conversions.
I guess, this is really just underlining the importance of Archive.org and their ilk. Not that I suppose anyone’ll care about what’s stored here.. much as the most read post here is my brother’s posts on linux beep music 😉
Heres a little something that has come about from a related project I have built (and need to test)
Maybe I’ll write up both projects together!
Relevant hashtags #RaspberryPi #HTML5 #WS2812b
Well, I’ve now debugged a few issues with my scripts from my last post.
(made them a bit more fault tolerant and actually take notice of $? exit statuses) .
Recap: Temperhum (USB) -> Raspberry Pi -> Xively chart, now also
RFDuino (bluetooth wireless) -> Raspberry Pi -> Xively chart
Tip: If you’re struggling with the bluetooth on linux giving rx timeout errors (check the syslog if it’s not in the console),
update the software with the following commands:
sudo apt-get update
sudo apt-get upgrade
The Rfduino has been sitting next to my usb Temperature and Humidity sensor for a few weeks collecting data.
RFDuino and Temperhum
Since it had been both collecting data for a few weeks and sending them to Xively / Pachube / Cosm, I had a quick look to see how closely the readings match.
The graphs do show correlation, thank goodness, but it looks like the RFDuino’s temperature scale isn’t right. The RFDuino is only updating the graph once a minute whereas the Temperhum is 2x a minute.
I didn’t really expect great accuracy for the RFduino thermometer seeing as it’s measuring from the chip. But this would still be useful in some more basic cases.
I think next on the roadmap for the RFduino is connecting sensors/remote controls (it would be cool to attach my RelaySockets to this and control the 2 connected relays via bluetooth from my Pi and Android smartphone!
My Humidity and Temperature sensor
A Temperhum from PCSensor.
A great little bit of kit – once you work out the conversion values for the C++ USB/i2c/HID code that lets linux talk to the thing!