hello friends! new(ish)!
Pleroma: Difference between revisions
>Dogjaw (Added more on why we switched from GNU Social) |
>Dogjaw m (Fixed vague terming) |
||
| Line 5: | Line 5: | ||
The project consists of several components: Pleroma is the server implementation, and comes bundled with '''PleromaFE''', the default frontend. Other useful utilities are also provided, such as an ActivityPub relay. | The project consists of several components: Pleroma is the server implementation, and comes bundled with '''PleromaFE''', the default frontend. Other useful utilities are also provided, such as an ActivityPub relay. | ||
Source: | Source: https://pleroma.social/ | ||
==Why are all the GNU Social instances running Pleroma now?== | ==Why are all the GNU Social instances running Pleroma now?== | ||
Simply put, GNU Social was a trainwreck. It was an inactive project written in cryptic PHP using a database library older than old grandpa Judd. Its default UI, while JS free, was akin to wading through waste deep mud in practice, and its only real alternative before Pleroma came around was Qvitter which was practically required for the instance to be usable. | Simply put, GNU Social was a trainwreck. It was an inactive project written in cryptic PHP using a database library older than old grandpa Judd. Its default UI, while JS free, was akin to wading through waste deep mud in practice, and its only real alternative before Pleroma came around was Qvitter which was practically required for the instance to be usable. GNU Social was known for being a gigantic pain in the admin's ass since it never worked quite right, especially its queue, which lead to instances "time travelling", where they sent and received posts so slow it was like they were in another point in time, shitposter.club was particularly notorious for this as many users of the age will tell you. Mastodon unintentionally(?) had a habit of effectively collectively DDoSing smaller instances which choked out some small ones, leading a few instances to block Mastodon entirely. Ostatus documentation was complicated and at times near non existent. People had been writing alternatives in Java, Clojure, and Common LISP for a long time, some tried to fork GNU Social to try and make it not suck. Ultimately, Pleroma was designed by people who didn't have as many brain cells as fingernails so naturally it started dominating easily. There is no reason to make a GNU Social instance at this point, just stick to Pleroma. | ||
==Why use this over Mastodon?== | ==Why use this over Mastodon?== | ||
| Line 16: | Line 16: | ||
Just like [[GNU_Social]] and Mastodon, Pleroma is part of the fediverse, meaning that anyone can host their own instance | Just like [[GNU_Social]] and Mastodon, Pleroma is part of the fediverse, meaning that anyone can host their own instance | ||
There are many instances up for public registration such as: | There are many instances up for public registration such as: | ||
*[https://pleroma.fuwafuwa.moe fuwafuwa] | *[https://pleroma.fuwafuwa.moe fuwafuwa] | ||
| Line 21: | Line 22: | ||
*[https://freesoftwareextremist.com free software extremist] | *[https://freesoftwareextremist.com free software extremist] | ||
[[Category:Internet]] | [[Category:Internet]] | ||
[[Category:Fediverse]] | [[Category:Fediverse]] | ||
[[Category:Culture]] | [[Category:Culture]] | ||
Revision as of 03:28, 3 July 2019
What is Pleroma?
Pleroma is a free, federated social networking server built on open protocols. It is compatible with GNU Social, Mastodon, and many other ActivityPub and OStatus implementations.
The project consists of several components: Pleroma is the server implementation, and comes bundled with PleromaFE, the default frontend. Other useful utilities are also provided, such as an ActivityPub relay.
Source: https://pleroma.social/
Why are all the GNU Social instances running Pleroma now?
Simply put, GNU Social was a trainwreck. It was an inactive project written in cryptic PHP using a database library older than old grandpa Judd. Its default UI, while JS free, was akin to wading through waste deep mud in practice, and its only real alternative before Pleroma came around was Qvitter which was practically required for the instance to be usable. GNU Social was known for being a gigantic pain in the admin's ass since it never worked quite right, especially its queue, which lead to instances "time travelling", where they sent and received posts so slow it was like they were in another point in time, shitposter.club was particularly notorious for this as many users of the age will tell you. Mastodon unintentionally(?) had a habit of effectively collectively DDoSing smaller instances which choked out some small ones, leading a few instances to block Mastodon entirely. Ostatus documentation was complicated and at times near non existent. People had been writing alternatives in Java, Clojure, and Common LISP for a long time, some tried to fork GNU Social to try and make it not suck. Ultimately, Pleroma was designed by people who didn't have as many brain cells as fingernails so naturally it started dominating easily. There is no reason to make a GNU Social instance at this point, just stick to Pleroma.
Why use this over Mastodon?
Pleroma is more lightweight, can be implemented easily on a server and it's very customizable allowing many themes to be made.
Where do I sign up?
Just like GNU_Social and Mastodon, Pleroma is part of the fediverse, meaning that anyone can host their own instance There are many instances up for public registration such as: