Avatar
Mark
4bc6e43c4a86c764208104fc8c2e18cb38a50b4bbe2eaac63aa196f588e97178
One day, I'll be good at producing quality software and will have intelligent things to say about it

"Many people think they are thinking when they are merely rearranging their prejudices." William James

I'm not against it - on twitter I tended to follow people I actually know, and then put others in lists and essentially use them as a news source.

Is there any nostr client that does something similar to twitter's lists? Always surprised by how few people use twitter lists - only way to make twitter usable imo #asknostr

"To realize the spirit of Mu you must, without being sidetracked, travel along an iron rail stretching to infinity. One halt, much less many, will thwart enlightenment. The narrowest separation from Mu becomes a separation of miles. So take care, be vigilant! Don’t let go of Mu even for a moment while sitting, standing, walking, eating, or working.”

One underrated thing about vim modal editing is the magic of having the cursor bounce and then transforming characters in a few keystrokes. It's not even about efficiency. It's the innocent fun of a kid in a jungle gym. And it never seems to get old. It significantly increases the joy of coding for me

Replying to Avatar waxwing

https://hodlboard.org

To sign up for writing on the forum, you need to prove current ownership of one utxo (which you do not reveal; zkp) of taproot type of value 500K sats or more.

Instructions on how to do it linked from that main page. It's a bit fiddly but not difficult if you have tech experience. You can use Sparrow for accessing the coins after creating the ZKP of ownership, or you can use Core.

(Also it *should* be easy, not 'fiddly' but wallets don't support accessing private keys).

Despite the 'hodl' name, the coins are not locked after you make the proof, you can spend them immediately.

General background reading, first half of https://reyify.com/riddle

The anonymity set is about 200-300K utxos, but the server can verify your proof ~immediately!

The proving tool is at https://github.com/AdamISZ/aut-ct ; follow installation instructions on readme or choose binary release for macos or linux.

Still a WIP. Keep a copy of the private key until you spend it! Bear in mind the keyset updates once per 24 hours. Make sure your utxo was confirmed before the blockheight of the current keyset in /keysets.

Is it possible to create multiple accounts with the same utxo? If not, this seems like a great solution to spam

I think the more devs that accept the possibility of jail and continue anyway, the lower the chance gets.

Which begs each person to ask themselves a question: Is jail a price worth paying to defeat this injustice?

Already watched it, and felt optimistic myself. I think their bucket already has too many holes, and more are being created, at an ever increasing rate - it's too late to plug them all.

It's unfortunate the powers that be cannot see this - or maybe they do but they feel they have to try, that this is just the way it has to be.

It seems they intend to throw a tantrum. I imagine it'll be scary, some will have wealth confiscated, some will be jailed - all in their desperate attempt to swim against the current. And then they'll lose the financial powers they have anyway. Such a waste.

Long article, but worth the read.

https://medium.com/@john_25313/c-isnt-a-hangover-rust-isn-t-a-hangover-cure-580c9b35b5ce

"But, the reputation that memory safety problems currently have of being plentiful and trivial for sophisticated attackers to find and exploit is wrong.

[...]

C programs generally have a small number of external dependencies, where often those dependencies are among the most used pieces of software out there [...] Most other languages are much better equipped to support programmers leveraging the work of other programmers. In some sense, that’s a good thing from a business perspective. But from a security perspective, more dependencies not only tends to increase our attack surface, but it leaves us more open to supply chain attacks.

[...]

I have personally always been far more concerned about minimizing dependencies than buffer overflows. There are straightforward approaches to minimizing memory safety problems [...] But digging into each and every dependency?

[...]

My intent here isn’t to argue for using C over Rust, it’s to show that decisions around language choice are far more complex than the sound bytes people fling around."