pull down to refresh

I don't understand the technology behind it. Is this a choice or is it an unavoidable feature of the protocol, much like how bitcoin block transactions are public?
100 sats \ 0 replies \ @Scoresby 4h
I was watching @moneyball's talk at bitcoin++ (05:25:04) and he talks about this a little (apparently it only recently became public knowledge).
When I inquired, it's not a technology limitation but actually an intentional policy decision by their NC...uh...I can't steelman the argument. They feel like it's disingenuous to users to not publish it because of the risk of a Spark Operator potentially publishing it
Also, I did a quick scan of @BTCsessions recent WoS tutorial and he doesn't mention this privacy trade-off.
Seems like Spark maybe might have wanted to make this design decision a little more clear to users.
reply
an unavoidable feature of the protocol,
It's not a protocol, it's a centralized exchange.
The server inherently needs telemetry to operate, this would be exposed by someone else had they not front-run it.
reply
100 sats \ 1 reply \ @k00b OP 5h
It's either a choice or an oversight afaict. They are encoding the spark address into the invoice when they could, if they wanted, obscure it.
reply
Spooks be spookin.
reply