Thanks for the advise, I will follow 🫂
It's been hard to discover new users to follow and interact with. Any recommendations? 🧐
#nostr #plebchain #grownostr #asknostr
Felicidades por el lanzamiento de NDK 1.0! Ojalá veamos más desarrollo en el ecosistema 🫂
📢 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.
Cómo afecta esto a Boca?
Back in Chile 🇨🇱 ready to develop projects!
Sharing the view of Cordillera de Los Andes
Refund my taxes Argentina 😤
Promise won't ever buy a plane ticket with a stopover of 5 hours to save $20 😵💫
https://void.cat/d/RA5DZHkCMx4vsoUf427rxY.webp
https://void.cat/d/H4hRiCuiGmiHTkzPEyXsjx.webp
Professional apps need professional logo's.
Current Amethyst logo:
- has the wrong colors
- the eye is not part of the compound path
- lacks alignment
- the A is hard to recognize
Redesign I did a while back:
No pressure though nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z 😉
#nostrdesign #logo
Pull request it 👏
GN folks! It's been a nice night to share with all of you 🫂🫶
Great advise, I will follow it tomorrow and try to figure out if in 1 hour I can come up with a solution for hashtags recommendation.
If not i will post about it in habla so hopefully someone better suited for the job picks it up 😂
It has helped me to find accounts that actually talk about stuff I'm kind of interested.
Still feels kind of empty because not everyone is that conscious of using then.
A hashtag recommendation would work for fast typers that are not thinking on the potential impact of their post.
What is your thought process when selecting hashtags?
Is nostr.band but doesn't suck, I've been told 🤔
🫂🫶
