Pixelfed Glitch

Releasing a hotfix because we found some early issues.
I took the time to add more possible formats to use for Stories.

https://github.com/pixelfed-glitch/pixelfed/releases/tag/v0.12.6-glitch.1.12.1

Happy New Year 2026 !
How about a new version to celebrate ?

https://github.com/pixelfed-glitch/pixelfed/releases/tag/v0.12.6-glitch.1.12.0

Mainly we updated from upstream, kept the docker setup updated and fixed some db related stuff.

Here, for people that like having the shiny last number :neocat_bongo_down:

Nothing to report here, only updating numbering to match upstream :neocat_pat:

If you are on v0.12.4-glitch.1.10.1 you basically have all the features from this one :neocat_blep:

https://github.com/pixelfed-glitch/pixelfed/releases/tag/v0.12.5-glitch.1.10.1

I said it and I will say it again : 0.12.4+glitch.1.10.1 contains all changes that was pushed to Pixelfed 0.12.5.

You can check the upstream diff here. It's just typos : https://github.com/pixelfed-glitch/pixelfed/compare/v0.12.4-glitch.1.10.1...pixelfed:pixelfed:v0.12.5

@innkeeper@gamerstavern.online haha Thanks for clarifying, I did get the joke 😄

Yay new upstream version !

Should we bump? We already shipped all of this yesterday in v0.12.4+glitch.1.10.1 🤔

https://github.com/pixelfed/pixelfed/releases/tag/v0.12.5

Feedback of the day :
"Thanks for understanding that versioning matters"

It's the little things

If you tried updating your docker image and did not get glitch.1.10.1 on latest or nightly, that's my bad, I just realized they were not pushed (only tagged version was).

My sincere apologies for the delay 🙇

Small version :neofox_uwu:

Thanks upstream for the AVIF support and resend email verification feature, among other things.

On our side :

Force recreating cache to avoid issues on updates and restart (make sure to use env files and variables and not cache as source of truth)
Updated trusted proxies for IPv6 private addresses with Apache (thanks @lily@homestead.social )

https://github.com/pixelfed-glitch/pixelfed/releases/tag/v0.12.4-glitch.1.10.1

PSA : I'm very busy and in a difficult situation lately, so I will gladly let anyone ready for it keep the project updated.

@EighthLayer@gamerstavern.online @rauschen@uff.rip That's a subject we can look into. Unfortunately, migration can be a very heavy operation, and it seems ActivityPub does not standardize it (there's alternative implementations though). In microblogging, it does not make much sense to consider transfering so many old posts that nobody reads. Picture might be a bit different, but considering a social account as cold storage space is not recommended either.

It has come to my mind that some Pixelfed Glitch instances may have decided to not be listed on fedi crawlers, and we are totally ok with it.

As some users are asking for Glitch-based instances, if you want them to find you and to help them do that, please tag me, or use the #PixelfedGlitch hashtag. I'll repost it here too

@mat@zelk.space Hi.
I can't really point you to my own instances, as I never intended them to be big hubs.
But you can find some of the instances on FediDB Pixelfed versions page (https://fedidb.org/software/pixelfed/versions), even though the info seems lacking lately (I can't seem to find pix.lgbt event though they are one of the biggest instances and on latest version).

Release day 🎉

- Prettier DMs (as a treat) ✨
- fix DMs with media not showing message
- Allowing backups for all supported database
- fix MariaDB native usage
- Added schema dump for faster db population
- Fix PostgreSQL & strict MySQL migrations scheme
- Add bzip2 to packages for instagram import and backup
- Fix remote images not loading

https://github.com/pixelfed-glitch/pixelfed/releases/tag/v0.12.4-glitch.1.10.0