crashdoom

joined 2 years ago
MODERATOR OF
pawbsocial_feedback
aiquirks
adminlog
meta
pawbsocial_announcements
test
AITA
sorted by: new top controversial old
[RFC] Pawb.Social Service Performance in c/pawbsocial_feedback@pawb.social
[–] crashdoom@pawb.social 1 points 2 hours ago

Strangely... I was tweaking with Cloudflare rules again but I didn't think I changed anything that should affect that... Please do let me know if it occurs again, but I'm glad it's fixed now x3

[RFC] Pawb.Social Service Performance in c/pawbsocial_feedback@pawb.social
[–] crashdoom@pawb.social 1 points 3 days ago (2 children)

Investigating -- I'm not able to find anything obvious in our logs, and it doesn't look like requests from Jerboa are getting rejected per se. When it occurs again, could you try to access the same content via a browser and see if a message comes up from Cloudflare?

7
[RFC] Pawb.Social Service Performance (pawb.social)
 

Hey Everyone!

If you've noticed any performance issues (or hopefully performance improvements!) across any Pawb.Social service, please let us know here.

That includes: pawb.social (Lemmy), furry.engineer (Mastodon), and pawb.fun (Mastodon).

Ideally, if you could provide the following information when reporting a performance issue, it would be greatly appreciated:

  • What you were trying to do at the time? (Loading the homepage, opening a post on c/..., making a post on c/..., etc.)

  • What browser / app were you using?

  • About how long did it take for the action to complete?

Feel free to include anything else you might think is relevant, and we appreciate the community's assistance!

Issues with Voyager app in c/pawbsocial_feedback@pawb.social
[–] crashdoom@pawb.social 4 points 2 weeks ago (1 children)

Paradoxically, Voyager is what I use myself, so it was allowlisted! There were a ton of rules added during the DDoS, so I’ve trimmed it down a bit 😅

Issues with Voyager app in c/pawbsocial_feedback@pawb.social
[–] crashdoom@pawb.social 6 points 2 weeks ago (3 children)

Hey! I apologize for the inconvenience. We've adjusted some of the rules after it appears they're impacting a lot more users and were overly aggressive, I'm hoping this resolves the issue and I'm really sorry for the trouble this caused.

Post posted twice from posting normally in c/pawbsocial_feedback@pawb.social
[–] crashdoom@pawb.social 1 points 2 weeks ago

Appreciate this.. I'm wondering if there's some kind of race condition that's causing the DB (or your client) to retry posting. Will investigate once I'm back from a work trip early next week!

Does this instance respect DNP lists? in c/pawbsocial_feedback@pawb.social
[–] crashdoom@pawb.social 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Good question, and I've not thought about it previously other than that we would remove content if the original artist requested us to do so. Though, we don't have a formal list of DNP content, we just expect that users post content they're permitted to or that is already otherwise shared on other sites (like e621).

I'm not against a DNP list, but I think I'd lean more towards respecting an existing DNP like https://e621.net/wiki_pages/85. Though, if we did end up getting to the point of having a lot of DNPs that don't appear on their list, we'd probably move to making our own.

I'll bring this up to the rest of the team too for feedback!

Are you feeling it now, Mr. Quark? in c/tenforward@lemmy.world
[–] crashdoom@pawb.social 2 points 3 weeks ago

Phlox’s amazing smile absolutely sends me every time XD

[PSA] Known Issue: Posts in NSFW Communities in c/pawbsocial_announcements@pawb.social
[–] crashdoom@pawb.social 4 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

I'm not able to replicate this myself as it's showing on both the Create Post and editing modes. I've cleared the site cache on Cloudflare as it could be it's caching an old version of the UI. I'd also encourage clearing your browser cache / force refreshing.

[PSA] Known Issue: Posts in NSFW Communities in c/pawbsocial_announcements@pawb.social
[–] crashdoom@pawb.social 4 points 3 weeks ago (4 children)

We've got a fix deployed that'll allow the NSFW box to be toggled again for new and existing posts -- Is there any chance you'd be able to facilitate that on your existing posts? We're hoping that'll alleviate reports and complaints in the interim while we wait for the permanent backend fix x3

