tell me… for what do you query? incorrect glibc version.
it’s december! and the second saturday of december at that, which means it’s 2022.12 time. let’s make like chris pratt and a-go
The headlines (yes, headlines, there’s a lot this month) are:
static fe… a feature that was more or less abandoned back in ye olde pleroma days, has receieved what can only be termed the face-lift of a lifetime
no longer is it basically unstyled and monotone, but it looks like this now:
check out otp.akkoma.dev for a live demo
you guys really want to follow hashtags, huh?
well now you can hooray hooray
hashtags will now have a little “+” icon in the top right, which if clicked, will cause you to follow the hashtag, and all public posts made to it will appear in your home timeline
this is 100% compatible with mastodon’s API, so apps like tusky and others that have this functionality will work just fine
akkoma already had the ability to set automatic post deletion server-wide, but never per-user. well, now it does!
simply navigate to your profile settings, and you can set the number of days after which to automatically delete your posts.
if you run this alongside the server-side MRF, whichever expiry comes first will be applied.
akkoma (as pleroma before it) gathers a lot of… nonsensical activities as time goes on. delete messages for posts that have been deleted, rejected follow requests, and so on
these is now an automatic task to remove these activities after 30 days (which provides ample time to act on them, if we needed to)
meaning you can install the site directly to your phone!
in practice this mostly means that it’ll go full-screen
As ever, see akkoma/CHANGELOG.md at develop - akkoma - Akkoma Development for a full list of changes
Is as ever
sudo systemctl stop akkoma git pull git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1) MIX_ENV=prod mix deps.get MIX_ENV=prod mix compile MIX_ENV=prod mix ecto.migrate MIX_ENV=prod mix pleroma.frontend install pleroma-fe --ref stable sudo systemctl start akkoma
!! there have been breaking changes in the backend since the release of 2022.12. if you are on the develop branch, use develop frontend refs.
but ideally you should be on the stable branch
./bin/pleroma_ctl update --branch stable ./bin/pleroma stop # or systemctl stop ./bin/pleroma_ctl migrate ./bin/pleroma daemon # or systemctl start ./bin/pleroma_ctl frontend install pleroma-fe --ref stable
See the changelog for any post-upgrade steps
oh my quite the list this month. i might have to stop doing these soon because the list is getting too long :aa:
thankies go out to:
- beefox for fixing a bunch of little annoying bugs in the frontend
- mergan for the above and also doing a bunch of triage on new issues on fe issues - it helps a lot!
- sfr for the entire static FE upgrade. how is your sanity still in tact after handling that stuff?
- darkkirb, Karl Prieb , astra akari for misc bugfixes on the FE
- r3g_5z for looking over all sorts of default configs and making the config closer to recommended settings
- ilja for bugfixes to MRFs, and for looking into some of the deep dark parts of the software
- norm again for doc fixes
there’s probably more, but there are so many of you now that collating is proving difficult
if you’re not here, thanks goes out to you as well!
and a couple of non-feature-related headlines for you lot
there will not be a 2023.01 release, since i will be off with family over christmas, and that’ll leave very little time to get things ready for january - hence, next release will be 2023.02. also, contributors: take some time off yourselves, you all deserve it
also, the akkoma network™ now stands at 360 nodes. which is absolutely insane.
also there’s a logo now. yes it looks like an amogus. this is partially to issue a challenge to you to replace it :evil:
have a nice end of the year everyone~
see you in the next