Lists: message a lot of people, one at a time

Save your own named groups of connections — "the book club", "Sunday five-a-side" — and send one message that arrives as an ordinary private message to each of them.

Not a group chat. Not a broadcast anybody can spot. Each person gets a normal one-to-one message in your normal conversation with them, and replies come back to you privately, one conversation at a time. It's the difference between emailing forty people and putting forty people in a room together — and sometimes the first one is exactly what you want.

Your lists are yours

This is the part worth knowing up front: nobody can see a list you've made, and nobody can find out they're on one. There's no screen that shows it, no setting that reveals it, no notification that mentions it. Rename a list, reshuffle it, delete it entirely — nothing happens to anybody else, and nobody is told. It's your address book, not a club with a membership.

Delete a list and the people, your conversations with them, and your connections are all exactly as they were. You've thrown away a piece of paper, not a relationship.

Building one

Make a list, give it a name, add people from your Connections — the people who follow you back.
Adding someone needs a current connection. Removing someone never does. You can always take a name off your own list.
If a connection later lapses, the list keeps the name. It's your record, and we don't quietly edit it behind your back. The check that matters happens when you send, not when you build.

Sending

Open a list, press Send, and the compose window opens with everyone already selected — and says so, before you've written a word ("Sending to 12 of 12 on this list"). Write, send, done.

Want a subset? Pick the people you want and it goes to exactly them. Leave the selection alone and it goes to the whole list. Nothing ever sends from a single press — Send opens the window, and you send from there.

The report

After a send you get a plain summary, and it stays on screen until you close it — it's the one thing you can't ask for again:

Sent to 11 of 12; 1 is no longer a connection.

Anyone skipped because you're no longer connected is named, so you can do something about it — disconnecting is visible either way, so there's nothing there you couldn't already see.

The limits, and why they're there

100 people per send. More than that and the send is refused whole — not trimmed to the first hundred, not quietly split into batches. You'd have no way of knowing who got it, and a half-sent message is worse than an unsent one. The refusal tells you the count, the limit, and what to do instead — because past a hundred people what you have is an audience, and the right tool is a Room.
500 people a day, counted in people rather than sends. A few full-list sends a day is generous for a person and stifling for a spam script, which is the point.
500 people per list, 50 lists. A list bigger than the send limit is perfectly legal to keep — you just can't reach all of it in one act.

A refused send costs you nothing against the day's allowance. Nothing was sent, so nothing was spent.

Good habits

Name lists after the occasion, not the people — "book club" survives someone leaving; "Ana, Sam and Jo" doesn't.
Don't prune your lists when a connection lapses. The send-time check handles it and names the skip for you.
When you find yourself sending to the same forty people every week, that's a Room. Lists are for messages that deserve a private, individual reply.

Did you know? Your recipients can't tell. The message they get is a completely ordinary private message in your ordinary conversation — no "sent to a list" tag, no group, no other names. Which means a reply is just a reply, and the conversation you had is the one you'd have had anyway.