LibrarianSync: Kindle collections builder

[hius07]

Why don't you like the files attached to the first post of this thread?

[shamanNS]

@LuiMD: Download this: https://www.mobileread.com/forums/at...2&d=1569975082

(it is from the first post of this topic)

[ilovejedd]

Do note, there’s a new version of LibrarianSync updated June 2020 on:

https://github.com/NiLuJe/librariansync

As for installation, that’s done by unzipping and then copying the librariansync folder to the extensions folder (e.g. X:\extensions\librariansync on Windows).

[LuiMD]

@shamanNS, thanks! Its done

[Kornison]

Hello all,

My PW4 is stuck on "Rebuilding collection (from Calibre)..." for many hours.

Now I have Python 3.8 installed and read that may be the issue and would like to uninstall it and try 2.7 version to see if it makes a difference.
Should I do this? And if so, how do I uninstall it? Haven't found instructions and in the Python folder from snapshots there is both install and Update_python_0.15.N_uninstall.bin file for older version but for Python3 only Update_python3_0.15.N_install_pw2_kt2_kv_pw3_koa_k t3_koa2_pw4_kt4.

Thanks

[ilovejedd]

Originally Posted by Kornison

My PW4 is stuck on "Rebuilding collection (from Calibre)..." for many hours.

Now I have Python 3.8 installed and read that may be the issue and would like to uninstall it and try 2.7 version to see if it makes a difference.
Should I do this? And if so, how do I uninstall it? Haven't found instructions and in the Python folder from snapshots there is both install and Update_python_0.15.N_uninstall.bin file for older version but for Python3 only Update_python3_0.15.N_install_pw2_kt2_kv_pw3_koa_k t3_koa2_pw4_kt4.

What firmware version do you have installed on the PW4? I believe LibrarianSync stopped working in 5.12.x. Doesn't work in 5.13.x either.

You don't need to uninstall Python3. You just need to install Python2. Make sure you're using NiLuJe's updated version of LibrarianSync from github.

[lrpirlet]

I did deep dive the LibrarianSync module/software... That software does NOT work anymore... And probably will not work without some big change... See this entry.

Technically, as far as I understand, one way to be able to access the involved databases was to use

http://localhost:9101/change

(see wiki section Collections).

Amazon decided that it was not their policy (their policy seems to be: make money, only make money... do NOT consider customer desiderata that was NOT planned in their business plan and implement their plan even if it breaks a nice hack... close any open gate that could let a hacker change the customer expectation... In fact they act as if they had a monopoly not considering that other companies do provide similar product that CAN be hacked/improved/tuned...)

Again, as far as I understand, the database is undergoing changes and LibrarianSync would have come in their way, so they were obliged to brake it (poor developpers hit by hacks... Luckily, for me, they are not developping linux; unluckily, for us, they are not from Microsoft who would have bought the technology... sight).

Note that I could NOT find anymore the reference documents used by those who did develop the LibrarianSync hack.

I do see a way to repair the LibrarianSync, but it would be a big work for me and I feel that it will be invalidated as soon as I publish it, so I just use my kindle till it dies while looking around for a better alternative...

Anyway I share the frustration. I doubt that I will buy Amazon kindle or even Amazon products anymore. I would give my kindle a 3 out of 10 in any Net Promoter Score survey and such a high result would be only for the quality of the harware...

[MrTick]

I think I've solved the problem with 5.12+ firmware.
Now the localhost:9101/change requires some form of authentication.
After some poking around with tcpdump I've managed to find the following solution:

9101 POSTs require to authenticate with AuthToken field.
The value is then compared with current session token that's stored in... /tmp/session_token (it changes every reboot at least).

I'm uploading modified cc_update.py (it has to be replaced in extensions/librariansync)

201101:165222 system: I LibrarianSync:cc_update:: Sending commands...
201101:165223 system: I LibrarianSync:cc_update:: Success.
201101:165223 system: I LibrarianSync:main:: Done in 0.63s.

I've verified in for PW4 5.13.2 and 5.13.3

[NiLuJe]

@MrTick: Kudos! Can you send a PR to my GitHub fork?

[MrTick]

Originally Posted by NiLuJe

@MrTick: Kudos! Can you send a PR to my GitHub fork?

Sure, but as I haven't done that for a while, it'd take up to an hour

EDIT: done! (and took only 44 minutes )

[ilovejedd]

Originally Posted by MrTick

I think I've solved the problem with 5.12+ firmware.
Now the localhost:9101/change requires some form of authentication.
After some poking around with tcpdump I've managed to find the following solution:

9101 POSTs require to authenticate with AuthToken field.
The value is then compared with current session token that's stored in... /tmp/session_token (it changes every reboot at least).

I'm uploading modified cc_update.py (it has to be replaced in extensions/librariansync)

201101:165222 system: I LibrarianSync:cc_update:: Sending commands...
201101:165223 system: I LibrarianSync:cc_update:: Success.
201101:165223 system: I LibrarianSync:main:: Done in 0.63s.

I've verified in for PW4 5.13.2 and 5.13.3

Awesome news!

Question though, will this fix work with unregistered Kindles as well?

[MrTick]

Originally Posted by ilovejedd

Question though, will this fix work with unregistered Kindles as well?

If by unregistered you mean hack-registered then I'm 90% sure it'll work.

[ilovejedd]

Originally Posted by MrTick

If by unregistered you mean hack-registered then I'm 90% sure it'll work.

As in never registered to Amazon. No fake reg or anything.

[MrTick]

Originally Posted by ilovejedd

As in never registered to Amazon. No fake reg or anything.

In that case I think collections are still unavailable and enabling them would require hacking the framework itself

I don't quite understand why Amazon forces user to register before collections are enabled (actually I do understand, I just disagree totally with that politics)

[lrpirlet]

Originally Posted by MrTick

I think I've solved the problem with 5.12+ firmware.
Now the localhost:9101/change requires some form of authentication.
After some poking around with tcpdump I've managed to find the following solution:

9101 POSTs require to authenticate with AuthToken field.
The value is then compared with current session token that's stored in... /tmp/session_token (it changes every reboot at least).

I've verified in for PW4 5.13.2 and 5.13.3

I did try with wireshark but did not get anything (that I could use, I may have missed it in the HUGE file I got)...

Out of curiosity, to learn some, what did you monitor with tcpdump that leaded you to check the /tmp/session_token ?

It does work for me too on 5.12.4...