and ajax picks this as a wonderufl time to bring a living, screaming, angry SQUIRREL into my house

OK so here's my situation:

Arch pulled a pacman and upgraded me from postgresql 17 to postgresql 18 without prompting.

I dumbly ran this upgrade. OK fine, whatever they provide a shim in the form of posgresql-old-ugrade to get you a functional psotgres 17 environment until you can get your data exported/imported/whatever

I dumbly earlier enabled rum extensions, which apparently unlike posgresql-old-ugrade, there is no shim for. now whenever pleroma tries to access my database it complains that the rum extension can't be loaded and all queries fail. but I can see my all my old data in a data admin app on desktop.

when I try to disable rum exensions on thep leroma side (maybe it's just as simple as disabling it on the client side to make this work?) pleroma fails to start entirely. grrr probably some app-level thing idk.

am I truly hosed?

agh maybe I need to make a db dump. Or just eat the loss and start again.

I hosed my fucking instance again

the son of profit

this instance has cool emoji i need to get un-lazy and add more emoji to my instance

Good evening friends
Tonight I have a very sweet painting for you
9x12" oil painting, available now
Painting: https://www.etsy.com/listing/4390981053/
Store: https://www.etsy.com/shop/ScenesbyColleen

thank you for your hospitality @sam I think I'll keep this alt around

Get Mel on the phone, weve got a film to make and also cast me as the incel

@bajax test

@pwm rofl still can't make it work... So now pleroma just plain can't send ANYTHING to ANYONE, even if I completely disable the outbound proxy in its config (is it maybe keeping some config directive around in the database? fuck!) the proxy works normally testing it with curl, but my instance just throws a whole mess of this shit in its logs whenever I make a post:

holy shit what have I done?

Oh yeah, whatever became of that guy lol