Yakread sharing notes

(this is a message I wrote up today on my tools for online speech Discord server, on the #yakread channel)

A feature idea I'm currently mulling over: make it easy for people to share collections of publications that you can subscribe to with yakread (or any other rss reader).

example of how this might look: Add a page at yakread.com/share where you can paste in links to newsletters/blogs/etc. yakread fetches the RSS feed for each of the links you paste, if there is one. Then you get a link, e.g. something like yakread.com/subscribe?collection=.... If someone clicks that link, they see a list of all the publications + a checkbox for each one (checked by default). Then there's a text box where they can type in their email. If they hit subscribe, they're subscribed to yakread, and all the RSS feeds they've selected are added to their account.

more details:

• if someone is already signed in to yakread when they click on the shared link, then the email field gets prefilled
• the subscribe page could also have a link to download the raw OPML file. people can download that if they want to subscribe with a reader other than yakread. (it can work with the checkboxes too--the opml file will omit any publications that you've deselected)
• when you create the share link, maybe add a commentary field for each publication. so when people visit yakread's subscribe page, they can read any commentary you've put in.
• add some stats pages so you can see how many subscribers you've referred to each feed. also make it so people can see how many people on yakread have subscribed to/been referred to their own feed. stats could also include # of times feeds have been exported to an opml file--then the stats still work to some extent if people subscribe with other readers.

(As an aside, I've been thinking that Yakread should focus more on RSS than on email--and this is a great example of why. It's taken a ton of effort just to make simple email 1-click subscribes work cross-platform on The Sample.)

If any other RSS readers support it, I'd even be down to add buttons to make it easy to subscribe to the feeds with those instead of yakread without needing to download the opml file. I'm not aware of any readers actually supporting this today, but I'd just need to be able to pass a link to the opml file. e.g. if readwise supported it, I could have a button that leads to something like readwise.io/subscribe?opml=....

It would be cool if this could recreate cross-promotion network effects that are coming from substack's recommendations, but have it be cross-platform (and still just as frictionless)

Addendum A

This could also support regular email clients as one of the reader app options. If the user opts for that (instead of opting to subscribe with Yakread or another RSS reader), then Yakread uses an RSS->email service to deliver their RSS subscriptions via email: whenever there's a new item from any of the feeds, it's sent immediately via email. It should replicate as closely as possible the experience of subscribing to each of the feeds via email (i.e. for those feeds which are already provided as email newsletters).

In this case, Yakread could provide a way for newsletter writers to export their subscribers. If a writer proves that they own an RSS feed*, then they could export a CSV with anyone who is currently receiving their newsletter via the RSS->email service. Any exported subscribers would be automatically unsubscribed from the RSS->email service, under the assumption that the writer is going to immediately import them into their regular mailing list. Yakread could provide integrations to automatically export subscribers for newsletter providers that have APIs (for heaven's sake, Substack!), just like The Sample currently provides.

*For example, by signing in to Yakread with an email address listed within the RSS feed as the owner. I see that feeds for Substack newsletters include such an address; feeds for Ghost newsletters do not.

Next step: when creating a share link, provide settings for which publications should be shown before the reader clicks subscribe, and which should be shown after. This could be used to create a signup page that works the same way as Substack's (and others who have copied the recommendations feature, like Beehiiv): you can select your own newsletter to be shown first, and then after the reader subscribes, the other newsletters would be shown. You could also specify what the default reader app should be. For example, you could select "regular email" as the default for your own newsletter, and then use Yakread as the default for the other publications you're recommending.

(That's a particularly good combination IMO since Yakread is great at managing lots of subscriptions that you're interested in but not able to read every issue of. But in any case, subscribers can always select a non-default reader app. I'm excited for the potential of this to help RSS readers become as mainstream as email clients.) 

Given all that, this subscribe page could well be used as the main landing page for your newsletter, if you want. I could make the page embeddable (and highly customizable) so you can put it inline on your own website, while matching your site's style. This is particularly dope because it would even work on a simple static blog--you could start out by leaving your subscribers on Yakread's RSS->email service, and if later on you decide to upgrade to your own newsletter provider, then you can export.

And there you have it: a fully cross-platform, recommendations-enabled signup solution for everyone, which puts all participants--both on the publishing side and on the reading side--on equal footing.