Got you. Yeah tested now and some crashed, others did not but it took a while to get the data. Using Vanadium browser.
Not sure if I understood what preset by height is, but had no problem on the page, changed the many timescale of the chart and wen to the many options on the bottom toolbar without a problem. Phone gets a bit hot though.
*It doesn't format
Maybe you can use this :
https://chromewebstore.google.com/detail/oblisk-sync/jbjbhombfpkgggbghnjgdigbkflocmlk
It does format for reading, or anything like that, it just allows you to save pages.
Is there a nostr-based service like Pocket https://getpocket.com ? Just a browser addon to send a webpage to a read-it-later list, already formatted for easy reading without the website clutter.
Maybe you can use this :
https://chromewebstore.google.com/detail/oblisk-sync/jbjbhombfpkgggbghnjgdigbkflocmlk
Phoenix desktop is the way. Node in the phone not a good idea.
The fiat/shitcoin linear mind is a terrible thing. About bitcoin magazine article about hodler fee(LMAO) and all that are concerned about "security budget", Satoshi said in a comment something that relates to this, unlike other commodities , bitcoin's cost of production(mining/hashrate) tends towords the price, this means that the higher the price the higher the hashrate, the lower the price lower the hashrate. This means that hashrate/security finds an equilibrium according to btc price, wich means the network security will always be adjusted according to the network total value(market cap). So stop crying about security budget and that we must find a way to give poor miners fees, either way bitcoin magazine can always donate to miners.
I avoid web frameworks, for simple things I just use plain ts/js, for medium complex sites i just need a non intrusive binding js lib, i like jails js and simulacra. That's it, I like my html as plain as possible.
Wss also rely on dns, the nostr advantage is that notes go to many relays, blocking on relay wont do anything, so your wallet and mint won't have one domain as a single point of failure.
If it's done like I said in my comment, it doesn't matter if they attack a relay because the note/commands will go to many different relays.
Yes that's what I assume, the same way an lnaddress returns an invoice you can setup to always return the bolt12, should be easier since it's a static code, but it's not retro compatible, wallets that don't support bolt12 will ask for an invoice and won't know how to handle it.
Not sure but I would say it is.
Been diving into how DNS changes impact ecash. Took a look at Fedimint and Cashu’s approaches and possible solutions. Would love your thoughts on it. 
https://open.substack.com/pub/orangewindjammer/p/5-on-ecash-dns-and-configuration
As for the ecash mints nostr solution i am not expecting nostr to be used to get the updated mint url like your flow diagram, I'm expecting the wallet to send and receive commands/data over nostr notes, not api calls.
Yeah got it, and I'm with grapheneos, no google, could be just luck on timing, will need to test more to see if payment fails when the wallet is closed. But this is very cool!