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
- Instance: pisskey.io
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Nazi imagery, affiliated with poa.st and other known abusive instances
- Fediseer Action: Censured
- Instance: the.asbestos.cafe
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Homophobia, harassment, trolling, admin involved abuse
- Fediseer Action: Censured
Block has been applied to the entire domain.
Evidence
- https://the.asbestos.cafe/objects/14decba5-b6fb-4c20-b8d7-8cf68374ec58
- https://the.asbestos.cafe/objects/094cfc21-7182-471a-90cc-a493fb126635
- https://the.asbestos.cafe/objects/764af9ee-288c-4151-aa41-b2e295dc95cc
- https://the.asbestos.cafe/objects/3f5960bb-8fc1-41b0-b180-7748cd0e15b3
- https://the.asbestos.cafe/objects/bee81dc2-85ee-45ae-b1b6-39f2d2d4dd6f
- Instance: lab.nyanide.com
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Trolling, harassment, homophobia, nazi imagery, admin / mod engaged abuse
- Fediseer Action: Censured
Block has been applied to the entire domain.
- Instance: cunnyborea.space
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Racism, antisemitism, homophobia, abusive admin, nazi imagery
- Fediseer Action: Censured
Evidence
- https://i.imgur.com/HgvMVOh.png
- https://union.place/@inquiline/111247251661793670
- Instance: bv.umbrellix.org
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Toxicity, abusive admin, death threats, emotional abuse
- Fediseer Action: Censured
Evidence
- (CW: Abuse) https://bv.umbrellix.org/notice/AZwi9Is6mxT9vo5TSi
- https://sunbeam.city/@kayttaja@toot.site/111142509643025163
Admin Note: This block applies to the root domain (umbrellix.org) and all associated sub-domains.
- Instance: liberdon.com
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Harassment, trolling, misinformation, sexism, homophobia
- Fediseer Action: Censured
Evidence
- https://liberdon.com/@ghast
- https://liberdon.com/@ghast/111178732016951128
- https://liberdon.com/@rimugu/111178647646581863
- https://liberdon.com/@aristoh4ck8r/111177188127718387
- https://liberdon.com/@gunkslinger/111175171054509579
- https://liberdon.com/@TylerAbeoJordan/111174105820298526
- https://liberdon.com/@TylerAbeoJordan/111174078685171464
- https://liberdon.com/@TylerAbeoJordan/111173743376687580
- https://liberdon.com/@medicineman9/111173062104385765
- https://liberdon.com/@spinneria/111169619274938220
- https://liberdon.com/@nosat/111165212240469156
- Instance: asimon.org
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Racism, homophobia, transphobia, trolling, abusive admin
- Fediseer Action: Censured
Evidence
https://asimon.org/@coin/posts/Aa8tebnT4kYwTVwrwW https://asimon.org/@coin/posts/AZxmCGq8YxrIx5B6UC https://asimon.org/objects/eda7faae-454b-46f7-a309-94066c261ce6 https://asimon.org/@coin/posts/AZKA8C9YIF3zLb2WLA
- Instance: eveningzoo.club
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Trolling, racism, harassment, no moderation policy
Evidence
- https://eveningzoo.club/notice/AZQrHEzRzNTbuXl2VU
- https://eveningzoo.club/notice/AZRLrlgctoMuMoHpYW
- Instance: shitpost.cloud
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Trolling, racism, harassment, no moderation policy
Evidence
- https://shitpost.cloud/@Hoss/posts/AZQgtK4WdzKlw6SGiO
- https://shitpost.cloud/@Hoss/posts/Aa5wKz5h08jGFC2fw0
- https://shitpost.cloud/@Hoss/posts/AZQgtK4WdzKlw6SGiO
- Instance: justbros.xyz
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: unmoderated, troll, epileptic imagery
- Instance: clew.lol
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: troll, homophobia, no moderation, spinoff of poa.st
- Instance: burggit.moe
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: CSAM / Loli / Rule 1
- Instance: federated.fun
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Trolling, transphobia, hate speech, unmoderated / single-user instance
- Instance: ligma.pro
- Type: Defederation
- Affects: Pawb.Social, furry.engineer, pawb.fun
- Reason: Trolling, harassment, gaslighting admin
CW: remote links, harassment
Original post: https://ligma.pro/@r000t/110701630028315917 Gaslighting: https://ligma.pro/@r000t/110701722350085299
Cleared The Shifting Oubliettes of Lyhe Ghiah with a group of four, hitting every single exclamation mark (though two were secret sweeper trolls)!
Love the fact the devs are willing to troll you. FFXIV is awesome XD
Crashdoom @pawb.social Network Administrator for Pawb.Social, furry, and a programmer
Mastodon: @crashdoom@furry.engineer