![](https://programming.dev/pictrs/image/2d8cc2a9-ef50-4dcc-bb4c-a3208cfe352c.png)
![](https://beehaw.org/pictrs/image/1be75b15-2f18-429d-acf7-dcea8e512a4b.png)
18·
10 months agoWell you could, it’s just the usual pros and cons. How will you get momentum and community around the fork and how will you get a sufficient amount of instances to switch to a fork to have any impact. Not sure we’re at that point yet.
Edit; checked the PR you referenced and it’s just a stylistic issue apparently. While a bit pedantic imho, I think a fork reaction to this is overblown. It was merged later in another PR; https://github.com/LemmyNet/lemmy-ui/pull/2032
If it’s important that it keeps running then it should just be redundant and taking one node down for an update shouldn’t be an issue. I know this is wishful thinking for a lot of services but I refuse to be on call for something if the client can’t be bothered to make it redundant.