Analytics

Graph of visits for all pages hosted on http://stenoknight.com since November, 2009 (when I started using Analytics) until today:



I just thought it was awesome and hilarious. I love the internet so much.

New Donation Page

Wow, it's been an exciting couple of days. We've already collected $200 in Plover donations, and after receiving feedback from one donor, I've made a dedicated donation page for Plover, detailing exactly where the money goes. (Right now it all goes to help our devs write code for Plover without taking too much of a financial hit when they take time away from their day jobs or freelance work; later we might use some of it as seed money to start fabricating Plover hardware, like qwerty-to-steno keyboard overlays or low-cost USB steno keyboards that plug into a computer and immediately start outputting English when they receive steno input. I've never taken any money for Plover, and I don't intend to start. My own venal reason for founding the project was to bring more people into my profession so it doesn't collapse due to the ever-increasing shortage of stenographers. If I can help raise up the next generation of captioners, transcriptionists, and steno amateurs, I'll feel more than repaid for the money I've spent getting Plover developed.) Ever since landing on Hacker News, the interest in Plover has spiked dramatically, which is glorious. Later today I'm going to try to make an entry on our wiki detailing all the various jobs that we need help with and the current state of who's working on what. Thanks for all the email and offers of support I've gotten so far! It's so inexpressibly wonderful to see this tiny little two-person project explode into a complex and multivarious international community.

OpenSource.com Article on Plover

Longtime Plover ally Mel Chua has just written a fantastic article on OpenSource.com about Plover! Go check it out. If any of you have come to this blog via the article, welcome! Try out the demo on your qwerty keyboard, check out the Launchpad page, or join the Google group or the Aviary to talk with Plover users and devs about open source steno and the next steps for the Plover Project.

Plover 2.2.0 Released!

Woke up this morning to an email from Josh, Plover's dauntless programmer:

"Hi all,

I'm happy to announce the latest feature release of Plover! Version 2.2.0 includes the following features and fixes:

* a new graphical user interface that supports both older and newer versions of Ubuntu, with and without Unity
* auto-start configuration option
* hotkey commands to suspend/resume Plover, bring up the configuration dialog, and bring the main Plover window to the foreground
* support for the TX Bolt/Gemini TX protocol, which will open the way to using many Stentura machines
* protection against running more than one instance of Plover at a time
* proper handling of the number bar
* updated user guide


This is all fine and good, but what I'm happiest about is the high level of community involvement that went into this release, including Stan and Tony sending me a steno machine to test on (thanks, I'm finally ready to send it back!), the great suggestions for features and improvements to both the software and the user guide from many people on the mailing list, Hesky's seamless contribution of code to support the TX protocol (and ongoing experimental Windows port), generous financial support from various corners of the world, and, of course, Mirabai's relentless advocacy, encouragement, and testing.

As usual, the latest version can be downloaded from:

https://launchpad.net/plover

Also, for the first time, I've made Plover available from the official Python package index, which provides yet more methods of installing Plover for those adventurous enough to learn about it:

http://pypi.python.org/pypi/plover/

Please report any problems to the mailing list.

Happy stenographing, Josh"

This is awesome. I've been testing out this version for the past few weeks, and it is rock solid. Being able to use Unity is really convenient, and the number bar bugfixes mean that I can now write the Steno 101 lesson on numbers, fingerspelling, and metacommands that I've been planning for months! Look for that by the end of this week. The auto-start option is also great when you want to invoke Plover (I use Gnome-Do, so I only need to do Alt-Space, P, and Enter to set it going) and start writing steno right away without fiddling with the mouse. The new Plover Guide (PDF file) is also extremely useful, and we'll hopefully be mirroring it on the Wiki for easy reference fairly soon. So if you have Linux and a Sidewinder (or Majestouch or Noppoo Choc Mini or any other qwerty keyboard with n-key rollover) or a Gemini PR/TX machine or a Lightspeed or a Protege, install the new version and enjoy! If you don't have Linux, either take the plunge and install Ubuntu as a dual-boot option, or wait a few more days until the Windows port is complete. Feel free to leave feedback -- feature requests, bug reports, et cetera -- in comments here, at the Launchpad page, on the Google group, or on the (newly restyled) Aviary. Many, many thanks to Josh for his fantastic work. We've come a hell of a long way from "catalogue catalogue Log Cat log".

Plover Aviary

