MobileRead Forums - View Single Post - Kepub - Calibre

davidfor · 07-07-2014, 09:15 PM

Thalinor: As the developer of the KoboTouch driver in calibre and the Kobo Utilities plugin, I'll back everything that jgoguen said. Kobo definitely know who I am and what I do. They have never asked me to stop doing it. They also don't actively support it. But, I have reported bugs to them that I found because of what I do with the driver, plugin and discussions here and seen them fixed. And they do occasionally answer my questions. Having said that, I have stated here that if Kobo asked me to stop doing something, I would think about it. Whether I would, would depend on what they were asking. And how they asked. Happily, they haven't felt the need to.

As to the driver and plugin, they are aimed at improving the user experience with the Kobo firmware. That means I do stick within what the firmware is capable of. If you want something else, then look at the other reader apps or installing Android. All of which are heavily discussed here and Kobo have made no efforts to block.

There are things I don't do. For example I rely on the firmware to process the books and add them to the internal database. I could do that and I have looked at it and written some of the code. But, I can't guarantee I would get it right and the details have changed with firmware releases. My decision was that it didn't offer enough benefits to make it worthwhile. You might interpret that as being lazy, and you are at least partly true. And to be honest, the Kobo Utilities plugin exists purely because I was lazy and wanted an easy way to do some experiments. And most of the rest of the function was added for the same reason.

As to Kobo staff here, as far as I can tell, there is only one actively involved here. There used to be more. I don't know why they don't post, but I am pretty sure they monitor the forum. Again, I have had no requests from them or MobileRead to stop doing anything I am doing.

07-07-2014, 09:15 PM	#9
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Thalinor: As the developer of the KoboTouch driver in calibre and the Kobo Utilities plugin, I'll back everything that jgoguen said. Kobo definitely know who I am and what I do. They have never asked me to stop doing it. They also don't actively support it. But, I have reported bugs to them that I found because of what I do with the driver, plugin and discussions here and seen them fixed. And they do occasionally answer my questions. Having said that, I have stated here that if Kobo asked me to stop doing something, I would think about it. Whether I would, would depend on what they were asking. And how they asked. Happily, they haven't felt the need to. As to the driver and plugin, they are aimed at improving the user experience with the Kobo firmware. That means I do stick within what the firmware is capable of. If you want something else, then look at the other reader apps or installing Android. All of which are heavily discussed here and Kobo have made no efforts to block. There are things I don't do. For example I rely on the firmware to process the books and add them to the internal database. I could do that and I have looked at it and written some of the code. But, I can't guarantee I would get it right and the details have changed with firmware releases. My decision was that it didn't offer enough benefits to make it worthwhile. You might interpret that as being lazy, and you are at least partly true. And to be honest, the Kobo Utilities plugin exists purely because I was lazy and wanted an easy way to do some experiments. And most of the rest of the function was added for the same reason. As to Kobo staff here, as far as I can tell, there is only one actively involved here. There used to be more. I don't know why they don't post, but I am pretty sure they monitor the forum. Again, I have had no requests from them or MobileRead to stop doing anything I am doing.