OK, then optional subscription_id string after message seems to be the least disruptive option.

Do any clients even use the NOTICE messages? Theyโ€™re useful during development, but do any user-land clients process/surface them for users?

I mostly use Damus. Iโ€™ve never seen evidence of NOTICE messages, but then again, it may be just that there havenโ€™t been any?

Reply to this note

Please Login to reply.

Discussion

Astral Ninja used them. Newer clients seem to hide the notices.

ndk-svelte-component's RelayList component will display them

make NOTICES user-facing again! ๐Ÿ˜€

https://nostr.build/av/627f5b66ae4bf760e575a303d48eb355a887abbbfab87c81f77fcc586b870a40.mov

Good to know! This is also a good example of why Iโ€™d like to see new message types.

These ERRORs are due to a โ€œbad msgโ€ with additional information that thereโ€™s an unrecognized filter item. In HTTP, this would be a 400 Bad Requestโ€”the status code tells you the sort of error youโ€™re experiencing.

A new message type that allows an object payload would give us room to more clearly describe the sort of ERROR thatโ€™s occurring.

Some other ways a REQ could fail:

- bad msg for other reasons like empty arrays, wrong types, strings too long, negative numbers, etc.

- too many REQs from same client

- too many filters

- AUTH required (HTTP 401 equivalent)

- forbidden (HTTP 403 equivalent)

- database error (HTTP 502 equivalent)

REQ Non-errors:

- limit field too high

CLOSE errors:

- no such subscription_id (HTTP 404)

- subscription_id missing

- subscription_id wrong type

- extra message entries detected

- subscription_id too long

Are these NDK-svelte components available somewhere?

these sounds very much like plural, sir!

๐Ÿ˜‚

yeah

https://github.com/nostr-dev-kit/ndk-svelte-components

but so far I've only added one

there will be a LOT more coming very soon

Thank you! This (singular) is exactly what I need in my life. ๐Ÿ˜‚ I made a rudimentary version of this about a month ago. Iโ€™m really looking forward to more components.

haha awesome!!

I've heard on a podcast that nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn was going to create a kickass ndk svelte content parsing component, with nip19 mentions, link/image previews, the whole nine-yards

Huge if true!

๐Ÿ˜‰๐Ÿ˜‰๐Ÿ˜‰๐Ÿ˜‰๐Ÿ˜‰

๐Ÿ‘€ Iโ€™m so bullshit on this.

๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚

yeah, me too

At this point, you canโ€™t still be in #Nostr and not be bullshit

๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