Messaging is a new addition to Mituyu. So far, it's only available with Twitter accounts, but this will soon be expanded to other networks that allow it. It can take up to ten minutes from adding a channel for messaging to be fully-activated.

Mituyu periodically checks your channels for messages, and displays them as threads. A thread is a conversation, which is either on a person-by-person basis, or as more traditional threads where the network (such as Facebook) enables messaging between more than two people.

First, go to your inbox (unread) folder - here you'll find any new messages your networks have received. Each thread is displayed with details of the sender, the channel it's from, the number of items it contains, and the most recent message date.

Clicking on a message thread will display it in a pop-up window as a message history, a text box with which you can send replies, and some buttons to decide the status of the message (mark unread, mark read, etc).

Message states

inbox (unread) is self-explanatory - it contains all new, unread threads that Mituyu finds. Threads in body read and discarded will be moved back to here when new messages are received in them.

read messages is a useful place to store messages that you've read, but don't want to delete.

discarded threads are just that - items you don't want to see any more. These messages aren't really deleted at the moment; they're just stored here, and can be retrieved at any point.

blocked threads behave in a slightly different way; you can think of this as acting in the same way as the discarded folder, with the slight difference that these threads won't be moved back to the inbox when they update.

Sending messages

To send a message, simply view the thread and type your reply into the box. In some cases you'll have the option to send your message in more than one way - in the case of Twitter, you can send by direct message or by mention. You'll see the method used for each message written next to its date.

You'll also see size counters in some instances, as some platforms restrict the message length.

This service uses cookies to enable log-ons, enhance your user experience, and aid in content delivery. It also employs third-party services that may also issue cookies.