{"id":92614,"date":"2020-08-29T07:42:25","date_gmt":"2020-08-29T05:42:25","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/pleroma-2-1"},"modified":"2020-08-29T07:42:25","modified_gmt":"2020-08-29T05:42:25","slug":"pleroma-2-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/pleroma-2-1","title":{"rendered":"Pleroma 2.1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"


\n \"Pleroma<\/p>\n

<\/a><\/p>\n

<\/p>\n

The community of enthusiasts is excited to present the new version Pleroma<\/a> \u2014 a server for managing blogs with a markup language written in Elixir and using the standardized W3C protocol for federated networks ActivityPub<\/a>. This is the second most popular<\/a> server implementation.<\/p>\n

<\/noindex><\/noindex>
\n<\/p>\n

Comparing it to the closest competing project \u2014 Mastodon<\/a>, written in Ruby, operating within the same ActivityPub network, \u2014 Pleroma boasts a smaller size and fewer external dependencies, making it cheaper to maintain and usable on a wider range of configurations. At the same time, this is achieved without sacrificing functionality; in fact, Pleroma has far fewer limitations and more customizable options, whereas Mastodon often resorts to hardcoding. Moreover, Pleroma implements the Mastodon API, allowing the use of client applications from Mastodon and even its web interface, which comes alongside the Pleroma web interface.<\/p>\n

<\/noindex><\/p>\n

For users of Twitter and other proprietary centralized services, Pleroma may be appealing due to its customizable limit of 5000 characters per post<\/strong> by default, text formatting in Markdown<\/strong>\/BBCode\/HTML, \u0440\u0430\u0441\u0448\u0438\u0440\u0435\u043d\u043d\u044b\u043c \u043f\u0440\u043e\u0444\u0438\u043b\u0435\u043c, \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e\u043c \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441\u043e\u0432 \u2014 \u043a\u0430\u043a \u0432 \u043a\u043b\u0430\u0441\u0441\u0438\u0447\u0435\u0441\u043a\u043e\u043c \u0441\u0442\u0438\u043b\u0435, \u0442\u0430\u043a \u0438 Tweet Deck, custom emojis<\/strong> and stickers, a theme engine<\/strong> interface, and much more. An important feature is the nature of federated networks: you can choose a server with the rules and audience you prefer, or set up your own, fully controlling the data on it without depending on a single point of failure.<\/p>\n

<\/p>\n

It is worth noting the development of a Twitter-like interface for Pleroma \u2014 Soapbox<\/a>, characterized by simplicity, minimalism, and performance.<\/p>\n

<\/noindex>
\n<\/p>\n

The main feature of this release is the addition of a federated chat<\/a>, also operating on the ActivityPub protocol! It is available as direct messages, where, like in regular posts, attachments and custom emojis can be uploaded. Plans for a group chat version and E2E encryption<\/a>. This is not the first iteration of real-time messaging. A simple centralized chat was previously added, located in the corner of the interface, where any user from the server could write, and everyone else would see it. Integration with the XMPP server MongooseIM was also added, but without the ability to use XMPP directly from the Pleroma interface.<\/p>\n

<\/noindex>
\n<\/p>\n

At the same time as the chat feature in Pleroma was released, a brutalist and ultra-minimalist ActivityPub server has gained the same functionality Honk<\/a>, written in Go. While statuses in Honk are called 'honks', instant messages have been named 'chonks'. Honk-honk!<\/p>\n

<\/noindex><\/p>\n

And in the context of other changes:<\/p>\n