For the past 3 or so days, at least once per day, I will load pawb.social and discover that I'm not logged in anymore. I had the same problem for several days about 3 weeks ago

Page load times have been very slow for some communities, especially those hosted on other instances, and especially over the past few days. Not sure if this was related to the maintenance over the weekend. Here's some quick examples from a sample of 3 communities. I'm listing them in the order that I visited them (I'm not sure if images et. al. are cached across instances, but just in case):

• https://pawb.social/c/196@lemmy.blahaj.zone - Load: 6.8s
• https://lemmy.blahaj.zone/c/196 - Load: 655ms
• https://lemmy.world/c/196@lemmy.blahaj.zone - Load: 705ms

• https://lemmy.world/c/technology - Load: 705ms
• https://pawb.social/c/technology@lemmy.world - Load: 17.58ms
• https://yiffit.net/c/technology@lemmy.world - Load: 557ms

• https://yiffit.net/c/memes - Load: 557ms
• https://lemmy.world/c/memes@yiffit.net - Load: 699ms
• https://pawb.social/c/memes@yiffit.net - Load: 587ms

Of these three tests, we performed fine on one, but the other two were markedly slower. Refreshing the home feed (settings: Subscribed, New) has also been very slow (with load times in excess of 5 seconds being very common).

Is anyone else seeing this, or is this a 'Me' problem?

(I swear I don't only complain.) :D

We can't set an avatar for ourselves! It gives this error:

{"data":{"msg":"exiftool Failed with signal: 13 (SIGPIPE)","files":null},"state":"success"}

Update: This applies to all images, not just account pictures. Also the community icon on the right is broken, too!

-- Frost

Profile images don't appear to be working correctly. I can't see any when viewing profiles, I can't change mine, and when I try to view the image I get a sled-error "IO error: Os { code: 5, kind: Uncategorized, message: "I/O error" }"

Edit: Fixed by Crashdoom. Thank you.

Hey, I recently received a 14-day ban from lemmy.ml for this comment:

While I suppose it wasn't the nicest thing I could have said, here's what bothers me. They cited rule 1 as the ban reason. Now, lemmy.ml's news community doesn't have its own rules section, so I was left to assume that they were applying the instance-wide "rule 1" which was, "no bigotry".

No Bigotry.

Apparently calling someone a tankie and a redfash accelerationist is bigotry? Are they seriously trying to equate being a tankie with being trans, gay, black and/or native american? Seriously? That's incredibly bigoted and offensive; and that's ignoring the fact that the common tankie idols like Stalin, Putin, Xi Jinping and Kim Jong-un are deeply intertwined with things like nationalism, ethnic superiority, queerphobia and the like.

Meanwhile, their modlog shows that they've dealt with multiple instances of actual queerphobic bigotry by removing the comment while also letting the user go.

Do we really want to be associated with bigots like that?

The thing that sucks is that there are communities I genuinely enjoy on lemmy.ml, however getting banned for bigotry after calling someone a tankie and redfash accelerationist while actual bigots are allowed to keep hanging out on lemmy.ml is like a slap to the face.

I'm honestly considering leaving Lemmy and social media at this point. It seems like my two choices are corporate-owned black-box algorithms populated by soft-spoken bigots and pissed-off centrists looking for an axe to grind, and FOSS-based federated platforms where you still have to tolerate bigotry because there apparently aren't enough users and interesting content otherwise.

Inb4 I start getting harassed by lemmy.ml admins or something.

Receipts (click links for images)

(Community ban)

(Instance ban)

(No rules for lemmy.ml/c/news)

(Rules for lemmy.ml)

(Transphobia let off with a slap on the wrist)

(Queerphobia let off with a slap on the wrist)

Been meaning to ask for awhile; especially relevant with the most recent Pawb outage apparently being due to lack of storage space.

A post from 6 months ago claims that Lemmy as a whole still doesn't support AVIF or JXL uploads; is that also true of Pawb?

Given the size the community has grown to and concerns around our current approach to maintenance, I’d like to get some feedback on when we should look to schedule maintenance going forward.

There’s two cases covered by the poll, so please choose the all options that fit your preferences.

Case 1: Non-interactive Maintenance This covers any maintenance where we don’t actively need to monitor the upgrade process; Copying data from one location to another, etc. (Usually, this could be left overnight and brought back up in the morning)

Case 2: Interactive Maintenance This covers any maintenance that requires us to perform a series of actions and continually monitor the process to ensure no issues; Upgrading Mastodon or Lemmy, database migration, or upgrading the Kubernetes cluster. (Usually, this would need to occur during the day due to time constraints)

To vote, please find the corresponding pinned comments and upvote them!

If you’ve got any questions, concerns, etc. please leave them below and we’ll get back to them asap!

Due to the recent spam waves affecting the Fediverse, we'd like to open requests for comment on the use of automated moderation tools across Pawb.Social services.

We have a few ideas on what we'd like to do, but want to make sure users would feel comfortable with this before we go ahead with anything.

For each of these, please let us know if you believe each use-case is acceptable or not acceptable in your opinion, and if you feel like sharing additional info, we'd appreciate it.

1. Monitoring of Public Streaming Feed

We would like to set up a bot that monitors the public feed (all posts with Public visibility that appears in the Federated timeline) to flag any posts that meet our internally defined heuristic rules.

Flagged posts would be reported per normal from a special system-user account, but reports would not be forwarded to remote instances to avoid false-positives.

These rules would be fixed based on metadata from the posts (account indicators, mentions, links, etc.), but not per-se the content of the posts themselves.

2. Building of a local AI spam-detection model

Taking this a step further, we would like to experiment with using TensorFlow Lite and Google Coral Edge TPUs to make a fully local model, trained on the existing decisions made by our moderation team. To stress, the model would be local only and would not share data with any third party, or service.

This model would analyze the contents of the post for known spam-style content and identifiers, and raise a report to the moderation team where it exceeds a given threshold.

However, we do recognize that this would result in us processing posts from remote instances and users, so we would commit to not using any remote posts for training unless they are identified as spam by our moderators.

3. Use of local posts for non-spam training

If we see support with #2, we'd also like to request permission from users on a voluntary basis to provide as "ham" (or non-spam / known good posts) to the spam-detection model.

While new posts would be run through the model, they would not be used for training unless you give us explicit permission to use them in that manner.

I'm hoping this method will allow users who feel comfortable with this to assist in development of the model, while not compelling anyone to provide permission where they dislike or are uncomfortable with the use of their data for AI training.

4. Temporarily limiting suspected spam accounts

If our heuristics and / or AI detection identify a significant risk or pattern of spammy behavior, we would like to be able to temporarily hide / suppress content from the offending account until a moderator is able to review it. We've also suggested an alternative idea to Glitch-SOC, the fork we run for furry.engineer and pawb.fun, to allow hiding a post until it can be reviewed.

Limiting the account would prevent anyone not following them from seeing posts or mentions by them, until their account restriction is lifted by a moderator.

In a false-positive scenario, an innocent user may not have their posts or replies seen by a user on furry.engineer / pawb.fun until their account restriction is lifted which may break existing conversations or prevent new ones.

We'll be leaving this Request for Comment open-ended to allow for evolving opinions over time, but are looking for initial feedback within the next few days for Idea #1, and before the end of the week for ideas #2 through #4.

On Feb 14th we migrated Lemmy from its standalone Docker setup to the same Kubernetes cluster operating furry.engineer and pawb.fun, discussed in https://pawb.social/post/6591445.

As of 5:09 PM MT on Feb 14th, we are still transferring the media to the new storage, which may result in broken images. Please do still reply to this thread if your issue is media related, but please check again after a few hours and edit your comment to say "resolved" if it's rectified by the transfer.

As of 11:02 AM MT on Feb 15th, we have migrated all media and are awaiting the media service coming back online and performing a hash check of all files. Once this is completed, uploads should work per normal.

To make it easier for us to go through your issues, please include the following information:

• Time / Date Occurred
• Page URL where you encountered the issue
• What you were trying to do at the time you encountered the issue
• Any other info you think might be important / relevant