14,300
edits
Craftplacer (talk | contribs) (Initial draft of the Pleroma page) |
mNo edit summary |
||
(11 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{draft}} | {{draft}} | ||
[[File:Pleroma logo.png|thumb|''Pleroma logo'']][[File:Pleroma FE.png|thumb|''Screenshot of Pleroma-FE'' | <!-- Infobox uses Pagename. Remove commentations when inserted. | ||
{{Infobox Platform | |||
|name= | |||
|short_name= | |||
|abbreviation= | |||
|logo=Pleroma logo.png | |||
|logo_width=125px | |||
|color=fba457 | |||
|screenshot=Pleroma FE.png | |||
|screenshot_width=300px | |||
|screenshot_description=Screenshot of Pleroma-FE | |||
|website=[https://pleroma.social/ pleroma.social] | |||
|author= | |||
|developer= | |||
|release=22 February 2016<sup>[https://pleroma.social/blog/2019/02/22/pleroma-0.9.9/]</sup> | |||
|termination= | |||
|repository=[https://git.pleroma.social/pleroma git.pleroma.social] | |||
|language=[https://en.wikipedia.org/wiki/Elixir_(programming_language) Elixir] | |||
|license=AGPLv3 | |||
|documentation=[https://docs-develop.pleroma.social/ docs-develop.pleroma.social] | |||
|documentation_api=[https://api.pleroma.social/ api.pleroma.social] | |||
|instances= | |||
|instances_list=[https://pleroma.social/#featured-instances List] | |||
|forum= | |||
|donation= | |||
}} | |||
--> | |||
[[File:Pleroma logo.png|thumb|''Pleroma logo''|200x200px]][[File:Pleroma FE.png|thumb|''Screenshot of Pleroma-FE'' | |||
{| | {| | ||
|Official homepage | |Official homepage | ||
Line 28: | Line 59: | ||
|} | |} | ||
]] | ]] | ||
== Features == | |||
Pleroma's API is built upon Mastodon's and shares thereby many features, over time more and more unique features were added such as: | |||
* Reacting to posts with Unicode emoji | |||
* Making posts formatted as either HTML, BBCode or Markdown | |||
* Chatting with other users (Currently only compatible with other Pleroma instances) | |||
Unfortunately, Pleroma does not implement the entire Mastodon feature set so there are features that are unsupported such as: | |||
* User migrations | |||
** Pleroma does notify the follower if the user they follow has migrated and also follows them back if configured by the follower | |||
* Trends | |||
* Endorsements (= User's choices) | |||
* Identity proofs | |||
=== Removed limits === | |||
Different to Mastodon, Pleroma has lifted and increased many limits. These are now customizable by the instance administrators. Configurable limits are: | |||
* '''Profiles''' | |||
** Profile name length (100 characters by default) | |||
** Profile description/biography length (5000 characters by default) | |||
** Profile fields count (10 by default for local instance, 20 by default for remote instances) | |||
*** Name of a profile field can be up to 512 characters long by default | |||
*** Value of a profile field can be up to 2048 characters long by default | |||
** Pinned post count (5 by default) | |||
* '''Posts''' | |||
** Post content warning/subject + text length (5000 characters by default for local instance, 100k characters by default for remote instances until post gets dismissed) | |||
** Poll option count (20 options with 200 characters each by default) | |||
=== Message rewrite facilities (MRFs) === | |||
Pleroma has a feature called MRF which stands for Message Rewrite Facility, these are pieces of configurable code which can change the federation behavior of Pleroma instances. | |||
Which MRFs are enabled and enforced are generally publicly available under the instance's about page (<code>/about</code>) or over the API (<code>/api/v1/instance</code>, JSON property: <code>pleroma.metadata.federation</code>). Administrators can choose to omit this information. | |||
Further reading: [https://docs-develop.pleroma.social/backend/configuration/cheatsheet/#message-rewrite-facility Configuration Cheat Sheet - Pleroma Documentation # Message rewrite facility] | |||
==== Example of MRFs ==== | |||
* '''<code>mrf_steal_emoji</code>''' Saves received custom emojis from entered instances | |||
* '''<code>mrf_follow_bot</code>''' Automatically follows discovered remote users for helping the local instance to federate | |||
* '''<code>mrf_hellthread</code>''' Decreases prominence of hellthreads by unlisting them from the public timeline and not notifying mentioned users. | |||
* '''<code>mrf_hashtag</code>''' Marks posts as NSFW, unlists posts or rejects them completely based on what hashtags they contain. | |||
===== <code>mrf_simple</code> ===== | |||
This MRF allows instance administrators to reject activities and content from certain remote instances. Possible configurations are: | |||
* Rejecting of all reports, attachments, avatars, banners or federated deletions | |||
* Marking all attachments of entered instances as NSFW | |||
* Unlisting from the federated timeline (also known as The Whole Known Network) | |||
* Enforce all remote statuses to be followers-only | |||
{{Category |category=Pleroma}} {{Category |category=Advanced}} |