I still don't understand what data is exactly used where and why that is now so... (ie for ex local:32080 editing no longuer working)
Can U please transparently describe, when using DMS, what data is exactly stored where and for which purpose ??
Let's assume I keep my DMS logged into my account (no log-out after activation/scrapping)
:
- What information/data exactly is transmitted / stored when I first activate my DMS ?
- Is there usage data you collect when movies are watched or other activites are performed with DMS?
- Where are the scrapping results stored ? If the results are in a local DB why do I need to login into my cloud account to be able to edit it ?? the local :32080 was all I needed.
- can the wall populate ONLY wit local stored NFO's
So why do I need to login to dvdfab cloud in order to edit my poster wall ...?
- Can I delete/erase permanently and completely the metadata of my library de facto now stored in your cloud ?
Thanks
PS : In short : this hardware could be a very promising standalone network media PLAYER...i don't need another media SERVER with cloud based "functionalities"...
Can U please transparently describe, when using DMS, what data is exactly stored where and for which purpose ??
Let's assume I keep my DMS logged into my account (no log-out after activation/scrapping)
:
- What information/data exactly is transmitted / stored when I first activate my DMS ?
- Is there usage data you collect when movies are watched or other activites are performed with DMS?
- Where are the scrapping results stored ? If the results are in a local DB why do I need to login into my cloud account to be able to edit it ?? the local :32080 was all I needed.
- can the wall populate ONLY wit local stored NFO's
So why do I need to login to dvdfab cloud in order to edit my poster wall ...?
- Can I delete/erase permanently and completely the metadata of my library de facto now stored in your cloud ?
Thanks
PS : In short : this hardware could be a very promising standalone network media PLAYER...i don't need another media SERVER with cloud based "functionalities"...
Comment