In look for a "consolation sat" (is it how we say "gol de honra" in english?)
Where are the 21 sats meme donations? 😄
Just launched a campaign at Geyser: https://geyser.fund/project/44billion/prelaunch
Apparently it will auto-close if it doesn't reach $210 goal 😱😱😱😱
If you like the project, please contribute or share to your follows!
*followers
Just launched a campaign at Geyser: https://geyser.fund/project/44billion/prelaunch
Apparently it will auto-close if it doesn't reach $210 goal 😱😱😱😱
If you like the project, please contribute or share to your follows!
I feel so light using js without typescript!
=O~ from https://zap.stream/videos
Best nostr clients hands-down:
yakihonne for Android and cobrafuma.com
I've read the MLS NIP and its PoC app code. 🙊
From talking to chatgpt, yes NIP-17 is safer.
A Signal group chat member can provide chat read-only access to anyone, without revealing their own main private key, while with NIP-17 the member would need to reveal it.
Signal chat member could simply keep sending a flow of up-to-date group keys and of received messages for anyone to be able to decrypt (showing not only the plaintext messages but who signed them), without admins or other members noticing it.
Chatgpt may be wrong, though, but the logic seems correct.
yeah I wonder if what you said could really bring in a considerable amount of sats.
maybe I could make a closed source nostr app and apply for an opensats or similar grant to turn it into open source and support further development 🤔
After much thought, I came up with a great (unreleased) NIP
that keeps nostr keys safe without an increase in complexity.
But this v4v thing doesn't seem to be working for protocol specs.
Sats income after 1.7 years of contributions: 1363 sats =O~
Free(mium) relays existence is nostr killer feature. They must exist to give voice to everybody.
The event persistence will inevitably be the same as on the "disappering messages" feature.
On mobile browser the font size is too small. I had to apply 135% zoom
Rate-limiting by IP (for example, how fast an user can read or write nostr events) is the most widely used technique to reduce spam on servers that don't require user login.
If nostr gets popular, there will be millions of simultaneous active users.
There are ~2000 tor exit IPs.
If clients start defaulting to using tor for all their users, expect to be heavily rate-limited by most relays.
nip96 at start of PR dicussions had fixed routes with no nip96 config, just like blossom, but stakeholders wanted to specify custom api url to serve files from a different infra. download_url is optionally for using CDNs. Other keys are all optional.
Also nip96 servers, specially free ones, may want to compress images/videos. That's why the file identifier is the file hash before compression. When using blossom, the client is supposed to compress before uploading.
Wish I could focus solely on nostr dev. One day I'll finish this baby.
https://video.nostr.build/cbc41730576d28b24cdac1fa9d1306224035c463e9abac5ff3a32a8163660ac2.mp4
I think reposting (kind 16) the kind 30023 article wouldn't have the said side-effect. Although when reposting, one can't include additional text like when quoting with kind 1 events.
Not sure about kind 16 reach though.