@freemo is there a plan to get any of the nice features such as Domain follow into the main Mastodon trunk repo so that you can more easily keep qoto.org at a recent software version. Mastodon is on version 4.0 while qoto lags on 3.3 I think.
🇳🇱
@peterwhisker The version doesnt really mean much anymore in that sense as we are a fork of mastodon. The versions dont track as I have brought in bug fixes and new features piece meal.
That said there are some new features we want to bring in from vanilla (and from other forks). I am talking with one of the other Mastodon coders out there and offering to pay him to do some of that work. In the past I have done it but I am very busy and have more money than time right now so I am doing it that way.
I spoke with him about it just recently so he is reviewing the code this weekend and then we are doing to negotiate and start doing some of that work.
It will probably be on a new major version ourselves in a week or so.
@freemo I did try to build the qoto fork from git.qoto but ran into issues as my Debian was too new. It looks like the git hasn't been updated for 2 years. Some clients like Hyperspace refuse to connect to Qoto but work with vanilla Mastodon. But qoto is a fork which makes a much more user-friendly experience. Thank you 😊
@peterwhisker The code on the server is more up to date than the repo, I just need to sync it (which i will do in the coming days/week as im working on it again).
The issue with compatability is that QOTO uses parts of the ActivityPub standard (the standard mastodon talks) that mastodon doesnt. For example a client that is mastodon-only might just assume a 500 word limit without querying the API to ask what the real limit is, even though the API call is part of the standard.
Long story short, the problem is with poorly built clients and not with how old QOTO is.
That said QOTO does need to pull in some new code from vanilla, so we are a bit behind, but not by that much.