Thread by @TfTHacker

1/ Readwise Tip - Use highlight_id in your exports

The @readwiseio export feature allows you to export your highlights to various tools like @obsdmd, @RoamResearch, @NotionHQ and more. The export can be configured to export these highlights in a format that works best for you.

2/ One possible issue when exporting highlights is that you can lose context of where they come from. Each TfT tools might have their own way of creating references to a source (example: block references).

How can we connect our TfT back to its source consistently?

3/ Readwise’s highlight_id to the rescue.

Use highlight_id in your export configurations.

It is Readwise’s internal identifier for that highlight. This means that every highlight you create gets its own unique identifier and is globally unique to the Readwise system.

4/ There are 2 benefits to using highlight_id

1. Unique identifier always the same no matter where you export it to

2. I can run the export command as many times as I want in my vault/graph and the highlight will always have the same ID. Great for referencing highlights.

5/ In effect, Readwise becomes your single source of truth for highlights in the form of highlight_id, and that ID can be used across tools and you can always trace it back.

For more info and how to do this with Obsidian:

craft.do/s/JxGqtPMkM8ve…