Two nice little updates, while we wait for the newest Plover release (which is imminent) and the completion of the Windows experimental version (which should hopefully happen by the end of the week). First, Amber from the Google group has created a list of 21 sentences using the most common words in the English language; all together, the words in these sentences (which she's posted to the Plover Wiki) comprise 50% to 65% of all words used in English, so it's useful to have them under your belt. Check 'em out:

Practice Sentences with Common English Words

Another brilliant idea of Amber's was for there to be a forum for steno newbies and new Plover users, so that they could share tricks and travails with each other and maintain a form of reference that was less static than the Wiki and less linear than the the Google group. So this morning I installed phpBB (a surprisingly painless process), and I can now introduce to you:

The Plover Aviary

I've started it off with a few posts to get it going, including one where I took Amber's practice sentences and wrote them out on my steno machine using a dummy dictionary (with all the entries replaced with "STKPWHRAOEUFRPBLGTSDZ", so they came out as raw steno. For some reason, when I deleted all but one entry and tried to use that dictionary, Plover gave me an error, but it worked fine with all the entries redefined). If we can get more practice sentences from Plover users, I'll hopefully be able to plump up the previous Steno 101 lessons into a more useful form.

With luck the Aviary will soon be full of questions and answers and feature requests and competitive speed bragging. I also count today a success because I learned the word "dotterel", which I've used for the steno veterans forum (because after "hatchlings" and "fledglings" just comes "full-grown birds", and I thought that lacked panache.) According to its Wikipedia entry, a dotterel is both "a small wader in the plover family" and "a doting old fool", which fit my steno-obsessed batty old self perfectly. So there it is. Another place to go and get your Plover on with other steno neophytes. Have fun!

Fly, Plover! Fly!

Plover photo by Changhua Coast Conservation Action

Pragma Nolint, a member of the Plover Google Group, has just written a training program for the qwerty-to-steno layout. It's called Fly, and you can download it here:

http://stenoknight.com/plover/Fly_v0.0.1.tar.gz


Fly screenshot

Hover Plover is still very much in the planning stage, so having this available right now is incredibly useful, especially considering that I still haven't gone back into the Steno 101 lessons to add practice material. Instant interactive feedback is a better way to learn this stuff anyway.

Currently it just works with Ubuntu, but I've put out a call for volunteers to port it to Windows and/or a web-based version, so we can reach as many Plover users as possible. Keep in mind that it uses code from Plover (and Plover's default dictionary), but you don't want Plover to be running while you're using Fly, or it won't work properly. Fly will offer up drills based on single letters, words, or even sentences, so you can learn the steno keyboard from the bottom up. If you use Fly, comment here to relate your experience, report bugs, or request features.

Many thanks to Pragma! The ever-growing Plover community never ceases to amaze and delight me. Share Fly among your friends and bring more people into the glorious world of open source steno.

Housekeeping

I love long weekends. Thanks to the first decent amount of free time I've had in a while, I've been able to change some little things on the Plover Blog and Wiki that were long overdue.

* http://ploversteno.org now redirects to the Plover Wiki instead of the static FAQ page that it's superseded.

* I've put a slightly cleaned-up version of the qwerty-to-steno layout chart right at the top of the blog, where people can see it straight away. It should probably get a more prominent place in the Wiki too, though I'm not sure where; right now it's kind of buried in the FAQ.

* I've put a link to the Plover Demo near the top of the blog's sidebar and on the front page of the Wiki, because I believe that it's Plover's best low-stakes ambassador for stenocurious newcomers.

* I've updated and expanded the Wiki's Plover Cheat Sheet a bit, adding to the chart of the most common prefixes and clarifying a few of the more confusing features of Plover's default dictionary. I also submitted a bug to the Launchpad page, because the default dictionary that comes with Plover defines -FPLT as -FRPBLGTS and STPH as STKPWHR, which is only useful if you're me and you're using Plover for offline transcription work, which you almost certainly aren't. I should have changed those definitions to {.} and {?} respectively before submitting the dictionary to Josh for packaging, but I didn't, and the result is that the Hello, world. instructions on the Wiki don't work properly. Boo me.

* I've updated the Plover Blog sidebar with links to videos and interviews featuring Plover.

* I thought of another Hover Plover minigame, one that would appeal to the puzzle solvers rather than the fast-twitch kids, and which would take minimal graphical expertise to write. You'd start out with a block of text in steno, and every time you wrote one of the strokes, it would transform into its English equivalent. So at the end, you'd wind up with a block of English text. Here's a mockup, showing the starting state, the middle state, and the completion state. I based the text on a puzzle I made for a friend who didn't know steno but who liked solving cryptograms. (Solution here. Don't click the link to the graphical version if you want the fun of puzzling it out for yourself, since it shows the solution on the bottom.) I figure it'll have the satisfaction that you get from a game like Minesweeper, but without the nervous tension, because there are no penalties for misstrokes. You're just clearing the field and building up your muscle memory as you go. You'll probably start out just writing the strokes without knowing what they say, but eventually as you get more comfortable with the theory, you'll start predicting the translations before you write them.

* I'm also currently trying to sort through these guidelines for open source development, posted by Ms. Gardiner to the Plover Google Group a while back. Plover is the first open source project I have direct experience with, and since I'm not a coder myself (except on a seriously elementary level), I'm at sort of a disadvantage in figuring out the best way to organize it. The code started out completely in Josh's domain. Then Hesky joined in on the experimental branch. We've gotten several more offers of coding help since then, but except for side projects like the Plover Demo, I don't think we've had any actual committed code from anyone other than Josh and Hesky so far. I definitely want to change that, though, especially as Hover Plover development gets off the ground. Any specific advice on making the Plover Project more friendly to community development would be very welcome.