A collection worth reading is the difficult, unglamorous half of a newsletter, and you have been doing it for months.
Kyurations turns any published collection into a newsletter. What you save between issues becomes the issue: up to five items, composed and laid out, mailed to subscribers every week, fortnight or four weeks. You do not write it, and you do not press send.
Anyone who saves seriously ends up with the raw material of a very good publication and no publication. The reading is done. The judgement is done. What is missing is the half-hour every fortnight to write it up, and that half-hour is where almost every personal newsletter quietly dies.
Live lists remove that half-hour rather than help you find it. You keep saving the way you already do. When an issue comes due, what you have added since the last one is composed into it and sent. There is nothing to draft, nothing to schedule, and no send button.
This is not a mockup. It was rendered by the same function that sends the real ones, from a real published collection, which is why the thumbnails are somebody’s actual saved posts.

The list's name, your handle and the date. Readers subscribed to your taste, so the issue is presented as yours rather than as ours.
A short paragraph on what is in this one, composed from the items themselves. It is the difference between a newsletter and a notification.
The newest thing runs first, at full width, with its cover and a line on why it is worth your evening. Video gets a play mark that opens at the source.
Everything else follows as short entries with square thumbnails, sized and cropped so the issue keeps its rhythm whatever shape the covers are.
One click, from any mail client, no login and no confirmation screen. Easy to leave is what keeps a list full of people who want to be on it.
Everything lives in the share dialog you already use to publish a list. There is no separate newsletter section, no sender to verify and no domain to configure.
A newsletter runs on top of a public collection, so give the list a public link first.
A switch in the same share dialog, under Quick settings. A Subscribe button appears on the list's public page the moment it is on.
Every week, every two weeks, or every four. Two weeks is the default because it is the one most people can keep.
It goes to your own account email and it is exactly what a subscriber receives. Worth doing once before anyone else is on the list.

The one decision worth thinking about for a minute. Match it to how much you already save, and the issues write themselves from there.
For someone saving most days, where a fortnight would mean leaving good things out of the issue entirely. The most momentum, and the most to say each time.
The default, and the right answer for almost everyone. Long enough that five genuinely good things have accumulated, short enough to stay a habit.
For a narrow subject you read deeply but not often, or a collection you add to in bursts. Every issue arrives with a month of judgement behind it.
The part no interface shows you, and the reason an issue arrives looking considered rather than automated.
The people this works best for are not the ones planning a publication. They are the ones who have been quietly building the material for one and had not thought of it that way.
You already save constantly and have nothing to show for it beyond a private pile.
You want the smallest possible commitment: no drafting, no scheduling, no send button to forget.
You would rather publish something honest every fortnight than something ambitious never.
You are selling a collection and want buyers to keep hearing from it as it grows.
You have taste in a specific corner of the web and a handful of people who keep asking what you are reading.
You want the writing, the layout and the sending to be somebody else's problem.
Once a list is mailing it shows subscribers, views, likes, how many items it holds and when the next issue is due. It is the only per-list panel of numbers in the product, and it appears here because a list with readers is the only kind where the numbers mean anything.
Every issue carries a one-click unsubscribe that works from any mail client, with no login and no are-you-sure. Making it hard to leave is how a list fills up with people who resent it.
Sharing, in the guideIf one is missing, the guide covers sharing in full, and there is a feedback item in the account menu that reaches the person who builds this.
A newsletter is only worth sending if what is behind it is worth reading, so the first step is not this feature. It is saving nine things you would stand behind.