Another few points to keep in mind:
\- Having a nostr account connected in my BF profile does NOT mean I can use this account to comment.
To be able to comment means that I'm able to sign my comments using either an extension or some tool.
\- Syncing profile data between BF profile & nostr profile
These are 2 different profiles, think like your google profile, & any other profile you signed-in to using your google profile.
Updating one profile data doesn't mean (most of the times) that the other profile is getting updated automatically.
Cause there will be several issues if this would to happen.
Also, updating nostr profile data also requires signing the update event by the private key.
I personally think that we don't necissarly need to allow the user to update his nostr profile from bolt.fun
(& I think we should definitely not try to automatically update it)
2 reasons:
\- It can get out of sync easily. Whenever the user changes any of his info from any other nostr client, the profiles data will be out of sync with our BF profile.
\- We are almost not using the user's profile data anywhere.
We try to see if this nostr profile is connected to one of our BF profiles, & if so, we always display our BF profile data.
So we are not making any use of his nostr profile data if it's created on some other client.
\- Should we allow users to comment using a nostr profile that is NOT connected to a BF account??
Currently, we do.
Mtg /
npub1zu…tdx38
2023-11-09 10:22:18
in reply to nevent1q…zm9j
Author Public Key
npub1zug85tns97cfxafjpa2rh28d45d6h4txgxt3vr8rxe9czr85j47qntdx38Published at
2023-11-09 10:22:18Event JSON
{
"id": "b6d7d8aaab1a01f65f71f88319777c5385baca2a84162d49a77961e9d14ea6a3",
"pubkey": "17107a2e702fb09375320f543ba8edad1babd5664197160ce3364b810cf4957c",
"created_at": 1699525338,
"kind": 1,
"tags": [
[
"client",
"bolt.fun"
],
[
"c",
"bolt.fun"
],
[
"e",
"9cada5169fd9dfa8a2a30e2b0911b92af3424d92759ca5341b29119c4e66090b",
"",
"root"
],
[
"r",
"https://bolt.fun/story/1321"
],
[
"e",
"e10c48778fc29dc41242940d28977fc7fe3177acfd3dae97d6c8751f918aa8f1",
"",
"reply"
]
],
"content": "Another few points to keep in mind:\n\n\\- Having a nostr account connected in my BF profile does NOT mean I can use this account to comment.\n\nTo be able to comment means that I'm able to sign my comments using either an extension or some tool.\n\n\\- Syncing profile data between BF profile \u0026 nostr profile\n\nThese are 2 different profiles, think like your google profile, \u0026 any other profile you signed-in to using your google profile.\n\nUpdating one profile data doesn't mean (most of the times) that the other profile is getting updated automatically.\n\nCause there will be several issues if this would to happen.\n\nAlso, updating nostr profile data also requires signing the update event by the private key.\n\nI personally think that we don't necissarly need to allow the user to update his nostr profile from bolt.fun\n\n(\u0026 I think we should definitely not try to automatically update it)\n\n2 reasons:\n\n\\- It can get out of sync easily. Whenever the user changes any of his info from any other nostr client, the profiles data will be out of sync with our BF profile.\n\n\\- We are almost not using the user's profile data anywhere.\n\nWe try to see if this nostr profile is connected to one of our BF profiles, \u0026 if so, we always display our BF profile data.\n\nSo we are not making any use of his nostr profile data if it's created on some other client.\n\n\\- Should we allow users to comment using a nostr profile that is NOT connected to a BF account??\n\nCurrently, we do.",
"sig": "d3c66f69a46320ac7e8cd255ec3a37b6c5e6942860bf6a2a7451518bc6ab9151d51f231d50070d09a3d5ceb62f74da652709aed7707bc06f70ef67c5b4248d68"
}