Replying to Avatar JeffG

Yeah – I've thought about that a bunch. I believe the best way to create reviews and endorsements would be to use labels (nip-32). But extended profile information is a bit trickier. In theory, because kind:0 metadata is just a JSON string in the content of the event, you can put whatever into that. It would break convention a bit but it's the "right" place for that sort of data and clients could handle it or not depending on their use case.
Avatar
τέχνη 2y ago

The “extended profile” would theoretically be like a “ostrich.work” object with a bunch of its own fields?

That is basically app-specific file paths at that point, I suppose. But should it be app specific or use case specific. Much to ponder

Reply to this note

Please Login to reply.

Discussion

Avatar
JeffG 2y ago

I’m not sure you’d put it into it’s own object with the name of the app. I think you’d just add fields to the main metadata. There is also a nip that describes an event for app specific settings… that might be part of it.