102 sats \ 4 replies \ @jeff 31 Oct 2021 \ on: SN RFC: substackers meta
Amazing creativity. My 2 satoshi.
  1. Interesting. Will you be able to sign up for the subsub, but ignore the sub (parent)?
  2. It's typed more than it's said out loud. I think a shorthand will be created. Eg. s, ss, sss... ssssss. Then, memes will follow related to sinking ships -- which is okay. :)
  3. Fun. But, would the substacker be stacker.news<substacker name>/<substacker name>?
  4. I think you need to launch, with a well-thought-out abandonment policy. Squatting will happen quite fast, I suspect. Or, maybe you could use some bootstrapping funds - sell the initial rights to the substack for a fixed amount of satoshi. I think you could do some really cool stuff if you allowed a mini-turing complete language to run against the object model you have. Examples: give 25% of revenue to a random charity. Give 5% of revenue from the top 5 posts to the top post. Give 20% of post-revenue to a random user (or comment) each week (making commenting akin to entering a lottery. I think a garden of models would bloom, each kind of both competing and doing their own thing.
write
preview
13 sats \ 1 reply \ @k00b OP 31 Oct 2021
  1. yes I think so
  2. yes
  3. I think to create a sub there might be an upfront cost or like 10,000 sats.
reply
1 sat \ 0 replies \ @gmd 31 Oct 2021
re 3) 10k sats Not terrible- at the current sats/USD, it's similar to price of buying a domain for a year, which might be enough of a deterrent.
I wonder if maybe it could be something the community votes on for approval to avoid the potential spamming. Haven't been on indiehackers for a while but I think their subforum/groups functionality, after you apply and you need a certain number of people to express interest in joining before it becomes a real group.
reply
13 sats \ 1 reply \ @jeff 31 Oct 2021
Just checked out the repo, if your ambitions are to eventually make this distributed. You could make the payout-hook into a callable with some kind of standardized output format that the server understands. Then allow a substacker to config a pointer to the endpoint.
ex: stacker.news would send a POST w/ a body such as {'substack' : '/s/mysubstack', 'commenter' : '/u/jeff', 'comment' : '1234', 'tip' : '100'} ...and then my own server could send back: [{'payto' : '/u/jeff', 'amt' : '50'}, {'payto' : '/s/erickuhn19', 'amt' : '20'}, {'payto' : '/u/anonporridge', 'amt' : '30'}]
...this could be open sourced, or closed source. People could audit both the history, and "test" the endpoint themselves with a hypothetical POST-body.
reply
1 sat \ 0 replies \ @jeff 31 Oct 2021
Figuring out how to give the callable more context would get more interesting.
reply