Avatar
Elephant in the root
6e77f4f3c9995e0887d02dc95b39692f58641ed5b073972ef86cd6b61ecc6bae
Poisonous anti-plantist, anti-fungist, anti-shitcoinist, anti-governmentalist, anti-wokist, anti-bullshitist.

That's one of the few things I don't like either. More precisely, I don't like implementing it. Using it is OK. Some sort of first-class support would be nice. But thankfully I only had to implement it very few times.

Still, the rest is too good not to use it.

Replying to Avatar Max

The nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 software license agreement is really bad...

eCash projects should learn from the mistakes of Chaum, instead of doubling down in the same direction. It is ESSENTIAL for these tools to be FOSS.

> You are not permitted to lease, rent, distribute or sublicense the Software or any rights therein.

> You also may not install the Software on a network server, use the Software in a time-sharing arrangement or in any other unauthorized manner.

> Further, no license is granted to you in the human readable code of the Software (source code).

> You agree that you have no right, power or authority to make any modifications to or unauthorized copies of the Software.

> You may reproduce and provide one (1) copy of the Software and Documentation for each device, computer or workstation on which the Software is installed. [QubesOS users go lol]

> You agree not to modify, translate, reverse engineer, decompile, disassemble, or create derivative works of the Software or assist someone in performing such prohibited acts.

> You agree not to import or export the Software or any Documentation (or any copies thereof) or any products utilizing the Software or any Documentation in violation of any applicable laws or regulations of the United States or the country to which you have imported or exported.

https://www.fedi.xyz/eula-en

That's disappointing.

Yes, that. To succeed we need to keep theAPI accessible. Having great libraries can help but only TypeScript is not going to cut it. I suspect we'll need more of the performance focused languages as nostr is very heavy.

You have to handle

- cryptography

- communication with a central server

- UI

- ...

vs user choses any external app he likes.

The latter is clearly simpler.

A protocol to ask external wallet for cashu-zaps could partially solve it but there's still the added complexity of parsing and validating new kinds of events.

I'm skeptical of microwaves being an issue. Visible light has *more* energy and is harmless. I'm not aware of any RCTs on this topic either.

Various multicoiners call maxis toxic but did anyone measure what percentage of them can provide a coherent argument for having multiple monies without using strawmans, ad hominems or similar attacks? And how does this compare to maximalists?

My guess: the percentages are about the same in those groups.

BBQr - Better Bitcoin QR (https://BBQr.org)

Why? "I fckng hate animated qr" – nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx

In making of #COLDCARD Q we (Coinkite) wanted a simpler, low dependency & very compressed Bitcoin Static/Animated QRs—looking for feedback

Whole source in this animated QR!

License: Public Domain

First of all you should focus on reliability. Get the cheapest, shittiest phone and try to scan it.

I still have hunger pains 😕 I wish they were at least less intense...