2021-01-03, 01:48
Here's a crazy idea that might take a little development, but could be a solution for storage, bandwidth, and general "uptime".
Could it be possible to come up with a "virtually local scraper" in IPFS?
It would take a little technical know-how, but if everyone were to install an actual IPFS client/server on their systems, then "mount" the IPNS directory maintained by someone, such as KyraDB was, it would be possible for our Kodi installs to IPFS "pin" the posters we need - making them available on our local systems, which would in turn share the posters we use with everyone else. To do it properly would require a single server running the IPNS directory - which could itself be mirrored in full by anyone charitable enough to mirror the whole thing by pinning - and all updates would be done by republishing the IPNS list when updated by whoever maintains the IPNS directory. Every person who uses a poster would in turn share THAT poster. The more people use it, the less bandwidth any individual - including the official maintainer - uses.
If the original maintainer goes AWOL any individual with a full (or even partial for that matter) backup of the last IPNS announcement could publish what they have and fork it immediately. It would just be a matter of getting the word out to look at a different IPNS address.
Could it be possible to come up with a "virtually local scraper" in IPFS?
It would take a little technical know-how, but if everyone were to install an actual IPFS client/server on their systems, then "mount" the IPNS directory maintained by someone, such as KyraDB was, it would be possible for our Kodi installs to IPFS "pin" the posters we need - making them available on our local systems, which would in turn share the posters we use with everyone else. To do it properly would require a single server running the IPNS directory - which could itself be mirrored in full by anyone charitable enough to mirror the whole thing by pinning - and all updates would be done by republishing the IPNS list when updated by whoever maintains the IPNS directory. Every person who uses a poster would in turn share THAT poster. The more people use it, the less bandwidth any individual - including the official maintainer - uses.
If the original maintainer goes AWOL any individual with a full (or even partial for that matter) backup of the last IPNS announcement could publish what they have and fork it immediately. It would just be a matter of getting the word out to look at a different IPNS address.
