Allow the node to submit pins for validation by the website in their response message. i.e. "Is this hash a podcast episode?"
If you're running a "podcast only" node (default), you should only be pinning podcast episodes. A missed "delete" task to unpin a file, or other pinned files could remain on the node.
The node could send a hash to the website via a response message that asks the website to confirm if the file should be pinned. If the website determines the hash should be unpinned, it will send a "delete" command in the next request.
Only send one hash per response (not your entire datastore). The node would need to figure out how to "rotate" through the currently pinned hashes to send one hash per response.
Cons: If they're running a custom IPFS node (not "podcast only"), there will be other files pinned that would be removed by this process unless a "podcast only" option were configured. Default to "false" for the python version, "true" for Umbrel, Start9, etc.
Allow the node to submit pins for validation by the website in their response message. i.e. "Is this hash a podcast episode?"
If you're running a "podcast only" node (default), you should only be pinning podcast episodes. A missed "delete" task to unpin a file, or other pinned files could remain on the node.
The node could send a hash to the website via a response message that asks the website to confirm if the file should be pinned. If the website determines the hash should be unpinned, it will send a "delete" command in the next request.
Only send one hash per response (not your entire datastore). The node would need to figure out how to "rotate" through the currently pinned hashes to send one hash per response.
Cons: If they're running a custom IPFS node (not "podcast only"), there will be other files pinned that would be removed by this process unless a "podcast only" option were configured. Default to "false" for the python version, "true" for Umbrel, Start9, etc.