ed on Nostr: that's what i thought. In the nostr.json we could put an "event" (as defined in ...
that's what i thought. In the nostr.json we could put an "event" (as defined in NIP-01); the content field should be the domain claimed by the profile. The signature of that event is computed in the familiar way, so it shouldn't require any special work, and clients can ignore that data if they wish. (In my view, the profile is "notes and other stuff" and it should be signed, it seems an oversight that it is not).
can even bring over the blue ticks just for those "validated" profiles ha
Published at
2024-09-16 23:50:27Event JSON
{
"id": "ad9dbc3d84b723d5aee03dba7a134ffa4e46a26334b8d597f1ae722bbb63d554",
"pubkey": "acf88a0308156dd1b3f9de7573f88dd03dea512afadfa37ac35bcf66906d5d4c",
"created_at": 1726530627,
"kind": 1,
"tags": [
[
"e",
"f86e0c742c27ccef50cefba43d057957a64652ba9c92a6be9b87a9ba033503fa",
"",
"root"
],
[
"e",
"1f661ef7e87649d47642d13ec27f01b6d16239729e7b61c7354d8ffb9fdc7c70",
"",
"reply"
],
[
"p",
"76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa"
],
[
"p",
"6042d70377f8ae95c160a64cbe0f632578f0b53b2c76095449e7053be3e62213"
]
],
"content": "that's what i thought. In the nostr.json we could put an \"event\" (as defined in NIP-01); the content field should be the domain claimed by the profile. The signature of that event is computed in the familiar way, so it shouldn't require any special work, and clients can ignore that data if they wish. (In my view, the profile is \"notes and other stuff\" and it should be signed, it seems an oversight that it is not).\n\ncan even bring over the blue ticks just for those \"validated\" profiles ha",
"sig": "d60e63a9c301c65eabca83033e77b802c8932ed994f55ff57ff471eb24af0e99635165797a2390dc0d401e8878ec70f48878dea53e3f1ae42e7d7d199a47c70c"
}
