Conversation
Notices
-
Wall-of-text alert, pondering Fediverse software options.
Background: I moved from a community fediverse server (bsd.network) to my own a while back. This was because of a truly unfortunate defederation decision that split the group of FreeBSD people that I cared to interact with roughly in half. To this day, I vehemently disagree with the decision and feel that it was unjustified.
Anyway, In theory the switch was easy enough. But that lead to choices of software to run. And there's the rub. They all have major pros/cons. And some are truly Major cons to all of them.
In summary: whatever you pick, you picked the wrong one.
And on top of that, now you have to maintain it. The one I'm using appears to be on the path to abandonware (the primary developer has a new stack), and I'm looking to move, again.
The teaser is that it might be possible to keep my post and comment history if I tweak a bunch of database migration scripts and stay within the pleroma universe. Maybe. It's far from a given. Anyway, of those my least-terrible choices seem to be pleroma itself (which also seems to be on the downward trend for development) or perhaps Akkoma (which appears to be picking up rather than declining).
Going to one of the mastodon stacks is a "safe" choice, but I dislike mastodon for many reasons. And obviously a start-from-scratch.
There's many others too, but many of them tend to be focused on a particular niche that don't make them a good fit for me.
Ultimately, what I want is a simple text-centric twitter-like UI/UX with decent local search and reply-thread back-fill capabilities. What I'm using now has that.
So, my quandary. For a replacement, do I:
* suck it up and build a personal Mastodon in spite of my disklike of it? (at least that way I could know its not going away any time soon.)
* go back from a pleroma fork to pleroma-base?
* chase pleroma fork-of-the-month, presumably Akkoma?
* Another fedi stack entirely that still meets my needs, perhaps one that's not on my radar? (Suggestions?)
* Move to a server run by somebody else and ignore having been burned by bsd.network?
* Give up and perhaps go to bluesky or threads?
* Twitter (mentioned for comedy value only.)
I am really loathe to move to a server run by somebody else.
Akkoma has some really nice features that I like (but don't need), eg: automatic continuous language translation (eg: I'd see all the French/Spanish/Portugese/etc posts already translated for me). But the present forced-migration is still stinging and I really don't want to discover that I need to re-migrate again in a few years.
Thoughts? I feel like this is all compromises and tradeoffs. Is there an obvious solution I'm missing?
-
@feld @pete_wright @karinjiri >I'm actually investigating refactoring that so it can run as an independent service on another computer
I don't have preview proxy enabled, just regular mediaproxy, but just running an empty secondary instance with the same secret_key_base and then pointing mediaproxy's subdomain/path to that instance in nginx does the trick. Helps speed things up in setups like mine where I host the instance at home and proxy it to a remote server.
-
@pete_wright @karinjiri I'm currently focused on trying to make Pleroma run better on low resource servers. This has been going well.
I'm currently running on a 4-core 4GB RAM "server" of a Wyse 5070 thin client with an SSD. FreeBSD, but UFS because of lower resources. Just runs Nginx, Postgres, Pleroma.
last pid: 51675; load averages: 0.17, 0.31, 0.38 up 15+01:25:41 20:51:29
19 processes: 1 running, 18 sleeping
CPU: 1.9% user, 0.0% nice, 0.3% system, 0.0% interrupt, 97.8% idle
Mem: 908M Active, 1283M Inact, 571M Laundry, 765M Wired, 378M Buf, 288M Free
I'm connected to some large relays to pull as many posts in as possible and it continues to run great.
cheese_prod=# select count(*) from objects;
-[ RECORD 1 ]--
count | 1431463
So I'm pretty happy with it right now. I only wish it had a bit more power for MediaPreview Proxy so I can have images/video thumbnails enabled. I'm actually investigating refactoring that so it can run as an independent service on another computer. It wouldn't be hard then to simply start up another Pleroma Elixir instance in a limited mode that does nothing but the transcoding/thumbnailing. I could run it on my laptop or another server, and if they go offline it just reverts back to not doing the transcoding/thumbnailing work.
-
@karinjiri
I've been a happy on stock Pleroma for a few years now. I migrated off of bsd.network as well, but this was a while ago during one of the early twitter exodus waves happened.
It mostly just works for my personal fedi server. I run both the app and the psql database in a small bhyve VM without any issues. if i ever decide to move to a server someone else manages i'd probably kick the tires on bsd.cafe as they seem to be building a nice community.
-
@mint @pete_wright @karinjiri yeah that's one way to do it, but I'd like to be able to farm out that work automagically to connected nodes with BEAM's clustering.
I've got some plans to refactor the caching to be cluster-aware too so as long as you have S3 or an NFS mount for media and a network reachable database you can have a highly-available cluster running Pleroma across various devices, like a handful of RPis or something :)
Peter Wemm
feld
Pete Wright
All ０７６萌ＳＮＳ content and data are available under the