Show HN: Seedling – A Decentralised Medium (seedling-d.app)
Current version lets authors publish markdown content from their GitHub account and lets users tip articles. No wallet or GitHub account is needed to browse content.
Authors link their GitHub account or organisation to their wallet address via oauth and an on-chain user registry, after which they can submit article URLs directly to the on-chain content registry. The content registry ensures only registered users can publish, and only from their registered GitHub account.
By adding different hosting options and expanding the feature set, the ultimate goal is to create a platform for independent journalists to publish without fear of censorship or repression, and to fund their journalism through direct tipping, subscriptions and profit sharing models.
48 comments
[ 3.1 ms ] story [ 105 ms ] threadAnd well, the original idea of blogs was completely decentralized (“there is this thing accessible through HTTP”) with bunch of ad-hoc API surfaces for metadata and “pingbacks” (ie. back references). Then in the last few years there is Medium.
Bottom line: You are solving solved problem and have some kind of path-dependent view of that problem space that does not really make sense.
A better thing to use to be decentralised is ipfs. Which worse comes to worst if your file gets unhosted then do your own node.
Or Nostr would be good and might avoid needing a blockchain (and thus the expense and complexity)
Ideally many different hosting options should be supported.
FTFY.
Remember many on this site are partially responsible for the ad-ridden web and a proliferation of all sorts of spyware.
OTOH, we wouldn't skewer someone for charging for yet another toy SaaS and posting a Show HN, so... let's be a little more balanced.
A common motivating concept for decentralized is no authoritarian oversight to deplatform you.
You're seeking editorial influence (control) from the start.
Setting aside what users want versus what you want, as a platform technology you need to be careful here.
You way want to brush up on the safe harbor laws for Internet infrastructure/pipes/hosting firms and technologies versus the lack of safe harbor for platforms with desire or ability to exercise editorial influence or control on a user or content basis.
You can navigate this, by having reasons such as "I'm not editing, but by associating users with a non-anonymous identity they will self moderate", as you've noted. You can, with such reasons, still have a bit of cake after eating it. But be careful not to veer into actual editorial control unless you're prepared for full liability.
Need to balance the freedom to publish anonymously with the risk of people claiming credit for other people’s work.
Perhaps the platform should allow any url to be published and restrict tipping to only authenticated users’ content.
Is there a reasonable long term platform fee that you would find acceptable? Say 1% or 0.1%?
Also, the data is always available on-chain and the protocol is open so other people can write an alternative ui with their own blockchain query capabilities. Like Bress.xyz does with Mirror.xyz.
Payments can be automated on-chain.
UserRegistry: https://polygonscan.com/address/0x5Ec6A3284049E8b3e5966882fd...
ContentRegistry: https://polygonscan.com/address/0xF86eFfA878F484DF4a2D2d1703...
TipJar: https://polygonscan.com/address/0x1c4a6b233DABf5566Ae7196657...
Slightly different vision and approach but both are publishing platforms. There’s plenty of room for competition in this space, I think.
Monetisation: Seedling uses direct tipping instead of NFTs. Plans for paid subscriptions to private content. Crowdsourcing will offer share of tips for investment.
Architecture: Seedling is primarily a discovery service and will allow content to be hosted on different platforms. Seedling has no backend server to deliver content.
Any plan on integrating other chains? This would be great on Solana
I've noticed occasional issues with Polygon, which is frustrating, and some intermittent viem/Metamask errors that I only seem to get with Polygon. I've put it down to the immaturity of the web3 stack for now but it needs to get better.