arthurfranca

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.

2024-12-05 13:19:44 UTC

- reply

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 🤔

2024-12-05 13:11:42 UTC

- reply

thx @npub1vwv…9tm0 🥲❤️

2024-12-05 01:12:39 UTC

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~

2024-11-27 18:02:23 UTC

- reply

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.

2024-11-26 18:23:11 UTC

- reply

On mobile browser the font size is too small. I had to apply 135% zoom

2024-11-22 12:33:22 UTC

- reply

Don't worry, Disney! I'm just 3d printing this mickey mouse to make some bucks

2024-11-19 15:40:13 UTC

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.

2024-11-09 01:13:23 UTC

- reply

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.

2024-11-08 15:15:55 UTC

- reply

Cough cough ez pz
#nevent1q…7neq

2024-11-08 14:51:28 UTC

Wish I could focus solely on nostr dev. One day I'll finish this baby.
https://video.nostr.build/cbc41730576d28b24cdac1fa9d1306224035c463e9abac5ff3a32a8163660ac2.mp4

2024-11-08 13:11:17 UTC

- reply

Maybe requiring outbox implementation before giving away grants to client devs would work better than the current approach 🤔
The client I'm using can't see the referenced note. Won't tell which one I'm using cause I have honor. I will just say it supports edits =x

2024-11-08 13:02:31 UTC

- reply

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.

2024-11-07 20:41:57 UTC

- reply

Valid point of view

2024-11-07 17:27:39 UTC

- reply

Off-topic: notice how using kind:1 to announce other kinds end up hurting the other event by splitting comments in two places 🧐

2024-08-27 16:21:10 UTC

- reply

If we forbid dots on nip05 usernames, we enable @username.subdomain.domain.tld

2024-08-11 19:30:27 UTC

- reply

Negative Zaps is like casting a "macumba" on someone?

2024-08-08 16:04:23 UTC

- reply

Its great that there are clients that compress media before uploading. But one of the good things of NIP-96 is that it makes it easy for clients to offer uploads by not requiring any client-side media transformation logic.

2024-08-08 15:54:15 UTC

- reply

An amend to NIP-96 could add a query string like `?ref=x` when downloading to only respond succesfully if server has a file with `x` value equal to the hash used to request the file.
For uploads, NIP-96 already has "no_transform" field, which would make `ox` equal to `x`.

2024-08-08 14:22:51 UTC

- reply

Twitter killer

2024-08-02 14:50:21 UTC

Reporting: still building the web client. This thing takes huge time to develop properly. I mean, there are clients that are here for years and don't even have outbox model implemented yet, which is basic. Atleast I got this done. I got a great app name too lol this is the most important step.
I'm not giving details yet cause I am avoiding saying "X feature currently is not done right in other nostr apps and I have a solution to that" while implementation isn't finished. I have a bunch of new ideas to work on.
Believe mah words!

2024-07-20 13:24:56 UTC

- reply

Topzera

2024-07-19 17:45:41 UTC

- reply

Right, now make all this simultaneously for two feeds and merge them into one ⚰️

2024-07-19 17:42:07 UTC

- reply

Great, I see you're building a web client too! Maybe If one of us manage to dethrone primal.net we can make a petition to change the nostr mascot from an ostrich to Blanka https://image.nostr.build/ea014ac63fbdfca0cea1945fbd2af5d4cbc9ea40858053b31ea4e3ce60714a79.gif

2024-07-09 18:31:58 UTC

- reply

https://image.nostr.build/b36505a8d8ef18f2779d70b3afae6de72f8af57fa81be4ba45bce9da9f7554b9.gif

2024-06-24 01:34:30 UTC

- reply

Performers from Brazil called Carreta Furação
https://www.tiktok.com/@memestrenzinhos/video/7317363637516012805

2024-06-22 14:51:53 UTC

Day 1 of coding the nostr client...
Once a nostr elite told me "It might be harder than you think".
It made me think of Naruto anime where there are some elite characters ranked as geniuses, naturally talented, while some plebs like Naruto himself and Rock Lee never gave up trying to improve themselves by relying on hard working.
https://image.nostr.build/e3135f22e59fd4a19b7c321bdad1a4d99efc6ca581678a7bd439b1d62883a639.gif

2024-06-22 01:47:57 UTC

- reply

https://image.nostr.build/e5e7ab3b3173fbe95495d476cee013333192e2479218cfdfe7b1684adbc30629.gif

2024-06-21 20:02:30 UTC

- reply

Time to apply all the theory learned at the University of NIPs. I completed the course with an average grade of 5.7 rounded to 6.

2024-06-21 17:11:48 UTC

- reply

Not necessarily gonna pursue low-data usage at the cost of poor ux. It is more like taking advantage of knowing well how nostr works to not ship code that carelessly connect to more relays and asks more events than needed.

2024-06-21 17:04:14 UTC

- reply

I think NIP-27 and NIP-96 were very important to the protocol, although the latter was a real pain to get everybody on the same page and merge. It was also important to be there and nag about NIP-42 till @nprofile…2kfz came up with the "CLOSED" message as a solution to most problems. I like unmerged inline metadata NIP that I think @nprofile…2dqr is still using and I will too but I guess nobody else is for now.
Some things had to change on the protocol before being too late to change, even though I wasn't implementing anything at the time.
I see your point though.

2024-06-21 14:31:56 UTC

- reply

Agree. When writing a NIP I think of implementation though its hard to spare enough time to actually implement it. Until now the way I wanted to help was just writing NIPs so others that had clients/relays would implement them instead of me.
I did write some relay and client code though I need to inject some caffeine and complete the damn things.

2024-06-21 14:23:43 UTC

- reply

I was thinking of lazy loading feed with manual refresh (also lazy loading threads instead of loading all thread notes at once like most clients do). No new live events until user manually refreshes.

2024-06-21 13:30:34 UTC

I'm thinking of starting development on a new nostr web client to implement my ideas that always get bashed on the NIPs repo by the nostr gods.
If you are seeing this in the middle of a million notes on a global feed and is interested in an web client that won't suck all your mobile internet plan in a day, follow me for news.. and for rants on nostr NIPs repo scene =]~.
PS: any huebr there?

2024-06-21 12:01:13 UTC

- reply

I suppose this is related to event sets pr defacement =s

2024-05-27 14:49:59 UTC

- reply

There's a NIP-96 ?w=<image-container-pixel-width> query param that clients should use when requesting images.
We should add something similar for videos

2024-05-23 22:02:21 UTC

- reply

"In rare cases, the Bluesky moderation team may need to open your DMs"
This is not a DM feature announcement, it's Group Chat! Chat members: the user, another user and all bluesky moderators!

2024-05-13 19:19:25 UTC

- reply

Kind:1111 to the rescue
https://github.com/nostr-protocol/nips/pull/1233 mind taking a look?

2023-07-02 22:12:44 UTC

- reply

Could you review this NIP pull request related to file storage? https://github.com/nostr-protocol/nips/pull/547

2023-03-29 14:16:49 UTC

- reply

This is a test
#[0]