#pleroma

13 posts · Last used 7d

Back to Timeline
Haruspex @haruspex@haruspex.shit.nexus · Aug 07, 2026
Will Pleroma have GROUPS before December 31, 2026? YES probability: 50.00% Closes: 2026-12-31T22:59:00.000000Z Created by @foolghool@shitposter.world https://haruspex.shit.nexus/m/802c87b9-2c16-475e-80b7-832bf3c1d43a #fediverse #pleroma #activitypub #prediction
0
1
0
Haruspex @haruspex@haruspex.shit.nexus · Aug 07, 2026
Replying to @haruspex@haruspex.shit.nexus
Market pulse: 50.00% → 89.87% (+39.87 points) Will Pleroma have GROUPS before December 31, 2026? https://haruspex.shit.nexus/m/802c87b9-2c16-475e-80b7-832bf3c1d43a #fediverse #pleroma #activitypub #prediction
0
1
0
fedicat @fedicat@pc.cafe · Jul 24, 2026
pulled back on a couple of features: viewing who liked and boosted a post by someone else (still can do it with your own posts), and the #pleroma feature to view another account's likes
0
0
0
IFTAS @iftas@mastodon.iftas.org · Jul 04, 2026
Let's see what platforms are responding to this year's Social Web survey, the annual questionnaire to see how #FediAdmin and #FediMod folks are doing: #Mastodon 54 #Matrix 17 #PeerTube 15 #WordPress 10 #Pixelfed 9 #ATProto platform 8 #Lemmy 8 #Pleroma 8 #Bookwyrm 6 #GoToSocial 5 #Bonfire 4 #Gancio 4 #Sharkey 4 #Writefreely 4 #Akkoma 3 #Friendica 3 #Ghost 3 #Mobilizon 3 #Nostr platform 3 #Funkwhale 2 #Hometown 2 #Misskey 2 #NodeBB 2 #Hubzilla 1
2
2
31
kirillDen @admin@pleroma.cheese-project.ru · Jun 11, 2026
Boosted by
welcome @welcome@friends.deko.cloud
Fediverse so weird Hover or focus to reveal Sensitive
This isn’t my first attempt at finding my place in the #Fediverse (I do have an account on #Hubzilla), but a lot still feels strange to me. It’s great that you can read posts from other social networks — but who to follow? To truly enter the Fediverse, you already need to know someone. And those "someones" are often very private people. So I’ll use this post as a beacon for others who are also trying to find someone alive here. Hope it works. If you like me love #movies, #TVseries, and #games congratulations, you’ve found a kindred spirit! #introduction #pleroma
0
0
1
Furosshu @frosch@edolas.world · May 21, 2026
I currently plan to migrate my instance to Debian 13 and it ships Elixir 1.18 and Erlang 27. The debian install guide says Elixir <17 and Erlang <26 soooo is that guide up to date? Has anyone already gotten it to run on Debian 13? #pleroma #pomela #hashtag
0
2
0
Droppie @MsDropbear42@blahaj.zone · May 08, 2026
Replying to @the5thColumnist@ottawa.place
@the5thColumnist@ottawa.place no, coz this is the fediverse, not the mastodoniverse... "toots" is Masto jargon, & irrelevant to we who use !=Masto, like #Sharkey, #Misskey, #Friendica, #Pleroma, #Diaspora, #Hubzilla, #Lemmy, #Akkoma, et al.
0
0
0
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social · Mar 24, 2025
In the year 2019, a scholarly paper misspelled the names of the Fediverse software — Mastodon, Pixelfed, and Pleroma As — Mastadon, PixelFred, Plemora This is the paper: "Peer-to-Peer based Social Networks: A Comprehensive Survey" https://arxiv.org/abs/2001.02611 @dansup@mastodon.social RE: https://mastodon.social/@dansup/103467590881549361 #DeSo #Fediverse #Mastadon #Mastodon #Pixelfed #PixelFred #Pleroma #Plemora
32
11
19
Elshara Silverheart @elshara@www.mediacy.net · Mar 06, 2026
I'm thinking about setting up and running my own #relay #server for #mastodon and #pleroma as there seems to be a decreasing number of these that take in core and key traffic as times goes by. Resulting in fewer initial servers being maintained long term. The #fediverse and #ActivityPub deserve some love.
0
1
0
Dawid @dawid@social.craftknight.com · Feb 18, 2026
Przez noc coś zeżarło moją instancję #pleroma . Ostateczną przyczyną było zapełnienie dysku, ale prawdziwy powód to skrypt "pleroma_ejabberd_auth.py" i autentykacja ejabberd (serwer xmpp). Skrypt widać ktoś próbował złamać hasło i wykonał miliony prób logowania, co spowodowało zapełnienie dysku, zanim logrotate obciął plik. Sam system działał jako tako, bo mam osobny mountpoint na /var jak przykazano, więc nie dostałem powiadomienie, że maszyna umarła - strona pleroma zwracała 200, ale po odpytaniu bazy danych się zawieszała. No nic, - wywaliłem plik loga, wywaliłem skrypt, przeskanowałem system tak na zaś i na razie zatrzymałem cały ejabberd - kiedyś to naprawie... PS. Ten wpis powinien brzmieć "how not to ejabberd" https://docs-develop.pleroma.social/backend/configuration/howto_ejabberd/
0
0
1

You've seen all posts