Content
@
0 reply
0 recast
0 reaction
Kaloh
@kaloh
Hello word 👋 I'll be posting snippets of my content (newsletter & podcast) here. This should be a place to discuss blockchain art, products, and tech. /kaloh
9 replies
7 recasts
78 reactions
Callum Wanderloots ✨
@wanderloots.eth
Awesome! Love the use of a channel for this, really helps tie together external writing into a single spot ✨ I came across your substack newsletter when I first started there, but now it looks like you post on paragraph? Do you double publish it or is it different writing? Trying to figure out my own workflow 😊
1 reply
0 recast
0 reaction
Kaloh
@kaloh
I’m publishing twice, but only sending via substack or paragraph so readers only get 1 email Migrating to paragraph at the moment, but need to move premium subs + make sure delivery works well Then I’ll set up an onchain membership (not only fiat) Lots to do
1 reply
0 recast
0 reaction
Callum Wanderloots ✨
@wanderloots.eth
I see, so you’ve blended the email address list between the two, rather than separate the paragraph list and substack list? And for on chain membership, is that where @hypersub comes in? Appreciate the insight! Still trying to figure out a workflow with minimal double posting, considering I also put on my blog
1 reply
0 recast
0 reaction
Kaloh
@kaloh
Yes, i was blending towards Substack Now I am blending towards Paragraph At some point I will just use Paragraph, ideally soon Hypersub is for the onchain subs, currently using normal subs via substack. That's the last step
2 replies
0 recast
0 reaction
Jonny Mack
@nonlinear.eth
@wanderloots.eth the nice thing about having the subscription data onchain is that it becomes permissionlessly composable, meaning: token-gated mints, group chats, irl events, airdrops, etc. no need to query a hypersub api, wait for integrations, or ask for our blessing. its a recurring payment rail that ✨you✨ own
1 reply
0 recast
0 reaction
Callum Wanderloots ✨
@wanderloots.eth
Yes! Exactly! Appreciate your input, these are features I’m very excited about with true web3 integration to publishing systems My current issues relate to bridging my web2 audience (since I do a lot of educating people new to web3) and maintaining domain authority of my own website while adding web3 functionality
0 reply
0 recast
0 reaction
