31–40 of 49 posts
Where are the actual content payloads stored?
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.
Earlier quoted context omitted.
Lol! It’s not my intention for this to be a get rich quick scheme but there are running costs (user registration and TheGraph network payments). If the platform is to be self sustaining it needs to cover its costs. Is there a reasonable long term platform fee that you would find acceptable? Say 1% or 0.1%?
So it sounds like you can DoS the service through user registration and graph usage?
Do you have a link to the contracts?
I'd rather use Nostr and a client focussing on long posts :) Like https://habla.news/
If there is requirement to link a github account, then there isn't any kind of decentralization, as github is then the one centralized point. And 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 solve…
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)
If there is requirement to link a github account, then there isn't any kind of decentralization, as github is then the one centralized point. And 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 solve…
I agree, if you have to use github they have pages. 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.
Earlier quoted context omitted.
I agree, if you have to use github they have pages. 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)
IPFS and Nostr are both brilliant but they have their limitations. The main issue I see for an app like seedling is that by submitting your content you lose control over it. You cannot edit or delete. Ideally many different hosting options should be supported.
Earlier quoted context omitted.
I don't think it's unbalanced to call BS on a service claiming to be decentralized that in fact relies on a single centralized service they do not control, twice over. (Once for auth, second for content).
Yeah, I guess it’s more accurate to call it an [almost] fully decentralised discovery service rn. Decentralised hosting should come later. The almost is for the oauth server, which can be improved by adding other independent trusted servers in a permissioned network.