[PSA] Known Issue: Posts in NSFW Communities in c/pawbsocial_announcements@pawb.social
[–] crashdoom@pawb.social 8 points 3 weeks ago
Update, Apr 27, 2025

We've updated Lemmy UI to a hotfix version of 0.19.11 that re-enables the NSFW field on the Create Post form for NSFW communities. This should once again allow users to correctly mark posts explicitly with the NSFW tag.

While a permanent fix is in development by the Lemmy team, please ensure you check this NSFW toggle if you're posting to a NSFW community.

Thank you for your understanding and patience.

53
[PSA] Known Issue: Posts in NSFW Communities (pawb.social)
 

We’ve been made aware that it is no longer possible to identify posts as NSFW in a NSFW community as of Lemmy 0.19.11 (https://github.com/LemmyNet/lemmy-ui/pull/2887), and as a result some posts appear to be not marked as NSFW.

While some apps (Voyager is the only one I have personally verified) do correctly flag the posts in NSFW communities as NSFW by default.

We’ve verified on 0.19.11 Lemmy will blur the image and not tag the post as NSFW, but we haven’t verified behavior from older instances viewing our communities / posts.

Due to the current time as of writing this, I’m not able to investigate further until the morning but I hope this provides some basic information on the situation for now.

3
AITA: Welcome, FAQ, and How to Post (pawb.social)
submitted 4 weeks ago* (last edited 4 weeks ago) by crashdoom@pawb.social to c/AITA@pawb.social
0 comments fedilink
 

Welcome to Pawb.Social's c/AITA!

While furry-themed, this is a general purpose Am I The Asshole community intended to help posters see their situations from another perspective and grow.

How to Post
  • Ensure your title starts with "AITA" and explains (concisely) what happened (e.g. "AITA for downing all the punch?")
  • Describe the situation as objectively as you can, ensuring you anonymize other participants in the situation
  • Include how the other participants are upset with you or believe you to be the asshole (as much as you're aware)
  • Include why you believe you might be the asshole at the end of your post
  • Try to keep posts reasonably concise. Only provide backstory information where it's absolutely necessary and cannot be summarized.
FAQs
Voting Guide / Terminology
  • 🟢 NTA – Not The Asshole
  • 🟡 ESH – Everyone Sucks Here
  • 🔴 YTA – You’re The Asshole
  • 🔵 NAH – No Assholes Here
  • 🟣 NMI - Need More Information
unable to toggle nsfw in default front end in some communities in c/meta@pawb.social
[–] crashdoom@pawb.social 2 points 1 month ago (1 children)

I believe there was a change to some Lemmy communities where if the community itself is marked as "NSFW" there's no ability to toggle it off anymore: https://github.com/LemmyNet/lemmy-ui/pull/2887 (https://join-lemmy.org/news/2025-04-08_-_Lemmy_Release_v0.19.11).

If the post isn't flagging automatically as NSFW in a NSFW community, then there may be a backend bug that needs to be reported to the Lemmy developers via GitHub.

Is there an issue with federation right now? in c/meta@pawb.social
[–] crashdoom@pawb.social 8 points 1 month ago (1 children)

Update: Turns out a security feature we enabled to block "AI Bots" (like ChatGPT) was blocking federation traffic... Since it's affecting stuff right now, I've disabled it again until I can get time after LVFC to take a look into building a comprehensive "allow list" of different federation traffic headers.

tl;dr Give it a little bit and things should hopefully catch up with new posts, but I don't know if Lemmy post-syncs old posts without someone searching for them on our instance.

59
[IMPORTANT] Pawb.Social Organizational Changes (pawb.social)
submitted 3 months ago* (last edited 3 months ago) by crashdoom@pawb.social to c/pawbsocial_announcements@pawb.social
19 comments fedilink
 

This notice is also being sent by email to all users with a verified email on Pawb Social services. (Completed as of 02/13/2025)

UPDATE (02/13/2025)

ℹ️ If you received the "Important - Pawb.Social is re-structuring as an LLC!" email from us about an account you don't recognize, or no longer wish to have, on our services and would like the account deleted:

Please email network@pawb.social from the SAME email address, and we'll be able to lookup your accounts and remove them.

If your account has any content, we will issue a backup to the email on file and wait 7 days before deleting the account, unless you ask us to delete it immediately after we inform you that content exists.

Begin Original Post

As of Friday, February 14th, we will be transitioning the management and ownership of our instances to PawbSocial LLC, a new limited liability company (LLC) registered in the State of Colorado.

This change is primarily driven by the desire to ensure legal protection and mitigate liability concerns in light of the current political climate, but has been a task we would have eventually needed to face as Pawb Social grows.

What does this mean?

There will be no changes to the team running any of our instances, and PawbSocial LLC will continue to be owned and operated by Crashdoom.

Donations will now be made to PawbSocial LLC, though there should be no changes necessary to existing donations. PayPal donations via Ko-fi going forward (one-time or recurring) will show PawbSocial LLC instead of "Pawb.Social".

Existing assets and hardware bought for Pawb.Social using donations will be transferred to PawbSocial LLC's ownership.

Our contact information remains the same: You can contact the Network Admin team by email at network@pawb.social.

We felt it important to inform all of our users of this change despite there being no change in leadership or effective ownership as a show of good faith and transparency.

We appreciate your understanding and continued support as we take these steps to ensure the long-term stability and security of our community.

Please feel free to reach out if you have any questions or concerns.

Crashdoom

Owner / Network Admin, PawbSocial LLC

27
[Maintenance Update & Postmortem] Lemmy 0.19.6-beta.13 and "Toastify is awesome!" (which it is.) (pawb.social)
submitted 6 months ago* (last edited 6 months ago) by crashdoom@pawb.social to c/pawbsocial_announcements@pawb.social
5 comments fedilink
 

Firstly, the maintenance for Pawb.Social services has been completed and we've upgraded Lemmy to 0.19.6-beta.13, and our Mastodon instances to v4.3.0.

Thanks for your patience.

and now, onto the "Toastify is awesome" (because it is. Totally.) postmortem:

Short summary: Crash did a stupid with the config and emails weren’t getting sent (oops). Emails should now be working again, and registration shouldn't require admin intervention.

Longer story:

Lemmy has several configuration options that need to be updated to correspond to the specific instance that's running it. For example, here's a snippet of Pawb.Social's config:

{
  database: {
    host: "the.best.db.url.internal"
    user: "pawbsocial_lemmy"
    database: "pawbsocial_lemmy"
    password: "pawbsocial_do_you_really_think_i_would_leak_this"
    pool_size: 128
  }
  hostname: "pawb.social"
  pictrs: {
    url: "http://pawb-social-pictrs:8080/"
    api_key: "sekrit"
  }
  email: {
    smtp_server: "email-smtp.us-east-2.amazonaws.com:587"
    smtp_login: "pls_send_emails"
    smtp_password: "jeff_im_begging_you"
    smtp_from_address: "Pawb.Social Lemmy <{{domain}}>"
    tls_type: "starttls"
  }
}

Can you spot the problem? (No, it's not my awful password, or the pleading I'm doing with AWS to send emails so y'all stop having email problems.)

Originally, Lemmy was deployed through docker-compose which uses variable replacement to change something like {{domain}} to pawb.social automatically. Crash swapped away from using docker-compose due to repeated issues with trying to deploy the Lemmy changes and opted for a more bare Docker configuration.

Can you guess what didn’t get changed? …Yeah, the {{domain}} part was never removed and replaced with pawb.social so Lemmy correctly caught the error and threw an exception. The unfortunate part is that the thrown exception caused the whole comment process to close the connection to the web proxy server which returned a 502 Bad Gateway, which gave the UI HTML instead of a JSON response. The response handler in the UI then tried to figure out what was wrong, failed to translate the HTML to JSON, and gave the default error message “Toastify is awesome!” (which it is. Objectively.)

HOPEFULLY. This does fix the issue. I can’t guarantee it, but I’ve been able to replicate it by replying to someone else’s comment (which usually triggers an email notification) and after making the change, it successfully sent off the comment with a happy green confirmation toast.

33
[Maintenance Update] Lemmy v0.19.4 / v0.19.5 Updates (pawb.social)
submitted 8 months ago* (last edited 8 months ago) by crashdoom@pawb.social to c/pawbsocial_announcements@pawb.social
5 comments fedilink
 

We've successfully upgraded Lemmy from v0.19.3 to v0.19.5 and have a bunch of changes to share!

Bug Fixes

  • Previously users were reporting that the web client kept logging them out. This was suspected to be due to a misconfiguration of the cookie storing the session information and should be fixed.

  • Some communities were slow to load. Federation changes in v0.19.4 and v0.19.5 should rectify some federation issues. Additionally, we increased the number of database connections for Lemmy and will gradually increase this if we identify any further slowdowns.

(Longer term, we're planning to upgrade the database hardware which should improve the performance for all services)

Local Only Communities

When creating or editing your communities, you'll now see a "Visibility" option that allows you to choose between "Public" and "Local Only".

The "Public" setting will continue to operate as normal and federate your community to all other instances we federate with.

"Local Only" will disable federation for your community and restrict the community to being viewed by local logged in users only; Logged out users may not be able to see your community until they log in.

Image Proxying

Once we've established that the database is no longer under substantial load and the performance issues previously experienced are fixed, we'll be enabling an image proxying mode which will allow us to locally cache images from remote instances rather than serving them directly.

This will allow us to improve the performance of loading images without applying additional load to other instances, and prevent remote bad actors from trying to scrape IP addresses.

Other changes

There are a handful of other miscellaneous changes that you can view in the full change logs:

10
[Maintenance] Sept 22 - Login Issues on Pawb.Social (pawb.social)
 

We’re aware of an issue affecting our Lemmy service (pawb.social) that seems to be causing users to be randomly logged out. We believe we’ve identified the issue thanks to a bug fix in a newer version of the UI code.

We’re needing to verify there are no other breaking changes for the upgrade process, and expect to perform maintenance this Sunday, Sept 22nd at Noon US Mountain Time (https://everytimezone.com/s/7abd4955). We’ll provide an update tomorrow to confirm the maintenance window.

Thank you to everyone who brought this to our attention and we apologize for the inconvenience.

32
[Limit] tenforward.social (pawb.social)
submitted 8 months ago* (last edited 8 months ago) by crashdoom@pawb.social to c/adminlog@pawb.social
9 comments fedilink
 

After reviewing a report regarding the personal account of the admin of tenforward.social, and discussing with other fediverse admins, we're deciding to suspend the admin and limit tenforward.social until this blows over. I'll explain why on both, starting with the admin themselves.

Suspending packetcat@tenforward.social

Rule 1: Threats of Violence

packetcat made several posts[1][2] that were perceived as a threat of violence, metered by it being "theoretical". This is not acceptable behavior for any user, especially an instance administrator, irrespective of the intended target of their annoyance.

This comes across as extremely volatile and dangerous, and on any other platform (except the cesspool that is X / Twatter) would be immediately removed.

Rule 6: No Spam

packetcat appears to have been going on a run of posts using several hashtags excessively in ways we, and other instances, have previously actioned as abuse / spam.

In the first case, the #fediblock hashtag was being used for its intended purpose to inform and make other instances aware of abusive conduct by other users. More specifically, their posts[3][4] were about Eris (originally from disqordia.space)[5] -- None of this is at issue as there's a laundry list of poor and "edgy" conduct that the historical receipts appear to cover, and privately corroborated by other instance admins we're in contact with.

However, that then began to devolve into airing their grievances generally and repeatedly escalating their posting when users began to report them, unaware they were the instance administrator of tenforward.social[6][7][8][9][10].

Later, they made two posts[11][12] with the #Mastodon4Harris hashtag for seemingly no other reason than one of their users said they should[13] and wanting to instigate drama[14]. This is just petty and childish trolling.

Rule 3: Harassment of Other Instances and Users

As tenforward.social received reports from other instances, packetcat would post the report[3][6] and in some cases encourage the administrators of other instances to take action against the reporters[10][15]. In the case of latter request to remove content, the linked post has been deleted so assumed to be a valid request to remove content, but their reaction threatening defederation is unwarranted[15].

While this isn't entirely unusual for an admin to do (we reach out and have other instances reach out to discuss reports), airing it in public is not acceptable, especially given tenforward.social's explicit statements about using the report system and confidentiality of reports[16] and then posting an email chain report from a concerned user[17][18]. Revealing private information publicly, especially like this, is utterly unacceptable and a gross violation of trust.

Limiting tenforward.social

As a result of the actions above, we're locally suspending packetcat@tenforward.social across all of our instances, and we're limiting tenforward.social due to the instability of their admin and egregious breach of trust that makes us concerned with interactions going forward.

We realize there are connections back and forth between our Mastodon instances (furry.engineer and pawb.fun) and tenforward.social, so we don't want to unduly impact our users or theirs based solely on their administrator's conduct by suspending and permanently breaking those connections.

Should there be additional poor conduct or an improvement in the situation, we'll re-review our stance in a few weeks time.

Important Reminder

It should really go without saying, but DO NOT use this as an excuse to harass packetcat or anyone else involved in this situation. Any users found doing so will be suspended without warning per Rule 3. While their conduct is unbecoming, it does not warrant abuse.

Clarification: What is a Limit

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.

References

CW: Threats, Harassment; Some linked posts have content warnings, but have been omitted here for transparency.[1] @packetcat@tenforward.social (Sept 7, 2024) "I saw some folks talking about baeddel on the TL earlier and my thoughts: If I ever encounter these baedellist fuckers, I'm going to buy an AK-47 and shoot them in the head. That's too quick of a death for them because I'm merciful." Retrieved from https://tenforward.social/@packetcat/113097974087422618. [REMOVED] see note below.

[2] @packetcat@tenforward.social (Sept 7, 2024) ""The AK-47, officially known as the Avtomat Kalashnikova (Russian: Автомат Калашникова, lit. 'Kalashnikov's automatic [rifle]'; also known as the Kalashnikov or just AK), is an assault rifle that is chambered for the 7.62×39mm cartridge. Developed in the Soviet Union by Russian small-arms designer Mikhail Kalashnikov, it is the originating firearm of the Kalashnikov (or "AK") family of rifles. After more than seven decades since its creation, the AK-47 model and its variants remain one of the most popular and widely used firearms in the world." https://en.wikipedia.org/wiki/AK-47 The AK-47 is the people's weapon. And it is the people's justice enacted on these fuckers." Retrieved from https://tenforward.social/@packetcat/113097988673182417. [REMOVED] see note below.

Note: Since the posts linked above have been subsequently deleted, a screenshot has been attached from the furry.engineer admin panel:

[3] @packetcat@tenforward.social (Sept 7, 2024) "A new (to me) Eris account was just reported to me. Y'all wanna block/suspend this one real quick. eris@yourwalls.today #fediblock" [Extended Thread] Retrieved from https://tenforward.social/@packetcat/113096843977126847.

[4] @packetcat@tenforward.social (Sept 8, 2024) "Racism in the Fediverse: Eris of Disqordia. https://www.youtube.com/watch?v=WUXOUd2AENo. I wanted to put my thoughts on Eris and racism on fediverse in video form so here it is. I want this wide. Boost boost boost. I want this on every fediverse instance's timeline." Retrieved from https://tenforward.social/@packetcat/113102432762834938.

[5] @puf@rage.love (Aug 15, 2022) "if you need some proof that eris is a unpleasant individual

make your own choices whether this is #fediblock worthy, but note that i know some instances defederated from disqordia due to the below, among other things: this thread is cached correctly here, on the external server, but eris' original toots were lost when the old disqordia instance went down https://cybre.space/@DangerDyke/108595663835969647 (top of thread at https://jubi.life/@sixthhokage95/108592329213498710)" Retrieved from https://rage.love/@puf/108829412633265534.

[6] @packetcat@tenforward.social (Sept 7, 2024) "I just got this report. This is the divide and conquer tactic these people play. @OttawaPlaceAdmin you want to ban whoever this is. Trust me you don't want them in your space. They are accusing me of transphobia. Right. Of course they are. I've seen this play before. It ain't working on anyone anymore Eris. We know your game. Also accusing @so_treu of deadnaming her. Which they haven't done because I know what actually happened." Retrieved from https://tenforward.social/@packetcat/113098074860190153.

[7] @packetcat@tenforward.social (Sept 7, 2024) "don't fuck with me. https://infosec.space/@kkarhan/113098123869087463 https://infosec.space/@kkarhan/113098129378235029 This is what Eris does." Retrieved from https://tenforward.social/@packetcat/113098141033911677.

[8] @packetcat@tenforward.social (Sept 7, 2024) "Telling me to use the report system is hiliarous mate. Yeah mate. I know about the report system. Not like I'm a moderator and admin of a Mastodon instance since 2017. Fucking cunt." Retrieved from https://tenforward.social/@packetcat/113098152858203750.

[9] @packetcat@tenforward.social (Sept 7, 2024) "techhub.social/@Raccoon/113098175071285637 lol. lmao. Now this is some proper entertainment only the fediverse can give me." Retrieved from https://tenforward.social/@packetcat/113098184753861669.

[10] @packetcat@tenforward.social (Sept 7, 2024) "lmao. mastodon.top now eh? @thomas_virtubox hey. ban whoever is the originator of this report. you don't them in your space." Retrieved from https://tenforward.social/@packetcat/113098204368592089.

[11] @packetcat@tenforward.social (Sept 8, 2024) "I'll improve more Americans' lives in 1 hour than Kamala Harris ever will in 4 years. https://subscribe.packetcat.ca" Retrieved from https://tenforward.social/@packetcat/113103985937178864.

[12] @packetcat@tenforward.social (Sept 8, 2024) "I'm not American, or in America but I can help Americans from where I am and I do every single day. https://subscribe.packetcat.ca" Retrieved from https://tenforward.social/@packetcat/113103990459803459.

[13] Inken Paper, @crashglasshouses (Sept 8, 2024) "@packetcat that's gonna require trolling #MastodonForHarris and #Mastodon4Harris more" Retrieved from https://tenforward.social/@crashglasshouses/113103964074902674.

[14] @packetcat@tenforward.social (Sept 8, 2024) "Oh look I already caught a fish. From hachyderm.io. Wow what a surprise. alexhammy@hachyderm.io "Alexander Hamizdat for Harris" told me to "GFY". and immediately deleted it and blocked me. lol I saw it before you delete it lmao." Retrieved from https://tenforward.social/@packetcat/113104003943902913.

[15] @packetcat@tenforward.social (Sept 7, 2024) "kitty.social/notes/9xwbjjklx6v700cq another one for the blocklist. harassment. kitty.social, you have 24 hours to deal with this piece of shit. If you don't, I will terminate federation with you." Retrieved from https://tenforward.social/@packetcat/113098806737556514.

[16] About - Tenforward.Social "Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting an admin by using the report button. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Admins are obligated to maintain confidentiality with regard to the reporter of an incident." Retrieved from https://tenforward.social/about. Retrieved on Sept 8, 2024.

[17] @packetcat@tenforward.social (Sept 7, 2024) "lmao. Another challenger appears. Email too huh?" [Screenshot includes a report from a concerned user, and their full email address] Retrieved from https://tenforward.social/@packetcat/113098303738022025.

[18] @packetcat@tenforward.social (Sept 7, 2024) "lmao. free entertainment. Who needs Netflix when I have this?" Retrieved from https://tenforward.social/@packetcat/113098352226657071.

Edits

4
test (infosec.pub)
 

test

1
[RFC] Maintenance Windows (pawb.social)
 

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!

1
[RFC] Use of Automated Moderation Tools (pawb.social)
 

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.

1
[Feb 14] Pawb.Social Migration Bugs / Issues Megathread (pawb.social)
submitted 1 year ago* (last edited 1 year ago) by crashdoom@pawb.social to c/pawbsocial_feedback@pawb.social
0 comments fedilink
 

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
view more: next ›