Content [KUAL Extension] KlipShare – Share Kindle highlights to Threads (Meta)

[Lord Acton]

Hi everyone,

I built a KUAL extension called KlipShare that reads highlights from
My Clippings.txt and posts them directly to Threads (Meta) with a
single tap — without leaving the Kindle or touching your phone.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
FEATURES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
• One-tap posting — select a highlight from the menu, it posts immediately
• Shows up to 30 recent highlights with estimated post length [142 chars]
• Auto-formats the post: "quote" — Book Title #kindle #leitura
• Smart capitalization (including accented characters)
• Offline queue — saves posts when no WiFi, sends on next connection
• Auto-refreshes the access token before expiry (60-day tokens)
• KOReader highlights support (reads .sdr/metadata.*.lua files)
• Title cleanup — strips z-library tags, [PDF]/[EPUB], emoji, etc.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
REQUIREMENTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
• Jailbroken Kindle
• KUAL 2.x or later (JSON + dynamic menu support)
• KOReader installed (provides the curl binary used for API calls)
• A Threads account

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
INSTALLATION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Download ZIP from GitHub and copy the klipshare/ folder to
extensions/ on your Kindle
2. Visit https://klipshare.vercel.app/setup on the browser where
you're logged into Threads
3. Click Authorize → copy the generated credentials.conf content
4. Create extensions/klipshare/config/credentials.conf and paste it
5. Eject, open KUAL → KlipShare → Update list

Full instructions: https://github.com/lordlobo1/KlipShare

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DOWNLOAD
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
https://github.com/lordlobo1/KlipSha...heads/main.zip

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PRIVACY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
KlipShare does not collect or store any data. Highlights are read
locally from My Clippings.txt. The only network calls are to the
official Threads API (Meta) to publish the post you authorize.
The access token is stored locally on the device only.

Feedback and bug reports welcome — happy to hear if it works on
your device model.

[Frogm4n]

Be aware that My Clippings.txt is not official or a stable way to access highlights. It's just a scratchpad that the Kindle uses for input. You should be using the book sidecars.

[Lord Acton]

Originally Posted by Frogm4n

Be aware that My Clippings.txt is not official or a stable way to access highlights. It's just a scratchpad that the Kindle uses for input. You should be using the book sidecars.

Thanks for the heads-up — that's a fair point and worth keeping in mind!

You're right that My Clippings.txt isn't an official API, and I'm aware of its limitations (duplicates, no guaranteed consistency, etc.). That said, KlipShare already handles most of those edge cases in the parser — including duplicate entries, BOM stripping, and some quirky title formats from sideloaded books.

The main reason I went with My Clippings.txt is pragmatic: it's plain text, readable with standard POSIX tools, and has been stable across Kindle firmware versions for well over a decade. Parsing .mbp sidecars in a busybox shell environment on the Kindle itself would be a significantly heavier lift, and the format isn't publicly documented.

That said, KlipShare does already read KOReader sidecar files (metadata.*.lua) as a second source for users who use that reader — so the sidecar idea isn't off the table.

If you know of a reliable way to parse the native .annot or .mbp files in a minimal shell/awk environment, I'd genuinely love to hear about it. Always open to making this more robust!