diff --git a/.github/workflows/deploy-docs.yml b/.github/workflows/deploy-docs.yml deleted file mode 100644 index 45121dd0..00000000 --- a/.github/workflows/deploy-docs.yml +++ /dev/null @@ -1,48 +0,0 @@ -name: Deploy Documentation - -on: - push: - branches: [main] - -jobs: - deploy: - runs-on: ubuntu-latest - - permissions: - contents: read - pages: write - id-token: write - - environment: - name: github-pages - url: ${{ steps.deployment.outputs.page_url }} - - steps: - - name: Checkout - uses: actions/checkout@v4 - - - name: Setup Node.js - uses: actions/setup-node@v4 - with: - node-version: "20" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: Build documentation - run: | - cd docs - npm run build - - - name: Setup Pages - uses: actions/configure-pages@v4 - - - name: Upload artifact - uses: actions/upload-pages-artifact@v3 - with: - path: ./docs/build - - - name: Deploy to GitHub Pages - id: deployment - uses: actions/deploy-pages@v4 diff --git a/docs/.gitignore b/docs/.gitignore deleted file mode 100644 index b2d6de30..00000000 --- a/docs/.gitignore +++ /dev/null @@ -1,20 +0,0 @@ -# Dependencies -/node_modules - -# Production -/build - -# Generated files -.docusaurus -.cache-loader - -# Misc -.DS_Store -.env.local -.env.development.local -.env.test.local -.env.production.local - -npm-debug.log* -yarn-debug.log* -yarn-error.log* diff --git a/docs/README.md b/docs/README.md deleted file mode 100644 index 2fdbdc3a..00000000 --- a/docs/README.md +++ /dev/null @@ -1,25 +0,0 @@ -# Cyd Docs Website - -The Cyd docs website is built using [Docusaurus](https://docusaurus.io/). - -### Installation - -```sh -npm install -``` - -### Local Development - -```sh -npm run start -``` - -This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. - -### Build - -```sh -npm run build -``` - -This command generates static content into the `build` directory and can be served using any static contents hosting service. diff --git a/docs/blog/2025-03-06-cyd-1.1.0.md b/docs/blog/2025-03-06-cyd-1.1.0.md deleted file mode 100644 index fade009b..00000000 --- a/docs/blog/2025-03-06-cyd-1.1.0.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -slug: cyd-1.1.0 -title: Cyd 1.1.0 released ---- - -**We're pleased to announce Cyd 1.1.0 is released.** This is a major release that fixes several bugs and adds support for, among other things, _migrating your tweets from X into Bluesky_! Here's what's new: - -- Major feature: You can now [migrate your tweets to Bluesky!](/docs/x/migrate-bluesky) ([#369](https://github.com/lockdown-systems/cyd/issues/369)) -- Major feature: Cyd now has [documentation](/docs/intro/) (that's this website you're reading now) ([#374](https://github.com/lockdown-systems/cyd/issues/374), [#412](https://github.com/lockdown-systems/cyd/pull/412)) -- Minor feature: New "Enable Clicking in Browser" while Cyd does its think with the embedded browser ([#435](https://github.com/lockdown-systems/cyd/pull/435)) -- Bug fix: When you import an X archive, or build your database from scratch, GIF media is handled correctly ([#421](https://github.com/lockdown-systems/cyd/pull/421)) -- Bug fix: Fix crash when importing certain tweets that contain links ([#432](https://github.com/lockdown-systems/cyd/issues/432)) -- Bug fix: Fix displaying names of direct message users in the X archive ([#416](https://github.com/lockdown-systems/cyd/issues/416)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.0). - - diff --git a/docs/blog/2025-03-11-cyd-1.1.1.md b/docs/blog/2025-03-11-cyd-1.1.1.md deleted file mode 100644 index 44992913..00000000 --- a/docs/blog/2025-03-11-cyd-1.1.1.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -slug: cyd-1.1.1 -title: Cyd 1.1.1 released ---- - -**We're pleased to announce Cyd 1.1.1 is released.** This is a minor release. Here's what's new: - -- Docs: The docs website (that's this website!) now has privacy-friendly [Plausible analytics](https://plausible.io/) so we can see what pages are getting read ([#444](https://github.com/lockdown-systems/cyd/pull/444)) -- Bug fix: When connecting a Bluesky account, your handle can start with the `@` character ([#450](https://github.com/lockdown-systems/cyd/pull/450)) -- Bug fix: If initializing the Bluesky client fails, delete the state/session and try again ([#453](https://github.com/lockdown-systems/cyd/pull/453)) -- We updated Node.js dependencies ([#452](https://github.com/lockdown-systems/cyd/pull/452)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.1). - - diff --git a/docs/blog/2025-03-19-cyd-1.1.2.md b/docs/blog/2025-03-19-cyd-1.1.2.md deleted file mode 100644 index d2fd34e4..00000000 --- a/docs/blog/2025-03-19-cyd-1.1.2.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -slug: cyd-1.1.2 -title: Cyd 1.1.2 released ---- - -**We're pleased to announce Cyd 1.1.2 is released.** This is a minor release. Here's what's new: - -- Bug fix: Increase the timeout when deleting DMs, which was preventing DMs from being deleted for accounts with lots of DMs ([#459](https://github.com/lockdown-systems/cyd/pull/459)) -- Bug fix: In migrate to Bluesky from X, force disconnecting from Bluesky after connection failure ([#458](https://github.com/lockdown-systems/cyd/pull/458)) -- Bug fix: Fix crash on timing out when indexing DMs ([#461](https://github.com/lockdown-systems/cyd/pull/461)) -- Feature: Error reports include stack traces, which will make them far easier to debug ([#462](https://github.com/lockdown-systems/cyd/pull/462)) -- Feature in-progress: Preliminary support for Facebook is getting merged into this release, but it's still hidden behind a feature flag ([#405](https://github.com/lockdown-systems/cyd/pull/405)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.2). - - diff --git a/docs/blog/2025-04-02-cyd-1.1.3.md b/docs/blog/2025-04-02-cyd-1.1.3.md deleted file mode 100644 index 9ec69d17..00000000 --- a/docs/blog/2025-04-02-cyd-1.1.3.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -slug: cyd-1.1.3 -title: Cyd 1.1.3 released ---- - -**We're pleased to announce Cyd 1.1.3 is released.** This is a minor release. Here's what's new: - -- Bug fix: Increase timeouts when loading X DMs page ([#471](https://github.com/lockdown-systems/cyd/pull/471)) -- Bug fix: Make loading URLs more robust to fix GUEST_VIEW_MANAGER_CALL errors ([#485](https://github.com/lockdown-systems/cyd/pull/485)) -- More work towards Facebook support ([#472](https://github.com/lockdown-systems/cyd/pull/472), [#475](https://github.com/lockdown-systems/cyd/pull/475), [#467](https://github.com/lockdown-systems/cyd/pull/467), [#477](https://github.com/lockdown-systems/cyd/pull/477)) -- Docs: Add Troubleshooting Cyd page to docs ([#479](https://github.com/lockdown-systems/cyd/pull/479)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.3). - - diff --git a/docs/blog/2025-04-04-cyd-1.1.4.md b/docs/blog/2025-04-04-cyd-1.1.4.md deleted file mode 100644 index 82a8c04c..00000000 --- a/docs/blog/2025-04-04-cyd-1.1.4.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -slug: cyd-1.1.4 -title: Cyd 1.1.4 released ---- - -**We're pleased to announce Cyd 1.1.4 is released.** This handles changes in X's API that prevented saving tweets and likes from working. Here's what's new: - -- Bug fix: Handle change in X API responses ([#490](https://github.com/lockdown-systems/cyd/pull/490)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.4). - - diff --git a/docs/blog/2025-04-09-cyd-1.1.5.md b/docs/blog/2025-04-09-cyd-1.1.5.md deleted file mode 100644 index 74e0a61c..00000000 --- a/docs/blog/2025-04-09-cyd-1.1.5.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -slug: cyd-1.1.5 -title: Cyd 1.1.5 released ---- - -**We're pleased to announce Cyd 1.1.5 is released.** This is a minor release. Here's what's new: - -- Bug fix: Make X platform considerably more efficient, and prevent freezes, for users with lots of data ([#493](https://github.com/lockdown-systems/cyd/pull/493)) -- Refactor: Improve release scripts ([#489](https://github.com/lockdown-systems/cyd/pull/489)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.5). - - diff --git a/docs/blog/2025-04-18-cyd-1.1.6.md b/docs/blog/2025-04-18-cyd-1.1.6.md deleted file mode 100644 index 9848a684..00000000 --- a/docs/blog/2025-04-18-cyd-1.1.6.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -slug: cyd-1.1.6 -title: Cyd 1.1.6 released ---- - -**We're pleased to announce Cyd 1.1.6 is released.** This is a minor release. Here's what's new: - -- Refactor: Improve how Cyd builds the local X archive, and improve the local X archive website itself ([#505](https://github.com/lockdown-systems/cyd/pull/505)) -- Bug fix: Fix problem where users sometimes got a "userInfo is null" error ([#456](https://github.com/lockdown-systems/cyd/pull/503)) -- Docs: Update text on the Premium page ([#499](https://github.com/lockdown-systems/cyd/pull/499)) -- Feature: Let users know about Premium, Cyd for Teams, and donating after they finish running jobs ([#501](https://github.com/lockdown-systems/cyd/pull/501)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.6). - - diff --git a/docs/blog/2025-05-13-cyd-1.1.10.md b/docs/blog/2025-05-13-cyd-1.1.10.md deleted file mode 100644 index 3cffeb1f..00000000 --- a/docs/blog/2025-05-13-cyd-1.1.10.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -slug: cyd-1.1.10 -title: Cyd 1.1.10 released ---- - -**We're pleased to announce Cyd 1.1.10 is released.** This is a minor release. Here's what's new: - -- Refactor: Improvement to automatic updates ([#508](https://github.com/lockdown-systems/cyd/pull/508)) -- Feature: More Facebook support, hidden behind a feature flag ([#482](https://github.com/lockdown-systems/cyd/pull/482)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.10). - - diff --git a/docs/blog/2025-05-14-cyd-1.1.11.md b/docs/blog/2025-05-14-cyd-1.1.11.md deleted file mode 100644 index 3808bace..00000000 --- a/docs/blog/2025-05-14-cyd-1.1.11.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -slug: cyd-1.1.11 -title: Cyd 1.1.11 released ---- - -**We're pleased to announce Cyd 1.1.11 is released.** This is a minor release. Here's what's new: - -- Bug fix: Fix problem where GUEST_VIEW_MANAGER_CALL errors randomly occur ([#524](https://github.com/lockdown-systems/cyd/pull/524)) -- Bug fix: Don't show old archive warning in Migrate to Bluesky if there's no local data yet ([#517](https://github.com/lockdown-systems/cyd/pull/517)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.11). - - diff --git a/docs/blog/2025-05-28-cyd-1.1.12.md b/docs/blog/2025-05-28-cyd-1.1.12.md deleted file mode 100644 index 2df24f1b..00000000 --- a/docs/blog/2025-05-28-cyd-1.1.12.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -slug: cyd-1.1.12 -title: Cyd 1.1.12 released ---- - -**We're pleased to announce Cyd 1.1.12 is released.** This is a minor but important release. Here's what's new: - -- X changed how it works, which broke Cyd. This fixes it again. ([#528](https://github.com/lockdown-systems/cyd/pull/528)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.12). - - diff --git a/docs/blog/2025-05-28-cyd-1.1.13.md b/docs/blog/2025-05-28-cyd-1.1.13.md deleted file mode 100644 index 11b81f4d..00000000 --- a/docs/blog/2025-05-28-cyd-1.1.13.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -slug: cyd-1.1.13 -title: Cyd 1.1.13 released ---- - -**We're pleased to announce Cyd 1.1.13 is released.** This fixes a bug related to the previous release earlier today. Here's what's new: - -- Bug fix: Rollback updates that caused crash in Cyd 1.1.12 ([#532](https://github.com/lockdown-systems/cyd/pull/532)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.13). - - diff --git a/docs/blog/2025-07-07-cyd-1.1.15.md b/docs/blog/2025-07-07-cyd-1.1.15.md deleted file mode 100644 index 4c2ac16a..00000000 --- a/docs/blog/2025-07-07-cyd-1.1.15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -slug: cyd-1.1.15 -title: Cyd 1.1.15 released ---- - -**We're pleased to announce Cyd 1.1.15 is released.** This is mostly a user experience release. Here's what's new: - -- Add X dashboard, and overhaul user interface ([#538](https://github.com/lockdown-systems/cyd/pull/538)) -- Upgrade dependencies ([#534](https://github.com/lockdown-systems/cyd/pull/534), [#540](https://github.com/lockdown-systems/cyd/pull/540)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.15). - -![New Cyd user interface](./img/2025-07-07-cyd.png) - - diff --git a/docs/blog/2025-08-03-cyd-1.1.16.md b/docs/blog/2025-08-03-cyd-1.1.16.md deleted file mode 100644 index 4f6f6204..00000000 --- a/docs/blog/2025-08-03-cyd-1.1.16.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -slug: cyd-1.1.16 -title: Cyd 1.1.16 released ---- - -**We're pleased to announce Cyd 1.1.16 is released.** Here's what's new: - -- Ability to Migrate to Bluesky if you have already deleted your X account ([#512](https://github.com/lockdown-systems/cyd/pull/512), [#549](https://github.com/lockdown-systems/cyd/pull/549)) -- When signing into a Cyd account, make the checkbox opt-in to signing up for the Lockdown Systems newsletter instead of the Cyd newsletter ([#547](https://github.com/lockdown-systems/cyd/pull/547)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.16). - - diff --git a/docs/blog/2025-08-04-cyd-1.1.17.md b/docs/blog/2025-08-04-cyd-1.1.17.md deleted file mode 100644 index b2958f19..00000000 --- a/docs/blog/2025-08-04-cyd-1.1.17.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -slug: cyd-1.1.17 -title: Cyd 1.1.17 released ---- - -**We're pleased to announce Cyd 1.1.17 is released.** Here's what's new: - -- Bug fix: Ensure that importing an X unzipped archive doesn't delete the original folder ([#552](https://github.com/lockdown-systems/cyd/pull/552)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.17). - - diff --git a/docs/blog/2025-08-11-cyd.1.1.18.md b/docs/blog/2025-08-11-cyd.1.1.18.md deleted file mode 100644 index db007c91..00000000 --- a/docs/blog/2025-08-11-cyd.1.1.18.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -slug: cyd-1.1.18 -title: Cyd 1.1.18 released ---- - -**We're pleased to announce Cyd 1.1.18 is released.** Here's what's new: - -- Bug fix: Allow migrating tweets that have already been deleted ([#555](https://github.com/lockdown-systems/cyd/pull/555)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.18). - - diff --git a/docs/blog/2025-08-23-cyd.1.1.21.md b/docs/blog/2025-08-23-cyd.1.1.21.md deleted file mode 100644 index d20c6cc7..00000000 --- a/docs/blog/2025-08-23-cyd.1.1.21.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -slug: cyd-1.1.21 -title: Cyd 1.1.21 released ---- - -**We're pleased to announce Cyd 1.1.21 is released.** Here's what's new: - -- Bug fix: Resolve issues migrating media in Bluesky ([#560](https://github.com/lockdown-systems/cyd/pull/560)) -- Bug fix: Use existing user folder if it exists for exports ([#562](https://github.com/lockdown-systems/cyd/pull/562)) - -See the [release on GitHub](https://github.com/lockdown-systems/cyd/releases/tag/v1.1.21). - - diff --git a/docs/blog/authors.yml b/docs/blog/authors.yml deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/blog/img/2025-07-07-cyd.png b/docs/blog/img/2025-07-07-cyd.png deleted file mode 100644 index edad0244..00000000 Binary files a/docs/blog/img/2025-07-07-cyd.png and /dev/null differ diff --git a/docs/blog/tags.yml b/docs/blog/tags.yml deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/docs/contributing/_category_.json b/docs/docs/contributing/_category_.json deleted file mode 100644 index ccaf75c5..00000000 --- a/docs/docs/contributing/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Contributing to Cyd", - "position": 6, - "link": { - "type": "generated-index", - "description": "Get involved in the Cyd development community!" - } -} diff --git a/docs/docs/contributing/code-of-conduct.md b/docs/docs/contributing/code-of-conduct.md deleted file mode 100644 index b29df889..00000000 --- a/docs/docs/contributing/code-of-conduct.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -sidebar_position: 5 -title: Code of Conduct ---- - -# Contributor Covenant Code of Conduct - -## Our Pledge - -We as members, contributors, and leaders pledge to make participation in our -community a harassment-free experience for everyone, regardless of age, body -size, visible or invisible disability, ethnicity, sex characteristics, gender -identity and expression, level of experience, education, socio-economic status, -nationality, personal appearance, race, caste, color, religion, or sexual -identity and orientation. - -We pledge to act and interact in ways that contribute to an open, welcoming, -diverse, inclusive, and healthy community. - -## Our Standards - -Examples of behavior that contributes to a positive environment for our -community include: - -- Demonstrating empathy and kindness toward other people -- Being respectful of differing opinions, viewpoints, and experiences -- Giving and gracefully accepting constructive feedback -- Accepting responsibility and apologizing to those affected by our mistakes, - and learning from the experience -- Focusing on what is best not just for us as individuals, but for the overall - community - -Examples of unacceptable behavior include: - -- The use of sexualized language or imagery, and sexual attention or advances of - any kind -- Trolling, insulting or derogatory comments, and personal or political attacks -- Public or private harassment -- Publishing others' private information, such as a physical or email address, - without their explicit permission -- Other conduct which could reasonably be considered inappropriate in a - professional setting - -## Enforcement Responsibilities - -Community leaders are responsible for clarifying and enforcing our standards of -acceptable behavior and will take appropriate and fair corrective action in -response to any behavior that they deem inappropriate, threatening, offensive, -or harmful. - -Community leaders have the right and responsibility to remove, edit, or reject -comments, commits, code, wiki edits, issues, and other contributions that are -not aligned to this Code of Conduct, and will communicate reasons for moderation -decisions when appropriate. - -## Scope - -This Code of Conduct applies within all community spaces, and also applies when -an individual is officially representing the community in public spaces. -Examples of representing our community include using an official email address, -posting via an official social media account, or acting as an appointed -representative at an online or offline event. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported to the community leaders responsible for enforcement at -collective@lockdown.systems. -All complaints will be reviewed and investigated promptly and fairly. - -All community leaders are obligated to respect the privacy and security of the -reporter of any incident. - -## Enforcement Guidelines - -Community leaders will follow these Community Impact Guidelines in determining -the consequences for any action they deem in violation of this Code of Conduct: - -### 1. Correction - -**Community Impact**: Use of inappropriate language or other behavior deemed -unprofessional or unwelcome in the community. - -**Consequence**: A private, written warning from community leaders, providing -clarity around the nature of the violation and an explanation of why the -behavior was inappropriate. A public apology may be requested. - -### 2. Warning - -**Community Impact**: A violation through a single incident or series of -actions. - -**Consequence**: A warning with consequences for continued behavior. No -interaction with the people involved, including unsolicited interaction with -those enforcing the Code of Conduct, for a specified period of time. This -includes avoiding interactions in community spaces as well as external channels -like social media. Violating these terms may lead to a temporary or permanent -ban. - -### 3. Temporary Ban - -**Community Impact**: A serious violation of community standards, including -sustained inappropriate behavior. - -**Consequence**: A temporary ban from any sort of interaction or public -communication with the community for a specified period of time. No public or -private interaction with the people involved, including unsolicited interaction -with those enforcing the Code of Conduct, is allowed during this period. -Violating these terms may lead to a permanent ban. - -### 4. Permanent Ban - -**Community Impact**: Demonstrating a pattern of violation of community -standards, including sustained inappropriate behavior, harassment of an -individual, or aggression toward or disparagement of classes of individuals. - -**Consequence**: A permanent ban from any sort of public interaction within the -community. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 2.1, available at -[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. - -Community Impact Guidelines were inspired by -[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. - -For answers to common questions about this code of conduct, see the FAQ at -[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at -[https://www.contributor-covenant.org/translations][translations]. - -[homepage]: https://www.contributor-covenant.org -[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html -[Mozilla CoC]: https://github.com/mozilla/diversity -[FAQ]: https://www.contributor-covenant.org/faq -[translations]: https://www.contributor-covenant.org/translations diff --git a/docs/docs/contributing/contributor-license-agreement.md b/docs/docs/contributing/contributor-license-agreement.md deleted file mode 100644 index 1daff93a..00000000 --- a/docs/docs/contributing/contributor-license-agreement.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -sidebar_position: 6 ---- - -# Contributor License Agreement - -Thank you for your interest in contributing to Lockdown Systems LLC's Cyd ("We" or "Us"). - -The purpose of this contributor agreement ("Agreement") is to clarify and document the rights granted by contributors to Us. By Submitting any Contributions to Us, you have agreed to this Agreement. - -## 1\. Definitions - -**"You"** means the individual Copyright owner who Submits a Contribution to Us. - -**"Contribution"** means any original work of authorship, including any original modifications or additions to an existing work of authorship, Submitted by You to Us, in which You own the Copyright. - -**"Copyright"** means all rights protecting works of authorship, including copyright, moral and neighboring rights, as appropriate, for the full term of their existence. - -**"Material"** means the software or documentation made available by Us to third parties. When this Agreement covers more than one software project, the Material means the software or documentation to which the Contribution was Submitted. After You Submit the Contribution, it may be included in the Material. - -**"Submit"** means any act by which a Contribution is transferred to Us by You by means of tangible or intangible media, including but not limited to electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Us, but excluding any transfer that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution." - -**"Documentation"** means any non-software portion of a Contribution. - -## 2\. License grant - -### 2.1 Copyright license to Us - -Subject to the terms and conditions of this Agreement, You hereby grant to Us a worldwide, royalty-free, NON-exclusive, perpetual and irrevocable (except as stated in Section 8.2) license, with the right to transfer an unlimited number of non-exclusive licenses or to grant sublicenses to third parties, under the Copyright covering the Contribution to use the Contribution by all means, including, but not limited to: - -- publish the Contribution, -- modify the Contribution, -- prepare derivative works based upon or containing the Contribution and/or to combine the Contribution with other Materials, -- reproduce the Contribution in original or modified form, -- distribute, to make the Contribution available to the public, display and publicly perform the Contribution in original or modified form. - -### 2.2 Moral rights - -Moral Rights remain unaffected to the extent they are recognized and not waivable by applicable law. Notwithstanding, You may add your name to the attribution mechanism customary used in the Materials you Contribute to, such as the header of the source code files of Your Contribution, and We will respect this attribution when using Your Contribution. - -## 3\. Patents - -### 3.1 Patent license - -Subject to the terms and conditions of this Agreement You hereby grant to Us and to recipients of Materials distributed by Us a worldwide, royalty-free, non-exclusive, perpetual and irrevocable (except as stated in Section 3.2) patent license, with the right to transfer an unlimited number of non-exclusive licenses or to grant sublicenses to third parties, to make, have made, use, sell, offer for sale, import and otherwise transfer the Contribution and the Contribution in combination with any Material (and portions of such combination). This license applies to all patents owned or controlled by You, whether already acquired or hereafter acquired, that would be infringed by making, having made, using, selling, offering for sale, importing or otherwise transferring of Your Contribution(s) alone or by combination of Your Contribution(s) with any Material. - -### 3.2 Revocation of patent license - -You reserve the right to revoke the patent license stated in section 3.1 if We make any infringement claim that is targeted at your Contribution and not asserted for a Defensive Purpose. An assertion of claims of the Patents shall be considered for a "Defensive Purpose" if the claims are asserted against an entity that has filed, maintained, threatened, or voluntarily participated in a patent infringement lawsuit against Us or any of Our licensees. - -## 4. Disclaimer - -THE CONTRIBUTION IS PROVIDED "AS IS". MORE PARTICULARLY, ALL EXPRESS OR IMPLIED WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE EXPRESSLY DISCLAIMED BY YOU TO US AND BY US TO YOU. TO THE EXTENT THAT ANY SUCH WARRANTIES CANNOT BE DISCLAIMED, SUCH WARRANTY IS LIMITED IN DURATION AND EXTENT TO THE MINIMUM PERIOD AND EXTENT PERMITTED BY LAW. - -## 5. Consequential damage waiver - -TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL YOU OR WE BE LIABLE FOR ANY LOSS OF PROFITS, LOSS OF ANTICIPATED SAVINGS, LOSS OF DATA, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL AND EXEMPLARY DAMAGES ARISING OUT OF THIS AGREEMENT REGARDLESS OF THE LEGAL OR EQUITABLE THEORY (CONTRACT, TORT OR OTHERWISE) UPON WHICH THE CLAIM IS BASED. - -## 6. Approximation of disclaimer and damage waiver - -IF THE DISCLAIMER AND DAMAGE WAIVER MENTIONED IN SECTION 4. AND SECTION 5. CANNOT BE GIVEN LEGAL EFFECT UNDER APPLICABLE LOCAL LAW, REVIEWING COURTS SHALL APPLY LOCAL LAW THAT MOST CLOSELY APPROXIMATES AN ABSOLUTE WAIVER OF ALL CIVIL OR CONTRACTUAL LIABILITY IN CONNECTION WITH THE CONTRIBUTION. - -## 7. Term - -7.1 This Agreement shall come into effect upon Your acceptance of the terms and conditions. - -7.3 In the event of a termination of this Agreement Sections 4, 5, 6, 7 and 8 shall survive such termination and shall remain in full force thereafter. For the avoidance of doubt, Free and Open Source Software (sub)licenses that have already been granted for Contributions at the date of the termination shall remain in full force after the termination of this Agreement. - -## 8 Miscellaneous - -8.1 This Agreement and all disputes, claims, actions, suits or other proceedings arising out of this agreement or relating in any way to it shall be governed by the laws of United States excluding its private international law provisions. - -8.2 This Agreement sets out the entire agreement between You and Us for Your Contributions to Us and overrides all other agreements or understandings. - -8.3 In case of Your death, this agreement shall continue with Your heirs. In case of more than one heir, all heirs must exercise their rights through a commonly authorized person. - -8.4 If any provision of this Agreement is found void and unenforceable, such provision will be replaced to the extent possible with a provision that comes closest to the meaning of the original provision and that is enforceable. The terms and conditions set forth in this Agreement shall apply notwithstanding any failure of essential purpose of this Agreement or any limited remedy to the maximum extent possible under law. - -8.5 You agree to notify Us of any facts or circumstances of which you become aware that would make this Agreement inaccurate in any respect. diff --git a/docs/docs/contributing/contributors.md b/docs/docs/contributing/contributors.md deleted file mode 100644 index 2a873924..00000000 --- a/docs/docs/contributing/contributors.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -sidebar_position: 1 ---- - -# For Contributors - -Thanks for your interest in contributing to Cyd! The source code and issue tracker are hosted on [GitHub](https://github.com/lockdown-systems/cyd). - -## Code of Conduct - -All members of the Cyd community must agree to comply with our [Contributor Covenant Code of Conduct](./code-of-conduct). - -[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](./code-of-conduct) - -## Legal stuff - -- Lockdown Systems LLC owns the copyright for Cyd. -- Cyd is released under the [GNU General Public License v3](https://github.com/lockdown-systems/cyd/blob/main/LICENSE) license. -- By contributing code to the project, you have agreed to the version of our [Contributor License Agreement](./contributor-license-agreement) that was in the `main` branch of the `lockdown-systems/cyd` GitHub repository at the time of your contribution. - -## Bugs and feature requests - -After reviewing existing [open issues](https://github.com/lockdown-systems/cyd/issues), you can report new issues on GitHub. - -- [Report a bug](https://github.com/lockdown-systems/cyd/issues/new?template=bug_report.md) -- [Request a feature](https://github.com/lockdown-systems/cyd/issues/new?template=feature_request.md) - -## Security issues - -If you found a security bug, email security@lockdown.systems instead of reporting it on GitHub. - -## Writing code - -If you'd like to contribute code to Cyd, check out [Developing Cyd](https://github.com/lockdown-systems/cyd/blob/main/DEVELOPMENT.md) for instructions on setting up a local development environment. - -When you're ready to contribute code, open a pull request in the GitHub repository and one of the project maintainers will review it and possibly ask questions, request changes, reject it, or merge it into the project. diff --git a/docs/docs/contributing/developers.md b/docs/docs/contributing/developers.md deleted file mode 100644 index e0fea26b..00000000 --- a/docs/docs/contributing/developers.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -sidebar_position: 2 ---- - -# For Developers - -Cyd is a desktop app for Windows, Mac, and Linux written in Node.js. To run Cyd locally, you need is [Node.JS LTS](https://nodejs.org/en) for your operating systems. - -Install dependencies. - -```sh -npm install -``` - -Configure your Cyd environment to use "open" mode. This disables the server, which allows outside contributors to build features. - -```sh -npm run config-open -``` - -Run Cyd: - -```sh -npm start -``` - -To make it so devtools automatically opens, and so each embedded webview has a separate devtools window open, set the environment variables `CYD_DEV` to `1`: - -```sh -CYD_DEV=1 npm start -``` - -Run the tests: - -```sh -# Node.js tests -npm test -``` - -## Other server modes - -If you're an outside contributor you'll want to use "open" mode, as described above. - -If you're part of Lockdown Systems and you need to test functionality that uses the server, you need "local", "dev", or "prod" mode: - -```sh -# local mode: use a locally-hosted server at localhost:5000 -npm run config-local - -# dev mode: use the dev server at dev-api.cyd.social -npm run config-dev - -# prod mode: use the prod server at prod-api.cyd.social -npm run config-prod -``` diff --git a/docs/docs/contributing/img/devtools-console.png b/docs/docs/contributing/img/devtools-console.png deleted file mode 100644 index ed099d23..00000000 Binary files a/docs/docs/contributing/img/devtools-console.png and /dev/null differ diff --git a/docs/docs/contributing/img/toggle-devtools.png b/docs/docs/contributing/img/toggle-devtools.png deleted file mode 100644 index 4a514005..00000000 Binary files a/docs/docs/contributing/img/toggle-devtools.png and /dev/null differ diff --git a/docs/docs/contributing/testers.md b/docs/docs/contributing/testers.md deleted file mode 100644 index a53fec0e..00000000 --- a/docs/docs/contributing/testers.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -sidebar_position: 3 ---- - -# For Testers - -This page is intended for people who are running the dev version of Cyd to help test it. - -:::info -The dev version of Cyd uses a dev server which limits what email addresses are allowed to sign up for Cyd accounts. While anyone can download the dev version, you can only sign up for a test Premium plan if you've spoken a member of the Lockdown Systems Collective and we have agreed to let you test. -::: - -## Accessing Premium features while testing - -Once you're signed into your dev Cyd account, you can sign up for Premium using the following test credit card: - -- Card number: `4242 4242 4242 4242` -- Expiration date: anything in the future -- Security code: make it up -- Billing address: make it up - -## Download Cyd Dev - -### For Windows and Mac users - -Here's where to download the latest development release of Cyd: - -- macOS: https://dev-api.cyd.social/download?platform=macos -- Windows x64: https://dev-api.cyd.social/download?platform=windows -- Windows arm64: https://dev-api.cyd.social/download?platform=windows&arch=arm64 - -### For Linux users - -Here are instructions for .deb repos: - -```sh -# Import the signing key -curl -fsSL https://releases.lockdown.systems/signing-key.asc | sudo gpg --dearmor -o /usr/share/keyrings/lockdown-systems-archive-keyring.gpg - -# Add the repository -echo "deb [signed-by=/usr/share/keyrings/lockdown-systems-archive-keyring.gpg] https://releases.lockdown.systems/debian/ dev main" | sudo tee /etc/apt/sources.list.d/lockdown-systems.list - -# Install Cyd -sudo apt update -sudo apt install cyd -``` - -Here are instructions for .rpm repos: - -```sh -# Import the signing key -sudo rpm --import https://releases.lockdown.systems/signing-key.asc - -# Add the repository -sudo tee /etc/yum.repos.d/lockdown-systems.repo < Your information is being prepared for export. We’ll let you know when it’s ready. - -You should receive an email or text message from Facebook when your archive is ready to be saved. **Don't start deleting your Facebook posts using Cyd until after you have saved your archive.** diff --git a/docs/docs/facebook/img/dashboard.png b/docs/docs/facebook/img/dashboard.png deleted file mode 100644 index ea050b66..00000000 Binary files a/docs/docs/facebook/img/dashboard.png and /dev/null differ diff --git a/docs/docs/facebook/img/meta-export1.png b/docs/docs/facebook/img/meta-export1.png deleted file mode 100644 index 8f8d13ee..00000000 Binary files a/docs/docs/facebook/img/meta-export1.png and /dev/null differ diff --git a/docs/docs/facebook/img/meta-export2.png b/docs/docs/facebook/img/meta-export2.png deleted file mode 100644 index bafe6a53..00000000 Binary files a/docs/docs/facebook/img/meta-export2.png and /dev/null differ diff --git a/docs/docs/facebook/img/meta-export3.png b/docs/docs/facebook/img/meta-export3.png deleted file mode 100644 index 3ca33394..00000000 Binary files a/docs/docs/facebook/img/meta-export3.png and /dev/null differ diff --git a/docs/docs/facebook/img/sign-in.png b/docs/docs/facebook/img/sign-in.png deleted file mode 100644 index 97c38537..00000000 Binary files a/docs/docs/facebook/img/sign-in.png and /dev/null differ diff --git a/docs/docs/facebook/sign-in.md b/docs/docs/facebook/sign-in.md deleted file mode 100644 index 1c8ba489..00000000 --- a/docs/docs/facebook/sign-in.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -sidebar_position: 1 ---- - -:::warning[Beta Feature] - -These features are under beta testing right now and not available in the latest release. - -::: - -# Sign In to Facebook - -When you're on the new account screen in Cyd, choose the Facebook platform. You'll see the following screen: - -![Sign in to Facebook](./img/sign-in.png) - -Cyd (the bird) is at the top of the window giving you instructions, and the bottom part of the window is Cyd's embedded web browser. - -:::tip The Cyd server doesn't have any access to your password or your data -When you sign into your Facebook account within Cyd's embedded browser, it's the same as signing in using any other browser on your computer: **Your password is sent directly from your computer to Facebook's servers and it's encrypted using HTTPS. Cyd's server doesn't collect your password or have any access to your account.** Only the Cyd app running locally on your computer does. -::: - -Go ahead and sign in to your Facebook account using your username and password. - -After you sign in, Cyd will immediately start driving your browser to determine your username, your profile picture. When it's done, you'll end up at the Dashboard screen. Continue to [Dashboard](./dashboard). diff --git a/docs/docs/getting-started/_category_.json b/docs/docs/getting-started/_category_.json deleted file mode 100644 index b9460215..00000000 --- a/docs/docs/getting-started/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Getting Started", - "position": 2, - "link": { - "type": "generated-index", - "description": "Get started using Cyd." - } -} diff --git a/docs/docs/getting-started/download.md b/docs/docs/getting-started/download.md deleted file mode 100644 index f15a0aa9..00000000 --- a/docs/docs/getting-started/download.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -sidebar_position: 1 ---- - -# Download Cyd - -Cyd is desktop app available for Windows, Mac, and Linux. - -:::info -There are currently no plans to make a mobile verson of Cyd for Android or iPhone. Cyd works by controlling a web browser on your device, sometimes for several hours at a time without sleep, and this is notoriously hard to do on mobile operating systems. -::: - -## Cyd for Windows and Mac - -If you're using Windows or Mac, download Cyd from the main website: - -Download Cyd - -## Cyd for Linux - -Are you a Linux user? You're in luck! Cyd is 100% nerd compatible. - -There are Debian and RPM-based repositories for Cyd. And if that doesn't work for you, you can download a ZIP file (and its PGP signature) which will run on any distro. - -### Debian-based Distros - -Follow these instructions to add the Lockdown Systems repository and install Cyd on Debian-based distros, like Debian or Ubuntu. - -```sh -# Import the signing key -curl -fsSL https://releases.lockdown.systems/signing-key.asc | sudo gpg --dearmor -o /usr/share/keyrings/lockdown-systems-archive-keyring.gpg - -# Add the repository -echo "deb [signed-by=/usr/share/keyrings/lockdown-systems-archive-keyring.gpg] https://releases.lockdown.systems/debian/ prod main" | sudo tee /etc/apt/sources.list.d/lockdown-systems.list - -# Install Cyd -sudo apt update -sudo apt install cyd -``` - -### RPM-based Distros - -Follow these instructions to add the Lockdown Systems repository and install Cyd on RPM-based distros, like Fedora or CentOS. - -```sh -# Import the signing key -sudo rpm --import https://releases.lockdown.systems/signing-key.asc - -# Add the repository -sudo tee /etc/yum.repos.d/lockdown-systems.repo < Watching Cyd work was mesmerizing. My posts flashed by almost too fast to read; it was like watching my life pass before my eyes. It was fun to revisit my posts at warp speed, but painful, too, because each time something appeared on the screen, it was also being deleted. Photo from my wedding? Gone. Photo of my pet rat, Pepper? Gone. The process made me choke up a bit. - -### December 13, 2024 | Lifehacker - -[**This Free App Archives and Deletes Your Tweets**](https://lifehacker.com/tech/cyd-app-archives-and-deletes-tweets-for-free) by Justin Pot - -> Want to delete all of your tweets? Cyd, an application for Windows, macOS, and Linux, automates the process for you and even gives you an offline archive. Even better: This application runs entirely on your computer, meaning you don't need to trust a third party with access to your account in order to use it. - -### December 11, 2024: Freedom of the Press Foundation - -[**Clawing back your data on X**](https://freedom.press/digisec/blog/clawing-back-your-data-on-x/) by Dr. Martin Shelton - -> Just as journalists are making the jump to Bluesky, it’s become easier than ever to remove old posts on X. Our former board member Micah Lee created a new piece of software called Cyd, which helps you remove your data from X, with plans to extend this functionality to other social media sites like Facebook and Reddit. Instead of using the old developer tools, which have become prohibitively expensive in recent years, Cyd bypasses these limitations by essentially doing what any user would have to do manually in their browser: The software scrolls through the website and clicks the “delete” button, over and over again. - -### December 3, 2024: WIRED - -[**He Got Banned From X. Now He Wants to Help You Escape, Too**](https://www.wired.com/story/x-delete-posts-cyd-micah-lee/) ([archive link](https://archive.is/BwoxG)) by Andy Greenberg - -> When programmer Micah Lee was kicked off X for a post that offended Elon Musk, he didn’t look back. His new tool for saving and deleting your X posts can give you that same sweet release. - -### December 3, 2024: ZDNet - -[**I deleted thousands of tweets from X with this new tool - for free**](https://www.zdnet.com/article/i-deleted-thousands-of-tweets-from-x-with-this-new-tool-for-free/) by Jason Perlow - -> Now you can easily migrate from X with this powerful tool that deletes tweets, likes, and DMs, while backing up your data for a fresh start elsewhere. - ---- - -Ready to get started? [Download Cyd now](../getting-started/download). diff --git a/docs/docs/premium/_category_.json b/docs/docs/premium/_category_.json deleted file mode 100644 index 7e5d4613..00000000 --- a/docs/docs/premium/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Premium Plans", - "position": 5, - "link": { - "type": "generated-index", - "description": "How to manage your Premium plan." - } -} diff --git a/docs/docs/premium/img/dash-manage.png b/docs/docs/premium/img/dash-manage.png deleted file mode 100644 index d27927fc..00000000 Binary files a/docs/docs/premium/img/dash-manage.png and /dev/null differ diff --git a/docs/docs/premium/img/dash.png b/docs/docs/premium/img/dash.png deleted file mode 100644 index 444a7a15..00000000 Binary files a/docs/docs/premium/img/dash.png and /dev/null differ diff --git a/docs/docs/premium/intro.md b/docs/docs/premium/intro.md deleted file mode 100644 index 7af3d0e0..00000000 --- a/docs/docs/premium/intro.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -sidebar_position: 1 ---- - -# What are Premium Plans? - -Cyd is an [open source app](https://github.com/lockdown-systems/cyd) that allows you to delete all of your tweets for free. You can also save backups of your tweets, direct messages, likes, bookmarks, and retweets free of charge. [Download the Cyd app](https://cyd.social/download/) to get started. - -If you'd like to delete your likes, bookmarks and direct messages, to mass unfollow everyone, or to migrate your tweets to Bluesky before deleting them, you can do so with a Premium plan. We keep Cyd very affordable — about half the price of a cup of coffee each month. - -Check out the [Pricing page](https://cyd.social/pricing/) for more information. You can also [sign up for Premium](./sign-up) directly. - -If you're part of an organization and you think Premium accounts would be useful for your members, check out [Cyd for Teams](../cyd-for-teams/intro). - -Cyd is developed by the [Lockdown Systems Collective](https://lockdown.systems), a worker-owned cooperative. diff --git a/docs/docs/premium/manage.md b/docs/docs/premium/manage.md deleted file mode 100644 index 9ba3de2b..00000000 --- a/docs/docs/premium/manage.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -sidebar_position: 3 ---- - -# Manage Your Plan - -You can manage your Premium plan from the [Cyd Dashboard](https://dash.cyd.social/). - -After signing in with your email address, the dashboard will look like this: - -![Manage your Premium plan](./img/dash-manage.png) - -## Disable Automatic Renewal - -If you just want to use Cyd once and then not renew your Premium plan in a year, click **Don't Renew**. - -Your Premium plan will continue to be active until a year after you paid for it, and then you'll get downgraded to a free plan. You can always choose to enable automatic renewal again if you'd like. - -## Update Payment Method - -From the Cyd Dashboard, click the **Manage Payment Method** button to update your payment method. - -## Download Receipts - -If you scroll down to the bottom of the Cyd Dashboard, you can find all of your receipts available for download. diff --git a/docs/docs/premium/sign-up.md b/docs/docs/premium/sign-up.md deleted file mode 100644 index 895f68b1..00000000 --- a/docs/docs/premium/sign-up.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -sidebar_position: 2 ---- - -# Sign Up for Premium - -You can manage your Cyd account from the [Cyd Dashboard](https://dash.cyd.social/). - -To sign up, enter an email address. After verifying your email address, the dashboard will look like this: - -![Cyd Dashboard](./img/dash.png) - -The left column shows the features of the free plan, and the right column shows the price and the features of the Premium plan. When you're ready to upgrade to Premium, click **Upgrade Now**. - -On the next page, enter your payment info. And then that's it! You have a Premium account and you can use all of the Premium features in Cyd. - -Within the Cyd app, click the menu icon (`≡`) in the bottom left to sign into your Cyd account, or to manage your Cyd account if you're already signed in. diff --git a/docs/docs/tips/_category_.json b/docs/docs/tips/_category_.json deleted file mode 100644 index 9d3ec102..00000000 --- a/docs/docs/tips/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Tips", - "position": 7, - "link": { - "type": "generated-index", - "description": "Other tips related to using Cyd." - } -} diff --git a/docs/docs/tips/disable-sleep/_category_.json b/docs/docs/tips/disable-sleep/_category_.json deleted file mode 100644 index abf5d2d9..00000000 --- a/docs/docs/tips/disable-sleep/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Disable Sleep", - "position": 1, - "link": { - "type": "generated-index", - "description": "Learn how to disable sleep on your computer while Cyd works in the background." - } -} diff --git a/docs/docs/tips/disable-sleep/img/ubuntu-power-settings.png b/docs/docs/tips/disable-sleep/img/ubuntu-power-settings.png deleted file mode 100644 index 1ed325dd..00000000 Binary files a/docs/docs/tips/disable-sleep/img/ubuntu-power-settings.png and /dev/null differ diff --git a/docs/docs/tips/disable-sleep/img/windows-power-settings.png b/docs/docs/tips/disable-sleep/img/windows-power-settings.png deleted file mode 100644 index ab1d0d79..00000000 Binary files a/docs/docs/tips/disable-sleep/img/windows-power-settings.png and /dev/null differ diff --git a/docs/docs/tips/disable-sleep/intro.md b/docs/docs/tips/disable-sleep/intro.md deleted file mode 100644 index 1734a656..00000000 --- a/docs/docs/tips/disable-sleep/intro.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -sidebar_position: 1 ---- - -# Disabling Sleep - -Follow these instructions to disable sleep in your operating system: - -- [Disable sleep in Window](./windows.md) -- [Disable sleep in macOS](./mac) -- [Disable sleep in Linux](./linux) diff --git a/docs/docs/tips/disable-sleep/linux.md b/docs/docs/tips/disable-sleep/linux.md deleted file mode 100644 index c9ca6b29..00000000 --- a/docs/docs/tips/disable-sleep/linux.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -sidebar_position: 4 ---- - -# Disable Sleep in Linux - -Cyd runs directly on your computer. If you need to run it for hours or days (X has some annoying rate limits, so this possible), you should prevent your computer from going to sleep while it's working. - -Follow these instructions to temporarily prevent your computer from going to sleep in Ubuntu. (The steps should be similar for other Linux distributions too.) - -First, make sure your computer is plugged in while running a Cyd job. - -Second, make sure your computer does not automatically go to sleep after being idle when plugged in: - -- Open the **Settings** app -- Choose **Power** in the left panel -- Under **Power Saving**, click **Automatic Suspend** -- Make sure it's disabled under **Plugged In** - -![How to prevent your computer from automatically sleeping when idle](./img/ubuntu-power-settings.png) - -Now you can safely run Cyd for an extended period of time without. - -:::warning Keep your laptop lid open - -Note that your computer will still go to sleep if you close the laptop lid. So, don't close your laptop while you're doing a long-running Cyd session. - -::: diff --git a/docs/docs/tips/disable-sleep/mac.md b/docs/docs/tips/disable-sleep/mac.md deleted file mode 100644 index 89f515de..00000000 --- a/docs/docs/tips/disable-sleep/mac.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -sidebar_position: 3 ---- - -# Disable Sleep in Mac - -Cyd runs directly on your computer. If you need to run it for hours or days (X has some annoying rate limits, so this is possible), you should prevent your computer from going to sleep while it's working. - -The simplest way to prevent your Mac from automatically going to sleep is to use [Caffeine](https://www.caffeine-app.net/), a tiny free and open source app. - -Download and install Caffeine from https://www.caffeine-app.net/. When you run it, an empty coffee cup icon appears in the top-right of your menu bar. Click it (the icon changes to a cup full of hot coffee) and Caffeine will prevent your computer from sleeping. Click it again to disable it. - - - -Now you can safely run Cyd for an extended period of time. - -Remember to disable Caffeine when you don't need to use it. - -:::warning Keep your laptop lid open - -Note that your Mac will still go to sleep if you close the laptop lid. So, don't close your Mac while you're doing a long-running Cyd session. - -::: diff --git a/docs/docs/tips/disable-sleep/windows.md b/docs/docs/tips/disable-sleep/windows.md deleted file mode 100644 index 4a180ff1..00000000 --- a/docs/docs/tips/disable-sleep/windows.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -sidebar_position: 2 ---- - -# Disable Sleep in Windows - -Cyd runs directly on your computer. If you need to run it for hours or days (X has some annoying rate limits, so this is possible), you should prevent your computer from going to sleep while it's working. - -Follow these instructions to prevent your computer from going to sleep in Windows 11. - -First, make sure your computer is plugged in while running a Cyd job. - -Second, make sure your computer does not automatically go to sleep after being idle when plugged in: - -- Open the **Settings** app -- Click the **System** tab on the left panel -- Click **Power & battery** -- Expand **Screen and sleep** -- Make sure the settings include: - - When plugged in, put my device to sleep after: **Never** - -![How to prevent your computer from automatically sleeping when idle](./img/windows-power-settings.png) - -Now you can safely run Cyd for an extended period of time. - -:::warning Keep your laptop lid open - -Note that your computer will still go to sleep if you close the laptop lid. So, don't close your laptop while you're doing a long-running Cyd session. - -::: diff --git a/docs/docs/x/_category_.json b/docs/docs/x/_category_.json deleted file mode 100644 index 22de9553..00000000 --- a/docs/docs/x/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "X Platform", - "position": 3, - "link": { - "type": "generated-index", - "description": "Control your data on X using Cyd." - } -} diff --git a/docs/docs/x/archive-only.md b/docs/docs/x/archive-only.md deleted file mode 100644 index dd2dfa7c..00000000 --- a/docs/docs/x/archive-only.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -sidebar_position: 2 ---- - -# Archive Only Mode - -Archive Only Mode is a limited version of Cyd that lets you use the features that are possible without having access to sign into an X account. If you can still sign into your account, [continue to Dashboard](./dashboard.md) instead. - -![Archive Only Mode](./img/archive-only-mode.png) - -To continue, you'll need to have already [requested your X archive](https://help.x.com/en/managing-your-account/how-to-download-your-x-archive) from X, and then downloaded it, before deleting your X account. - -And in order to migrate your tweets to Bluesky, you'll also need a Cyd [premium plan](../premium/intro.md). - -Start by clicking Continue to **Import X Archive**. - -![Browse for an X archive to import](./img/archive-only-import.png) - -From here, browse for your X archive, and then click **Start Import**. - -![After importand an X archive](./img/archive-only-imported.png) - -After the import succeeds, click Go to Dashboard. When you're in Archive Only Mode, the dashboard is limited to only features that work without a signed in X account, which right now is just Migrate to Bluesky. - -![Dashboard in Archive Only Mode](./img/archive-only-dashboard.png) - -Click **Migrate to Bluesky** to migrate your tweets to Bluesky. For more information, see [Migrate to Bluesky](./migrate-bluesky.md). diff --git a/docs/docs/x/archive.md b/docs/docs/x/archive.md deleted file mode 100644 index f443950f..00000000 --- a/docs/docs/x/archive.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -sidebar_position: 4 ---- - -# Browse Your Local Archive - -When you build your local database for each X account, Cyd saves your data in your `Documents` folder on your computer. For example, if your X username is `cyd_social`, your Cyd data will be stored in `~/Documents/Cyd/X/cyd_social`. - -This folder includes `index.html` which contains an archive website that you can use to browse your data locally. For the nerds out there, it also contains `data.sqlite3` — the raw database, in SQLite3 format. - -If you ever need to find your local archive, you can open Cyd, select your X account, and click the **Browse Archive** and **Open Folder** buttons in the right sidebar. These buttons won't appear until you build your local database for the first time. - -## Cyd's Archive Website - -By clicking **Browse Archive**, or loading `index.html` in a web browser, you can browse the X data from your local database. For example, here's a screenshot of looking through tweets: - -![Browsing the local archive](./img/archive-browse.png) - -In the top-right of this website, there are navigation buttons for each type of data you have saved from your X accounts: tweets, retweets, likes, direct messages, and bookmarks. - -You can filter your data using the filter input field at the top. - -Each tweet contains the following information: - -- The tweet itself: the username, date, and content of the tweet, including media, as well as number of retweets and likes. -- The date you saved the tweet, and the date you deleted it (if you deleted it with Cyd). -- If you used Cyd to save an archived HTML version of the tweet, a link called **archived** to this local HTML file. -- A link called **original** to the original URL of the tweet, hosted at x.com. - -If you saved an archived HTML version of the tweet, here's what it looks like: - -![An HTML archived tweet](./img/archive-archived-tweet.png) - -Within your local archive, if you saved direct messages, you can browse and filter those as well. - -## Exploring the Files - -Here are the files and folders that Cyd creates when you build your local database: - -![The files Cyd saves for each X account](./img/archive-files.png) - -- `Archived Tweets`: If you saved archived HTML versions of your tweets, this folder contains a different HTML file for each tweet, named after the date of the tweet and its tweet ID. -- `assets`: Web assets used by your local archive website. This includes `assets/archive.js`, which contains a copy of your X data in JSON format. -- `data.sqlite3`: A copy of your X data, in SQLite3 format. -- `index.html`: Your local archive website. Open this in a web browser to browse your archive website. -- `Tweet Media`: Images and videos embedded in your tweets, retweets, likes, and bookmarks. diff --git a/docs/docs/x/dashboard.md b/docs/docs/x/dashboard.md deleted file mode 100644 index 67325e77..00000000 --- a/docs/docs/x/dashboard.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -sidebar_position: 3 ---- - -# Dashboard - -After signing in to your X account, you'll see that the main panel shows you a Dashboard that allows you to naviate between the different features: - -- [Local Database](./local-database/intro.md) -- [Delete from X](./delete) -- [Migrate to Bluesky](./migrate-bluesky) - -The main panel has a right sidebar that includes an estimate of the number of tweets and likes in your X account. While these numbers are often close to your actual number of tweets and likes, they are often inaccurate. - -![Dashboard](./img/dashboard.png) - -Cyd needs to know what's in your X account before it can delete your data from X or migrate it to Bluesky. Because of this, you must build a [Local Database](./local-database/intro.md) before anything else. diff --git a/docs/docs/x/delete.md b/docs/docs/x/delete.md deleted file mode 100644 index c763a58c..00000000 --- a/docs/docs/x/delete.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -sidebar_position: 5 ---- - -# Delete from X - -Once you've built your local database, you're ready to delete data from X! - -## Delete Options - -When you're ready to delete your data, you will see the following Delete Options screen. - -![Delete Options](./img/delete-options.png) - -Here's a description of each option: - -### Delete my tweets - -Delete the **tweets** in your account. If you don't check any checkboxes that modify it below, this will delete _all_ of your tweets. Optionally, you can choose which tweets you want to keep: - -- **older than \_\_ days**: You can choose to only delete older tweets. For example, if you want your X account to be ephemeral, you can choose to delete everything older 30 days. -- **unless they have at least \_\_ retweets**: You can see a retweets threshold, allowing you to keep tweets that went viral. -- **unless they have at least \_\_ likes**: You can see a likes threshold, allowing you to keep tweets that went viral. - -:::tip - -We recommend that you delete as many tweets as you feel comfortable with. - -::: - -### Delete my retweets - -Delete the **retweets** in your account. If you don't check any checkboxes that modify it below, this will delete _all_ of your retweets. Optionally, you can choose which retweets you want to keep: - -- **older than \_\_ days**: You can choose to only delete older retweets. - -:::tip - -We recommend that you delete all of your retweets. - -::: - -### Unfollow everyone - -Unfollow everyone. - -:::tip - -If you're abandoning your X account, we recommend that you do this. The list of people you used to follow on Twitter can be very revealing about you. - -::: - -### Delete my likes - -Delete all of the **likes** in your account. - -:::info Likes are private - -Likes are only visible to you on X (and, of course, to Elon Musk, X's employees, and anyone who can hack your X account). If you're primarily concerned about cleaning up OSINT crumbs about yourself, deleting your likes are optional. - -If you've been liking tweets for a very long time, there's a good chance that many of your old likes are [ghost likes](./tips/ghost-likes) and cannot be deleted. - -::: - -### Delete my bookmarks - -Delete all of the **bookmarks** in your account. - -Bookmarks are private in X. - -### Delete my direct messages - -Delete all of the **direct messages** in your account. - -This will only delete the direct messages from your account. The people you've sent messages to will still have copies of them unless they delete their direct messages too. - -:::tip - -Even though direct messages are private, and deleting them only deletes them for you, we still recommend that you delete them all. - -If you've been using X for years there's a good chance you have a lot of private messages in there. If your X account ever gets hacked, the hacker will have access to them all. The same is true if X ever decides to dig through your messages or share them with anyone. - -::: - -## Free and Premium Features - -Some of the Delete Options require a Premium plan - [learn more about Premium plans here](../premium/intro). And some of the options are free. If you're only using free options, there's no reason to create a Cyd account or sign up for a Premium plan. - -It's free to: - -- Delete _all_ of your tweets -- Delete _all_ of your retweets - -You need a Premium plan to: - -- Choose to keep tweets older than a specific date, or that don't meet a retweets or likes threshold -- Choose to keep retweets older than a specific date -- Unfollow everyone -- Delete your likes -- Delete your bookmarks -- Delete your direct messages - -## Review - -When you click **Continue to Review**, you have a chance to review your options before proceeding: - -![Review delete options](./img/delete-review.png) - -When you're ready, click **Start Deleting**. - -## Deleting - -Cyd is very fast at deleting tweets, retweets, likes, and bookmarks. You can watch your data flash before your eyes as Cyd deletes it from X. - -For these types of data, you can't watch Cyd work in the embedded browser because instead of clicking around, it relies on a JavaScript trick. Basically, what Cyd is doing is loading your profile in the embedded browser, opening developer tools, and running little bits of JavaScript over and over to delete your data. This is hundreds of times faster than scrolling around X's user interface and clicking buttons to delete your data. - -When you're unfollowing everyone and deleting direct messages, you can watch the embedded browser to see Cyd work. - -![Deleting data from X](./img/delete-deleting.png) - -:::warning Rate limits - -Cyd deletes your data as fast as it can, but X imposes limits on how fast this is. If you hit a rate limit, Cyd will wait for it to expire. Typically, you will need to wait less than 15 minutes before you can proceed. The second that X's rate limit expires, Cyd goes back to work delete your data. - -::: - -## Finished - -When Cyd is done deleting your data, it shows you a summary of what it deleted. Cyd also updates your local archive again to mark the date that you deleted each tweet, retweet, like, or bookmark. diff --git a/docs/docs/x/img/archive-archived-tweet.png b/docs/docs/x/img/archive-archived-tweet.png deleted file mode 100644 index 0d398891..00000000 Binary files a/docs/docs/x/img/archive-archived-tweet.png and /dev/null differ diff --git a/docs/docs/x/img/archive-browse.png b/docs/docs/x/img/archive-browse.png deleted file mode 100644 index 3d55339c..00000000 Binary files a/docs/docs/x/img/archive-browse.png and /dev/null differ diff --git a/docs/docs/x/img/archive-files.png b/docs/docs/x/img/archive-files.png deleted file mode 100644 index 9d6bb09e..00000000 Binary files a/docs/docs/x/img/archive-files.png and /dev/null differ diff --git a/docs/docs/x/img/archive-only-dashboard.png b/docs/docs/x/img/archive-only-dashboard.png deleted file mode 100644 index 91e074ba..00000000 Binary files a/docs/docs/x/img/archive-only-dashboard.png and /dev/null differ diff --git a/docs/docs/x/img/archive-only-import.png b/docs/docs/x/img/archive-only-import.png deleted file mode 100644 index 3384001a..00000000 Binary files a/docs/docs/x/img/archive-only-import.png and /dev/null differ diff --git a/docs/docs/x/img/archive-only-imported.png b/docs/docs/x/img/archive-only-imported.png deleted file mode 100644 index 1a478711..00000000 Binary files a/docs/docs/x/img/archive-only-imported.png and /dev/null differ diff --git a/docs/docs/x/img/archive-only-mode.png b/docs/docs/x/img/archive-only-mode.png deleted file mode 100644 index 11282ea8..00000000 Binary files a/docs/docs/x/img/archive-only-mode.png and /dev/null differ diff --git a/docs/docs/x/img/dashboard.png b/docs/docs/x/img/dashboard.png deleted file mode 100644 index 3a3037a2..00000000 Binary files a/docs/docs/x/img/dashboard.png and /dev/null differ diff --git a/docs/docs/x/img/delete-deleting.png b/docs/docs/x/img/delete-deleting.png deleted file mode 100644 index e1ae13fb..00000000 Binary files a/docs/docs/x/img/delete-deleting.png and /dev/null differ diff --git a/docs/docs/x/img/delete-options.png b/docs/docs/x/img/delete-options.png deleted file mode 100644 index 55d09bc4..00000000 Binary files a/docs/docs/x/img/delete-options.png and /dev/null differ diff --git a/docs/docs/x/img/delete-review.png b/docs/docs/x/img/delete-review.png deleted file mode 100644 index b651150f..00000000 Binary files a/docs/docs/x/img/delete-review.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-connect.png b/docs/docs/x/img/migrate-bluesky-connect.png deleted file mode 100644 index 5930ff31..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-connect.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-delete.png b/docs/docs/x/img/migrate-bluesky-delete.png deleted file mode 100644 index ab86b265..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-delete.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-finished.png b/docs/docs/x/img/migrate-bluesky-finished.png deleted file mode 100644 index d9fe481e..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-finished.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-migrating.png b/docs/docs/x/img/migrate-bluesky-migrating.png deleted file mode 100644 index 805083cb..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-migrating.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-oauth.png b/docs/docs/x/img/migrate-bluesky-oauth.png deleted file mode 100644 index be2ad5d7..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-oauth.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-pie-chart.png b/docs/docs/x/img/migrate-bluesky-pie-chart.png deleted file mode 100644 index 963a7394..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-pie-chart.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-timestamps1.png b/docs/docs/x/img/migrate-bluesky-timestamps1.png deleted file mode 100644 index ced6c195..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-timestamps1.png and /dev/null differ diff --git a/docs/docs/x/img/migrate-bluesky-timestamps2.png b/docs/docs/x/img/migrate-bluesky-timestamps2.png deleted file mode 100644 index 6160d4c6..00000000 Binary files a/docs/docs/x/img/migrate-bluesky-timestamps2.png and /dev/null differ diff --git a/docs/docs/x/img/sign-in.png b/docs/docs/x/img/sign-in.png deleted file mode 100644 index 04656b49..00000000 Binary files a/docs/docs/x/img/sign-in.png and /dev/null differ diff --git a/docs/docs/x/local-database/_category_.json b/docs/docs/x/local-database/_category_.json deleted file mode 100644 index 1c12a31f..00000000 --- a/docs/docs/x/local-database/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Local Database", - "position": 4, - "link": { - "type": "generated-index", - "description": "Build a local database of your X data." - } -} diff --git a/docs/docs/x/local-database/archive.md b/docs/docs/x/local-database/archive.md deleted file mode 100644 index 888c6301..00000000 --- a/docs/docs/x/local-database/archive.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -sidebar_position: 4 ---- - -# Save HTML Tweets, DMs, and/or Bookmarks - -If you built your database from scratch, you can skip this section. - -If you imported from an X archive though, you may wish to proceed with this section. X only gives you some of your data when you request an archive. Using this feature, Cyd can help you archive more of your data. - -## Archive Options - -If you choose to archive additional data, you will see the following Archive Options screen. - -![Archive options](./img/archive-options.png) - -Here is a description of each option: - -- **Save an HTML version of each tweet:** Make an HTML archive version of each of your tweets. This takes a long time, so only check this box if you care about this. -- **Save my bookmarks:** Scroll through your tweet timeline and save information about each bookmark. -- **Save my direct messages:** Scroll through your direct message conversations and save information about each conversation. Then, for each conversation, scroll through the message history and save information about each message. - -## Review - -When you click **Continue to Review**, you have a chance to review your options before proceeding: - -![Review archive options](./img/archive-review.png) - -When you're ready, click **Start Archiving**. - -:::tip Disable sleep - -Depending on how much data you have in your X account and how often X rate limits you, archiving additional data could take a long time. Make sure to disable sleep on your computer. There are guides for how to do this in the [Disable Sleep](../../tips/disable-sleep/intro) section. - -::: - -## Archiving Additional Data - -When you start archiving additional data, you can watch the embedded browser to see Cyd work. - -![Archiving additional data](./img/archive-saving.png) - -:::warning Rate limits - -Cyd saves your data as fast as it can, but X imposes limits on how fast this is. These are the same limits you would hit if you manually scrolled through your X account really, really fast. - -If you hit a rate limit, Cyd will wait for it to expire. Typically, you will need to wait less than 15 minutes before you can proceed. The second that X's rate limit expires, Cyd goes back to work saving your data. - -::: - -## Finished - -When Cyd is done archiving additional data, it shows you a summary of what it saved. diff --git a/docs/docs/x/local-database/build.md b/docs/docs/x/local-database/build.md deleted file mode 100644 index 518f22f0..00000000 --- a/docs/docs/x/local-database/build.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -sidebar_position: 2 ---- - -# Build Database from Scratch - -When you build your database from scratch, Cyd learns your tweet history the same way you would: By loading your profile to see your tweets, then scrolling down over and over until it gets to the bottom. If you don't have a lot of data in your X account, this is the best way to build your database. - -:::warning Limits to building a local database from scratch - -Unfortunately, X will only show you about between 2,000 and 3,000 of your most recent tweets and likes in this way. Even if you delete all of those, X simply won't show you any of your tweet or like history on your profile page anymore, even if you have thousands of older tweets. - -If your account has a lot of data, you should [import data from an X archive](./import) instead. - -::: - -## Build Options - -If you choose to build your database from scratch, you will see the following Build Options screen. - -![Build options](./img/build-options.png) - -Here is a description of each option: - -- **Save my tweets:** Scroll through your tweet timeline and save information about each tweet. - - **Save an HTML version of each tweet:** Make an HTML archive version of each of your tweets. This takes much longer, so only check this box if you care about this. -- **Save my likes:** Scroll through your tweet timeline and save information about each like. -- **Save my bookmarks:** Scroll through your tweet timeline and save information about each bookmark. -- **Save my direct messages:** Scroll through your direct message conversations and save information about each conversation. Then, for each conversation, scroll through the message history and save information about each message. - -## Review - -When you click **Continue to Review**, you have a chance to review your options before proceeding: - -![Review build options](./img/build-review.png) - -When you're ready, click **Build Database**. - -:::tip Disable sleep - -Depending on how much data you have in your X account and how often X rate limits you, building your database could take a long time. Make sure to disable sleep on your computer. There are guides for how to do this in the [Disable Sleep](../../tips/disable-sleep/intro) section. - -::: - -## Building Your Database - -When you start building your database, you can watch the embedded browser to see Cyd work. You'll see your tweets, likes, and other data scroll by. - -![Saving tweets, likes, and other data](./img/build-saving.png) - -As Cyd works, you can see what step it's currently on. In the screenshot above, it finished the "Logging in" step and it's working on the "Saving tweets" step. At any point you can click **Pause** to pause Cyd's work, or **Cancel** to cancel the work completely. - -:::warning Rate limits - -Cyd saves your data as fast as it can, but X imposes limits on how fast this is. These are the same limits you would hit if you manually scrolled through your X account really, really fast. - -If you hit a rate limit, Cyd will wait for it to expire. Typically, you will need to wait less than 15 minutes before you can proceed. The second that X's rate limit expires, Cyd goes back to work saving your data. - -::: - -:::info Clicking in the browser - -When Cyd is controlling the embedded browser on your behalf, clicking in it is disabled, as you might mess with what Cyd is trying to do. However, if you ever encounter a situation where Cyd is stuck and would continue if only you could click something, you can click the **Enable Clicking in Browser** to allow you to click. You can click **Disable Clicking in Browser** disables this again. - -::: - -## Finished - -When Cyd is done building your database, it shows you a summary of what it saved: - -![Finished saving data from X](./img/build-finished.png) - -In the right sidebar, you will also see the buttons **Browse Archive** and **Open Folder**. See [Browse Your Local Archive](../archive) for more information about these. - -There is also a summary of the amount of data in your local database. In the screenshot above, you can see the local database contains 317 saved tweets, 53 saved retweets, and 68 saved likes. So far, none of the tweets have been migrated to Bluesky. diff --git a/docs/docs/x/local-database/img/archive-options.png b/docs/docs/x/local-database/img/archive-options.png deleted file mode 100644 index 0ea3b491..00000000 Binary files a/docs/docs/x/local-database/img/archive-options.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/archive-review.png b/docs/docs/x/local-database/img/archive-review.png deleted file mode 100644 index 63c7940b..00000000 Binary files a/docs/docs/x/local-database/img/archive-review.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/archive-saving.png b/docs/docs/x/local-database/img/archive-saving.png deleted file mode 100644 index 5bf27b5b..00000000 Binary files a/docs/docs/x/local-database/img/archive-saving.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/build-finished.png b/docs/docs/x/local-database/img/build-finished.png deleted file mode 100644 index a40515b3..00000000 Binary files a/docs/docs/x/local-database/img/build-finished.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/build-options.png b/docs/docs/x/local-database/img/build-options.png deleted file mode 100644 index 425d71d7..00000000 Binary files a/docs/docs/x/local-database/img/build-options.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/build-review.png b/docs/docs/x/local-database/img/build-review.png deleted file mode 100644 index 7bf2dda2..00000000 Binary files a/docs/docs/x/local-database/img/build-review.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/build-saving.png b/docs/docs/x/local-database/img/build-saving.png deleted file mode 100644 index a52c533c..00000000 Binary files a/docs/docs/x/local-database/img/build-saving.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/import-browse.png b/docs/docs/x/local-database/img/import-browse.png deleted file mode 100644 index 624a5967..00000000 Binary files a/docs/docs/x/local-database/img/import-browse.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/import-finished.png b/docs/docs/x/local-database/img/import-finished.png deleted file mode 100644 index cdabd511..00000000 Binary files a/docs/docs/x/local-database/img/import-finished.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/import-instructions.png b/docs/docs/x/local-database/img/import-instructions.png deleted file mode 100644 index f353116b..00000000 Binary files a/docs/docs/x/local-database/img/import-instructions.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/local-database.png b/docs/docs/x/local-database/img/local-database.png deleted file mode 100644 index 325cd943..00000000 Binary files a/docs/docs/x/local-database/img/local-database.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/x-archive-email.png b/docs/docs/x/local-database/img/x-archive-email.png deleted file mode 100644 index ffa7dd82..00000000 Binary files a/docs/docs/x/local-database/img/x-archive-email.png and /dev/null differ diff --git a/docs/docs/x/local-database/img/x-download-archive.png b/docs/docs/x/local-database/img/x-download-archive.png deleted file mode 100644 index fcc6bb86..00000000 Binary files a/docs/docs/x/local-database/img/x-download-archive.png and /dev/null differ diff --git a/docs/docs/x/local-database/import.md b/docs/docs/x/local-database/import.md deleted file mode 100644 index 983ada40..00000000 --- a/docs/docs/x/local-database/import.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -sidebar_position: 3 ---- - -# Import X Archive - -If you have enough tweets or likes that building your archive from scratch won't work, you should import your X archive instead. X allows you to [request an archive of your data](https://help.x.com/en/managing-your-account/how-to-download-your-x-archive). This process takes time — typically at least a day, and sometimes longer. - -## Downloading Your Archive - -When you start downloading your archive, Cyd gives you the following instructions: - -![Instructions for downloading your X archive](./img/import-instructions.png) - -For your convenience, here are the instructions: - -- **Visit https://x.com/settings/download_your_data.** You might need to sign in to X first. -- **Prove your identity.** You'll probably need to type your X password. You might also need to get a verification code sent to your email, or do other things to verify your identity. -- **Click the "Request archive" button.** Be patient. After requesting your archive, you'll need to wait _at least a day_, and maybe longer. Sorry! -- **When it's ready, download the ZIP file from X.** After you've followed these steps and you have your archive ZIP file, click the button below. - -After requesting your archive, wait for an email from X. It should look something like this: - -![Email from X when your archive is ready](./img/x-archive-email.png) - -Click the **download** link, or load https://x.com/settings/download_your_data again, to download your archive. There should be a Download **archive button**, like this: - -![Downloading your X archive](./img/x-download-archive.png) - -When you download your archive, you will download a ZIP file. - -:::warning Are you using Safari? - -If you use Safari in macOS, when you download your archive ZIP file, your Mac will automatically unzip it. - -Cyd can import either an archive ZIP file, or an already-unzipped archive folder. - -::: - -## Importing Your Archive - -Once you've downloaded your X archive, click the **I've Downloaded My Archive from X** button in Cyd. You will see a screen like this: - -![Browse for your X archive](./img/import-browse.png) - -Browse for the X archive that you downloaded — either the ZIP file, or an unzipped folder will work. Then click **Start Import**. - -## Finished - -Cyd will validate that the archive actually appears to be an X archive and belongs to this X account. Assuming everything went will, Cyd will import the data from it into your local database. If something went wrong, Cyd will display an error message with more details. - -![Finished importing an X archive](./img/import-finished.png) - -In the right sidebar, you will also see the buttons **Browse Archive** and **Open Folder**. See [Browse Your Local Archive](../archive) for more information about these. - -The right sidebar also includes a summary of the amount of data in your local database. In the screenshot above, you can see the local database contains 76 saved tweets, and so far, none of the tweets have been migrated to Bluesky. You can see other metrics by scrolling down. - -:::tip The official X archive is missing some data - -X only gives you some of your data when you request an archive. Click **Backup More Data from X** if you'd like to download data that's missing from the official X archive. You'll be able to save your bookmarks, save HTML versions of your tweets, and download a robust backup of your direct messages from there. - -::: diff --git a/docs/docs/x/local-database/intro.md b/docs/docs/x/local-database/intro.md deleted file mode 100644 index 8eb38cff..00000000 --- a/docs/docs/x/local-database/intro.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -sidebar_position: 1 ---- - -# Introduction - -Cyd stores the data from your X account — your tweets, likes, bookmarks, direct messages, and so on — in a local database in the `Documents` folder on your computer. - -Before deleting your tweets, or migrating them to Bluesky, you need to create a local database of your data. When you instruct Cyd to delete tweets, it will reference this database. If you've built your database before, you can update it with the latest data from your X account by building it again. - -![Build a database of your X data](./img/local-database.png) - -There are three different ways of building your local database: - -- [Build Database from Scratch](./build): Cyd can scroll through your data to discover it. -- [Import X Archive](./import): You can import an official archive from X. -- [Save HTML Tweets, DMs, and/or Bookmarks](./archive): Cyd can scroll through your data to import types of data that aren't included in the official archive. diff --git a/docs/docs/x/migrate-bluesky.md b/docs/docs/x/migrate-bluesky.md deleted file mode 100644 index c48da294..00000000 --- a/docs/docs/x/migrate-bluesky.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -sidebar_position: 6 ---- - -# Migrate to Bluesky - -Once you've built your local database, Cyd can help you migrate your old tweets into Bluesky! - -:::info Cyd will only migrate tweets where it makes sense - -Cyd won't migrate retweets (that wouldn't make sense), and it won't migrate tweets that are replies to users on X (that also wouldn't make sense.) But it will migrate the rest of your own tweets, including replies to yourself. This means that your old Twitter threads will stay intact. - -Cyd will also migrate images and videos to Bluesky. - -::: - -:::tip Create a new Bluesky account for your archive of tweets - -While you can migrate your tweets into your main Bluesky account if you want, we recommend that you create a new Bluesky account just for your old archive. This way you can make it clear in this account's name and profile that it's an archive from X. - -::: - -## Connect a Bluesky Account - -When you click the **Migrate to Bluesky** button, you'll see the following welcome screen. - -![Connect a Bluesky account](./img/migrate-bluesky-connect.png) - -Type your Bluesky handle and click **Connect**. - -This will open a link in your web browser prompting you to login to your Bluesky account: - -![Signing into Bluesky](./img/migrate-bluesky-oauth.png) - -- Enter your password and click **Next**. -- On the next page, click **Accept**. -- You will get redirected to the Cyd website which will prompt you to open Cyd. Open it. - -If all went well, your Bluesky account will now be connected to your X account in Cyd. - -## Review your Data - -After you connect a Bluesky account, Cyd will show you a pie chart of all of your tweets including which ones are ready to migrate, which are already migrated, which are replies, and which are retweets. - -![Pie chart of your tweets](./img/migrate-bluesky-pie-chart.png) - -When you're ready to migrate your tweets, click **Continue to Review**. If all looks good, click **Start Migrating**. - -:::info Migrating to Bluesky is a Premium feature - -You need a [Premium plan](../premium/intro) to migrate your tweets to Bluesky. If you don't have one yet, when you click **Start Migrating** you will be prompted to sign up for one to continue. - -::: - -## Migrating Tweets to Bluesky - -You can watch your tweets quickly flash by on the screen as Cyd posts them to Bluesky. - -![Posting tweets to Bluesky](./img/migrate-bluesky-migrating.png) - -:::warning Rate limits - -Cyd migrates your tweets to Bluesky as fast as it can, but Bluesky imposes limits on how fast this is. You're allowed to post 1,666 times in an hour, and 11,666 times in a day. [Read more](https://docs.bsky.app/docs/advanced-guides/rate-limits) about Bluesky's rate limits. - -If you hit a rate limit, Cyd will wait for it to expire. Typically, you will need to wait about an hour before Cyd will automatically proceed. - -::: - -## Finished - -When Cyd is done migrating your tweets, it shows you a summary of what it just did: - -![Finished migrating tweets to Bluesky](./img/migrate-bluesky-finished.png) - -Cyd also updates your local archive again to include links to all of your migrated tweets on Bluesky. - -## Tips - -### Links, Media, Threads, Quotes, and Long Tweets - -When Cyd migrates your tweets to Bluesky, it does its best to keep everything the same: - -- **URL tracking is removed.** If your tweet includes links, those links are transferred over to Bluesky except without X's `t.co` URL tracking. The only exception is, if the URL you posted is exceptionally long and doesn't fit in a Bluesky post, Cyd will fallback to using the `t.co` link simply because it's shorter. -- **Media is preserved.** If you post images or videos, those images and videos are re-posted to Bluesky. The only exception is if the original media is too large to upload to Bluesky. Bluesky has a limit of about 1 MB for images and about 50 MB for videos. -- **Videos need time to process.** Videos on Bluesky might not work immediately after migrating them from tweets. If this happens, wait a few minutes for Bluesky to finish processing the video, and then they should play. -- **Threads are preserved.** If you posted a Twitter thread (which is just posting replies to your own tweets), they will get migrated as replies to your own posts in Bluesky. -- **Self-quote tweets are preserved.** If you quote tweet your own tweet, they will get migrated as quote posts of your original post in Bluesky. -- **Other quote tweets are not preserved.** If you quote tweet someone else, the link to the tweet you're quoting will get added to the end of your Bluesky post as a URL. -- **Mentions are not preserved.** If you mention X users, their usernames will be in the text of your Bluesky post, but you won't be able to click it to see who they are. -- **Long tweets get split into multiple Bluesky posts.** The length of a tweet on X and a post on Bluesky are calculated slightly differently, and they also have different maximum lengths. If, for whatever reason, a tweet you're trying to migrate does not fit on Bluesky, Cyd will automatically split it into two posts for you and post them both. - -### Your Bluesky Posts are Backdated - -After Cyd migrates a tweet to Bluesky, Bluesky keeps track of two separate timestamps: - -- When the post was created on Bluesky (the post timestamp) -- When the post was originally posted to Twitter/X (the archived timestamp) - -When you're viewing the posts in your Bluesky profile, it will show the post timestamp next to each post. However, if you click on a post, it will show both the post timestamp and the archive timestamp. For example, look at the following Bluesky post: - -![Both timestamps are displayed](./img/migrate-bluesky-timestamps1.png) - -Beneath the post text it says, "Archived from March 23, 2024 at 7:18 PM" — this is the archived timestamp. But under that it says, "March 4, 2025 at 1:34 PM" — this is the post timestamp. If you click on the archive timestamp, it shows more details: - -![Details about the archived timestamp](./img/migrate-bluesky-timestamps2.png) - -Because Bluesky can't confirm that the archived timestamp is authentic, it shows this warning. This is just how backdated posts in Bluesky work. - -### Getting Interrupted and Starting Over - -If, for whatever reason, you cancel migrating tweets in the middle, that's no problem. Just start migrating them again and they will continue where you left off. - -And if you want to delete all of your migrated tweets from Bluesky and start over, that's easy too. After you have migrated any tweets, a **Delete Migrated Tweets from Bluesky** button will appear. - -![Delete migrated tweets](./img/migrate-bluesky-delete.png) - -This will just delete the Bluesky posts that have been migrated from this specific X account. diff --git a/docs/docs/x/sign-in.md b/docs/docs/x/sign-in.md deleted file mode 100644 index 4dda2baa..00000000 --- a/docs/docs/x/sign-in.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -sidebar_position: 1 ---- - -# Sign In to X - -When you're on the new account screen in Cyd, choose the X platform. You'll see the following screen: - -![Sign in to X](./img/sign-in.png) - -:::tip Already deleted your X account? -If you've already deleted your account but you have an archive of your data, click **Import Archive Only**. This will bring you to [Archive Only Mode](./archive-only). -::: - -Cyd (the bird) is at the top of the window giving you instructions, and the bottom part of the window is Cyd's embedded web browser. - -:::tip The Cyd server doesn't have any access to your password or your data -When you sign into your X account within Cyd's embedded browser, it's the same as signing in using any other browser on your computer: **Your password is sent directly from your computer to X's servers and it's encrypted using HTTPS. Cyd's server doesn't collect your password or have any access to your account.** Only the Cyd app running locally on your computer does. -::: - -Go ahead and sign in to your X account using your username and password. - -:::info Do you use 2FA? -If you protect your X account with two-factor authentication, you'll need to enter the 2FA code you get to sign in here too. If you use a U2F security key (like a Yubikey), the screen will turn white when it's time for you to press the button. [Read more](./tips/u2f). -::: - -After you sign in, Cyd will immediately start driving your browser to determine your username, your profile picture, and an estimate of the number of tweets and likes in your X account. - -When it's done, you'll end up at the Dashboard screen. Continue to [Dashboard](./dashboard). diff --git a/docs/docs/x/tips/_category_.json b/docs/docs/x/tips/_category_.json deleted file mode 100644 index 832f9234..00000000 --- a/docs/docs/x/tips/_category_.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "label": "Tips", - "position": 7, - "link": { - "type": "generated-index", - "description": "Other tips related to X." - } -} diff --git a/docs/docs/x/tips/ghost-likes.md b/docs/docs/x/tips/ghost-likes.md deleted file mode 100644 index 78f10920..00000000 --- a/docs/docs/x/tips/ghost-likes.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -sidebar_position: 3 ---- - -# Ghost Likes - -One does not simply unlike old tweets. - -Did you just try deleting all of your likes with Cyd but notice that some of your likes are still showing up on X? X (and [Twitter before it](https://github.com/micahflee/semiphemeral?tab=readme-ov-file#deleting-old-likes)) works in mysterious ways. For reasons unknown, old likes may still appear in your like history, but they can't be unliked. Cyd refers to these as _ghost likes_. - -When you like a tweet on X, the heart icon turns red. When you unlike it, it turns grey again. If there are tweets listed in your likes but the heart icon is grey instead of red – meaning you can't unlike it – then this is a ghost like. - -The only way to delete a ghost like is to _like it again_, and then it lets you unlike it. This is very noisy because every time you re-like an old tweet, the user will get a notification. - -If you have many ghost likes, Cyd recommends you just don't worry about deleting them. Likes on X are private, so your ghost like history is not accessible to the public. diff --git a/docs/docs/x/tips/other-tweets.md b/docs/docs/x/tips/other-tweets.md deleted file mode 100644 index d9df9aa0..00000000 --- a/docs/docs/x/tips/other-tweets.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -sidebar_position: 2 ---- - -# Other Tweets - -As Cyd scrolls through your list of tweets or likes, X's website gives it a stream of tweets to save. Most of these tweets will be your actual tweets, retweets, or likes, but sometimes you get some other tweets too: - -- You might get other people's replies to your tweets -- You might someone's reply to a tweet that you liked -- If you liked a tweet in a thread, you might get the top tweet in that thread -- X works in mysterious ways, so there might be [ghost likes](./ghost-likes) in there too - -While the "other tweets" are saved in your local database, they do not appear in the HTML archive that Cyd creates for you. diff --git a/docs/docs/x/tips/u2f.md b/docs/docs/x/tips/u2f.md deleted file mode 100644 index f312e2fc..00000000 --- a/docs/docs/x/tips/u2f.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -sidebar_position: 1 ---- - -# U2F Security Keys - -If you use a U2F physical security key (like a Yubikey) to protect your X account, good for you! Security keys provide the best security to protect your online accounts. - -However, there is a known bug related to logging into your X account within Cyd's embedded browser with a security key. Here's how to work around it: - -- Plug in your U2F security key -- Add a new X account to Cyd -- Enter your username and click **Next** -- Enter your password and click **Log in** -- When the embedded browser shows a white screen, press the button on your security key to login -- The sign in process will finish successfully - -For some reason, when X is waiting for you to press the button on your security key it displays a blank white page. And due to an [upstream bug](https://github.com/electron/electron/issues/24573) in Electron, the framework that Cyd uses, Cyd isn't able to instruct you to press the button on your security key. - -Hopefully this will be fixed in a future version, but for now you can rely on this simple workaround. diff --git a/docs/docusaurus.config.ts b/docs/docusaurus.config.ts deleted file mode 100644 index fdd728e2..00000000 --- a/docs/docusaurus.config.ts +++ /dev/null @@ -1,167 +0,0 @@ -import { themes as prismThemes } from "prism-react-renderer"; -import type { Config } from "@docusaurus/types"; -import type * as Preset from "@docusaurus/preset-classic"; - -// This runs in Node.js - Don't use client-side code here (browser APIs, JSX...) - -const config: Config = { - title: "Cyd Docs", - tagline: - "Tech platforms can't be trusted. It's time to regain control of your data.", - favicon: "img/logo.png", - url: "https://docs.cyd.social", - baseUrl: "/", - onBrokenLinks: "throw", - onBrokenMarkdownLinks: "warn", - - // Even if you don't use internationalization, you can use this field to set - // useful metadata like html lang. For example, if your site is Chinese, you - // may want to replace "en" with "zh-Hans". - i18n: { - defaultLocale: "en", - locales: ["en"], - }, - - plugins: [ - [ - require.resolve("docusaurus-lunr-search"), - { - languages: ["en"], // language codes - }, - ], - ], - - presets: [ - [ - "classic", - { - docs: { - sidebarPath: "./sidebars.ts", - }, - blog: { - showReadingTime: true, - feedOptions: { - type: ["rss", "atom"], - xslt: true, - }, - // Useful options to enforce blogging best practices - onInlineTags: "warn", - onInlineAuthors: "warn", - onUntruncatedBlogPosts: "warn", - }, - theme: { - customCss: "./src/css/custom.css", - }, - } satisfies Preset.Options, - ], - ], - - themeConfig: { - // Replace with your project's social card - image: "img/social-card.png", - navbar: { - title: "Cyd Docs", - logo: { - alt: "Cyd Logo", - src: "img/logo.png", - }, - items: [ - { - type: "docSidebar", - sidebarId: "docsSidebar", - position: "left", - label: "Docs", - }, - { to: "/blog", label: "Development Blog", position: "left" }, - { - href: "https://cyd.social", - label: "Cyd Website", - position: "right", - }, - { - href: "https://github.com/lockdown-systems/cyd", - label: "Source Code", - position: "right", - }, - ], - }, - footer: { - style: "dark", - links: [ - { - title: "Navigation", - items: [ - { - label: "Docs", - to: "/docs/intro/", - }, - { - label: "Development Blog", - to: "/blog", - }, - { - label: "Cyd Website", - to: "https://cyd.social", - }, - ], - }, - { - title: "Community", - items: [ - { - label: "Bluesky", - href: "https://bsky.app/profile/cyd.social", - }, - { - label: "Mastodon", - href: "https://infosec.exchange/@cyd", - }, - { - label: "GitHub", - href: "https://github.com/lockdown-systems/cyd", - }, - { - label: "X", - href: "https://x.com/cyd_social", - }, - ], - }, - { - title: "More", - items: [ - { - label: "Newsletter", - href: "https://cyd.social/#/portal/signup", - }, - { - label: "Pricing", - href: "https://cyd.social/pricing/", - }, - { - label: "Download", - href: "https://cyd.social/download/", - }, - { - label: "Lockdown Systems Collective", - href: "https://lockdown.systems/", - }, - ], - }, - ], - copyright: `Copyright © ${new Date().getFullYear()} Lockdown Systems Collective`, - }, - prism: { - theme: prismThemes.github, - darkTheme: prismThemes.dracula, - }, - } satisfies Preset.ThemeConfig, - scripts: [ - { - src: "https://plausible.io/js/script.js", - defer: true, - "data-domain": "docs.cyd.social", - }, - ], -}; - -export default config; diff --git a/docs/package.json b/docs/package.json deleted file mode 100644 index c5ebe37a..00000000 --- a/docs/package.json +++ /dev/null @@ -1,48 +0,0 @@ -{ - "name": "docs", - "version": "0.0.0", - "private": true, - "scripts": { - "docusaurus": "docusaurus", - "start": "docusaurus start", - "build": "docusaurus build", - "swizzle": "docusaurus swizzle", - "deploy": "docusaurus deploy", - "clear": "docusaurus clear", - "serve": "docusaurus serve", - "write-translations": "docusaurus write-translations", - "write-heading-ids": "docusaurus write-heading-ids", - "typecheck": "tsc" - }, - "dependencies": { - "@docusaurus/core": "3.9.2", - "@docusaurus/preset-classic": "3.9.2", - "@mdx-js/react": "^3.1.1", - "clsx": "^2.1.1", - "docusaurus-lunr-search": "^3.6.0", - "prism-react-renderer": "^2.4.1", - "react": "^19.2.4", - "react-dom": "^19.2.4" - }, - "devDependencies": { - "@docusaurus/module-type-aliases": "3.9.2", - "@docusaurus/tsconfig": "3.9.2", - "@docusaurus/types": "3.9.2", - "typescript": "~5.9.3" - }, - "browserslist": { - "production": [ - ">0.5%", - "not dead", - "not op_mini all" - ], - "development": [ - "last 3 chrome version", - "last 3 firefox version", - "last 5 safari version" - ] - }, - "engines": { - "node": ">=18.0" - } -} diff --git a/docs/sidebars.ts b/docs/sidebars.ts deleted file mode 100644 index f5dd00f4..00000000 --- a/docs/sidebars.ts +++ /dev/null @@ -1,9 +0,0 @@ -import type { SidebarsConfig } from "@docusaurus/plugin-content-docs"; - -// This runs in Node.js - Don't use client-side code here (browser APIs, JSX...) - -const sidebars: SidebarsConfig = { - docsSidebar: [{ type: "autogenerated", dirName: "." }], -}; - -export default sidebars; diff --git a/docs/src/css/custom.css b/docs/src/css/custom.css deleted file mode 100644 index 4026c76d..00000000 --- a/docs/src/css/custom.css +++ /dev/null @@ -1,48 +0,0 @@ -/** - * Any CSS included here will be global. The classic template - * bundles Infima by default. Infima is a CSS framework designed to - * work well for content-centric websites. - */ - -:root { - --ifm-color-primary: #3b6ea3; - --ifm-color-primary-dark: #315b85; - --ifm-color-primary-darker: #26476a; - --ifm-color-primary-darkest: #1b324f; - --ifm-color-primary-light: #4986c9; - --ifm-color-primary-lighter: #5a9bd4; - --ifm-color-primary-lightest: #6faedc; - --ifm-code-font-size: 95%; - --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1); - --ifm-color-secondary: #e6a23c; - --ifm-footer-link-hover-color: #ffeed1; -} - -/* For readability concerns, you should choose a lighter palette in dark mode. */ -[data-theme="dark"] { - --ifm-color-primary: #a5c3e4; - --ifm-color-primary-dark: #8fb0d1; - --ifm-color-primary-darker: #7a9cbb; - --ifm-color-primary-darkest: #6687a5; - --ifm-color-primary-light: #b7d0e9; - --ifm-color-primary-lighter: #c8dced; - --ifm-color-primary-lightest: #d9e8f1; - --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.3); - --ifm-color-secondary: #ffc663; - --ifm-footer-link-hover-color: #ffeed1; -} - -video { - max-width: 100%; -} - -/* Make body text links have underlines, to help color blind users distinguish between links and non link texts */ - -.theme-doc-markdown a:link, -.theme-doc-markdown a:visited { - text-decoration: underline; -} - -.theme-doc-markdown a:hover { - text-decoration: none; -} diff --git a/docs/src/pages/index.tsx b/docs/src/pages/index.tsx deleted file mode 100644 index 2202e276..00000000 --- a/docs/src/pages/index.tsx +++ /dev/null @@ -1,7 +0,0 @@ -import React from "react"; -// eslint-disable-next-line import/no-unresolved -import { Redirect } from "@docusaurus/router"; - -export default function Home() { - return ; -} diff --git a/docs/static/.nojekyll b/docs/static/.nojekyll deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/static/CNAME b/docs/static/CNAME deleted file mode 100644 index f32c6fb3..00000000 --- a/docs/static/CNAME +++ /dev/null @@ -1 +0,0 @@ -docs.cyd.social \ No newline at end of file diff --git a/docs/static/img/logo.png b/docs/static/img/logo.png deleted file mode 100644 index a658218f..00000000 Binary files a/docs/static/img/logo.png and /dev/null differ diff --git a/docs/static/img/social-card.png b/docs/static/img/social-card.png deleted file mode 100644 index e6d0aa9b..00000000 Binary files a/docs/static/img/social-card.png and /dev/null differ diff --git a/docs/tsconfig.json b/docs/tsconfig.json deleted file mode 100644 index 920d7a65..00000000 --- a/docs/tsconfig.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - // This file is not used in compilation. It is here just for a nice editor experience. - "extends": "@docusaurus/tsconfig", - "compilerOptions": { - "baseUrl": "." - }, - "exclude": [".docusaurus", "build"] -}