#asknostr
Nostr is NOT PsyOps nor Algorithm resistance - architecturally speaking!...
Here is why:
As opposed to what I read from other people's posts here and what I first thought of Nostr that "it does not have an algorithm to beat like the centralised platforms where you are not served by contents based on what you like, based on your likes or engagement patterns, etc."
This is technically NOT TRUE! The documents that I read from the developer of Nostr says otherwise.
"Techniques to trick the user:
Each client can decide how to best show posts to users, so there is always the option of just consuming what you want in the manner you want — from using an AI to decide the order of the updates you’ll see to just reading them in chronological order. " @fiatjaf from
https://fiatjaf.com/nostr.html
Yes, at the moment, as far as my user experience from the clients that I am using. I am consuming content feed based on chronological order or based on the filters of feed that I want like in Primal - eg Latest, Trending, #travel, Latest Replies, etc.
But this does not mean it will never change!
It only means NO CLIENTS yet (not that I am aware of, or at least I have not used yet!) have the same algorithm as most centralised platforms where encourages you to consume more content based on which content attracts you the most!
As a former programmer and a data consultant, I became curious about the architecture of Nostr. Hence, I took time to read the above and nostr-resources. However, I am very keen for any references that you can recommend for further reading to expand my understanding of #nostr.
As someone new to this platform and really rooting for its success because of its opportunity and potential. I believe as a user it is worth knowing the future of Nostr strategically speaking.
At the end of the day, every projects, start-up or innovation requires funding. I am yet to find the plans for nostr. I have not read the NIPS yet so will be next.
USER DATA CONTROL:
Where I am not clear from the docs is about the user data control.
1.) Delete Events or Notes:
In order for clients to query and retrieve my events or posts, it must be stored somewhere. I have to requests to DELETE EVENTS/Notes depending on the clients that I used. I have not used clients yet that let me delete my notes without needing to contact the client's admin . This user effort is not ideal. Perhaps this is already on the to-do lists of devs?
2.) Account deletion. I know each user has public key but I do not believe I can DELETE my public key should I wish so. Or at least I can only see deletion of my posts/notes functionality. I don't believe this functionality is available yet or will be available. From the docs that I read Nostr is decentralised through Relays and each relays do not have to communicate with each other. But some have already the capability to broadcasts your data for further distribution. Does this mean my public key along with its metadata, once out there, it is FOREVER there? I am genuinely curious because I have not seen this on my research yet. I know everything is tag as EVENTS and each events has its "kind".
Any further reading about data control or reference guide is greatly appreciated!
Enjoy your Sat night! 😀
#grownostr #architecture #tech #decentralise #lifecoach #growthteacher
Cheers,
M💋
maegrowthteacher / Lady Mae
npub12u…ye0ve
2024-08-10 19:32:07
Author Public Key
npub12u56mxg60cxt3zt3emfrfp6czptep4g3vzsfkgksmreeefmzmcgsuye0vePublished at
2024-08-10 19:32:07Event JSON
{
"id": "de196676b0aa1862ec85e9adbebb8a92fd113a736e4c7c428a8f2cbb0c01aabe",
"pubkey": "5729ad991a7e0cb88971ced2348758105790d51160a09b22d0d8f39ca762de11",
"created_at": 1723311127,
"kind": 1,
"tags": [
[
"t",
"asknostr"
],
[
"t",
"travel"
],
[
"t",
"nostr"
],
[
"t",
"grownostr"
],
[
"t",
"architecture"
],
[
"t",
"tech"
],
[
"t",
"decentralise"
],
[
"t",
"lifecoach"
],
[
"t",
"growthteacher"
]
],
"content": "#asknostr\n\nNostr is NOT PsyOps nor Algorithm resistance - architecturally speaking!... \n\nHere is why:\n\nAs opposed to what I read from other people's posts here and what I first thought of Nostr that \"it does not have an algorithm to beat like the centralised platforms where you are not served by contents based on what you like, based on your likes or engagement patterns, etc.\" \n\nThis is technically NOT TRUE! The documents that I read from the developer of Nostr says otherwise. \n\n\"Techniques to trick the user:\n\n Each client can decide how to best show posts to users, so there is always the option of just consuming what you want in the manner you want — from using an AI to decide the order of the updates you’ll see to just reading them in chronological order. \" @fiatjaf from \nhttps://fiatjaf.com/nostr.html\n\nYes, at the moment, as far as my user experience from the clients that I am using. I am consuming content feed based on chronological order or based on the filters of feed that I want like in Primal - eg Latest, Trending, #travel, Latest Replies, etc.\n\nBut this does not mean it will never change!\nIt only means NO CLIENTS yet (not that I am aware of, or at least I have not used yet!) have the same algorithm as most centralised platforms where encourages you to consume more content based on which content attracts you the most!\n\nAs a former programmer and a data consultant, I became curious about the architecture of Nostr. Hence, I took time to read the above and nostr-resources. However, I am very keen for any references that you can recommend for further reading to expand my understanding of #nostr.\n\nAs someone new to this platform and really rooting for its success because of its opportunity and potential. I believe as a user it is worth knowing the future of Nostr strategically speaking. \n\nAt the end of the day, every projects, start-up or innovation requires funding. I am yet to find the plans for nostr. I have not read the NIPS yet so will be next.\n\nUSER DATA CONTROL:\nWhere I am not clear from the docs is about the user data control. \n1.) Delete Events or Notes:\nIn order for clients to query and retrieve my events or posts, it must be stored somewhere. I have to requests to DELETE EVENTS/Notes depending on the clients that I used. I have not used clients yet that let me delete my notes without needing to contact the client's admin . This user effort is not ideal. Perhaps this is already on the to-do lists of devs?\n2.) Account deletion. I know each user has public key but I do not believe I can DELETE my public key should I wish so. Or at least I can only see deletion of my posts/notes functionality. I don't believe this functionality is available yet or will be available. From the docs that I read Nostr is decentralised through Relays and each relays do not have to communicate with each other. But some have already the capability to broadcasts your data for further distribution. Does this mean my public key along with its metadata, once out there, it is FOREVER there? I am genuinely curious because I have not seen this on my research yet. I know everything is tag as EVENTS and each events has its \"kind\". \n\n Any further reading about data control or reference guide is greatly appreciated!\n\nEnjoy your Sat night! 😀\n\n#grownostr #architecture #tech #decentralise #lifecoach #growthteacher\n\nCheers,\nM💋\n\n\n\n\n",
"sig": "e00d7d25fa85272dfec7cd8b3ea2856bef4e8f4af3c10150b6c4dd04e63fc44782f65eabae044506d7eb8636138870a6ae0e915899f3ca521e5a25a6f82091e7"
}