Network Administrator for Pawb.Social, furry, and a programmer
Mastodon: @crashdoom@furry.engineer
👋 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.
Should be fixed now, if folks could give it a try again!
As a test, have a picture of a sandwich!
US Mountain Time! (I put that on the other posts, but forgot here, my bad!)
Maintenance will typically be as needed, but I think I’ll need to make a new poll for capturing weekend / weekday preferences, I hadn’t thought about differentiating that.
Case 2 - Overnight (10 PM to 8 AM)
Case 2 - Evening (5 PM to 10 PM)
deleted by creator
Case 2 - Daytime (8 AM to 5 PM)
Case 2: Interactive Maintenance Poll
Case 1 - Daytime (8 AM to 5 PM)
Case 1 - Evening (5 PM to 10 PM)
Case 1 - Overnight (10 PM to 8 AM)
Case 1: Non-Interactive Maintenance Poll
Apologies for the delay. We’re working on this over the course of the weekend trying to restore the emojis.
So, the issue lays in that there’s no technical way to notify the remote user (someone not on furry.engineer or pawb.fun) that they’ve been suspended on our end, without sending a message to them directly. If we suspend them on our end, that doesn’t per se suspend them on their end and they wouldn’t know that their messages were no longer reaching our users; They would still be able to message other users on their instance, and users on other instances, but not to our users.
We’re apprehensive about notifying remote accounts specifically because we don’t often know the moderation practices of the remote instance (to know if they’ll deal with it, or if they have open-registration allowing anyone to join without approval) and it may encourage further abusive behavior through ban evasions (creating new accounts on that instance or elsewhere to continue messaging) from the user being made aware that we’re no longer receiving their messages.
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.