Avatar
semisol
52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd
πŸ‘¨β€πŸ’» software developer πŸ”’ secure element firmware dev πŸ“¨ nostr.land relay all opinions are my own.

I did not watch the linked videos because most podcasts are crap, but yes.

UTXO set polluters will keep polluting. They do not care about OPR only that their data becomes β€œpermanent” and unprunable in the UTXO set.

Inscribers will not pay 4x either because they like their SegWit discount

So this benefits no one

βœ…

nostr:note1dqezywlynumu2v6csv8vmw9tr8xv74xpylgpwnm3ql0gkzqdjyfqj5y2xg

the future API now has an internal cache state

now the future value is automatically copied into Go-space and cached in the future struct once you do Get()

it will automatically release the future as well when you run Get() or Cancel() as it is no longer needed because you either already have the value cached now or discarded the result

NFDB progress: I hate the Go bindings and therefore am forking them

Direct-to-dev funding has never been as important.

By going through OpenSats and the likes, you let OpenSats decide what you are voting for with your money. Which is usually a corporate agenda, as a majority of the board is.

Fund devs directly. Cut your donations when you disagree.

nostr:note1zjf58dcrxd2ultl0ndw6a3uh9ey4jn9x9up8tfy8qfvs762x594syqp7j4

Replying to Avatar semisol

Yes

OP_R only has a benefit above SegWit at <512 bytes or so. Otherwise they will keep polluting the UTXO set with stamps the same reason they did even while SegWit exists. And also the SegWit discount is appealing to people that don’t want to pollute

So it’s just a giant distraction not unlike politics

I thought [removed] was bad but this is worse.

how is x86-64 a real ISA

🀣

recommend me some niche relays*

my indexer is limited to 700Mbps of peak throughput on a total of 50 relays

the problem is that the relays are slow as shit

recommend me some relays