pull down to refresh

One of those things you referred to in your first point is the wallets that I have been working on.
Being able to send credits to each other directly affects the UX of wallets. If we only allow sending sats:
  • No confusion about why one is receiving credits: you don't have a wallet or it's failing.
  • No confusion about whether you’re sending credits or sats: you’re sending sats.
  • No confusion about how payments between stackers work: everyone is sending sats to each other.
  • No confusing credit fallbacks that depend on whether the sender or receiver failed.
  • No need to ever mention “credits are turned into sats via rewards,” “half-life of credits,” etc.
So I think it’s absolutely fair to suggest this change now, since it has a direct impact on what I’m currently working on. I’m essentially maintaining code that I know would be a lot simpler and could provide a better UX if I were allowed to change something that seemingly seems unrelated but is actually very related on closer inspection.
Additionally, you’ve brought up multiple times that we need to make the product simpler by a lot in general, but to me, it looks like you currently don’t want to consider the one change that could actually make the product simpler by a lot… because it’s too early to consider it?
0 sats \ 3 replies \ @k00b 3h
It is fair to suggest it. I never said it wasn't. I just don't want to fight about it (i.e. sides, i know it's better, the one true simplification, you think this and that, you're doing this and that), especially here, and when you're on a vacation.
reply
0 sats \ 2 replies \ @ek 3h
Fair
reply
50 sats \ 1 reply \ @siggy47 OP 1h
What's more fun on a vacation than a good SN "airing of opinions"?
reply
reply