With firmware 6 using the same renderer for both, will kepub go away?

[MGlitch]

I’d think it would require them either declaring all devices that they aren’t going to send 6.0 to (or whatever it gets to when it’s beyond beta) EoL or finally bring all the devices to it.

I haven’t updated in ages because I just don’t see the point. I haven’t seen any features in the sub 5.0 firmware that I need to have. And with kobo deciding to have different versions out at the same time it became more hassle to update and patch than the update was worth.

[rantanplan]

They can still release updates to the 4.38.x version though. Which is what they are already doing anyway.

[Dal Bhat]

Originally Posted by Sirtel

There is a patch requiring your consent before updating. It works perfectly. I've turned wifi on for one of my Kobos several times in the past year and it's still on an older firmware.

I've searched and cannot find a single patch for firmware 4.45.23655.

[DNSB]

Originally Posted by rantanplan

Why would they have to pay Adobe? Kobo uses their own DRM scheme on the devices.

On kepub.epub, Kobo uses their own DRM. On .epub, Kobo uses Adobe's ADEPT DRM and Adobe's Content Server backend. This keeps allows users without Kobo devices/apps to use their services.

On the v6 firmware, kepub.epub, LCP DRMmed .epub and DRM free .epub files use Kobo's webkit based renderer called TENG. Adobe DRMmed epubs are opened with RMSDK (library books, downloads from other sites, etc.) for compatibility. You can also download a .acsm file and it will open on the Kobo.

In my limited testing, TENG seems to treat all epubs the same as far as statistics go though only ebooks synced from Kobo seem to have their statistics stored on Kobo's servers.

[DNSB]

Originally Posted by Dal Bhat

Are older device capable of running the newer renderer?

In theory yes. It will take some work to make it as speedy as the old code.