bc55241c9a
* Fix: include alt text on the web lightbox image * a11y: Dont read the 'ALT' label * a11y: remove a wrapper behavior from posts This appears to have been introduced with the goal of creating meta actions on posts, but the behavior seems counter-productive. The accessibility inspector was unable to access individual items within the post and therefore most content was simply skipped. There may be a way to support the post actions without losing the ability to access the inner elements but I couldnt find it. -prf * a11y: apply alt tags to image wrappers so they get read * a11y: set Link accessibilityLabel to the title if none set * a11y: skip the SANDBOX watermark * a11y: improve post meta to not read UI and give a useful date * ally: improve post controls * a11y: add labels to lightbox images on mobile * fix types |
||
|---|---|---|
| .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!