Post
To be honest I am still too much in a NIP & Kind detail learning phase to give a good opinion on this. We find out, learn by trail & error. Currently it's working basically, but as you suggested it's not a good technical approach we should optimize it. In the future with yumyume (and other social bookmarking tools) I would like to see:
- Signing date of the first bookmark per profile (who started bookmarking an URL)
- Signing date of the updated bookmark per profile
- Optimally (speed) filter the social bookmarks on hashtags, bookmark / URL, profiles
- Search within descriptions
- Public & Private bookmarks
- Enhance with tools to optimize social bookmarking such as repeatedly 404 detection removal of bookmark (DVM?), LLM to filter on bookmarks during browsing (browser plugin or so). Idea I had for years , and also saw something similar suggested by rabble
0
0
0
0
I believe the scheme above allows for all these features to be built, and I can't think of anything else better, but there may as well be, who knows.
The only problem with finding out is that when you find out it's often too late to switch because of network effect (this is the fate of Nostr itself and probably all of its subprotocols). Any small network effect is already too much. This is not to say you shouldn't try and error, I'm just stating a conundrum.
0
0
0
0