docs: fix wrong-org README links (bitsocialhq → bitsocialnet)

[tomcasaburi]

What

Corrects copy-paste org/repo errors in README.md. These links pointed at the old bitsocialhq org (since renamed to bitsocialnet), so they currently 404.

Changes

• Build Status, Release, and License badges → bitsocialnet/seedit
• Desktop & mobile "download link in the release page" → bitsocialnet/seedit
• GUI "latest release" link → bitsocialnet/seedit
• bitsocial-cli "latest release" link → bitsocialnet/bitsocial-cli
• 5chan link → bitsocialnet/5chan
• Build-scripts (release.yml) link → bitsocialnet/seedit
• Default community list link → bitsocialnet/lists, and updated the filename to the current seedit-default-subscriptions.json (the old default-multisub.json no longer exists in that repo)

All target repos and paths were verified to exist under bitsocialnet.

Scope: link/badge corrections only — no license changes (those were handled separately).

---

Note

Low Risk
Documentation and generated LLM context only; no runtime, auth, or dependency changes.

Overview
Updates README GitHub URLs from the retired bitsocialhq org to bitsocialnet so badges, release downloads, related repos (bitsocial-cli, 5chan), and the release.yml workflow link stop 404ing.

The s/all default-community doc now points at bitsocialnet/lists and seedit-default-subscriptions.json instead of the old default-multisub.json filename.

The embedded README section in public/llms-full.txt is updated to match so LLM context stays in sync with the readme.

^{Reviewed by Cursor Bugbot for commit 66df824. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
seedit	Ready	Preview, Comment	Jun 9, 2026 12:43pm

[coderabbitai]

Warning

Review limit reached

@tomcasaburi, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 626b3683-70dc-4a85-b693-29e54d086be7

📥 Commits

Reviewing files that changed from the base of the PR and between 061cd08 and 66df824.

📒 Files selected for processing (2)

• README.md
• public/llms-full.txt

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/readme-links

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[tomcasaburi]

Updated this PR on top of current master after #818 landed, resolved the README badge conflict by preserving the GPL-3.0-or-later badge while switching links to bitsocialnet, and regenerated public/llms-full.txt. Local verification passed: corepack yarn install, yarn llms:generate, yarn build, yarn lint, yarn type-check, and git diff --check. No actionable review comments remain.