pull down to refresh
So to use hosted SaaS, not only do I give you my bitcoin addresses, but I pay you with KYC'd fiat, associating my identity with my bitcoin.
Who is the SaaS version for exactly? The people that are, correctly, paranoid enough to self-custody, yet not paranoid enough to let you know who they are, where they live, and how much bitcoin they have?
A self-hosted watch-only wallet with some privacy preserving observability alerts makes some sense to me, but I don't understand the SaaS version. The customers would be naive/mistaken and you'd be creating a honey pot, right?
By fast food analogy: I like in-n-out because it serves hamburgers with little variation and has a relatively limited menu. It makes great hamburgers, and at scale, because it makes them with little variation and has a relatively limited menu.
I'm much more interested in building, and using, an In-n-out than a McDonalds.
Beyond information overload and engineering overload, it'd fracture everyone's experience on SN.
Under high variation regimes, the things I say about my experience aren't likely true of yours. e.g. this discussion we are having would be much harder to have if there were even a handful of modes of SN.
There's something special about us all playing the same game at the same time.
On that point I disagree because counting people, determining with 100% certainty that one zap = one human, is impossible today and will be more impossible tomorrow. Trust/reputation can be used to make better guesses about who is human, but it makes the system opaque and unfair. As is, it may be unfair, but it's transparent.
I agree.
Optimism, after Scoresby did, made the point that in tuning for sybil risk we underestimated "activism" risk.
I'm thinking we should make upsats = downsats = boostsats in terms of weighting. Game theory tells us what people should do when they are rational and energetic. It's a great starting point for system design, but alone it tends to produce systems that humans don't like, because on average we are irrational and lazy.
Seems like something with your alby extension. I'd refresh the site and alby, then try it.
You can also disable webln (which is used to pay directly from the extension) by unchecking enabled.
Why does the project need a stripe integration?
Replacing is the wrong word imo. Displacing is more accurate. Humans will always value humans for their humanness, and will be displaced in everything else given enough time.
Even those that think capital will keep them competitive are wrong. At some point machines will be the wealthiest entities on earth and deploy capital and other machines better than any human.
If we don't destroy ourselves along the way, I think most humans will merge with machines. First in relatively crude ways. Later in more sophisticated ways. And finally by creating organic machines that we, in effect, reproduce with.
In 5-10 years I think employment numbers won't be much different than they currently are. Our work will just become increasingly abstract as it has always tended to.
Smart! I’m a pathological squasher.
@pitiunited cool beans breh
Making weight of zaps = weight of downzaps = weight of boost is another thing we're considering. But it makes defense 3x more expensive for the same provable sacrifice. It's tricky.
I'm implementing things we were planning to implement anyway, because they get at the issue obliquely. If that's not enough, we'll go a more direct route.
I'm thinking of allowing folks to toggle on the horse/gun from their settings - no wallet required. We've also been wanting to only display them on profile pages for clutter reasons.
Also, I'm implementing #1406989 this week which should help in fighting fits of irrationality - past downzaps are on unequal footing with current upzaps.
k clank on