nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

wat is this:

```

{

"id": "580bc013c2c5c335b772f2f1f333f39a1f17ad535a5b56bfbd117b88dbf7b854",

"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",

"created_at": 1765975658,

"kind": 0,

"tags": [

[

"client",

"noStrudel",

"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"

],

[

"alt",

"User profile for mleku"

],

[

"name",

"mleku"

],

[

"display_name",

"mleku"

],

[

"picture",

"%22

],

[

"banner",

"%22

],

[

"website",

"https://github.com/mleku%22

],

[

"about",

"Creativity is trying stuff and having happy accidents. The unknown unknowns are infinite.\n\nbuilding https://next.orly.dev/ - fast, configurable and scalable relay engine.\n\ntelegram: @mleku1\n\nmatrix: @mleku17:matrix.org\n\nsimplex: https://smp15.simplex.im/a#PPkiqGvf5kZ3AbFWBh3_tw1b_YgvnkSgDEc_-IuuRWc%22

],

[

"nip05",

"me@mleku.dev"

],

[

"lud16",

"mlekudev@getalby.com"

]

],

"content": "{\"lnurl\":\"lnurl1dp68gurn8ghj7em9w3skccne9e3k7mf09emk2mrv944kummhdchkcmn4wfk8qtmdd3jkkatyv4mqk2pts2\",\"name\":\"ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ\",\"picture\":\"/%22,/%22display_name/%22:/%22%E1%B4%9B%CA%9C%E1%B4%87 ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ\",\"displayName\":\"ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ\",\"about\":\"ʏᴏᴜ ᴀʀᴇ ɴᴏᴛ ʀᴇᴀᴅʏ.\",\"website\":\"https://i.nostr.build/pqpCXrPHeoafW8M5.jpg" class="embedded-image" loading="lazy">/%22,/%22pubkey/%22:/%224c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f/%22%7D%22,

"sig": "d86bb2eccc67d294b71462027741ab90b47c01d0704d1e773e4dc7cd2fee24fbbdafc81acd6d63d2418900e19cf588f99d23a89aa56ea77768b6e284151622da"

}

```

Reply to this note

Please Login to reply.

Discussion

Kind 0 - nostr user metadata. Looks like the json for mleku's profile.

ʏᴇꜱ ʙᴜᴛ ᴡʜᴀᴛ ɪꜱ ᴀʟʟ ᴛʜᴏꜱᴇ ᴛᴀɢꜱ???

This NIP defines one basic kind:

0: user metadata: the content is set to a stringified JSON object {name: , about: , picture: } describing the user who created the event. Extra metadata fields may be set. A relay may delete older events once it gets a new one for the same pubkey.

correct

"Extra metadata fields may be set"

ᴀɴʏᴛʜɪɴɢ ʙᴀꜱɪᴄᴀʟʟʏ, ᴛʜᴇ ꜱᴘᴇᴄɪꜰɪᴄᴀᴛɪᴏɴ ɪꜱ ꜱᴏ ᴡᴇᴀᴋ ʏᴏᴜ ᴏɴʟʏ ɴᴇᴇᴅ ᴛᴏ ʙʀᴇᴀᴛʜᴇ ᴏɴ ɪᴛ ᴛᴏ ʙʀᴇᴀᴋ ɪᴛ. ᴘᴀᴛʜᴇᴛɪᴄ.

ɪᴛ'ꜱ ᴘʀᴏʙᴀʙʟʏ ʜᴇʀ. ɴᴏ ᴘʀᴏʙʟᴇᴍ, ᴊᴜꜱᴛ ɢᴏᴛ ᴄᴏɴꜰᴜꜱɪɴɢ

I only edit tags in Wikistr, not in Jumble, and you have to sign off on changes to your profile event.

It's an extra form, in all Jumbles and in my Wikistr.

Tags are definitely the future, but I don't remove the stringified json. Some clients still use that, even though it's retarded.

Wed Dec 17 2025 12:47:38 GMT+0000

Very recent created-at and it's missing the Jumble client tags and Imwald alt tag. 🤔

You must have edited your profile event, yesterday, to add the death font stuff, which gave you the Nostrudel tag.

The rest looks like standard Jumble tags. Mine has similar ones and I just changed the profile pic.

Looks fine, to me.

Not sure, noStrudel overrides the "client" tag when the event is modified in the client but it does it best to preserve any existing tags or extra fields in the JSON. so they are probably coming from another client 🤷

ᴍᴀᴋᴇꜱ ꜱᴇɴꜱᴇ. ꜱᴏ ɪ ᴏɴʟʏ ᴜꜱᴇ ᴊᴜᴍʙʟᴇ, ꜱɪʟʙᴇʀᴇɴɢᴇʟ ᴊᴜᴍʙʟᴇ, ɴᴏꜱᴛʀᴜᴅᴇʟ ᴀɴᴅ ᴄᴏʀᴀᴄʟᴇ, ꜱᴏ ɪᴛ'ꜱ ᴏɴᴇ ᴏꜰ ᴛʜᴏꜱᴇ