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-only URL and badge updates with no runtime or security impact.

Overview
Updates README.md so GitHub badges, release/download links, and related docs point at the bitsocialnet org instead of bitsocialhq (which 404 after the rename).

Also fixes the default s/all community list link to bitsocialnet/lists and the current file seedit-default-subscriptions.json, replacing the obsolete default-multisub.json path. Related links now target bitsocialnet/seedit, bitsocial-cli, 5chan, and the release.yml workflow path.

^{Reviewed by Cursor Bugbot for commit e67f468. 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 2, 2026 5:05pm

[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 16 minutes. 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: 19da68ad-30a5-410e-9934-c186e284bd60

📥 Commits

Reviewing files that changed from the base of the PR and between 712253d and e67f468.

📒 Files selected for processing (1)

• README.md

✨ 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.}