I’m not in the EU so I have not, this is based on the technical changes mentioned, and what I’ve heard from people. Feel free to try if you are in the EU: kobo.com/update
Kobo is actually in the process of completely rewriting their e-reader software (you can download the beta in the EU), and I’m pretty sure it’s no longer based on RMSDK. Adobe basically handed the EPUB DRM market to LCP on a silver platter by being a poor maintainer and then selling off to a third party that had botched the migration and further angered end users and platforms, that are switching off Adobe faster than ever
That “compact JSON” format reminds me if the special protobufs JSON format that Google uses in their APIs that has very little public documentation. Does anyone happen to know why Google uses that, and to OP, were you inspired by that format?
A nonprofit I help out just moved from Slack to Discord for a very simple reason: Slack pricing was too expensive, and as the amount of people increased, the price continues to climb. Discord is free
Where can I learn more about hardware acceleration of WebP on mobile OSes? I haven’t yet come across a resource that confirms this is actually the case. I know it should theoretically be possible using the VP8 hardware decoders but I thought those were expensive to warm up just for images
It's somewhat popular for piracy, when you know that your site could never pass the Apple/Google store reviews. I've seen it with, for example, manga aggregators
I disagree regarding the choice of codec. Currently, I have no issues receiving, saving, and viewing H265 streams.
Any modern CPU/GPU can handle them natively (I use a 2018 Intel CPU w/ QSV), any modern desktop or mobile device (I use both Android and iOS) can stream it, and the recorded video takes up less space. What are you using that requires transcoding?
This would break way too many websites to be feasible. And if implemented, would be something requested on so many sites that users would learn to automatically say yes which would weaken the power of permission prompts in general.
For example, almost every major Japanese book/comic site uses canvas in their e-reader
Stripe also has a version of this called “Link”, which uses SMS authentication. Based on Stripe data on multiple platforms I have access to, quite a high percentage of people use it, probably due to how hard it’s pushed by the UI when adding a payment method
What I preferred recently when buying a used car over Craigslist was that I was able to vet the seller more easily because this was their Facebook profile. Like many other people on the older side, their profile was completely public, and I was able to scroll through over a decade of pictures, education, family etc. This was a very useful check against scams and lies.
I agree that AI translations are not close to the standards many people would expect, but there is a significant, growing population of readers (many with EN as a second language) that are fine with reading MTL using extensions such as this or fan-translated MTL with human assistance, and it is what many new fan translators are opting for as old groups retire.
The “speed translators” using MTL also demotivate the slower, better translators, as many people will no longer be as interested in their release.
I don’t think human translation will cease for a long time, but in the meantime, MTL as a percentage of new fan translations will continue to grow
You have much competition in this space with for example
https://ichigoreader.comhttps://ismanga.com
and many more (just search the chrome extension store for examples). What is your plan to stand out and remain competitive?
On a side note, if anyone’s been watching the fan translation community, it’s clear this is the end game.
What is wrong with frequent changing of jobs? It’s one of the easiest tools for increasing my compensation. The job market ideally should be so flexible you can switch to another company any time you want, no noncompetes.
It’s actually still a bit tedious on the Apple ecosystem. On the web (Safari) you have to wrap it in a WEBM or CAF container, and on iOS it’s similar. That’s a lossless process, but it’s still not the OPUS container
[username] at gmail dot com