Thread by @QuinnyPig

So, folks are asking how I did this. Thread time!

https://twitter.com/QuinnyPig/status/1445192062769319936

While I do enjoy Twitter, I believe it's important to "own my platform." As such, Twitter's not material to the functioning of my business.

But I do talk to a lot of folks here, and a "subscribe" button for @LastWeekinAWS in my profile can't hurt anything...

I started by emailing @revue and checking their Terms of Service. As of today, there's nothing against using their sign-up function and exporting the list to another platform unless I'm directly monetizing the subscribers via subscriptions.

I am not.

(Pro tip, don't build things that are going to get yanked away when one of your vendors finds out about it. Ask rather than hoping to sneak by.)

Revue has an API that lets me do all kinds of things with it. getrevue.co/api

A few tests with curl later, and I knew it could work. I set this up via Zapier.
("Why not a Lambda function?" Because I presumably might want someone else to maintain this.)

Since @revue forces a double-opt in confirmation process I can bypass the one I have in @ConvertKit; Zapier now takes new subscribers and injects them into a slightly modified onboarding flow.

To be clear: I would cheerfully pay @revue money for this, but the only way to do that right now would be to charge subscribers to the list. I'm... not interested in doing that.

There are only a couple of rough patches on the @revue side; I imagine those will get sanded down with time. DMs are open if anyone on that team is curious.

I don't manage unsubscribes in Revue, because only transactional messages go to subscribers from there, and only when they first sign up. If folks are already subscribers, nothing changes in the existing newsletter. It's kinda elegant!

All in all, not bad for a couple hours of work. Onward and upward?