MadMaxi on nostr

Recent Notes

Added what should be enough documentation for people to spin up their own zap-stream-core: https://github.com/v0l/zap-stream-core/blob/main/README.md#deploying If something is missing let me know. A...

MadMaxi @MadMaxi 1758558669

Yes, very interested in that!

goatmeal · 23w

the fetishization of non-mining raspberry pi basement nodes caused maxis to become blinded to the fact that node count is the most easily gameable stat on the network

MadMaxi @MadMaxi 1757686804

You calling me kinky?

nostrich · 23w

Based.

sedited · 23w

Not sure how you want to resolve a dispute about the effect of policy with a soft fork. Seems unrelated.

MadMaxi @MadMaxi 1757521424

Softfork to introduce new Consensus Rule maximum limit on OP_Return at 83 Bytes.

sedited · 23w

That won't solve this dispute, it is about prohibiting relay of data embedding transactions in general.

sedited · 23w

There is no resolution mechanism for the relay policy dispute. My hunch is this fight will persist for a long time. It is likely in my view that the share of knots nodes running on the network will ke...

MadMaxi @MadMaxi 1757516645

Incorrect.

The resolution mechanism is Nodes enforcing their Will upon the Miners, by activating a Softfork.

sedited · 23w

Not sure how you want to resolve a dispute about the effect of policy with a soft fork. Seems unrelated.

jimmysong · 41w

For me, the bigger question around this OP_RETURN debate is getting rid of the datacarriersize option (one proposal gets rid of it now, another deprecates it for getting rid of it in the future). The...

MadMaxi @MadMaxi 1746488952

Yes, it's important to distinguish the difference between changing a default value and removing a configuration option altogether. The two are being conflated, and it muddles discourse.

ODELL · 74w

I HAVE LOST A DECENT AMOUNT OF SATS RUNNING LIGHTNING NODES.

MadMaxi @MadMaxi 1726846994

SATS ARE NEVER LOST, THEY ARE ONLY M.I.A