5d5c0f4f43
* Work around Twidere and Tootdon bug Tootdon and Twidere construct @user@domain handles from mentions in toots based solely on the mention text and account URI's domain without performing any webfinger call or retrieving account info from the Mastodon server. As a result, when a remote user has WEB_DOMAIN ≠ LOCAL_DOMAIN, Twidere and Tootdon will construct the mention as @user@WEB_DOMAIN. Now, this will usually resolve to the correct account (since the recommended configuration is to have WEB_DOMAIN perform webfinger redirections to LOCAL_DOMAIN) when processing mentions, but won't do so when displaying them (as it does not go through the whole account resolution at that time). This change rewrites mentions to the resolved account, so that displaying the mentions will work. * Use lookbehind instead of non-capturing group in MENTION_RE Indeed, substitutions with the previous regexp would erroneously eat any preceding whitespace, which would lead to concatenated mentions in the previous commit. Note that users will “lose” up to one character space per mention for their toots, as that regexp is also used to remove the domain-part of mentioned users for character counting purposes, and it also erroneously removed the preceding character if it was a space. |
||
---|---|---|
app | ||
bin | ||
config | ||
db | ||
docs | ||
lib | ||
log | ||
nanobox | ||
public | ||
spec | ||
streaming | ||
vendor/assets | ||
.babelrc | ||
.buildpacks | ||
.codeclimate.yml | ||
.dockerignore | ||
.editorconfig | ||
.env.nanobox | ||
.env.production.sample | ||
.env.test | ||
.env.vagrant | ||
.eslintignore | ||
.eslintrc.yml | ||
.foreman | ||
.gitattributes | ||
.gitignore | ||
.haml-lint.yml | ||
.nanoignore | ||
.nvmrc | ||
.postcssrc.yml | ||
.profile | ||
.rspec | ||
.rubocop.yml | ||
.ruby-version | ||
.scss-lint.yml | ||
.slugignore | ||
.travis.yml | ||
.yarnclean | ||
Aptfile | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
Capfile | ||
Dockerfile | ||
Gemfile | ||
Gemfile.lock | ||
ISSUE_TEMPLATE.md | ||
LICENSE | ||
Procfile | ||
Procfile.dev | ||
README.md | ||
Rakefile | ||
Vagrantfile | ||
app.json | ||
boxfile.yml | ||
config.ru | ||
docker-compose.yml | ||
docker_entrypoint.sh | ||
jest.config.js | ||
package.json | ||
scalingo.json | ||
yarn.lock |
README.md
Mastodon is a free, open-source social network server based on open web protocols like ActivityPub and OStatus. The social focus of the project is a viable decentralized alternative to commercial social media silos that returns the control of the content distribution channels to the people. The technical focus of the project is a good user interface, a clean REST API for 3rd party apps and robust anti-abuse tools.
Click on the screenshot below to watch a demo of the UI:
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
- Frequently Asked Questions
- Use this tool to find Twitter friends on Mastodon
- API overview
- List of Mastodon instances
- List of apps
- List of sponsors
Features
No vendor lock-in: Fully interoperable with any conforming platform
It doesn't have to be Mastodon, whatever implements ActivityPub or OStatus is part of the social network!
Real-time timeline updates
See the updates of people you're following appear in real-time in the UI via WebSockets. There's a firehose view as well!
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 short videos
Upload and view images and WebM/MP4 videos attached to the updates. Videos with no audio track are treated like GIFs; normal videos are looped - like vines!
OAuth2 and a straightforward REST API
Mastodon acts as an OAuth2 provider so 3rd party apps can use the API
Fast response times
Mastodon tries to be as fast and responsive as possible, so all long-running tasks are delegated to background processing
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
The elephant friend illustrations are created by Dopatwo