309e1200d0
* Make a distinction between moderators and admins And rework the user list in the moderation interface, to be able to run the same action on many users, and to have a huge list of actions whithout loosing space. * Make user's role an enum + make it impossible for a moderator to escalate privileges With the help of diesel-derive-enum (maybe it could be used in other places too?) Also, moderators are still able to grant or revoke moderation rights to other people, but maybe only admins should be able to do it? * Cargo fmt * copy/pasting is bad * Remove diesel-derive-enum and use an integer instead It was not compatible with both Postgres and SQlite, because for one it generated a schema with the "User_role" type, but for the other it was "Text"… * Reset translations * Use an enum to avoid magic numbers + fix the tests * Reset translations * Fix down.sql |
||
|---|---|---|
| .circleci | ||
| .github/ISSUE_TEMPLATE | ||
| assets | ||
| migrations | ||
| plume-api | ||
| plume-cli | ||
| plume-common | ||
| plume-front | ||
| plume-macro | ||
| plume-models | ||
| po | ||
| script | ||
| src | ||
| templates | ||
| .codecov.yml | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CODE_OF_CONDUCT.md | ||
| crowdin.yml | ||
| diesel.toml | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| LICENSE | ||
| README.md | ||
| rust-toolchain | ||
Plume
Website — Documentation — Contribute — Instances list
Plume is a federated blogging engine, based on ActivityPub. It is written in Rust, with the Rocket framework, and Diesel to interact with the database. The front-end uses Ructe templates, WASM and SCSS.
Features
A lot of features are still missing, but what is already here should be quite stable. Current and planned features include:
- A blog-centric approach: you can create as much blogs as you want with your account, to keep your different publications separated.
- Media management: you can upload pictures to illustrate your articles, but also audio files if you host a podcast, and manage them all from Plume.
- Federation: Plume is part of a network of interconnected websites called the Fediverse. Each of these websites (often called instances) have their own rules and thematics, but they can all communicate with each other.
- Collaborative writing: invite other people to your blogs, and write articles together.
Get involved
If you want to have regular news about the project, the best place is probably our blog, or our Matrix room: #plume:disroot.org.
If you want to contribute more, a good first step is to read our contribution guides. We accept all kind of contribution:
- Back-end or front-end development
- Translations
- Documentation
- UI and/or UX design (we don't have a dedicated guide yet, but we can talk to see how we can work together!)
- Taking part in discussions
- Financial support
But this list is not exhaustive and if you want to contribute differently you are welcome too!
As we want the various spaces related to the project (GitHub, Matrix, Loomio, etc) to be as safe as possible for everyone, we adopted a code of conduct. Please read it and make sure you accept it before contributing.
Starting your own instance
We provide various way to install Plume: from source, with pre-built binaries, with Docker or with YunoHost. For detailed explanations, please refer to the documentation.