2017-11-10, 18:17
For this Christmas/Holiday 2017 (as in Dec 24) , Google Drive KODI plugin v0.9.0 will be released. I'm planning for a lot of new features, in addition to handling stability fixes.
Highlights:
- new run modes:
1) traditional -- like it is today where you load the plugin, authenticate your account with the plugin on the device, and access your media, create STRM files, load your KODI library, etc
2) sever-assisted mode -- where the plugin coordinates with a low powered VPS or google compute engine (you provide or use one provided) that will do the "hard lifting" associated with decrypting streams. This run mode is for those who want to use encfs or pycrypto but cannot get their device to load the appropriate decryption modules (ios, some android devices)
3) server-dedicated mode -- where your version of KODI (such as a KODI fork) doesn't support add-ons, the low powered VPS or google compute engine handles all the work and your KODI just opens the streams -- ideal for devices like IOS where side-loading KODI is not possible
4) web browser mode -- enjoy the Google Drive KODI plugin experience in any HTML5 browser, no KODI required to be installed on the device (powered by low powered VPS or google compute engine)
5) EmbyServer / Plex mode -- enjoy the Google Drive KODI plugin in EmbyServer and Plex, no KODI required to be installed on the device (powered by ow powered VPS or google compute engine)
6) server-managed mode - like traditional but credentials are handled in a low powered VPS or google compute engine
Other features in all versions, including the traditional KODI plugin form, will include automatic scheduled STRM creation and media upload.
Testing will be conducted in gdrive-testing releases throughout November and December (as 0.8.56+ leading up to 0.9.0).
low-powered VPS or google compute engine is defined as any Linux device with at least 128MB RAM (all development and testing will be performed on maximum 128MB RAM). This can be easily substituted with an embedded board like a raspberry pi.
Highlights:
- new run modes:
1) traditional -- like it is today where you load the plugin, authenticate your account with the plugin on the device, and access your media, create STRM files, load your KODI library, etc
2) sever-assisted mode -- where the plugin coordinates with a low powered VPS or google compute engine (you provide or use one provided) that will do the "hard lifting" associated with decrypting streams. This run mode is for those who want to use encfs or pycrypto but cannot get their device to load the appropriate decryption modules (ios, some android devices)
3) server-dedicated mode -- where your version of KODI (such as a KODI fork) doesn't support add-ons, the low powered VPS or google compute engine handles all the work and your KODI just opens the streams -- ideal for devices like IOS where side-loading KODI is not possible
4) web browser mode -- enjoy the Google Drive KODI plugin experience in any HTML5 browser, no KODI required to be installed on the device (powered by low powered VPS or google compute engine)
5) EmbyServer / Plex mode -- enjoy the Google Drive KODI plugin in EmbyServer and Plex, no KODI required to be installed on the device (powered by ow powered VPS or google compute engine)
6) server-managed mode - like traditional but credentials are handled in a low powered VPS or google compute engine
Other features in all versions, including the traditional KODI plugin form, will include automatic scheduled STRM creation and media upload.
Testing will be conducted in gdrive-testing releases throughout November and December (as 0.8.56+ leading up to 0.9.0).
low-powered VPS or google compute engine is defined as any Linux device with at least 128MB RAM (all development and testing will be performed on maximum 128MB RAM). This can be easily substituted with an embedded board like a raspberry pi.
