OH FUCK YEAH!
🤝
#[4]
lol, I run a fork too on f7z.io 🤝
do you know on what rev you got blacklisted? is your hex pubkey just hardcoded? wanna check my fork is not blacklisting you
I don't know who needs to hear this, but #[0] has a super nice coworking space in #madeira where a lot of nostr code (and this note) has been written by yours truly
highly recommend!
oh so it just blacklisted your pubkey?
damn!
#freesemisol 😂
wait, does it censor that one fake zap or all your zaps? 🤔
Literally every day I wake up and think “oh this is so cool; I could dedicate myself to building this one thing”
I’m puzzled by the fact that not every single developer on earth is building nostr stuff
where’s the efficient market hypothesis people at?!
> What’s still missing is attaching payment information to individual events (as opposed to user profiles)
This can already be done since the LNURL would get a 9734 so it knows how which event is getting zapped and can dynamically create a the appropriate split 👀
Yeah, I’ve been thinking about this and wanted to do it via HODL invoices on the splitter.
I still think this is probably the right approach.
Fucking loved it! This is a brilliant idea.
I wonder what would be the right representation of the data:
should a prism zap e tag the note and then p tag the recipients with an optional split amount going to them?
then a 9375 event with the p and an e that does not belong to p can be identified as a prism along with all the other recipients 🤔
that would mean that the 9374 needs to be collaboratively constructed with the LNURL backend (since the client wouldn’t know about the split structure)
I woke up this morning to three peacocks roaming our garden in #madeira.
Pretty sure #[1] and #[2] planted them to make us feel even more how magical #[3] is.
New stuff on https://nostrit.com
(the IFTTT of nostr posts)
* Create raw events without scheduling the publish (s/o #[0])
* dropped price of exact-date events to 1k sats
I've heard that one a million times, it's so dumb, one of the few FUDs you can debunk with:
"so?"
*who* created bitcoin makes absolutely no difference whatsoever
a 1-sat zap is ∞ more valuable than a like
KYC-free bitcoin from settling lunch with friends have a unique flavor.
I offer a 1Msat bounty for extending [nos2x-fox](https://github.com/diegogurpegui/nos2x-fox) to multiple accounts.
* When I pinned the extension, switching between keys can be done in the dropdown. With only this implemented (and the configuration of multiple keys) I offer 0.5Msat.
* nip07 methods accept an additional parameter - the expected pubkey. For example `window.nostr.nip04.encrypt(correspondentPubkey, plaintext, myPubkey)` instead of `window.nostr.nip04.encrypt(pubkey, plaintext)`
#[0]
why would you change the signature of the nip07 calls? that'll mean that each website using it would have to support this off-nip
why not just switch accounts at the extension level and the nip07 is called with the active key?
we often see #rektducation classes imparted in crypto universities
but it’s important to understand that #rektducation is an inherit attribute of fiat, not crypto
crypto being just a small subset of the much larger fiat system, inherits this property
A whole new class is getting #rektducated in real time
new instance of Blastr available ✅
wss://blastr.f7z.xyz
#[2]
cc #[0] #[1]
any interest in getting another #blastr running besides #[0]'s?
if this gets to 31337 sats I'll host a new instance of blastr
cc #[1]
#zapraiser 31337