Skip to content

Commit 70f8280

Browse files
committed
chore: update README with privacy info, remove unnecessary settings
1 parent e26e1ad commit 70f8280

File tree

1 file changed

+3
-26
lines changed

1 file changed

+3
-26
lines changed

readme.md

Lines changed: 3 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
# Chat Export Extension (LLM)
22

3-
[link-cws-keys]: https://github.com/fregante/chrome-webstore-upload-keys
4-
[link-amo-keys]: https://addons.mozilla.org/en-US/developers/addon/api/key
5-
63
[![Test](https://github.com/Trifall/chat-export/actions/workflows/test.yml/badge.svg)](https://github.com/Trifall/chat-export/actions/workflows/test.yml)
74

85
This extension allows you to export chat conversations from ChatGPT, and Claude to Markdown, XML, JSON, and HTML.
@@ -11,6 +8,8 @@ The export button is placed next to the share button.
118

129
I made this extension in my free time over a couple days because I wanted this feature and also [this tweet](https://x.com/tylerangert/status/1902038162836246550). Might be scuffed on edge cases but I tried my best.
1310

11+
This extension does **NOT** store, upload, or share any data remotely. It does **NOT** store any personal or private/identifiable data. All content is stored on the local machine and the local users's clipboard. Only stores the configuration for the output format (string enum [markdown, html, xml, json] for ease-of-use.
12+
1413
![Export Video Example](https://github.com/user-attachments/assets/2705e502-9e1f-41a8-88e9-3b41242d6c0f)
1514

1615
Extension Settings:
@@ -64,29 +63,7 @@ Here are some websites you should refer to:
6463

6564
- [Parcel’s Web Extension transformer documentation](https://parceljs.org/recipes/web-extension/)
6665
- [Chrome extensions’ API list](https://developer.chrome.com/docs/extensions/reference/)
67-
- A lot more links in my [Awesome WebExtensions](https://github.com/fregante/Awesome-WebExtensions) list
68-
69-
### Publishing
70-
71-
It's possible to automatically publish to both the Chrome Web Store and Mozilla Addons at once by adding these secrets on GitHub Actions:
72-
73-
1. `CLIENT_ID`, `CLIENT_SECRET`, and `REFRESH_TOKEN` from [Google APIs][link-cws-keys].
74-
2. `WEB_EXT_API_KEY`, and `WEB_EXT_API_SECRET` from [AMO][link-amo-keys].
75-
76-
Also include `EXTENSION_ID` in the secrets ([how to find it](https://stackoverflow.com/a/8946415/288906)) and add Mozilla’s [`gecko.id`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings) to `manifest.json`.
77-
78-
The GitHub Actions workflow will:
79-
80-
1. Build the extension
81-
2. Create a version number based on the current UTC date time, like [`19.6.16`](https://github.com/fregante/daily-version-action) and sets it in the manifest.json
82-
3. Deploy it to both stores
83-
84-
#### Auto-publishing
85-
86-
Thanks to the included [GitHub Action Workflows](.github/workflows), if you set up those secrets in the repo's Settings, the deployment will automatically happen:
87-
88-
- on a schedule, by default [every week](.github/workflows/release.yml) (but only if there are any new commits in the last tag)
89-
- manually, by clicking ["Run workflow"](https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/) in the Actions tab.
66+
- A lot more links in Fregante's [Awesome WebExtensions](https://github.com/fregante/Awesome-WebExtensions) list
9067

9168
## Credits
9269

0 commit comments

Comments
 (0)