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

Users can brute-force their way into reading private messages with Lemmy versions below 0.19.1. I know there was the question of federation issues previously, but it appears to have been largely mitigated with the later versions at this point. Are there any plans to upgrade pawb.social?

{"data":{"msg":"Too many frames","files":null},"state":"success"}

I tried uplading short clips at 30 and 25fps. The image above uploaded just fine so i don't know what to make of it.

Thank you for everything you do!

Getting a werid error when trying to upload a picture. https://imgur.com/mHoB4Ng

I've noticed that Pawb no longer seems to receive any new posts from any feddit.de communities. For example, if I view the "DACH" community through Pawb, the latest post is from 7 days ago, while on feddit itself, there were many posts in the last 7 days. Both instances still seem to be federated and aren't on each other's blocklists. Any idea what is happening here?

trying to upload an image returns the error {"data":{"msg":"Error in DB","files":null},"state":"success"} and i'm unsure of how to fix that

Can we get a Matrix Space for Pawb.social

I know that we have a telegram chat for announcements but I think it would also be a good idea to also have a matrix space where we can also get announcements and maybe even also chat and get support.

One of the reasons I think we should is that not everyone has Telegram and it requires a phone number to sign up to, but a lot of people have Matrix and even if they don't it's easy to sign up to. Another reason is that telegram isn't a great platform due to it being a centralized corporate platform which is now allowing/forcing ads on it, some of which for very sketchy blockchain services, which obviously isn't great and is a pretty big reason people would want to avoid it.

(I posted this from #Mastodon so it could reach further and also so I could mention people).

#matrix #Privacy #decentralization #communication #feedback

@pawbsocial_feedback @crashdoom

When I looked at the instances page (particularly the lists of linked instances and blocked instances), I see that the version numbers of various Lemmy instances is displayed as "2.0" and not the actual instance version numbers. I saw that same issue on Lemmy.studio, which was fixed after it was updated to 0.18.5 after I contacted that instance's admin. Since the version number of this instance is currently 0.18.3, could updating the instance version to 0.18.5 help?

I was thinking we could have like a old.pawb.social website that's a Mlmym instance for pawb.social. Thoughts?

I am unable to see communities such as Minecraft Help, Minecraft Commands, and Desktops.

I am testing if this goes through as well.

Performance on Pawb.Social specifically has been degrading significantly; it often times takes a very long time (10+ seconds) to load a post, for example, with a noticeable number of time-outs occurring. Opening the same post via its home instance in these cases typically works much faster, leading me to believe the problem is here, not with the host instance.

This is the case even with local communities.

Hoping to hear from other folks - are you also experiencing this? Is it a temporary issue, or indicative of a growing server-side problem?

When I visit, for instance, https://pawb.social/post/1768987, I can't see the title formatted in Markdown. However, https://lemmy.kde.social/post/60846 shows up correctly (aside from the last cut part).

Hi everyone! I've noticed for a while now that I can't reply to comments made by kbin accounts using my account here. Not even talking about kbin threads, but for example if I reply to any kbin-made comment over on feddit.de, once I click submit it just keeps spinning without ever posting the reply. I often see users from other lemmy instances replying to them though, so it doesn't seem like a general lemmy problem. Does everyone else here have this problem as well?

There was discussion on the lemmy fork thread about replacing the default 'Donate' link with a server-specific one, but given that's not available yet, is there somewhere we can contribute funds towards hosting costs?

Really, maybe such a link should be on the sidebar, at least - if there is one somewhere already, I wasn't able to find it, and as such I suspect other folks who would potentially be looking for one wouldn't find it, either.

Subscribed/Hot is increasingly filled with one month old submissions, often six month old submissions, to the point where sometimes there are no new submissions. Is this expected behavior, and is anyone else seeing this too?

Is it possible to turn off the post auto-collapse glitch-soc provides by default, so people who want it can opt-in to it? It's personally pretty annoying to expand every post, and while there is a way to disable it there seems to be the occasional problem where it resets that flag.

As mentioned in that post, it's not great if getting more creative types is a goal - auto-collapse includes images, not just text. Sharing art, commission open status, etc. would be pretty hampered if every post gets hard collapses.

For your consideration: https://github.com/promitheas17j/lemmy-ui-themes

They seem very straightforward to install even if you use docker so that's a good thing too.

Hello,

I'm not sure if this is the place for such things, but I've been having issues getting the subscribed feed to load on any of the apps I've tried even though it loads fine through a browser. Is the issue on my end or is it an issue with the instance?

Thanks

So I've read the CoC Content Warning policy in the announcements community and wanted to make sure of something to avoid making a mistake in my first post. In 5.1.1, there is:

Any NSFW content, including real or artistic (digital or otherwise), must be behind a content warning message. NSFW content includes, but is not limited to: nudity, sex, kink, and the discussion of such.

To be absolutely clear, should furry nudity absent of any, ahem, "parts" on display be tagged NSFW?

The UI does not react to any changes made to the database for comments sections (i.e. upvotes/downvotes don't show up, comments get an infinitely spinning wheel but are posted normally, etc.,) This could lead to doubleposting, but mainly it's just not how the site is supposed to work.

Problem first encountered on !furry, if that helps

Dankojn pro auxskultontajn, Kamarada Felano

(Edit: Also happens with posts.)