A client could get caught up on one hard POW and not be able to send other messages until they delete it from the sent tab. Process two messages instead of one at a time.Currently they can be bogged down with very big messages. Special Address Behavior, Allow setting for maximum message size to be broadcasted by pseudo-mailing-list.Multi Threading up to the number of cores installed when creating addresses or sending Messages (Medium.Separate messages.dat file into message.dat and addressbook.dat (easy.Option to export keys.dat and messages.dat files to an encrypted backup (medium, possibly difficult).Integrate encrypted database access into PyBitmessage: even after the client is launched, messages and keys should not be readable until passphrase is entered (ideally, passphrase should be demanded upon client launch).You'll notice that Bitcoin doesn't encrypt its database. EDIT: Bitcoin does this with it's wallet.dat, I'm sure the source code would reveal the method, also I don't see why gpg in symmetric mode wouldn't work. (difficult) EDIT: I spent some time searching for a way to encrypt the messages.dat file and only found proprietary solutions*. Encrypt keys.dat file and messages.dat file with a password.messages provided by an API-client, that isn't running Bitmessage, can create a Bitmessage and send it to the endpoint for the bm client to relay to the network) API endpoint to relay messages to the network.Option to not process messages if bandwidth " or this: "that programing expert i met ").This prevents "frameskips" in some games. CPU is busy the bitmessage application should check to see if the CPU is > 15% if so it will save decryption to a later time.Like bitcoin miners get revenues, nodes in the bitmessage network could get revenues from serving adds, and possibly by providing other services.Add keyboard shortcuts for cmd+(number key) to go to the different pages.Add support for Mac OS's full screen mode.Consider moving the User Interface toward more of an IRC interface: No subject, no attaching the previous message simply short messages into a channel.Perhaps Bitmessage could query other nodes, asking how big the current message store is (message.dat file size), and then provide a progress bar comparing local message.dat size against the average response from connected nodes, as a measure of the backlog. When Bitmessage is run, if the local client needs a lot of time to sync with the message backlog, there should be a progress bar or a time indicator (much like Bitcoin-QT, estimating how much time is necessary to get sync'd).First-Time start-up should provide better help for a new user, walking them through an echo test and providing other helpful info and links.I find with lots of BMs, there is too much noise and collapsable threads based on subject would be a little more manageable.
An option under Settings to group emails with similar subjects, ie: threads.This will make going through the inbox much easier w/o all the required clicking. For the Inbox, add the right-click menu items as buttons below "Search" box.Add the ability to "Flag" a message to bring attention to it in the Inbox.Its much more natural to keep them in Inbox. Avoid putting user in "Sent" tab after replying to a message from Inbox.Like how Bitcoin clients are opened if you click a link on the internet that has bitcoin: used.Ĭhovy - BM-2DBqvaVF2s6yKDg1xdFhd4j2DTKZpbnr9G Make bitmessage: links open up in PyMessage.
Would be nice to get a little notification in the systray/app icon that says I have a new message(s) with the number of messages.
0 kommentar(er)
