pull down to refresh
105 sats \ 5 replies \ @SimpleStacker 7 Aug \ parent \ on: Growing Stacker News From The Bottom Uprising meta
I think @sox was actively working on custom domains but not sure the current status. From what I can tell, @k00b is working on a major refactor of how the backend database works, which touches almost every functionality, so they may be focusing on that first before other major upgrades
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.