Live data from Hacker News

Substack writers, you need a website

elizabethtai.com

101–110 of 373 posts

Re: Substack writers, you need a website

#101
post #43

Earlier quoted context omitted.

What if I want people to read me without needing a subscription or email disclosure? What's the email for anyway? So that you can get sent notifications of new posts? ... People read those kinds of emails? I always curse myself for finding a way to get them sent to myself, and file them away somewhere until I can figure out how to turn them off.

> What if I want people to read me without needing a subscription or email disclosure? Medium is where you can post and get a bit of what substack offers while giving you the ability to make your post freely available via the web. > What's the email for anyway? So that you can get sent notifications of new posts? On substack, you get the whole newsletter in the email. you dont need to go to a website. I use https://k…

Pick Medium, it's great ... if you want a paywall to turn away half your visitors!

Re: Substack writers, you need a website

#102
post #84
post #39

Earlier quoted context omitted.

You could do the same thing through Ghost, which has an API, and not be using a service that proudly platforms the Tates and nazis.

I don’t know anything about the specific situation you’re referencing. That being said, getting mad at an organization, one that is built to be a “platform” for people to share their words, for not going out of its way to police which people share which words, seems to me to be unproductive at best, if not actively close minded and tribalistic.

oh it's more than the org. IIRC, it's also the founder.

Re: Substack writers, you need a website

#103
post #30

I'm pretty happy with the way I've resolved this. I publish everything to my personal blog first, then once a week I copy and paste it all into a Substack newsletter. I get to use Substack for email distribution (which would cost me hundreds of dollars a month using most other solutions, I have 66,000 subscribers now) but my own blog stays the original point of truth. Here's the tool I use for the copy-pasting: https…

It's sort of disgusting that inbox clutter from a publishing service is the dominant delivery paradigm as opposed to browsers natively checking bookmarked RSS feeds.

Email is so well designed, so resilient, and so ubiquitous that's very hard to displace it's use as a central check-in.

Re: Substack writers, you need a website

#104

Earlier quoted context omitted.

That’s exactly right. Finding ways to get paid for your work, and all the very complicated way taxes interact with it all, unless you’re going all-in on ads, is a messy problem that people will happily centralize for. And for the less technical people, we have 30+ years of solving this problem with different websites that each went in and out of vogue, from groceries and MySpace, through Facebook and now Medium and S…

I follow a very prolific open-source/FOSS podcasting network. All of their infrastructure from the very bottom to the very top is FOSS - except their membership program. It links to a third-party which processes payments compliantly. They've attempted a pivot to funding the network via BTC/Lightning but clearly that's polarizing to a lot of people even though it better aligns with their philosophy.

I'm not a lawyer; but I believe that even if they take payment through BTC, etc, they're going to need to take sales tax, etc, based on the location that their subscriber is ... which means they need to handle the tax hell that comes with it, so they'll find themselves better off with a Merchant of Record that can handle that for them ... which is almost certainly proprietary because ... it's a big mess.

Re: Substack writers, you need a website

#105
In system after system, people enthusiastically swarm to something which is easy to use. Then, after enshittification, they hang around too long because it's so hard to extract and send the meaningful data and metadata elsewhere.

If you write all your stuff in a location you control, and syndicate that out to the popular platform of the day, you can minimize your loss.

An astoundingly large percentage of my personal technical policies are guided by the idea that I want to minimize my losses after the next sudden yet inevitable betrayal.

Re: Substack writers, you need a website

#106
I'm one of the creators of Leaflet - https://leaflet.pub - also mentioned in another comment. We're making a publishing app kind of like Substack or Ghost, but connected to the open social ecosystem building on AT Protocol. There a lot of potential here, and a lot of tools that already exist.

We collaborated with other publishing apps (pckt & Offprint) to make Standard.site - https://standard.site - a simple set of standards for publishing interop that enables something like RSS but on top of a whole social network. More context: https://lab.leaflet.pub/3moomxyjssk2p

Others can leverage this to make e.g. a whole reader app where you can find everything people in your network are publishing: https://standard-reader.app

A key thing is it's very flexible, you can publish on Leaflet, or on a self-hosted blog, and make your content discoverable and subscribeable in the same way. And in either case, you own your content — even if you use Leaflet as your hosted CMS, published data lives in your PDS where you control it, and all the social graph stuff persists even if you stop using Leaflet or we ever shut down.

Self-hosting a website is great but also considerable overhead for many folks, and we want to make it easy to publish and still have control and avoid lock-in. We even see folks doing hybrid approaches, e.g. using Leaflet to publish (for easy to use CMS + nice social features) but also pulling published data to render directly on their own website.

It's very different from what you get with a concentrated single platform like Substack (or Instagram, YouTube, etc) as far as audience reach, and early days with the ecosystem, but I think it's valuable in a different way. It's more aligned with the open web, and importantly, it's more antifragile — there are many ways to reach people and interact with your readers, from Bluesky to Leaflet to other reader apps, search tools, etc. Network effects aren't there yet to the degree of Substack, but a lot of cool things are emerging and it feels like an exciting time to build here together.

Re: Substack writers, you need a website

#107
I just have website.com and my Substack is subdomain.website.com. If I ever wanted to move off (I definitely don't!) I could keep all the urls exactly the same with self-hosting.

But substack solved distribution (and community, and bookkeeping, un-distribution etc) and it solved getting paid for my writing, which is not enough to live on but its definitely significant and well appreciated. It is worth much more than its fees, because the counterfactual is that I don't have any of those things. I think it's a huge mistake to lump those together as "convenience", its a lot more than convenient!

The only important thing to me about having a non-substack website is that its good to have a place for more permanent information, lists, contact, etc. But even for many writers, that kind of stuff becomes stale so quickly that the personal sites don't tend to matter much, or even make them look worse! The floating social network spaces are much more valuable. Even losing my x.com would be much worse to my day-to-day life than losing my domain, though I may wish it were otherwise. And I cannot replicate that elsewhere. The social networks are big because they have genuine utility.

Re: Substack writers, you need a website

#108
post #8

Alternatively, use an open platform that doesn't lock you in: * Leaflet * Offprint * Pckt

I get that we all want people to be on open platforms but I feel like the really staunch part of the open platforms only crowd is not taking the time to understand why people like platforms like substack.

I agree, very aware it's way more than just the publishing / email tools! Also posted a top-level comment about building alternatives with https://leaflet.pub and https://standard.site - and yes I think really important to consider the full list of things you get with Substack: blog + email, easy to customize, monetization, social features + network, all in one platform, long tail of features…

Did a short talk on this at a local meetup recently, basically on how we might collectively re-create the entire stack of what Substack offers, in an open ecosystem, with a strong focus on network / distribution, more so than just features.

It's a tall order but I do think there's a big opportunity here beyond what any single app can or should tackle, in building an open alternative to the whole longform publishing stack, combining the tools and the social network side. AT Protocol and the Atmosphere (ecosystem of folks building on it) are pretty well positioned here. Lots of nice ways to get autonomy and ownership with web publishing + distribution and social affordances at the same time.

Of course a big challenge in bootstrapping the network and building the cultural footprint and giving folks flexible ways to make money and reach new readers, but I'm encouraged by how much progress we've made collectively just this past year.

Post reply on HN