b33626c3c7
* remove trailing / on meta tags Meta tags are [void elements](https://html.spec.whatwg.org/multipage/syntax.html#void-elements) which means they are self closing, and do not require a closing tag, nor a trailing `/`. The trailing `/` is something that was required in XHTML but [is ignored in HTML](https://html.spec.whatwg.org/multipage/syntax.html#start-tags). Quoth the spec: > On void elements, [the trailing slash] does not mark the start tag as self-closing but instead is unnecessary and has no effect of any kind. For such void elements, it should be used only with caution — especially since, if directly preceded by an unquoted attribute value, it becomes part of the attribute value rather than being discarded by the parser. * remove trailing / on link tags |
||
|---|---|---|
| .bundle | ||
| .github | ||
| __e2e__ | ||
| __mocks__ | ||
| __tests__/lib | ||
| assets | ||
| bskyweb | ||
| docs | ||
| jest | ||
| patches | ||
| scripts | ||
| src | ||
| web | ||
| .buckconfig | ||
| .detoxrc.js | ||
| .env.example | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.js | ||
| .ruby-version | ||
| .watchmanconfig | ||
| Dockerfile | ||
| Gemfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| app.json | ||
| babel.config.js | ||
| eas.json | ||
| index.js | ||
| index.web.js | ||
| metro.config.js | ||
| package.json | ||
| tsconfig.check.json | ||
| tsconfig.json | ||
| webpack.config.js | ||
| yarn.lock | ||
README.md
Bluesky Social App
Welcome friends! This is the codebase for the Bluesky Social app. It serves as a resource to engineers building on the AT Protocol.
- Web: bsky.app
- iOS: App Store
- Android: Play Store
Links:
Rules & guidelines
ℹ️ While we do accept contributions, we prioritize high quality issues and pull requests. Adhering to the below guidelines will ensure a more timely review.
Rules:
- We may not respond to your issue or PR.
- We may close an issue or PR without much feedback.
- We may lock discussions or contributions if our attention is getting DDOSed.
- We're not going to provide support for build issues.
Guidelines:
- Check for existing issues before filing a new one please.
- Open an issue and give some time for discussion before submitting a PR.
- Stay away from PRs like...
- Changing "Post" to "Skeet."
- Refactoring the codebase, eg to replace mobx with redux or something.
- Adding entirely new features without prior discussion.
Remember, we serve a wide community of users. Our day to day involves us constantly asking "which top priority is our top priority." If you submit well-written PRs that solve problems concisely, that's an awesome contribution. Otherwise, as much as we'd love to accept your ideas and contributions, we really don't have the bandwidth. That's what forking is for!
Forking guidelines
You have our blessing 🪄✨ to fork this application! However, it's very important to be clear to users when you're giving them a fork.
Please be sure to:
- Change all branding in the repository and UI to clearly differentiate from Bluesky.
- Change any support links (feedback, email, terms of service, etc) to your own systems.
- Replace any analytics or error-collection systems with your own so we don't get super confused.
Security disclosures
If you discover any security issues, please send an email to security@bsky.app. The email is automatically CCed to the entire team and we'll respond promptly.
License (MIT)
See ./LICENSE for the full license.
P.S.
We ❤️ you and all of the ways you support us. Thank you for making Bluesky a great place!