So, WarpWallet is a so-called brain wallet for Bitcoin. That is, you only have to remember a relatively short password and it generates the corresponding private key for use. It uses a memory and CPU hard set of cryptographic algorithms to ensure that brute-forcing is slowed way down. That is, when generating the private key, it takes considerable time. Their Javascript implementation takes over 10 seconds on my machine.

So the makers of it had challenges setup. By the time I stumbled on it, only the last challenge was left, with 6 months remaining. For that challenge, the reward for cracking an 8-character alphanumeric password was 20 BTC (and BCH and BTG!), which was worth over $100,000 USD at the time of the challenge end date.

For Windows 7, this turned out to be pretty easy to do via PowerShell. I just had to look for a native image resizing library since the lock screen for some odd reason, only supports JPEGs up to 256KB in size. Probably one of those legacy items left over from NT, like the file system permissions dialogs, and the built-in environment variables editor… I ended up using WIA’s ImageProcess COM library which worked surprisingly well.

I noticed during the (many) meetings I attend that disconnecting and reconnecting my laptop from the dock reorganizes all my windows to the laptop’s display. This got annoying to have to drag and resize everything when returning to my desk, which has a 3 monitor setup. So, I wrote this small Win32 application to allow you to save the positioning and size of all windows and then restore them at a later time.

This was the hardest part. If you wire the wrong things together you can brick your Pi. I took some time to decide on which pins to use, and after assembly and testing everything worked. I’ll explain which pins I picked, but note that this information will not work with other hardware configurations.[I originally had a Model B Pi, but due to needing the second hardware PWM (which is hidden on the B), switched to the B+.

I added an update to msqur today. Just a small update to the landing page since it was kind of blank. Moved the settings icon to the view page instead of every page. Also fixed the readme and license files for formatting. I get a lot of hits from Russia on that site. Actually, I get a lot of hits from Russia on all my sites. I imagine most of them are bots probing for weaknesses.

I produced some videos in 60 FPS, but couldn’t remember which ones. Since, of course, I didn’t label their FPS at the time, I needed to find them in vast sea of 30 FPS videos. Rather than just use a simple grep with ffmpeg to find which ones, I thought it might be more useful to find all videos that have a certain FPS threshold. Usage: ./60fps.sh [directory] #!/bin/bash SAVEIFS=$IFS IFS=$'\n' function fpscheck { FPS=$(ffmpeg -i "

As mentioned previously, I wanted to open the source to msqur up and put development on the backburner. I have added an appropriate license for it (although I do need to add library licenses/notices in there as well). It is now GPL licensed, and I have made the repository public. Some things I added: Added basic charts for the 2D tables Added table header text to tables Added reingest script to allow for easier MSQ cache updates Fixed some of the documentation up Known issues, mostly the same as before:

I dug in this past weekend and updated a few things: INI Parsing revamp. Support for more tables and curves. UI Update so that all this new information is somewhat organized A few minor bug fixes and enhancements Known issues: MS3 file support is poor Constants are just blurted out without any organization INI Parsing of formulas and directives not implemented yet I plan on opening the source code up under some kind of OSS license, after fixing a few more issues and updating the documentation.

A little while ago I updated msqur.com to 0.60b. Changes include: Added engine make/code fields for uploads Added view count and increment And less visibly: Finished OO refactor Update API documentation (not public yet) Added deployment scripts I still haven’t finished INI file parsing 100%. There’s a bit more to do, but I’ve been busy with work and other projects. I’m thinking of releasing the project under an appropriate open-source license once I finish that, so hopefully others can join in on the fun.

I’ve rolled out the update 0.53b to msqur.com. This includes: INI Parsing (i.e. better MSQ support) Bug fixes and better error handling So now it is a bit more usable. The INI Parsing turns out to be a bit more complex than I anticipated, but I rolled out a decent intermediate update in the meantime. Before completing the INI parsing (or anything else for that matter), I’ve decided to overhaul the entire codebase.