pull down to refresh
36 sats \ 8 replies \ @SimpleStacker 10h \ parent \ on: Growing Stacker News From The Bottom Uprising meta
I guess instead of competitive advantage, I meant more like "market niche." I don't think you can expect to compete with Substack directly at first, so you have to offer something different that attracts a group of users, and I thought Markdown support could be one of those things.
I think it could be attractive to the bitcoin community since there's a high proportion of devs, and markdown is the native language of all writing input on GitHub
But definitely, in the long run, it'll be P2P bitcoin that would mark it out as substantially different from Substack
Regarding your earlier point about SN being as big as we can get... I remember there was literally no sports discussion here before @grayruby arrived. He single handedly created all the alpha that now constitutes the most successful territory here. I can't help but think that can be replicated.
reply
I think that would be great. And by the way, I think the substack idea is pretty consistent with what you're thinking. Especially custom domains and customized landing pages for territories will let SN users create communities tailored to specific interests that attract people from across the internet without them even knowing at first what lightning and zaps are about.
reply
The custom domains and landing page would indeed be fantastic. I have listened carefully when @k00b talks about future plans. Is that what you think will eventually be implemented? I know there might be complications in coding it.
reply
reply
The custom domains work is done. It introduces some complicated security issues so we're holding off on shipping it until I can give it my full attention ... which it will have after I complete my boil-the-ocean refactor.
The refactor is important because it unlocks more complicated payment relationships (and that's basically what stacker news is: complicated payment relationships), e.g. crossposting in multiple territories (a post in N territories, needs to pay N territory founders ... and so does a zap on that post, and so does a comment and the zaps on those comments), paying for things with combinations of CCs and non-custodial payments, paying for routing fees with CCs, territory-specific reward pools, zap splits that don't use CCs, very detailed satistics, stacker, territory, and site-wide analytics.
reply
Most of this was relatively easy when we were custodial. Everyone had a balance and if you did things that cost money we could assume you paid with your balance. And if you received money, we could assume it went to your balance. But now:
- sometimes you pay with CCs
- sometimes you pay with reward sats
- sometimes you pay with an invoice
- sometimes you receive CCs
- sometimes you receive reward sats
- sometimes you receive via an invoice
- sometimes when you pay with an invoice it fails minutes, hours, or days later than when you attempted payment
- sometimes when you receive via an invoice the payment fails minutes, hours, or days later than the invoice was generated, or the invoice is never paid because (7) happened
- something you want to do (1), (2), and (3) (and implicitly (6)) simultaneously (as stackers have requested repeatedly)
So now when you do something that costs or earns you money, we can't assume anything and have to maintain detailed knowledge about which of 1-9, or combinations of 1-9, it was ... which only gets more complicated as we add more complicated payment relationships.
That's what the refactor does. And it's awesome. And I'm incredibly excited about (eventually) completing it.