Jonathan Carroll on Nostr: nprofile1q…u2yry nprofile1q…t52yx I don't think I want to force users to use a ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqmaq03gn6zgthz7puukm3f7hs829tp3t6t5l2cvyyfy3azwvrds4scu2yry (nprofile…2yry) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqswzr2edyz4evx62e8w8n8dfekcmyvh897q3ra5ejnsqdwfnw433s3t52yx (nprofile…52yx) I don't think I want to force users to use a specific store, I just want to track where the file is, so an ID, name, and location URI should be sufficient. Maintaining that is a people problem more than anything, but let's imagine the 'data group' had some authority over moving files around.

I imagine an API that takes an ID and returns these 3 things, to which one can query "where is this file stored?" Perhaps even the history of where it has been stored.