I hate when that happens and then I wake up.... no seriously, that sounds amazing 😻
It's almost sad to see how the things he thought about could not yet be verified, because we did not yet have the science or computational capacity to comprehend it...
Oh, you are a youngling then 😄 I have been there from 3.11 and that's not even how I started...
Don't mention the blue check to Odell 😉
It will be another year before they support ln addresses and zaps.
And I think protocols are 50% at fault here. Zaps shouldn't need the extra integration.
This is btw the same reason for why Nostr is growing so fast compared to other protocols.
The fact that initial protocol is super simple lures in the developers and then they grow together with the protocol as there are more features, nips, apps, services added, causing a positive feedback loop.
Compare this to some of the other protocols where some team blessed us with a complex spec after 4 years of work.
The trick is to send sats to the content you would like to see more in future... ⚡😉
Nice to see a positive story. Respect to the youtuber - if he's not just doing this to get views.
Give me option to not see the messages and we are all good 👍
It always comes down to better experience and better brand.
Handling cash sort of sucks, you have to count it manually, it smells weird, you have to have enough of it physically with you, it can be stolen or lost, it's not practical for large value (e.g. buying house).
If majority of people don't experience the issues with centralized plastic cards, they will prefer those to cash.
Now I'm excited about Bitcoin solutions with NFC cards and phones.
For example, I reprogrammed Hyatt hotel key card to be "tap-to-pay" Bitcoin gift card (using lnurlw) and the experience is great. I just tap someone's phone, it automatically opens their LN wallet and they get the sats... ⚡
Bitcoiners...
Need to have faces of other young people explaining you the content you are seeing... best is to start with lifestyle and with gamers.
New t-shirt, who dis?
#nostr
That generally happens when you login with your "account" in another app. And then the relays disappear in Amethyst.
There's a tool on https://metadata.nostr.com/ to recover them.
That's why the efforts like https://einundzwanzig.space/ and https://jednadvacet.org/ are so important. They are getting merchants to accept and communities to spend.
📢 NDK 1.0 is out!
Codename: Outbox ✅
When I set out to write NDK my main goal was implementing the gossip protocol, now known as *outbox model*. I wanted nostr applications to have decentralizing tendencies by *default*; transparent to the developer.
After a few failed attempts, it's finally here, which, paired with a bunch of non-backward compatible changes, prompts me to do a major version bump.
# What is outbox model?
In short, the outbox model allows nostr to fragment, instead of everybody coalescing around a few popular relay and using things like Blastr. Nostr simply doesn't work without the outbox model.
# Main changes:
* Outbox model support, obviously.
* `fetchEvent(s)` is now faster, (particularly with queries using exclusively `ids` filters).
* Fixed unstable relay back-off code (credit goes to nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 for the valuable testing infrastructure)
* Defaults to blacklisting wss://brb.io #censorship (credit goes to nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 for the widely hinted-at dead relay)
* Subscription aggregation now works when multiple filters run at the same time
* Subscriptions that should close when EOSEd are now closed when each individual relay EOSEs instead of waiting for all of them to EOSE.
* A better algorithm on when to signal a subscription's EOSE. The margin that NDK now gives to relays to EOSE is now a function of how many of the connected relays in the relay set have EOSEd (accounting for relays that are still sending events).
* There are *many* more changes that I needed to do to accommodate for this that I don't remember now.
Some of the most glaring breaking changes:
* `ndk.subscribe` now defaults to keeping the subscription alive; the default of closing subscriptions on EOSE was bothering me
* NDKUser changes the `hexpubkey` from a function to a getter, so wherever you were using `user.hexpubkey()` needs to change to `user.hexpubkey`.
# Enabling outbox model
Outbox model comes disabled by default *for now*, as soon as I test it more throughogly it will be the default.
To enable it you need to instantiate NDK with:
```
const ndk = new NDK({
explicitRelayUrls: [...],
outboxRelayUrls: ["wss://purplepag.es"],
enableOutboxModel: true,
})
```
The outbox model will largely be transparent to you and will work on the background once you enable it.
The "What is outbox model" section doesn't really explain what is the model 🤔🤐
Yeah it runs in Electrum. Intro is here https://stacker.news/items/247580
Yep and that sucks. There are some small nice steps like Joinstr (conjoin coordinated over nostr) happening, but it always feels like we are both really close and really far from much better privacy experience.
The annoying part is that self-custodial lightning experience is lacking.
Like even with Breez and Phoenix - you can't get lightning address, you can't set up zaps (afaik).