Last Notes
You can hire AI for less 🤣
Found this old tweet of Wolverine cyber bullying cyclops 👀🤭
https://i.nostr.build/2lK35zQ5HXH4rI2T.jpg
People just want to tip e-girls money for feet pics without having to scan 50 peanut wallet qr codes, & decrypt their wrapped lightning coinjoin whirlpool e-joined utxos.
Patreon, Venmo, Cash App, kofi, etc. already solved this but we want to reinvent the wheel because Bitcoin.
We either make better tools, or just integrate tools that already work well.
We shouldn’t be wasting time making new tools for a hyperspecific niche use case that most people realistically won’t use.
i watched it only because you told me how awesome it was.
jfc
there so much goddamn shit in Amethyst now
no, absolutely not.
As long as I can send some message inside an OP_RETURN, and this message is displayed in the zap notification, then I approve
My bad, your guicy ass, which could cause a car pileup at any intersection.
Restarted, seems like the right vibes for this 😂
In any given movement that’s bound to be orgies, and money transfers in the background amongst the high ranking leaders.
https://npub1p3za04z7mv86mkjzzhfkegxe4wsvwudct5m3wajt3gfg6hjy8exslltqmk.blossom.band/dd902bc5bb306450ec6c9b2b5871d217b3c2a5a599ee4d8edf74b03ee99d9e17.gif
I hate being broke because I can’t hire the dev nerds to make Nostr usable 😔✊.
Also implemented the "w" tags and the ability to have multiple lighnting addresses directly on the kind 0 profile. We're tip-agnostic, so we just implement every possibility.
But on-chain zaps is retarded.
Apple needs to hurry up 😂🤣
https://media1.tenor.com/m/DICsiY1sdZoAAAAC/mwahaha-laugh.gif
I agree, hopefully it’s currency secular though.
Allow for different things Venmo usernames, Cashtags, other coins address would be ideal but worse case scenario being able to copy and paste that section could work too.
Simplicity, & convenience.
We already have that, with the payto:// address scheme. They want to turn everything into zaps, tho.
Very balanced, like all things should be in this universe 🤣
No we must force everyone to accept our onchain UTXOs whether they like it or not
Yep, I can understand that
this is not about nostr dms
If someone gives me an ecash token I can’t know how many people or who has already passed it. And if any one of them rugs by spending a token they already gave to someone else (or giving the same token to two people), you have no way to know who did it
doxxathon?
https://media.tenor.com/NyF0cA41lWIAAAAC/dog-doggo.gif
Seems very trivial if you ask me, just add one more field to profile and have client handle it
GM☕️
(accepting on-chain zaps since a year ago, so far 0 has been transmitted 😂)
I added a random wallet to my profile, a while back. Nobody ever sent anything to it.
We have gotten on-chain donations, for larger amounts, but we don't post those addresses publically. We send them an invoice.
Bruh I wanna try wisp iOS. Very curious about this 👀 put me in coach 🫡
https://media.tenor.com/0kRKrbGSzn4AAAAC/kickball-fail.gif
Only one of these usecases is realistic, and in that case barter or people signing IOU’s is going to be much more likely to work (with proper accountability) than ecash which can be rugged with 0 reputation risk.
GM
https://image.nostr.build/9cbd5119109a2f5b1b18ab2615229635ecc4aecce51ea30dc83c95e7e91ea08c.gif
To be fair integrating into the client is good.
Or at the very least a uri scheme integrated into clients to open wallets to transmit would be nice.
Some clients aren’t friendly to copying from bio unfortunately.
Lightning is the universal layer. We don’t need ecash zaps when LN can already handle ecash, without the shared mint issue.
Don’t call this turd “zaps”
What good is an IOU I can’t even prove was sent to me with not even a single piece of proof to say that they are a scammer?
Or, even worse, an IOU that may have been passed through multiple people, any of which could rug me without any risk of being identified.
On top of this, everyone has to have trust in the same mint, which is impossible.
The concept is good, I like it.
“Offline” payments with ecash are vulnerable to double spends.
Nostr needs a Cash App like integration of a mechanism similar to stripe, Kofi, Patreon, etc.
Nostr’s insistence on Bitcoin only may be the biggest barrier to adoption.
I’d like to see a transition to an open money transmission protocol for Nostr so that we can transmit money in a permissionless manner.
Once you force a currency into the protocol it’s permissioned.
Nostr shouldn’t be Bitcoin only.
The only spec that fixes it is my spec rn. (Check the quoted note)
That’s the entire point.
No signers that I know of reliably show what is being decrypted so far. Sometimes you see the plaintext but that is often useless
You can also constructively and publicly address what you disagree with. Many of the people observing don't know the potential downsides and appreciate someone with a clue giving a reasoned review.
Not all reviews need to be positive, to be useful. The whole point of developing in public and publishing the code base is to receive public feedback.
We also haven't only gotten positive feedback and had to rethink our core design numerous times. That's normal, in engineering.
Well I just think it would be funny to get an on chain zap and never touch it. For both reasons that I don't care about them and won't use a Nostr client that is even aware of them.
It is not sufficient, if you allow decryption without confirmation. Even if you do, many signers do not show you what is being decrypted or show you a garbled mess that is not helpful.
Marmot is for group DMs, but many protocols need encryption for other things, like encrypting lists, collaborative documents, the initial setup phase for groupDM protocols, etc.
The encrypted message has two additional fields that are authenticated: kind + scope. The signer can restrict operations based on it.
It is not possible to tamper with the kind/scope field without the signer encrypting a fully new message, but you can’t encrypt what you don’t have the plaintext to
These fields are not encrypted though as they are meant to be derived from the (unencrypted) parent event and checked
Have you seen mempool.space ? https://image.nostr.build/6444edef288bde5d02325dc1fe9c31de918fc10c56bf6c7b6bf4972de784773b.gif
I'm trying to understand why that is. Are you saying you just don't care about them or can't access the sats?
I second this Nostr is confusing enough already.
We should be consolidating the complexities, and making it more flat for the baseline experience for beginner users, and allow advanced users to customize their own experience more precisely once they figure it out.
The money transmission layer should be as secular, open, and versatile as possible.