[–] 16 points 2 weeks ago

Feel free to reach out to network[at]pawb.social if you think there's issues we haven't resolved. Lemmy reports can also get resolved by community mods in which case the admin team won't see it. Masto is far better in that dept.

  • source
  • parent
  • context
  • [–] 7 points 6 months ago

    How can we fix LW and large instances being a problem we have to even care about?

    Move. Leave those instances. Make communities elsewhere. Be the change you want to see.

    There are no rules to who or what communities can be made here, other than I won’t platform hate, harassment, or abuse of any kind.

  • source
  • parent
  • context
  • [–] [M] 11 points 6 months ago (1 child)

    After discussing with the team internally (admins & mods), we’ve come to a few points:

    tl;dr We call on Lemmy.World to be fully transparent and explain their actions to the whole community, and we’re setting more concrete policies for our own moderation actions going forward.

    ——

    While we won’t be formally joining the boycott of Lemmy.World, for reasons I’ll go into in due course, we do call on them to be transparent with the community and act in good faith in regards to whom of their staff came to the decision, why they felt a non-directed comment is worthy of banishing an entire instance, and what they’ll be doing going forward to course correct.

    Defederation should not be a bludgeon to be waved around. Individual users commentary (admin or not) should never be the sole, snap reason that an instance is defederated due to the potential for irreversible damage to federation (loss of posts, comments, users, etc.) and the subsequent impact on users.

    There’s a way to handle problematic users who say things you don’t like, but they’re allowed to say: Block, and move on. Rash defederation instead demonstrates behavior akin to schoolyard bickering, not that of an admin, a custodian, operating a service for the good of their users.

    If allegations are true, LW has some cleaning up to do with their moderation policies, especially not using abusive tactics to hide or manipulate the Mod Log.

    On moderation policies, we have an internal document that explains our federation policies with other instances. We’ll be making this public in due course, but here’s a snippet from it that we’ve been using since Day 1:

    We are an open-first instance, however in rare cases where an instance has been identified as being, indifferent to, permissive of, or actively encouraging abusive conduct, that instance will be blocked from federation.

    At this time, while we have distain for how LW handled things and for their actions (if the allegations are true), we will not use defederation as a weapon as we believe it irresponsible and an avenue for subjective defederation actions in the future.

    Also, if the subtext is not clear: It is childish behavior to wield your admin powers as a bludgeon, and to use your admin tools for a personal grudge instead of blocking an offending user. “Go kill yourself” or anything akin is not a reason to defederate an instance, that’s overkill and I’m fucking disappointed, but when anyone can become a “fediverse admin” that’s the shit situation we’re in.

  • source
  • submitted 7 months ago by to c/adminlog@pawb.social
    locked comment fedilink
     
    • Instance: feral.bond
    • Type: Defederation
    • Affects: Pawb.Social, furry.engineer, pawb.fun
    • Reason: Zoophilia, Pedophilia (pedophilic commentary), underage users

    For obvious reasons, no evidence will be provided.

    Determination was made by reviewing text posts from users on the remote instance which were deemed sufficient to justify the defederation reason and action.

     

    EDIT, Update: We've been able to partially recover about 25% of the media uploaded to Pawb.Social.


    Upon further investigation, data from pawb.social was priorly moved to the new server and was inadvertently deleted as part of the earlier incident affecting furry.engineer and pawb.fun's cache while we were preparing the new server.

    furry.engineer and pawb.fun media is unaffected, but all media directly uploaded to pawb.social is unrecoverable and has been lost. A miscommunication on my part OK'd the removal without fully checking the scope of data that was being removed; This was intended to only remove test data we were using to stress test the new hardware, but affected live data as well.

    A large majority of posts are externally hosted and referenced (e.g. images from media.kbin.earth, d.furaffinity.net, etc.) are NOT affected. Only posts directly uploaded via the Create Post > Image field on pawb.social are affected.

    We had previously transferred pawb.social to the new hardware as a preliminary trial and I had forgot this occurred thus failing to bring it up prior to the deletion going through.

    I'm looking into options to be able to in-place reupload media on behalf of posters, but as the UUIDs are randomly generated by Pict-rs (the media service used by Lemmy), I'm unsure how to facilitate this. Any advice or information would be appreciated, and can be sent to network@pawb.social.

    I understand this is a serious incident and reflects poorly on us, and I can only apologize for this loss and work to prevent this happening again in the future.

    EDIT: I believe this will also impact profile pictures and community images (logos and banners), so please re-upload them at your earliest convenience.___

     

    Rule 9 is rescinded until further notice.

    We're holding off on implementing this rule while we re-evaluate with the feedback we've received thus far. Thank you for your feedback and patience.


    ⚖️ We appreciate the feedback we've received so far regarding the DNP rule, and will be holding off on implementing it while we re-evaluate the use of the e621 list and instead look at maintaining our own list.

    Upon re-evaluation, the differences between e621 as an image board and Pawb.Social as a social aggregator site don't quite line up in the same manner and the vast list provided by e621 is both cumbersome and not representative of those wanting to allow sharing via social aggregation sites but not via imageboards out of their control.

    This started to lead towards needing to maintain awareness of the e621 list and potentially an exceptions list that would overall make the moderation a complete headache.

    Once we've squared away the details, we'll be looking to announce the rule prior to it taking effect to ensure we strike the right balance.

    I'm sorry we didn't get this right and the approach seemed so hamfisted, and I'll strive to ensure better communication on these changes in the future.

    -Crashdoom, Pawb.Social Network Owner


    Original Post Begins Below

    In Short: Effective today, Friday, July 18th, 2025, Pawb.Social will be adopting e621.net's Avoid Posting List in a new Code of Conduct rule aimed to respect artist's wishes not to upload their content elsewhere.

    EDIT: To clarify, e621's additional rules on the DNP page, like the no "content that is not furry or furry-related" under "Avoid posting these things" do not apply. Non-furry posts are still permitted and encouraged as much as furry posts!


    Artists own their content and have a right to determine when and where their content is redistributed. That being said, trying to collate that information is time consuming and leads to a lot of duplicated effort already achieved elsewhere (such as e621's DNP list).

    Going forwards, we're introducing a new Code of Conduct rule to address these issues:

    Rule 9. DNP (Do Not Post) Content

    Our DNP content policies apply to images, videos, and other file-based content uploaded directly to any Pawb.Social service, but does not include content linked externally.

    DNP (Do Not Post) content rules falls into one of two categories: Static DNP, and Artist DNP.

    Rule 9.1. Static DNP

    Static DNP content is content that shouldn't be uploaded to Pawb.Social services, such as content that can realistically be expected to be private and not publicly shared, or content that breaks any other rule in the CoC; This includes, but is not limited to:

    • Any commercial content (e.g. content behind a paywall or similar access control, inc. Patreon and similar)
      • Similar to e621.net, Pay-what-you-want (PWYW) content that you can obtain for free may not be uploaded until at least 2 weeks (14 days) have passed. This allows for artists to still obtain revenue and traffic directly from PWYW content.
      • Additionally, when uploading PWYW content past this 2 week period, we require a link to the source to be provided in the description (or a top-level comment).
    • Content of a harassing, abusive, or discriminatory nature, or otherwise depicting hate, abuse, or discrimination through text, symbols, or other iconography.

    Rule 9.2. Artist DNP

    Artist DNP content is anything produced by an artist listed on e621.net's Avoid Posting List that you do not have explicit permission to repost.

    Linking to content by DNP artists on other websites where the artist themselves (or an authorized person) is the poster is permitted, but direct uploads are not.

    Rule 9.3. Exceptions

    If you have permission to upload something that is covered by the DNP rules 9.1 or 9.2, please include proof in the description of your post, otherwise it may be treated as DNP content and removed upon being flagged for review.

    Rule 9.4. Reporting / Moderation

    As content is not automatically reviewed and there's no tag system similar to e621 on Lemmy, we cannot effectively auto-moderate content that may be affected by the DNP nor do we have the resources to manually review every post, so we encourage users to report content that they find on the DNP list for the community Moderators / Admin Team to review.

    If you believe you've uploaded content that falls under one of these categories, we ask that you either delete the post directly or report it for a Moderator / Admin to action for you. Reports from the uploader will not receive a warning or further moderation action.

    However, repeated posting of Artist DNP (Rule 9.2) content without permission may result in a warning, or further moderation action, especially if it has already been brought to the user's attention.

    Rule 9.5. Direct Takedown

    Rule 9 and it's sub-sections do not remove the statutory right for an artist, character owner, or commissioner to submit a takedown / DMCA request directly to the Pawb.Social Admin Team.

    Content requested to be removed via a takedown / DMCA request can be submitted to network[at]pawb.social with the subject line: "Takedown Request: [name]", and include the URL(s) of the offending posts, and the reason / information relating to your ownership or right to request removal.

    We'll work with those submitting takedown requests to verify their authenticity, and once confirmed we'll notify affected user(s) about the takedown request we received via DM / email, and remove the offending post(s).


    We hope that still permitting links to externally hosted content where a DNP exists allows discovery of that artwork and artist, while respecting their wishes to ensure it's not directly reposted without permission, and ensuring minimal disruption to communities and users on Pawb.Social services.

    We'll be giving a grace period of 14 days from this announcement before any moderation actions above a warning will be issued to allow for public comment and feedback.

    Posts created prior to this announcement will not be subject to moderation action except removal of offending posts upon them being identified.


    We would also like to welcome and encourage feedback on this policy change in the comments here, and in our /c/meta community in general.

    -Crashdoom, Pawb.Social Network Owner

     

    Pawb.Social Logo

    Disclaimer and Preamble

    The Pawb Social administration team wants to create and foster a diverse, welcoming community, and a safe space where those within the LGBTQ+ community can be themselves.

    By continuing to access Pawb Social’s services, you agree be bound by these policies and terms.

    These terms and any dispute or claims arising out of or related to them and governed by the laws of the State of Colorado. Any legal action must be brought exclusively within the state or federal courts located in Colorado. You and Pawb Social consent to personal jurisdiction and venue in those courts and waive any objections based on forum and convenience.

    Pawb.Social Code of Conduct and Policies

    This Code of Conduct applies to all services run by Pawb Social LLC, including furry.engineer, pawb.fun, and pawb.social, any media or files uploaded by users to any of our services, as well as in any private communication conducted on or through any of our services.

    Rules

    By utilizing any of our services, you agree to abide by this Code of Conduct and breaking it may result in sanctions against your account.

    1. Illegal content or conduct

    Content or conduct that is illegal in the United States is strictly prohibited. Pawb.Social services are operated and maintained within the United States and all content must comply with the federal laws of the United States.

    For the avoidance of doubt, this includes but is not limited to: Instructions on how to commit crimes, encouraging acts of violence or terrorism, child sexual abuse material (CSAM) or depictions thereof, and unauthorized access or exploitation of computer systems.

    2. Racism, sexism, homophobia, transphobia, and other discrimination is prohibited

    We take a hard stance against any form of discrimination or abuse towards users in our community. Users who engage in such conduct are not welcome on our platform.

    3. Don’t stalk or harass other users

    Respect other users of our service and other federated instances. If someone doesn’t want anything to do with you, leave them alone. Attempts to bypass blocks, including creating alternate accounts for that purpose, is prohibited.

    “Screenshot dunking”, or the act of taking screenshots of posts to repost and harass without directly replying, is strongly discouraged. If someone is annoying you, harassing you, or a genuine danger to other users, block and report them.

    4. Misinformation and deceptive content is prohibited

    Misinformation, scams, Ponzi schemes, and other deceptive tactics have become rampant on other platforms and we don’t want to see a resurgence of it in the Fediverse.

    Examples of prohibited content include, but are not limited to, the following: COVID and health misinformation, pro-insurrection (Jan 6th) comments or endorsement, NFTs, “crypto” (blockchain & tokens, NOT cryptography), MLMs / pyramid schemes, flat earth claims.

    5. CW: Content warning policies

    Please see the Content Warning Policy post.

    6. Respect the service

    Do not perform any manual or automated penetration testing against our production services without prior written approval which can be obtained by contacting us at network@pawb.social.

    Spam and advertising is not acceptable, but friendly automated bots are welcome. Where possible, try to restrict any recurring automated posts to Unlisted to avoid cluttering the Local and Federated timeline.

    Use of automated tools on the service is permitted for personal use, where such tools do not impact the performance of the services.

    Additionally, the use of automated tools by, or on behalf of, archival organizations (such as WaybackMachine) are permitted when limited in scope. For example, archiving a user’s profile or a specific toot. For larger scopes, please contact us at network@pawb.social for approval and assistance.

    7. Use the report system

    If a user or instance is breaking the rules, we recommend just reporting the content and not engaging. We don’t want users to end up getting caught in the crossfire for attempting to correct a user in good faith, as this makes our jobs significantly harder.

    Additionally, the team is here to help – If you’re unsure on a particular post, user profile, instance, etc. and don’t think we’ve seen or dealt with it yet, please send in a report. No user will ever be penalized for genuine use of the report system.

    8. AP: Account policies

    8.1. Posting language

    While English is the primary language of the instance, we have no restrictions on the languages that can be used. However, we do require that all posts are properly marked with the language used, which can be done at the account level through the account preferences page, or per-post by clicking the language button next to “CW” (Content Warning).

    Setting the correct language allows users to utilize the built-in LibreTranslate system to translate posts to their preferred language, and assists the moderation team with addressing concerns raised by other users.

    8.2. Misleading or deceptive impersonation

    You may not impersonate an individual, group, or organization with the intent to deceive, confuse, and exploit other users.

    However, it is not a violation of this rule to impersonate for the purposes of parody, commentary, or fan accounts, so long as such accounts remain respectful and abide by the Code of Conduct. Parody accounts should tag themselves clearly in their profile description.

    8.3. Bot accounts

    Bot accounts must be marked as a bot using the “This is a bot account” option under Profile → Appearance.

    Bots must post using either “Unlisted”, “Followers only”, or “Mentioned people only”, so we can keep the local and federated timelines clear and focused on users.

    Bots must be made to heed the API rate-limits and should have a minimal impact on the instance performance.

    All bots are expected to refuse to communicate, scrape, or otherwise access profiles with the “#NoBot” (case-insensitive) tag in their profile.

    Restrictions on posts and interactions with users do not apply to official, administrative use bots.

    8.4. Brand and Government-affiliated accounts

    No brand or government-affiliated account may be registered on Pawb.Social services without prior written and publicly recorded approval, except furry fandom-operated brands and events covered by the exception below. This approval may be revoked by Pawb.Social at any time for any reason.

    Brand and Government-affiliated accounts and instances must post using either “Unlisted”, “Followers only”, or “Mentioned people only”, so we can keep the local and federated timelines clear and focused on users. Remote users and dedicated instances violating this rule will be limited and their content only available to followers and through boosts.

    However, furry fandom-operated brands and events are exempt from this rule as we want to encourage and support business within the fandom. This rule may be revised at a later date dependent on the future volume impact on the public timelines.

    8.5. Bypassing suspension

    If you have been suspended from any Pawb.Social instance, you may not create another account on any of our services.

    8.6. Inappropriate avatar or header image

    All avatars and header images must not contain any content that is prohibited by any other rule in the Code of Conduct, especially content that requires a Content Warning.

    Effective

    These terms and Code of Conduct shall be effective as of January 1st, 2026.

    view more: next ›