I made a big postmortem on it over at https://pawb.social/post/15732006 :3

Really glad to hear! Please do let us know if you encounter any problems! (CC @natebluehooves@pawb.social :3)

I THINK I’VE SOLVED THE MYSTERY.

deleted by creator

deleted by creator

It’s also hard to pin down too…

deleted by creator

deleted by creator

Thank you for doing your part, and thank you for the cute sticker!! :3

Apologies, a configuration change resulted in the entire database being taken down affecting all of the services. This was a preemptive change for the upgrade we’re planning in the next few days, but clearly the existing DB was not prepared for it. https://t.me/pawbsocial/210

We’re looking to perform an upgrade this weekend to see if this alleviates the issue. There seem to be quite a lot of problems lately with emails and comments where they either don’t send, or return an unhelpful “this is a toast” prompt… which isn’t useful. We’ll have a follow-up announcement soon.

Yes! This is on our radar for the next service we set up! We’re working to migrate and stabilize the database before rolling out new services, but expect that’ll occur this weekend, so hopefully before the end of the year we should have some news on the Pixelfed front :3

Also got this myself… Seeming like the API is throwing errors despite working (…what?! >.>). Taking a look

Looking like I had an off-by-one error, it’s actually fixed in the beta for 0.19.6; Will look at upgrading to that to fix the issue, just reviewing the changes to make sure there’s nothing else major there.

👋 This isn’t just you! We’re aware of the issue and believe that the latest version of Lemmy should fix it; It seems to be an issue with the cookies being set with Strict instead of Lax causing it to not be sent by your browser.

Full announcement for maintenance to perform the upgrade: https://pawb.social/post/14286683

👋 This isn’t just you! We’re aware of the issue and believe that the latest version of Lemmy should fix it; It seems to be an issue with the cookies being set with Strict instead of Lax causing it to not be sent by your browser.

Full announcement for maintenance to perform the upgrade: https://pawb.social/post/14286683

👋 Apologies for the late reply, but we have been investigating and believe that this isn’t an isolated case.

It initially appears like our database is being overloaded due to the vast queries that Lemmy runs for generating statistics, so we’re trialing a hardware upgrade for a new database server backed by NVMe drives to hopefully improve the throughput.

We’re not quite ready to go live with it yet, we’re still ensuring everything is in working order and the database replicates successfully from the live copy to the new database reliably.

We’re hoping to have this in place before the end of September and we’ll post an announcement for maintenance when we go to do the switchover, as the change will also affect furry.engineer and pawb.fun.

Oops, that’s entirely valid and I should have explained. A limit means that the instance is effectively hidden from view on furry.engineer and pawb.fun. All of the content still exists and can be found if searching or interacting (like following a user on tenforward.social), but won’t appear on the public timelines and won’t be recommended to our users.

If someone from tenforward.social tries to mention someone on furry.engineer or pawb.fun, and they aren’t being followed by that person, the message may not be visible. Similarly, if someone from tenforward.social tries to follow a furry.engineer, or pawb.fun user, they’ll instead send a follow request that you’ll need to approve.

Yep!