piranha: red origami crane (Default)
my kobo "wifi" is showing its age -- which is quite amusing, considering it's less than 2 years old. alas no more firmware upgrades seem to be coming along, since the company has now 2 further advanced models, and while always promising not to forget us "old" users, yeah right, i know insincere pep talks when i hear them. the interface is SLOW, parts of it are too slow for me to put up with anymore. organization? what organization. i have to modify filenames carefully so i can read them at all. also, the battery is holding less and less charge, and it's not replaceable.

i've taken to the ebook experience like a , uh, fish to water. ;) i hardly buy print books anymore, unless i know the author personally, or the book absolutely cannot be had in electronic format (and then i'll scan it). i love the light little thing; it weighs less than a paperback and it easier to hold, and takes less space to carry along. the e-ink is restful for my eyes. and i buy a lot of ebooks; more than i used to buy print books. there is no space issue with them. :)

so, i am thinking of upgrading. but i am not entirely sure buying another ebook reader is the answer. part of why i bought a kobo was that it was canadian, and i wanted to throw my purchasing power behind somebody other than amazon or sony, and hey, it was a nice thought for a "local" company to be successful in that market. which surprisingly they have been; in canada they have 46% of market share compared to 24% for amazon and 18% for sony. but now rakuten (a huge japanese conglomerate) owns kobo, so that incentive has gone away. sure, better rakuten than amazon, but still... no longer "local", no longer smallish. yes, i do have major peeves about large corporations.

still, the kobo "touch" looks decent, and it's come down in price which is now lower than what i originally paid for my first kobo. i am absolutely not going to buy a kindle, ever; amazon's walled garden philosophy makes me sick. am not all that interested in sony either. maybe a nook. maybe one of the "also ran" models, like from bookeen. or maybe i should be looking at android tablets? kobo's newest, the "vox", runs on android. that does away with the restfulness of the e-ink, and if android, why not get a real tablet then instead of a stunted ereader?

do you have an ereader and/or tablet? what do you love/hate about it? what would you buy instead if you were in the market? i'm not quite up-to-date with the tech anymore.
piranha: red origami crane (Default)
and even large companies like adobe and amazon seem blissfully unaware of such a thing. what is this, the dark ages?

so today i installed the kindle for mac program since i broke down to buy a book i really needed right away, and which was most easily available on the kindle.

the app died on me right away with the incredibly helpful error message "there was a problem". no shit?

fortunately we have the console, which told me:
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] dyld: Library not loaded: @executable_path/../Frameworks/libWEbCoreKRF.dylib
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] Referenced from: /Applications/Kindle.app/Contents/MacOS/../Frameworks/libWebCoreViewer.dylib
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] Reason: image not found

thanks to adobe i am primed to look for case-sensitivity issues, so the difference between libWEbCore and libWebCore jumped right out at me. looking inside the app bundle showed that indeed, libWebCoreKRF.dylib is present and accounted for.

fortunately this is easily fixed by creating a dynamic link from the correct lib to the misspelled one:

using terminal, admin privileges, go to the directory in question (/Applications/Kindle.app/Contents/Frameworks if you've installed in the usual place), and issue this command:

ln -s libWebCoreKRF.dylib libWEbCoreKRF.dylib

and the app will work for now -- until the next update. any bets on whether that'll fix the problem? yeah, didn't think so.

in better news, market day left us with ripe, local strawberries, and they are SO GOOD. and moroccan spice bread. and baked bread pudding. and fresh fudge.
piranha: red origami crane (Default)
and will never do so, no matter how spiffy they make them.

i don't want amazon deleting my copies because they've decided "there is a problem". that business model reeks to high heaven.

the whole idea that ebooks are licensed displeases me to begin with, but the big-brother approach amazon takes scared me off their product from the very start.
piranha: red origami crane (Default)
so a "glitch" is responsible? say what? since when do glitches send customer service letters signed with "ashley d"?

exactly what kind of glitch? you didn't answer the LA times when they asked. i dunno about you, but when i wrote for a large company with many, many clients, this was the process a software change went through:

- a proposal for change is thought up and presented.
- several someones up the management chain have to approve it.
- money has to be budgeted.
- code has to be spec'ed and written.
- the code has to be tested on a development system.
- bugs are fixed and retested.
- finally the change is rolled out into production.

in between are often some rounds of "what about this?", "ah, you're right, we gotta change that too".

so, what exactly here is the glitch? what did amazon _mean_ to do?

and how is it that it wasn't detected earlier? don't tell me amazon's programmers just let any old code loose on the production servers on the day before easter weekend. i know complexity is a complex thing, but that would just be lousy practice, and any internet company should know better.

also, whoever designed this craptacular way of using sales rankings to keep adult books out of certain searches, should be sent to reeducation bootcamp. there is absolutely no reason per se why it has to be done that way; it's profoundly inelegant. furthermore, what i do and don't get to see in searches should be up to _me_, and only me -- if i want to see cock, that should be my damn choice. i need no protection. well, maybe from twilight, but let me guess, that didn't get unranked.

amazon's latest statement.

and this theory seems to me the most plausible to date: former amazon employee talks about arcane bits of the editing system. i mean, everyone who works on LJ code can conceive of this, right? *wry grin*.

so, no more editing on live systems, hm, amazon? also, an apology would be nice.


piranha: red origami crane (Default)
renaissance poisson

July 2015

   123 4

Most Popular Tags

Expand Cut Tags

No cut tags


RSS Atom