I'm unfamiliar with Apples user interface. I tried to use one once and I was so unfamiliar with the gestures it was expecting from me. I was more accustomed to androids back home and menu button at the bottom of the screen.
Therefore Apple has bad UX
At least that's what you sound like to an android user and how people who say Bitcoin is hard sound like to Bitcoin users and how people who say noncustodial lightning is hard sound like to noncustodial lightning users.
Take into consideration "gaming for a non gamer"
https://www.youtube.com/watch?v=ax7f3JZJHSw
There are cues users (not just gamers) are just so familiar with that they associate that familiarity with good UX and non familiarity with bad UX although nothing could be further from the truth.
And the majority of the people in the comments is saying this is a nutso take lol.
No you have to get Bitcoin in their hands
Try lightsats.com to set her up.
Asked someone I know who doesn't use nostr what they would say, this was their answer:
"Salvadorans know volatility. They know the risks of corrupt money better than most. They simply need to ask themselves what is more volatile - the day to day speculations of Bitcoin buyers and sellers versus any other currency - or the money printing and management policies of opposing governments being elected every 4-8 years and each spending recklessly on opposing means."
I mean that's just nutty. I understand not activating anything that hasn't been clearly communicated, I understand using BIP-08 instead of BIP-09, but to seriously be completely against an upgrade that makes implementing channel factories significantly simpler is asinine. On what principal? With what purpose? To what end?
Long term thinking is the name of the game, but every time I meet a newbie, my first concern is that they don't go nuts dumping all of their money into it.
Instead, we (not just myself) encourage DCA (dollar cost average) which is what your president kinda started to do when they started buying 1 BTC everyday.... Allegedly.
Basically, if you buy once while its high and buy again when its low, your average buy in is in between. The longer its low, the lower your average buy in and if its high one day after that, then you might have more money than what you put in, even if its not as high as when you bought that one time when it was high.
Here's the lopp resources for DCA:
https://www.lopp.net/bitcoin-information/buying-earning.html#strategies
Hold my beer type post
Hear me out, half baked thought.
What if you just had a docker container that you distributed across a federation of cloud service providers which all run the same container and sent the hash of the output to each other.
Now you should get the hash of the output from all of them to make sure they're in consensus, but I know you'd probably just access the output from a website defeating the purpose of having a federation.
Also why aren't you just trusting the output of 1 cloud provider rather than getting the same output of a federation of cloud service providers? Idk but probably for the same reason you're using Liquid.
But think about it guys. No append only merkle tree, pay for what you use, very efficient, and much more honest about being a federated custodian.
nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8
Blockstream Green Wallet
It combines Bitcoin with Lightning and Liquid
Tether integrated
_______________________________________________________
Unlock the Power of Bitcoin: Mastering Blockstream Green Wallet
Which is why I don't use it lmao. I don't need bloat in my Bitcoin wallet lol.
Just the Mises institute site? Nah dawg, read the OG. "Human Action" by Ludwig Von Mises https://mises.org/files/human-actionpdf-0
"How The Economic Machine Works" by Ray Dalio could be a good primer too. Talks about how the system as it is now works
The other option is don't use Twitter
Twitter influencers: "Not possible!" XD goodness gracious
I pointed this out on like the day after release or something. I even pointed out how verification of apps can happen that you can't really do with webapps (you know, hash the apk). I pointed out that it just has an unreasonably larger attack surface. I then linked to a tweet by a web wallet dev who went through all the security problems they experienced and why they no longer do web wallets.
At the end of the day though, Tony has created an apk for Mutiny, which you can compile and hash to check against the precompiled binary.
https://github.com/MutinyWallet/mutiny-web/releases/tag/v0.4.8-1
You can't sanitize user input in the frontend that has to be done in the back end :clap: :clap: :clap:
I don't really know why we're doing this, but its fun
relayable.org is the relay I got it from.
This is the vid: https://m.youtube.com/watch?v=UVGwSqyGGH4
No, Tony is absolutely right. Best practices are a solution and pasting an invoice (that was not directly messaged for only 1 person to pay) is a bad practice that we did stop doing a while ago, so I'm a little amused that this has come up again lol.





