renovator - it's not just blogs, though, it's regular customers showing the new version to their friends - even when 2.0 was in beta-testing we often got e-mails from people asking how to get that cool software with the audio pronunciation feature they'd seen their classmates using.
I'd be wary of charging people a fee to add a feature to a new version - good way of collecting / validating votes, I guess, but then if we didn't deploy a particular feature we'd have to do a bunch of refunds / credits, and a lot of people would be confused by the whole system and think they were paying to enable access to that feature right away. Might be something a much bigger company could experiment with, but on the scale we deal with I don't think it would be very practical.
We might add an option to display words with more than 4 characters without magnification, haven't decided about that yet.
sinoreen - there wouldn't be anything if you had the software set to allow duplicates, at least not unless/until we add a separate Edit Card button (only a good idea once we get performance to the point where the icon for that can update without slowing down searches too much).
stephanhodges - I'd rather have the separate screen - we'd use the exact same dialog we do in, for example, the Card Info screen's category editor, so it would be very easy to code, it would fit more smoothly with that interface, it wouldn't require adding extra stars / boldface text / etc to the category tree (which I still don't like), and it would make it potentially very easy to edit default categories with a saved session in place.
The help page text is pretty much just copy-and-pasted from the instruction manual, so you can get a copy of it from there.
daniel123 - great idea; very easy (particularly on WM, where we just have to tell the tree view to make that first category visible and it will) and certainly a time-saver if you've got a lot of categories.
Sarevok - entry annotation is not a possibility for 2.0.1, actually, only flashcards (much easier to implement on the back end). And honestly even that I'm starting to think would be better saved for a later release; we're getting into the same darn feature-creep trap we were in with 2.0, we can't please everyone and the most important things to get working in 2.0.1 are things that make the existing functionality usable / erase some of the disadvantages compared with 1.0.