watchit-app
watchit-app copied to clipboard
WatchItDev
Feature Request: About
Feature Request:
- Delete option # Option to delete the movie.
- About option # About with Github link and version
Questions:
- Once a movie is downloaded. Wheres the movie location ?
- Are we seeding downloaded movies ? If yes, need option to copy the CID in order to seed from IPFS-desktop etc.
Hi @danrobi11 thank you for create an issue. "Delete option # Option to delete the movie" -> When you say you want to delete the movie, do you mean you want a tool to remove temporary download files or movie metadata from the local database?
"About option # About with Github link and version" -> Great idea!! It is a good idea to add to our roadmap, although maybe we could have it sooner with the help of the community, maybe you are interested in exploring the code a bit and send us your PR;).
Once a movie is downloaded. Wheres the movie location ? HLS does not download it. the movie it's buffered, in the torrent stream case they are stored in /tmp folder
Are we seeding downloaded movies ? If yes, need option to copy the CID in order to seed from IPFS-desktop etc. The application shares movies with the network depending on the streaming mechanism. In the case of torrents, you share parts of the movie only when you are watching it while others share you (TorrentNetwork). In the case of HLS it is very similar but in this case it depends if your node has the movie in the local repo, that is, if you have already watch the "movie" then it is temporarily cached in the local IPFS node and if someone else wants to watch the same "movie" then your node will have the expected behavior of transmitting part of the movie if another node requests it (BitSwap).
Thanks for the support @geolffreym
remove temporary download files or movie metadata from the local database?
Yes. Delete option would be nice to delete the cached movies.
maybe you are interested in exploring the code a bit and send us your PR
Unfortunately, I do not code :/
Closing
![allcontributors[bot] avatar](https://avatars.githubusercontent.com/in/23186?v=4 "Published by a pub.dev verified publisher"){kind=small}
About option must Show: Icon Contributors License GitHub link Current version
The application shares movies with the network depending on the streaming mechanism. In the case of torrents, you share parts of the movie only when you are watching it while others share you (TorrentNetwork). In the case of HLS it is very similar but in this case it depends if your node has the movie in the local repo, that is, if you have already watch the "movie" then it is temporarily cached in the local IPFS node and if someone else wants to watch the same "movie" then your node will have the expected behavior of transmitting part of the movie if another node requests it (BitSwap).
To make things easier.
1- Delete file option in the file page. Page with the play, trailer and description
2- Copy CID option. In the same page as above.
That way we could help seeding and manage as we please our files. I share my blog, website etc over IPFS. My node run 24/7.
I've tested the new v0.1.0-beta.8. Now the file that I previously loaded is gone. I'll have to load the file again. It would be better if the users could manage how they want to deal with their files.
New Edit Note: I run Galacteek as IPFS node. Galacteek does support torrent. Im not a dev so im not sure if the "vanilla" IPFS-desktop can "torrent" but Galacteek sure does. Torrent and file-sharing.
Have a look if you want. My Galacteek instance run 24/7 here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.