This. ☝🏼 for onboarding.
Zach. This solution is so transparent and brilliant. New users don’t need to “save” their first (public) key. They can trash it (after “accidentally” publishing it) and just link a new one to their “master” key profile. However many times as they like. Without needing ANY clients to update their code.
Nest question … What would be a web based UI for managing the keys linked to a master key? Can I integrate this into my onboarding client? We need to talk.
nostrmeet.me
ManiMe /
npub1ma…yn9tn
2024-07-22 13:12:51
in reply to nevent1q…sz5h
Author Public Key
npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tnPublished at
2024-07-22 13:12:51Event JSON
{
"id": "9301438fcebfc723775c25aaf765d17f142e2d3917a763a875278fa56e13ddc9",
"pubkey": "df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200",
"created_at": 1721653971,
"kind": 1,
"tags": [
[
"e",
"0f9fb1c0ce5249f4d4d6f72fadd113f72867745a2a4aeb6d8ce6ac74ee9e4939",
"",
"root"
],
[
"e",
"6a2d2071abbb57a3ee6ab6644b5ca88040e30c7397b46f6423a5257c823d2143",
"",
"reply"
],
[
"p",
"a80455732d5bfa792f279011a8c871853182971994752b9cf1169611ff91a578"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "This. ☝🏼 for onboarding. \nZach. This solution is so transparent and brilliant. New users don’t need to “save” their first (public) key. They can trash it (after “accidentally” publishing it) and just link a new one to their “master” key profile. However many times as they like. Without needing ANY clients to update their code. \n\nNest question … What would be a web based UI for managing the keys linked to a master key? Can I integrate this into my onboarding client? We need to talk. \n\nnostrmeet.me",
"sig": "23c44ca46deab13886bee6ff46c54385e4aaa06788e7db4a5f8f437400e64c4a3575b99e2570052fa2882a5f6543436f3591e49452414c59377934772fcf7626"
}