I was a big fan of popos (for a long time) and upgraded to the latest rust based one. However my firefox stopped working (no response for toolbar menu items and buttons).
The work around is to reset your display. After having to do this 5+ times a day (for months), I said sod it and went to ubuntu 22. Sad.
note: failed only my intel nuc, but not on thinkpad x1 carbon.
It works well and I haven’t had any issue. It doesn’t get full marks because it’s not an open device itself but more a device that’s easy to hack.
For example, most books in the kobo store have DRM (to be fair I don’t think it’s entirely their choice), albeit an easy one to break.
You see people here recommending “get a Kobo and install koreader”. That works and there is a one-click install process but it’s still an hack.
Another common thing to do is to keep the stock reader but tweak a file to point the store API to a self-hosted Komga/Calibre Web Automated/Grimmmory instance to get your own books in the system. Again, it works well enough but it’s not like these are documented API.
The bottom line is: it works very well and you can very easily tweak it but the way you tweak it are hacks (reasonable clean ones) rather than officially supported features. Thats why it loses a few marks
Said that, if you are not in the business of self-hosting, you can easily load books via USB or and it even has Dropbox or Google Drive integrations that work out of the box if you prefer network synchronisation
No issues here. I liberated my kindle library and put it in Google Drive. The Kobo can download books from there out of the box. The Kobo store works fine too, although a lot of books barely have any reviews if you’re into that. I have the Kobo Libra Colour and it’s by far the best reader I’ve ever owned.
It is a major pita dealing with the SES team. I originally wanted to send email from my web app (simply notification flow. i.e. you have a new request from user-123) and it is (IMHO) impossible to get past them. They won't tell you any reasons why. (Because they don't want devs gaming the system).
Nothing I could do could convince them that I wasn't trying to do 'bad' stuff. Just gave up and decided not to use any AWS tech.
> React is the worst thing to happen to the Javascript ecosystem. The idea is good, but the execution is just piss poor. I mean look at Vue and Svelte, they managed to do it right.
As a previously big React dev I agree 100%. If anyone feels this way please spend some time on doing Sveltekit project (e.g. rewrite a personal React project).
Also in the US (probably due to lack of training and the customer too embarrassed to complaining) tend not to fill it the brim (and so not even 16''). I've seen 2-3 inch heads and asked them to top it up. They look at me as if I've just insulted George Washington.
I still struggle with the fact that I was (or delusional) an effective C programmer "back in the day" (before google etc) and all we had was "man" to look up std/x11 system calls.
Now I am dismayed with juniors who can't even be bothered to use google (or llms) to look up stuff on their first hiccup.
I was a big fan of popos (for a long time) and upgraded to the latest rust based one. However my firefox stopped working (no response for toolbar menu items and buttons).
The work around is to reset your display. After having to do this 5+ times a day (for months), I said sod it and went to ubuntu 22. Sad.
note: failed only my intel nuc, but not on thinkpad x1 carbon.
reply