Hi,
Before I activate this plugin I just want to ask if it's the same format as the Roam Readwise plugin, or will I get duplicates?

It seems h.asin should be b.asin. The field asin is not set in the highlight, but it is set in the book data.

https://github.com/hkgnp/logseq-readwise-plugin/blob/be1b560cc1ca1460abf575b13789ba29cc915246/src/components/Sync.tsx#L75-L83

Example of a wrong url: kindle://book?action=open&asin=undefined&location=1126

Hi after importing I see entries like this:

And I have to add that Medium platform is bad for write, the editor is too much simple that became very complicate to use, for example there’re a lot of shortcust to insert Mardown sintax but they’re not the standard Mardown shortcuts, are not well
              link:: [null](null)
              on:: [[Jan 23rd, 2022]]
              tags::

Note the link:: [null](null)
I was expecting it would contain the link to the article.
Any ideas? Thanks for this great tool

Hi,
when I try to sync I get "Sync in progress initiated by different client" error.

Recently, I've reset my Logseq cache. After that, the error started to appear.

I've tried to reset Readwise plugin but it didn't fix the error.

If I watch the developer console, an error is throwed

Thank you for the great plugin!

When trying to use it I ran into the same issue that was reported with #2 and solved via this PR #3.

I just wanted to open a PR with the fix when I found the original issue.

The problem might be more prevalent now because the offending source in my case was the "Quick passages"-document that Readwise seems to add for all new users as an instruction manual. It does not have any highlights and when encountering it the sync freezes. As the document seems to have the date of the user signup and the newest sources are imported first, only one source was imported in my case before the import stopped. Deleting the document also does not help, because the API Responses seem to still contain ist, even though it does not show up in the UI any longer.

It looks like the fix mentioned above is not part of the source code anymore? Would you be open to add it again so that the plugin works in the mentioned case? I opened a PR that does that, but as the issue was solved before the credit should go to @MattHulse

It looks like only 100 sources will be imported. If I let the first sync complete will I be able to get the other sources on the next run?

I haven't let it complete yet because it seems like it is hanging at about the 50% mark.

Each imported book contains a properties section including retrieved:: .
This has a link to the journal date for when the highlight was imported, but also a hh:mm timestamp. This ends up creating odd pages in my graph like the following:

1:15:
1:16:
1:17:

The link to the date the items are imported is nice, and the time may be interesting in the context of the highlight (more interesting if it was the actual 24 hour time). However it is not something I want to link to.

Here is a sample header for an imported highlight:

retrieved:: [[Dec 28th, 2021]], 1:15:
              author:: [[Psychology Today]]
              category:: [[articles]]
              source:: [[reader]]

When I use the /Book renderer command, nothing displays.

I have the latest version of the both the plugin and Logseq.

Great plugin; thanks so much for creating it.
I'm having a couple of small issues with properties: the content of the properties bullet is invisible when it is not active, and changing the order of the properties lines deletes content. Here are two screenshots that show the properties bullet when active and not active:

With other properties bullets in Logseq, the properties bullet has a background and the properties are shown in bold. I've shown this default situation below, in case I am not describing it well:

So, there is something different about these Readwise properties that is preventing the background and bold effects and also making the bullet appear empty when it is not.
(In the first screenshot above I have removed the 14 spaces that the plugin inserts, for some reason, to each property line. I prefer the properties to be left-aligned. This change seems to make no difference to the issue I'm seeing. Also, if I move a property such as tags to the top of the list, that property is deleted when I click out of the bullet. I don't mind the order of the properties as it is; I just thought I would experiment with placing the tags at the top, to see if doing so would fix the issue, and that's when I noticed the deletion.)

After performing a Readwise import I can't open the Readwise Import window again until a restart of the Logseq app is performed.

In Step 3 when I start the sync the plugin gets stuck in x% (I'm not referring to the "Please wait for Readwise's cooling off period to lapse." message) and refuses to sync more highlights. If I manually activate "Stop Syncing", and restart de plugin it starts from the beginning and advances a little bit more, but eventually gets stuck again and I need to restart it multiple times.

My initial sync keeps hanging. It seems to stop at the same document every time. The last document processed appears to have been created successfully. Unfortunately I can't tell what the next document is as it is likely the one causing trouble. Sometimes article titles have characters that are not valid as filenames (I've noticed this in the Obsidian Readwise Export). So maybe one of the sources has a character that is invalid for a filename and that is causing the import to stop?

The exception I see in the console is this:

index.ddbc8bca.js:2 Uncaught (in promise) TypeError: Cannot read properties of null (reading '$cljs$core$IFn$_invoke$arity$1$')
    at $clojure$zip$node$$ (zip.cljs:64)
    at $frontend$modules$outliner$core$get_node_tree_topmost_last_loc$$ (core.cljs:355)
    at $frontend$modules$outliner$core$insert_nodes$$ (core.cljs:377)
    at $frontend$handler$editor$paste_block_vec_tree_at_target$$ (editor.cljs:2205)
    at $frontend$handler$editor$paste_block_tree_after_target$$ (editor.cljs:2267)
    at api.cljs:430
    at k (helpers.ts:141)
    at Ae.<anonymous> (LSPlugin.core.ts:186)
    at Ae.a.emit (index.js:181)
    at B.<anonymous> (LSPlugin.caller.ts:202)

My syncing no longer works. It just stops at some percentage.

I've tried downgrading to Logseq 0.6.5 because I say that in another issue. Same result though.

With 0.6.5 I get the following error in the console:

Seems to always happen with the same book.

Didn't find a good way to debug, any tips on how to proceed?

After importing my highlights from Readwise the Link of all highlights is [[null]]

.

Every time i synchronize data from readwise, there will find that duplicate blocks are created

When syncing a thread, In the readwise highlights section, the threads are synced in the reverse order, which means it's basically unreadable.

The linked reference that appears in the Journal daily page, has sorting which is even weirder, it does not seem to follow any kind of logical pattern of sorting.

Example in the linked image.

There should be an option to specify max image height/width and then scale down the images appropriately with this syntax

![book_image](link){:height 180, :width 120}

An entry from the built-in Zotero connection creates properties like so:

tags:: [[bias]], [[research]], [[uncertainty]]
date:: 2020
extra:: OCLC: 1061820225
isbn:: 978-0-425-28464-3
title:: @Skin in the game: hidden asymmetries in daily life
item-type:: [[book]]
original-title:: Skin in the game: hidden asymmetries in daily life
language:: English
short-title:: Skin in the game
authors:: [[Nassim Nicholas Taleb]]
library-catalog:: Open WorldCat
links:: [Local library](zotero://select/library/items/JG44VHNX), [Web library].
(https://www.zotero.org/users/5457446/items/JG44VHNX)

For a Readwise quotation from the publication above, the Readwise plugin creates properties like so:

retrieved:: [[Jan 15th, 2022]], :04:3
author:: [[Nassim Nicholas Taleb]]
category:: [[books]]
source:: [[kindle]]
tags:: [[uncertainty]], [[bias]], [[research]]

The two sets of properties refer to the same thing in two different ways: in this case, [[book]] vs. [[books]] (there may be other such instances in other types of references). The category (aka item-type) entries are not aligned, with the result that two pages are created (book and books) for the same type of thing.

Furthermore, each Zotero reference creates a separate page (with title of the form @Skin in the game: hidden asymmetries in daily life, and the Readwise plugin creates its own page of the form Skin in the Game (Readwise). It would be good to have a single unified page for each publication, showing both the Zotero citation and its accompanying Readwise quotations — instead of two different pages for the same publication. This might be tough to do, as some integration with the Zotero plugin would (probably) be required.

The plugin does not comply with prefer date format, i.e., all its dates are "MMM do, yyyy".

I'd wish to the plugin to honor the logseq prefer date format or have a config to set it up for itself.