NIP-33 is required for these kind of notes, I think nostr.wine does not support it https://void.cat/d/7tco76X31sN1NBWfgdzb2z.webp
A few days ago I published a long form note that has since disappeared from the various relays available on blogstack.io and habla.news.
I am running the nostr.wine filter to broadcast. Seems maybe that's creating an issue? When I went to republish this morning on habla through nostr.wine the note did not populate. Deselected nostr.wine and no problems.
Any thoughts #[0], #[1], #[2] , #[3] , #[4] ?
The republished note: https://blogstack.io/naddr1qqdxzat5dahx7mte946xsun0w4nksttpdehku7tdd968jqg5waehxw309aex2mrp0yhxgctdw4eju6t0qgsdprynz204esjj4yqhhaf0jzzsvzcswe3q5kxddy3fkv0rw0hue8crqsqqqa28mfy9ak
Discussion
Also having trouble with links to longform notes. Running into a lot of friction when trying to share notes to folks not already within the Nostr ecosystem.
E.g.: https://www.linkedin.com/feed/update/activity:7037527490478657536
Longform is a huge onboarding purple pill! Looking forward to using it more when kinks are worked out for sharing links.
#[4] #[5]
#[4] , are you planning on supporting this?
We’d like to but that’s up to Strfry to implement. Not something we can supplement in front.
We could ask Doug, but he’s a busy man and there are definitely higher priority items for us atm.
This is the first request I’ve seen so I’ve noted it.
Mmmm... I thought relay.damus.io also runs on strfry, and it's supporting NIP-33 and NIP-23 afaict... 🤔🤔
It’s not listed in the Strfry readme so I presume damus, nos.lol, and many top relays do NOT currently support it (damus used to run a different implementation).
Performance is our #1 right now and we believe there is only one implementation that can support our filter setup.
Ok, I may be wrong then!
Thanks! 🫂
One additional clarification…
nostr.wine does not support this and the event will be rejected.
Filter.nostr.wine works differently. It only broadcasts events it does not store them directly. If the event passes our schema (I’ll double check that today), we will pass it on to all of our broadcast relays regardless if Strfry considers it valid or not. If any of the relays on our broadcast lost support the event, it should be published there.
List*
That also doesn’t mean you’ll be able to read the event from filter.nostr.wine (as it will be rejected by Strfry and not be stored) but you still should have published the event remotely to any relay on our list willing to accept it.
So this was the issue I ran into, filter.nostr.wine was struggling to broadcast the note.
Damus relay, nos.lol seem to support longform notes (displaying w/o problems on both habla.news and blogstack.io) whether it's through nip-33 or not. Was able to publish through those relays.
Ok excellent that is good information.
Let me see if our schema held you up. Should be able to check shortly.
Can you verify it works directly to nostr.wine?
Unable to broadcast to either filter or Nostr.wine
But you’re sure it works on damus and nos?
Actually have less time than I was expecting today but that seems very unlikely.
Selecting nostr.wine from the front page on blogstack pulls up posts, are these not on nostr.wine?
Hmm ok about to head out but from everything I can see your note is on nostr.wine.
Habla.news also shows the note was seen on nostr.wine:
Cool. Thanks for taking time to dig in. I wasn't able to post direclty to nostr.wine or filter.nostr.wine, though, when I tested a new note isolating for those relays. The previous notes were broadcast to other relays (and maybe also wine?)
Another thing it could be is total event size. We probably have lower limits than some.
Can you look in your browser console when you try to publish and see if you see a response from our relay? It should say why we are rejecting it.