Feature request list

Show addresses without the hyphen (easy, under discussion) abandoned

Accept addresses without the hyphen (easy) Done, accepts address without "BM-"

Add support for SOCKS5 proxies (difficult) Done

Encrypt keys.dat file and messages.dat file with a password. (difficult) EDIT: I spent some time searching for a way to encrypt the messages.dat file and only found proprietary solutions.

On Address book tab, add right-click option to add person to subscription list (easy)

RPC API (difficult) Done

Sounds (easy. This is turning out to be more difficult; there doesn't seem to be a simple cross-platform method of playing sounds)

Ability to trash sent messages(easy) Done

Portable mode (easy) Done

Pseudo-mailing list mode for individual addresses (easy) https://github.com/Bitmessage/PyBitmessage/issues/51 Done

Clear the 'Send' tab after sending message or when acknowledgement received. (easy) Done

Ability to add a node to 'defaultKnownNodes' (easy)

Ability to disable the built-in defaultKnownNodes, useful for LAN use or people running their own BitMessage network (no need to interact outside of the designated network). (easy)

Offline mode (easy)

Option to export keys.dat and messages.dat files to an encrypted backup (medium, possibly difficult)

Add MD5 checksum to the wiki Main Page. (easy)

Add GnuPG sig file to download area. (easy)

Separate messages.dat file into message.dat and addressbook.dat (easy. I might not do this.)

Trim input when adding an subscription or address book address (very easy) Done

Headless operation (----)

Clicking the Windows notification balloon (New Message) will bring the Bitmessage window to focus. (----)

Do not open new messages automatically, and indicate if a message has been read. (----) Done

Confirm delete? (Doing the above might fix this issue as well, I was deleting a message and a new message came in so I deleted the new message). (----) Basically done- see above.

API ackdata lookup (easy, although I would like to make some internal Bitmessage changes first- for example, 'sentmessage' isn't a very useful status, but 'ackreceived' is better)

Ability to select multiple recipients on the Address Book tab before clicking "Send message to this address" Done

User can adjust font and font size for easy reading.

A search feature for the inbox and sent items

Ability to create subfolders and move inbox items into them. Also a rules dialog for automatically classifying new mail into subfolders. Rules would be too much to program unless someone else wants to tackle it. Folders we could do someday but it will not be high on my list of priorities.

Don't remove focus from current message when a new message arrives and denote unread messages (should be relatively easy, will require database changes) (--Isn't this done in 0.2.8?)

Multi Threading up to the number of cores installed when creating addresses or sending Messages (Medium)

Allow a label to be set when creating addresses. A number is appended when creating multiple addresses (easy) You can already do this.

Ability to disable and re-enable a subscription address. (easy) Done

Ability to delete addresses from "Your Identities" (Keeping the current enable/disable options). (easy)

Cancel messages in the sent folder before they are sent. (Sending them to trash does not work.)

• ATHEROS EDIT: Adding a check that runs every time a POW iteration is done would slow it down. How about if you trash a message and then restart Bitmessage? I'll make the necessary changes so that it doesn't restart the POW for trashed messages.
• Works for me, as long as a notification is displayed notifying the user that they need to restart the client

GUI interface for adding attachments to outgoing message and opening incoming attachments.

Groups in address book, sending a message to the group will message all of the users of that group. (keep the 'name or label' and 'address' but allow the address section to contain multiple addresses separated by semicolon?)

Allow LAN operation (or option to allow LAN operation (disabling non-private WAN ip ranges?)).

• ATHEROS EDIT: How about being able to add an IP in the user interface?
• I think that should be an option as well (see above define your own known nodes feature request) but would not allow a p2p style network unless you input every ip in use (since private ip addresses are blocked).

Built in text editor to send rich text natively. Someone else may work on this but I would prefer to keep it simple. It isn't as simple as just sending HTML as the client doesn't display HTML from strangers.

Better logging (medium)

A tab for browsing the broadcast streams. working example shown here

Ability to star or otherwise highlight a message (to find easier later). Open to other methods of accomplishing this.