pull down to refresh
"when goods don’t cross borders, soldiers will"
Twitter ratio: when the post gets more replies than RTs
SN ratio: when the top comment gets more sats than the original post
I came to a life-altering revelation today after some conversations, and I realized I've been lying my whole life. Pretending to be humble, even to myself. I've been so scared of being seen as arrogant. But I AM arrogant. So I spent 2000 sats on a stacker who called me out. Truth deserves reward.
Working on a small essay about why bitcoin maximalism, which I saw as a cult, is actually a very good strategy. Also going to include an example of how easily stacker.news can be controlled, and how cheap it would be. Guys, not storing IP addresses is not good, it just makes you easier to cyberturf. I'm gonna make sure about my assumptions though before I slander anything.
There is certainly incentive for stacker.news to not care about bots, if the bots are good enough to seem human, that's how you get good investors. So might be a valid strategy to not make such critique. Who cares if the site quality goes down for a while, when the upside is millions of dollars (yes, dollars, because I'm not here to play pretend that dollars aren't more stable than freakin bitcoin). The botting and ads are nearly, and actually, unsolvable in reality. I'm a stacker.news maximalist so I won't do anything that could harm the site.
End of very interesting observations.
Ah I see.
siggy47 said below there was an update as well from GrapheneOS. Apparently JavaScript JIT is disabled and we need to add an exception.
So solution:
Open Vanadium -> Settings -> Site Settings -> Scroll around the middle and under Content go to JavaScript JIT -> Add site exception -> add Stacker.news
Then reload and it should work
What started out as improving rendering performance ... led to me refactoring much of the code base and upgrading many of our dependencies last week ... that deployment failed so now I'm upgrading the remaining dependencies and other broad brush things that are too numerous to enumerate.
The next few changes we'll do will be big so it's nice to "clean our room" first.
Kudos to the spirit of experimentation. SN as a platform gives some tools, but that can't (and shouldn't) release people from the task of fucking around and seeing what they can accomplish using what's available to achieve their goals. This is a perfect example of that, thanks for elevating the discussion.
Hey, creator here! Happy to answer any questions.
Yes, today this is (essentially) private hashkey-lookups. Supporting range or batch queries (for example, to fetch data on all the addresses in your wallet) is something we are still working on.
We've had a few people suggest doing something like "private RPC". Do you know what metadata in particular (which RPC calls) is sensitive? Is the idea that miners and other full node operators would like to hide what blocks they look at etc? Or is it more for light clients that want to hide metadata about what they look at? Would people be willing to pay for a "private" (via homomorphic encryption) RPC endpoint?