👋 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!

Fixed: https://pawb.social/post/11661170

Should be fixed now, if folks could give it a try again!

As a test, have a picture of a sandwich!

Looks really, really well done! :D

Personally, I pronounce it “POB” because W’s are hard :p

Though, I totally didn’t realize when I chose the domain that Pawb also meant “everybody” in Welch as @match@pawb.social mentioned, but I think it makes it all the better :3

We’re using the Ansible playbook deployment, and I ended up giving the pictrs service a restart through docker (docker restart <id> and you can get the id by using docker ps).

It didn’t seem to be out of space or even offline, it just locked up and stopped responding to both new uploads and existing image requests.

Welcome!

This is an awesome write-up! I’ve run into the same issue trying to print QR and PDF417 barcodes on cards printed with the various Zebra ZXP printers I’ve got for testing with ConCat, but the same as you found, PDF417 appears to be far more reliable with the differing quality between each print.