mirror of https://github.com/mastodon/mastodon
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
669fe9ee06
* Fix JavaScript interface with long IDs Somewhat predictably, the JS interface handled IDs as numbers, which in JS are IEEE double-precision floats. This loses some precision when working with numbers as large as those generated by the new ID scheme, so we instead handle them here as strings. This is relatively simple, and doesn't appear to have caused any problems, but should definitely be tested more thoroughly than the built-in tests. Several days of use appear to support this working properly. BREAKING CHANGE: The major(!) change here is that IDs are now returned as strings by the REST endpoints, rather than as integers. In practice, relatively few changes were required to make the existing JS UI work with this change, but it will likely hit API clients pretty hard: it's an entirely different type to consume. (The one API client I tested, Tusky, handles this with no problems, however.) Twitter ran into this issue when introducing Snowflake IDs, and decided to instead introduce an `id_str` field in JSON responses. I have opted to *not* do that, and instead force all IDs to 64-bit integers represented by strings in one go. (I believe Twitter exacerbated their problem by rolling out the changes three times: once for statuses, once for DMs, and once for user IDs, as well as by leaving an integer ID value in JSON. As they said, "If you’re using the `id` field with JSON in a Javascript-related language, there is a very high likelihood that the integers will be silently munged by Javascript interpreters. In most cases, this will result in behavior such as being unable to load or delete a specific direct message, because the ID you're sending to the API is different than the actual identifier associated with the message." [1]) However, given that this is a significant change for API users, alternatives or a transition time may be appropriate. 1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html * Additional fixes for stringified IDs in JSON These should be the last two. These were identified using eslint to try to identify any plain casts to JavaScript numbers. (Some such casts are legitimate, but these were not.) Adding the following to .eslintrc.yml will identify casts to numbers: ~~~ no-restricted-syntax: - warn - selector: UnaryExpression[operator='+'] > :not(Literal) message: Avoid the use of unary + - selector: CallExpression[callee.name='Number'] message: Casting with Number() may coerce string IDs to numbers ~~~ The remaining three casts appear legitimate: two casts to array indices, one in a server to turn an environment variable into a number. * Back out RelationshipsController Change This was made to make a test a bit less flakey, but has nothing to do with this branch. * Change internal streaming payloads to stringified IDs as well Per https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452 we need these changes to send deleted status IDs as strings, not integers. |
8 years ago | |
|---|---|---|
| app | 8 years ago | |
| bin | 8 years ago | |
| config | 8 years ago | |
| db | 8 years ago | |
| docs | 8 years ago | |
| lib | 8 years ago | |
| log | 9 years ago | |
| nanobox | 8 years ago | |
| public | 8 years ago | |
| spec | 8 years ago | |
| streaming | 8 years ago | |
| vendor/assets | 9 years ago | |
| .babelrc | 8 years ago | |
| .buildpacks | 8 years ago | |
| .codeclimate.yml | 8 years ago | |
| .dockerignore | 8 years ago | |
| .editorconfig | 8 years ago | |
| .env.nanobox | 8 years ago | |
| .env.production.sample | 8 years ago | |
| .env.test | 8 years ago | |
| .env.vagrant | 8 years ago | |
| .eslintignore | 8 years ago | |
| .eslintrc.yml | 8 years ago | |
| .foreman | 8 years ago | |
| .gitattributes | 8 years ago | |
| .gitignore | 8 years ago | |
| .haml-lint.yml | 8 years ago | |
| .nanoignore | 8 years ago | |
| .nvmrc | 8 years ago | |
| .postcssrc.yml | 8 years ago | |
| .profile | 8 years ago | |
| .rspec | 9 years ago | |
| .rubocop.yml | 8 years ago | |
| .ruby-version | 8 years ago | |
| .scss-lint.yml | 8 years ago | |
| .slugignore | 8 years ago | |
| .travis.yml | 8 years ago | |
| Aptfile | 8 years ago | |
| CODEOWNERS | 8 years ago | |
| CONTRIBUTING.md | 8 years ago | |
| Capfile | 8 years ago | |
| Dockerfile | 8 years ago | |
| Gemfile | 8 years ago | |
| Gemfile.lock | 8 years ago | |
| ISSUE_TEMPLATE.md | 8 years ago | |
| LICENSE | 9 years ago | |
| Procfile | 8 years ago | |
| Procfile.dev | 8 years ago | |
| README.md | 8 years ago | |
| Rakefile | 9 years ago | |
| Vagrantfile | 8 years ago | |
| app.json | 8 years ago | |
| boxfile.yml | 8 years ago | |
| config.ru | 9 years ago | |
| docker-compose.yml | 8 years ago | |
| docker_entrypoint.sh | 8 years ago | |
| package.json | 8 years ago | |
| scalingo.json | 8 years ago | |
| yarn.lock | 8 years ago | |
README.md
Mastodon is a free, open-source social network server. A decentralized solution to commercial platforms, it avoids the risks of a single company monopolizing your communication. Anyone can run Mastodon and participate in the social network seamlessly.
An alternative implementation of the GNU social project. Based on ActivityStreams, Webfinger, WebSub and Salmon.
Click on the screenshot to watch a demo of the UI:
The project focus is a clean REST API and a good user interface. Ruby on Rails is used for the back-end, while React.js and Redux are used for the dynamic front-end. A static front-end for public resources (profiles and statuses) is also provided.
If you would like, you can support the development of this project on Patreon. Alternatively, you can donate to this BTC address: 17j2g7vpgHhLuXhN4bueZFCvdxxieyRVWd
Resources
- List of Mastodon instances
- Use this tool to find Twitter friends on Mastodon
- API overview
- Frequently Asked Questions
- List of apps
Features
- Fully interoperable with GNU social and any OStatus platform Whatever implements Atom feeds, ActivityStreams, Salmon, WebSub and Webfinger is part of the network
- Real-time timeline updates See the updates of people you're following appear in real-time in the UI via WebSockets
- Federated thread resolving If someone you follow replies to a user unknown to the server, the server fetches the full thread so you can view it without leaving the UI
- Media attachments like images and WebM Upload and view images and WebM videos attached to the updates
- OAuth2 and a straightforward REST API Mastodon acts as an OAuth2 provider so 3rd party apps can use the API, which is RESTful and simple
- Background processing for long-running tasks Mastodon tries to be as fast and responsive as possible, so all long-running tasks that can be delegated to background processing, are
- Deployable via Docker You don't need to mess with dependencies and configuration if you want to try Mastodon, if you have Docker and Docker Compose the deployment is extremely easy
Development
Please follow the development guide from the documentation repository.
Deployment
There are guides in the documentation repository for deploying on various platforms.
Contributing
You can open issues for bugs you've found or features you think are missing. You can also submit pull requests to this repository. Here are the guidelines for code contributions
IRC channel: #mastodon on irc.freenode.net
Extra credits
