In a previous post you’ve learned how to control your X10 devices using the Amazon Echo and the IFTTT service. But now Amazon allows you to code a Smart Home Skill so you can say Alexa turn on the lights instead of Alexa trigger lights on. It’s more convenient! Let’s extend the work we’ve already done to write a Smart Home Skill to natively manage your X10 devices.
Cmd.exe is the world worst software. It hasn’t really been updated ever, since its conception. When I say its conception I’m referring to COMMAND.COM. Fortunately, some guy called Maximus5 coded an extremely good console emulator for Windows called ConEmu. It features tabs, colors, easy copy and paste (have you tried to copy/paste using cmd.exe? Then you know what I mean), 32K lines history buffer, macros, and it’s totally customizable. It’s way more powerful than you think. Let’s take a look at this beautiful software.
UPDATE 01/22/2017: You can find a modded 4.3.0 version with the modifications from this post clicking here.
I really like my Pebble. Also, I really like notifications on my Pebble. But I really hate that I can’t filter those annoying WhatsApp groups notifications in my Pebble without losing all my WhatsApp notifications. The Pebble really needs a notification filtering system.
Most people solve this problem by deactivating the stock notifications and installing a third-party application for that. But usually, those applications are really slow sending the notifications and lose a lot of them. I tried several but I didn’t like any of them. So I decided I wanted the stock notifications but with regular expression filtering and went ahead to modify the original Pebble application for Android.
Are you one of those Amazon Echo users that have the house full of X10 devices and you’re sad you can’t use them with the Echo? There’s a way you can control them if you have a Linux server around, even if it’s something as simple and cheap like a Raspberry Pi!
The MinGW-w64 project is an improvement on the original MinGW (Minimalist GNU for Windows) project to support 64-bits targets. Currently MXE supports two MinGW-w64 targets: i686-w64-mingw32 for 32-bits executables and x86_64-w64-mingw32 for 64-bits executables.
This is a guide to cross-compile qBittorrent on Linux for Windows 64-bits only. As usual we’ll use Debian for this.
If you want to implement your own Alexa Skills for your Amazon Echo and don’t intend to make them public, you can use a self-signed certificate for your web service where you host the skill.
I’ve been impressed on how many developers can’t make this work and have opted to use a Lambda function as a proxy, when it is very easy to create the self-signed certificate.
If you intend to publish your skill then you’d need to buy a SSL Certificate. These steps won’t help you. You also need a real and trusted SSL Certificate if you want to host audio files to be used with the Audio SSML Tag.
The most popular questions about git always seem to be the same: When should I commit? How often should I commit? What exactly is a branch in my project? What is a tag?
Before getting into dirty grounds (and we’ll eventually get there) you should know a little about best practices when using git.
Note: If you haven’t read the post A Useful Git Tutorial – Part I you can check it here.
Since version 3.x of μTorrent some people like me got away from it, since it became bloatware. That all started when it was purchased by BitTorrent, Inc., and the client has gone down hill from there. It’s still the most popular torrent client on the planet though.
So I moved to qBittorrent which is a wonderful client, but it lacks a feature that I really use and need: the ability to specify cookies when downloading a torrent from a URL using the WebUI.
I also wanted another little feature that I really need: the forms have to support the autocomplete feature of the internet browsers. So when I fill a field in a form, the browser saves it for future use. For this to work the forms need to be actual forms, and you’ll see qBittorrent doesn’t use them.
Since qBittorrent is an Open Source project, it’s pretty easy to implement new features on.
You know what I really hate about git? Calling working directories as repositories and real repositories as bare repositories. This is somehow confusing for people like me coming from older and outdated control version systems like CVS or SVN.
But if you keep in mind what I said above and give git a chance you’d realize is the most powerful control version system ever created.
There are tons of git tutorials out there but I’m pretty sure none of them cover how 90% of the people use git: clone an existing project, make their own changes and try to keep them updated with the original project. Eventually submit patches.