@hfaust Why a Pleroma fork? Something wrong?
and somewhere around this time fucking Mastodon of all things got the ability to edit posts like I've been asking for since I started on fedi causing me to rage out
fucking MASTODON gets an actually good feature
what is the world coming to I swear to god
@shebang @waltercool @hfaust We Mastochads won. Everyone should go back to using it.
@waltercool @shebang @hfaust Well, the instance that I'm on is technically using a Mastodon fork.
@xianc78 @shebang @hfaust Isn’t that just a fork made by @matrix for his/her own instance?
I can clearly see himself/herself as the only maintainer and code supplier.
This kind of acts have only two options:
You keep an old version of Mastodon for your own needs.
Your job will be basically merging all Mastodon code into your own fork.
So no real gain.
@waltercool
Yeah, that's essentially what I'm doing. I forked a fork mastodon.host used and I'm basically just maintaining it by merging upstream Mastodon and adding a few tiny tweaks.
@shebang @xianc78 @hfaust
@matrix @shebang @xianc78 @hfaust Aren’t you afraid of being very de-synchronized with main branch?
That’s not an easy job.
But uncool for Mastodon for keeping so many settings hardcoded. Pleroma does a better job on that.
In other hand, Pleroma single-thread architecture is a waste of CPU resources, specially about queue management. Sidekiq is far more powerful in any sense.
@waltercool
Yes I'm, but so far I'm managing it without issues. For that reason I don't make any big fundamental changes that could become an issue when merging.
@shebang @xianc78 @hfaust
