Deleting messages in Facebook, and your “Other” folder

I learned today after years of using Facebook that I have an “Other” folder in Messages. There were messages there I’d never seen before, and from people I sometimes didn’t know.

I also found that rather than the “X” deleting messages, that it stores them in an archive. So here’s the quick on how to delete messages from Facebook and where to find your “Other” folder.

Click on Messages on the left-hand column. Once in Messages, at the top left you will see Inbox in bold type, and Other in gray type. Click Other to see what is currently in that folder. There may be nothing there, but in mine there were a handful of messages I’d never seen before.

If you hover over a message, two tiny icons appear in the lower right – a circle (Mark as unread) and an X (Archive). Most people are used to having an X remove an object or close a window. Instead, Facebook will remove the message from the current folder and archive in the not-so-obvious Archive folder.


In the upper left of the Messages section, to the right of Inbox and Other, there is a dropdown menu called More. Click this and you can see your Archive folder. This will probably contain messages that you thought you had deleted by clicking the X on various messages.


You have two options when deleting messages. You can delete individual entries, or you can delete the whole conversation.

To do either, first click on the message in the column on the left. The conversation (list of messages with that person) will appear to the right. Up above the conversation are three buttons: New Message, Actions, and a magnifying glass search icon.

Click Actions, then Delete Conversation (to delete all of this conversation), or Delete Messages, which then makes check-boxes appear next to each message and you can select which ones to delete.


Confirm deletion to complete.


Windows Alternative IP Configuration

I set up a laptop with a static alternative IP configuration ( for when it is not connected to a network that has a DHCP server. But when I would boot the laptop, it would still assign it an APIPA IP address (169.254.*.*) . This caused some concern for a while. But I had a bit of patience…

I found that it did eventually use the static IP configuration, but only after it tried for about 1 minute 45 seconds (after login) to get a response from a DHCP server. Or I could just let the laptop sit on the wire for 3 minutes before logging in and this also resulted in it choosing the static alternative IP.

A computer that is set up for DHCP will send out a broadcast looking for a DHCP server to respond. Normally this will keep happening until it gets a response. The alternative IP configuration causes the computer to quit trying after a few times and then switch to the user specified configuration.