Nostr Web Client

Hey nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl are you seeing this issue in all jumble instances? The original post has an error when displaying that it can't handle kind 6, then the post looks like it's parsed in a buggy way.

If you view the original post by me, it's fine, however.

nostr:nevent1qvzqqqqy2upzpk4yr0kmdpv3xcalgsrldp7tj7yuc4p76qjtka7z95kgfky02s2nqys8wumn8ghj7mn0wd68ytnnw4cx2unxwf5k2mnywvhx7mnvd9hx2tcpy4mhxue69uhksctkv4hzuum4wpjhyenjd9jkuern9ehkumrfdejj76twvfhhsqpqtr0ch7jk5w4l5psm9ll0ujs30m9y2gsz45679hm7yavxyh5lrtjq09rdsr

Cody 4d ago 💬 1

Why is he replying to a kind:6 event? 😂

Jumble indeed doesn’t handle this case, I didn’t expect this to happen at all. Now I’m really curious which client he’s using.

Reply to this note

Please Login to reply.

Discussion

Geektoshi 4d ago 💬 1

this might be a bug on my end...been testing a client i've been working on as my daily driver. i'll take a look.

arfonzo 4d ago

Thanks gents! I wasn't sure where this issue was coming from, makes sense. I've only seen it with your client's posts now that you mention that nostr:npub1m2jphmdkskgnvwl5gplksl9e0zwv2sldqf9mwlpz6tyymz84g9fsqr3wgu 🙏