Programming.Dev/p.d-legal
Programming.Dev/p.d-legal
6
2
Fork 2
Code Issues 1 Pull requests 1 Projects Activity

Compare commits

merge into: Programming.Dev:ategon-patch-3
Branches Tags
Programming.Dev:main
Programming.Dev:lesbian@lemmit.online
Programming.Dev:admin-changes
Programming.Dev:gaming@zip
Programming.Dev:ategon-patch-4
Programming.Dev:ategon-patch-3
Programming.Dev:rename
Programming.Dev:ategon-patch-2
Programming.Dev:ategon-patch-1
Programming.Dev:adjustments
...
pull from: Programming.Dev:main
Branches Tags
Programming.Dev:main
Programming.Dev:lesbian@lemmit.online
Programming.Dev:admin-changes
Programming.Dev:gaming@zip
Programming.Dev:ategon-patch-4
Programming.Dev:ategon-patch-3
Programming.Dev:rename
Programming.Dev:ategon-patch-2
Programming.Dev:ategon-patch-1
Programming.Dev:adjustments
Sign in to create a new pull request.

33 commits
ategon-pat ... main

Author SHA1 Message Date
CameronDev
ca8f1cbccf Merge pull request 'Add GirlsFrontlineNSFW@lemmynsfw.com to hide list' (#28) from hide/girlsfrontlinensfw into main 
Reviewed-on: #28
 2025-12-04 08:20:02 +01:00
CameronDev
31bf3daa12 Merge branch 'main' into hide/girlsfrontlinensfw 2025-12-04 03:16:33 +01:00
CameronDev
a5ee8ebdb5 Merge pull request 'Add lesbians@lemmit.online' (#26) from lesbian@lemmit.online into main 
Reviewed-on: #26
Reviewed-by: CameronDev <camerondev@noreply.localhost>
 2025-12-04 03:16:21 +01:00
CameronDev
25b33ecabf Merge branch 'main' into lesbian@lemmit.online 2025-12-04 03:15:36 +01:00
Cameron Cross
d664cac526 Add GirlsFrontlineNSFW@lemmynsfw.com to hide list 2025-12-02 11:19:21 +11:00
UlrikHD
c84f233d41 Merge pull request 'Add hotinfluences to hidden communities' (#27) from camerondev-patch-1 into main 
Reviewed-on: #27
Reviewed-by: UlrikHD <ulrikhd@noreply.localhost>
 2025-11-14 19:24:52 +01:00
CameronDev
f22be6ca6a Add hotinfluences to hidden communities 2025-11-12 22:22:22 +01:00
UlrikHD
636a01606a Add lesbians@lemmit.online 2025-11-04 13:36:11 +01:00
UlrikHD
085b0b5171 Merge pull request 'Add news.abolish.capital hidden communities' (#25) from news.abolish.captital_hidden into main 
Reviewed-on: #25
Reviewed-by: UlrikHD <ulrikhd@noreply.localhost>
 2025-11-04 03:27:07 +01:00
CameronDev
7a434a67fb Update content/docs/hidden-communities.md 2025-11-04 03:24:46 +01:00
CameronDev
e8a5a9220e Update content/docs/hidden-communities.md 2025-11-04 03:23:27 +01:00
CameronDev
b3f0b7f372 Add news.abolish.capital hidden communities 2025-11-04 03:18:13 +01:00
bugsmith
a036458cc8 Merge pull request 'Adds tiktokthots@lemmit.online to the list' (#24) from tiktok into main 
Reviewed-on: #24
Reviewed-by: CameronDev <camerondev@noreply.localhost>
Reviewed-by: bugsmith <bugsmith@noreply.localhost>
 2025-09-20 13:30:05 +00:00
UlrikHD
741428b23d Adds tiktokthots@lemmit.online to the list 2025-09-19 05:52:00 +02:00
UlrikHD
c896d8997c Merge pull request 'Updates the list with primarily political coms that have been hidden' (#23) from politics_cleanup into main 
Reviewed-on: #23
Reviewed-by: bugsmith <bugsmith@noreply.localhost>
Reviewed-by: CameronDev <camerondev@noreply.localhost>
 2025-09-17 15:44:52 +00:00
UlrikHD
f114db533c Fixes misplaced communities 2025-09-17 15:44:35 +00:00
UlrikHD
1e738f0028 Updates the list with primarily political coms that have been hidden 2025-09-17 15:44:35 +00:00
UlrikHD
0cf7c9100c Merge pull request 'Update content/docs/hidden-communities.md' (#22) from camerondev-patch-1 into main 
Reviewed-on: #22
Reviewed-by: UlrikHD <ulrikhd@noreply.localhost>
 2025-09-17 15:21:52 +00:00
CameronDev
1a3fc1fa98 Update content/docs/hidden-communities.md 2025-09-11 12:05:04 +00:00
CameronDev
83e406b98c Update content/docs/hidden-communities.md 2025-09-11 12:02:41 +00:00
CameronDev
413f9a43d5 Update content/docs/hidden-communities.md 
hide Hentai@reddthat.com
 2025-09-10 00:18:07 +00:00
CameronDev
4bae2fa450 Update content/docs/hidden-communities.md 
Add MeasuringTapesAndRulers@lemmynsfw.com
 2025-08-16 23:52:35 +00:00
Ategon
7aa87242dd Merge pull request 'Update content/docs/hidden-communities.md' (#21) from CameronDev/p.d-legal:girlsdrinkingcoffee_ignore into main 
Reviewed-on: #21
Reviewed-by: bugsmith <bugsmith@noreply.localhost>
Reviewed-by: UlrikHD <ulrikhd@noreply.localhost>
 2025-08-13 02:49:29 +00:00
CameronDev
184382c06e Update content/docs/hidden-communities.md 
Hide asslips@sh.itjust.works.
 2025-07-27 06:56:27 +00:00
CameronDev
ff8d02140c Update content/docs/hidden-communities.md 
Block gravure@lemmynsfw.com
 2025-07-26 05:23:08 +00:00
CameronDev
532b429976 Update content/docs/hidden-communities.md 2025-06-30 01:45:53 +00:00
Ategon
62d670818a Merge pull request 'Hides gaming@lemmy.zip' (#20) from gaming@zip into main 
Reviewed-on: #20
 2025-05-15 02:24:52 +00:00
UlrikHD
0b888d86dc Hides gaming@lemmy.zip 2025-05-14 14:43:34 +02:00
Ategon
7768f8fa9f Merge pull request 'Adds exception for actions not to be logged in the admin log' (#19) from admin_guidelines_specification into main 
Reviewed-on: #19
 2025-04-14 21:57:10 +00:00
UlrikHD
828ad99a53 Adds exception for actions not to be logged in the admin log 2025-04-14 10:05:31 +02:00
Ategon
7ca44cba55 Merge pull request 'Update content/docs/administration-guidelines.md' (#18) from ategon-patch-4 into main 
Reviewed-on: #18
 2025-04-11 22:20:20 +00:00
Ategon
b9a58d815c Update content/docs/administration-guidelines.md 2025-04-11 22:20:12 +00:00
Ategon
51bc164722 Merge pull request 'Update content/docs/administration-guidelines.md' (#17) from ategon-patch-3 into main 
Reviewed-on: #17
 2025-04-11 22:19:18 +00:00
2 changed files with 47 additions and 11 deletions
Show stats Expand all files Collapse all files

23
content/docs/administration-guidelines.md
View file

@ -28,7 +28,7 @@ Please prioritise contacting a community team member over non community team mem
## General Administration Guidelines
- The primary job of administrators is to maintain and develop programming.dev, both as a site and community. They should *strictly* enforce the rules and guidelines as laid out on https://legal.programming.dev/. This means that administrators should do their best to coordinate a similar interpretation of the rules and guidelines, and avoid adding their own flavour and personal rules that are not discussed and agreed upon by the rest of the admin team.
Note that we acknowledge that there may be grey areas, loopholes or contexts that are not directly covered by the guidelines, if an administrator encounters a case without any pre-established guidelines, they should consult the admin team before taking action. The written rules and guidelines does not supersede the collective opinion and conclusion the admin team may reach on a specific case. The guidelines should be updated to cover the gap for repeated cases.
- Administrators are expected to follow the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) to the highest standard, this applies to both their admin account and any other accounts they have that links them to programming.dev.
- Administrators are expected to follow the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) to the highest standard, this applies to both their admin account and any other accounts they have that links them to programming.dev.
Acts that qualify to linking their alt-accounts with their admin account are as follows:
- Accounts with an identical name or references to their admin account, be it a local account or an account linked to programming.dev via the ActivityPub protocol.
- They have revealed that they are an admin on programming.dev on their alt-account.
@ -37,18 +37,18 @@ Please prioritise contacting a community team member over non community team mem
- They have via any other way interleaved their alt-accounts such that someone interacting with their alt-account knows they are interacting with a programming.dev admin.
- It is recommended that administrators avoid getting into heated arguments with users. Administrators should as soon as they realise an argument is getting too heated or off-topic try to either de-escalate or disengage from the argument.
- If an administrator wishes to engage in controversial topics, it is recommended that they use an alternate account not linked to their admin account. While this is only a recommendation, it is a highly recommended one as the site has been drawn into needless admin drama with other instances as a result of this guideline not being followed in the past.
- Administrators are not allowed to moderate content they are personally entangled with. If a user posts a severe breach of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) that affects an administrator, the administrator should report the content and leave it to the rest of the admin team to handle. The administrator may not comment on the case unless questioned by the admin team and may under no circumstances suggest what action to take. The administrator is still allowed to temporarily remove the content if deemed necessary, such as in the instance of being doxxed, the administrator must however also immediately notify the admin team that they have taken such action. Breaking this *rule* is considered a severe breach of trust and power. Exceptions are made for CSAM, phishing attempts, or established spam/scam similar to the [Nicole spam](https://programming.dev/c/nicole@feddit.org).
- Administrators are not allowed to moderate content they are personally entangled with. If a user posts a severe breach of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) that affects an administrator, the administrator should report the content and leave it to the rest of the admin team to handle. The administrator may not comment on the case unless questioned by the admin team and may under no circumstances suggest what action to take. The administrator is still allowed to temporarily remove the content if deemed necessary, such as in the instance of being doxxed, the administrator must however also immediately notify the admin team that they have taken such action. Breaking this *rule* is considered a severe breach of trust and power. Exceptions are made for CSAM, phishing attempts, or established spam/scam similar to the [Nicole spam](https://programming.dev/c/nicole@feddit.org).
## When to Perform Admin Actions
- As a general rule, administrators should leave moderation to moderators. If an administrator steps in on behalf of a moderator, they should follow the guidelines as laid out in [Acting on Behalf of Moderators](#acting-on-behalf-of-moderators).
- If user content is breaking the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) and the severity is high enough to warrant admin action rather than waiting for mod action, the administrator must follow the protocol [Enforcing Programming.dev's Code of Conduct](#enforcing-programmingdevs-code-of-conduct) when deciding on what action to take. The boundary between when the severity is high enough for an administrator to step in and take action is purposefully left diffuse, but a guideline is that it at a minimum shouldn't be left to interpretation if the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md) has been breached or not.
- An administrator should never take administrative action on content that isn't strictly against our [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md). If an administrator believes they've found content that requires administrative action, but isn't covered by the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md), they should always consult with rest of the admin team before taking action.
- If user content is breaking the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) and the severity is high enough to warrant admin action rather than waiting for mod action, the administrator must follow the protocol [Enforcing Programming.dev's Code of Conduct](#enforcing-programmingdevs-code-of-conduct) when deciding on what action to take. The boundary between when the severity is high enough for an administrator to step in and take action is purposefully left diffuse, but a guideline is that it at a minimum shouldn't be left to interpretation if the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct) has been breached or not.
- An administrator should never take administrative action on content that isn't strictly against our [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct). If an administrator believes they've found content that requires administrative action, but isn't covered by the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct), they should always consult with rest of the admin team before taking action.
- If an administrator is not 100% sure if they should take action, they should consult with the rest of the admin team before taking action.
- Administrators should not moderate what federated users post on other federated instances. It sets a bad precedent and gives the admin team a workload it likely can't handle. We assume that federated instances comply with our [Defederation Policy](https://legal.programming.dev/docs/defederation-policy.md) and that administrators of the other instance will take action if necessary. Exceptions can be made for content of severity 4.
- Administrators should not moderate what federated users post on other federated instances. It sets a bad precedent and gives the admin team a workload it likely can't handle. We assume that federated instances comply with our [Defederation Policy](https://legal.programming.dev/docs/defederation-policy) and that administrators of the other instance will take action if necessary. Exceptions can be made for content of severity 4.
- Actions may be taken on our local users regardless of which instance they are interacting with, and on federated users that are interacting with our local users and communities.
- Admin moderated communities may be treated as site-wide communities, meaning that administrators may choose to apply admin actions instead of mod actions to content posted in those communities. This means that rather than banning someone from e.g. [programming@programming.dev](https://programming.dev/c/programming), they may ban them from the entire site. Such action can only be taken on content that breaks the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md). Breaches on community specific rules follow the guidelines in [Acting on Behalf of Moderators](#acting-on-behalf-of-moderators).
- Admin moderated communities may be treated as site-wide communities, meaning that administrators may choose to apply admin actions instead of mod actions to content posted in those communities. This means that rather than banning someone from e.g. [programming@programming.dev](https://programming.dev/c/programming), they may ban them from the entire site. Such action can only be taken on content that breaks the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct). Breaches on community specific rules follow the guidelines in [Acting on Behalf of Moderators](#acting-on-behalf-of-moderators).
### Guidelines on Content Severity
@ -74,18 +74,18 @@ When acting on behalf of moderators, administrators can only utilise the same to
The strike system is incremental, a user on strike 2 will always lead to a minimum of a strike 3 regardless of the severity on their next violation. A user without any strikes may be given a strike of any severity, but it's *strongly* recommended that users with zero strikes are never directly given a strike 3 (temporary ban). Offences that don't warrant a direct permanent ban should at a minimum be given a warning before any temporary bans are issued. Users that are given a strike may be put under supervision to make sure they don't repeat an offence, this supervision may only last for as long as the user has a strike.
A strike is decremented by 1 after 365 days without any further violations, for this specific purpose someone on strike 3.5 is treated as if they are on strike 3.
1\. For mild violations, a warning/reminder must be issued to the user in question and logged in the admin log.
1\. For mild violations, a warning/reminder must be issued to the user in question.
2\. For a repeated or more severe violation, a warning must be issued, notifying that a repeated offence will result in a temporary site ban.
3\. After receiving a warning notifying the user of a potential ban, a repeated offence should result in a temporary site ban. Ban length is recommended to be 4-14 days depending on the severity of the violations. E.g. 3 severity 1 violations may warrant a shorter ban that 2 severity 2 violations.
3\. After receiving a warning notifying the user of a potential ban, a repeated offence should result in a temporary site ban. Ban length is recommended to be 4-14 days depending on the severity of the violations. E.g. 3 severity 1 violations may warrant a shorter ban that 2 severity 2 violations. The user should be notified of the temporary ban and a warning that a repeated offence may result in a permanent ban.
3.5. A user that has already received a temporary ban once, may be given an additional temporary ban, and a final warning before incrementing to strike 4. Ban length is recommended to be 14-30 days depending on the severity of the violations.
4\. If the user repeats a violation after a temporary ban, a permanent ban may be issued.
4\. If the user repeats a violation after a temporary ban, a permanent ban may be issued. No message is required to be sent to user.
### Enforcing Programming.dev's Code of Conduct
If a user is found to be in violation of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct.md), the following steps should be taken:
If a user is found to be in violation of the [Code of Conduct](https://legal.programming.dev/docs/code-of-conduct), the following steps should be taken:
- Check if the user has previously been logged by another admin in the admin log, as of writing that would be #pd-warnings channel on discord.
- Enforce the 3-4 strike system based on previous history.
@ -94,7 +94,8 @@ If a user is found to be in violation of the [Code of Conduct](https://legal.pro
### Logging Admin Actions
Using whatever log system is currently in place, after an action is taken against a user, the administrator should log the following information:
After an action is taken against a user, the administrator should log the action in the admin log. Exceptions are made for direct permanent ban such as when banning spam bots, this is to avoid cluttering the admin log with unnecessary entries.
The administrator should log the following information:
- Add a new entry or update the entry with the following format as title: username@instance
- Provide a date and time of the action taken, and when the offending content was made. Format in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html).

35
content/docs/hidden-communities.md
View file

@ -24,6 +24,10 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- beehaw.org
- [news@beehaw.org](https://programming.dev/c/news@beehaw.org)
- [politics@beehaw.org](https://programming.dev/c/politics@beehaw.org)
- feddit.org
- [conservative2@feddit.org](https://programming.dev/c/conservative2@feddit.org)
- feddit.uk
- [uk_politics@feddit.uk](https://programming.dev/c/uk_politics@feddit.uk)
- hexbear.net
- [askchapo@hexbear.net](https://programming.dev/c/askchapo@hexbear.net)
- [chapotraphouse@hexbear.net](https://programming.dev/c/chapotraphouse@hexbear.net)
@ -34,6 +38,7 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [sino@hexbear.net](https://programming.dev/c/sino@hexbear.net)
- [the_dunk_tank@hexbear.net](https://programming.dev/c/the_dunk_tank@hexbear.net)
- lemmy.ca
- [boycottus@lemmy.ca](https://programming.dev/c/boycottus@lemmy.ca)
- [canadapolitics@lemmy.ca](https://programming.dev/c/canadapolitics@lemmy.ca)
- lemmy.ml
- [intelligence@lemmy.ml](https://programming.dev/c/intelligence@lemmy.ml)
@ -43,8 +48,15 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- lemmy.world
- [antitrumpalliance@lemmy.world](https://programming.dev/c/antitrumpalliance@lemmy.world)
- [conservative@lemmy.world](https://programming.dev/c/conservative@lemmy.world)
- [leopardsatemyface@lemmy.world](https://programming.dev/c/leopardsatemyface@lemmy.world)
- [news@lemmy.world](https://programming.dev/c/news@lemmy.world)
- [politicalmemes@lemmy.world](https://programming.dev/c/politicalmemes@lemmy.world)
- [politicalvideos@lemmy.world](https://programming.dev/c/politicalvideos@lemmy.world)
- [political_weirdos@lemmy.world](https://programming.dev/c/political_weirdos@lemmy.world)
- [politics@lemmy.world](https://programming.dev/c/politics@lemmy.world)
- [progressivepolitics@lemmy.world](https://programming.dev/c/progressivepolitics@lemmy.world)
- [toiletpaperusa@lemmy.world](https://programming.dev/c/toiletpaperusa@lemmy.world)
-
- lemmygrad.ml
- [asklemmygrad@lemmygrad.ml](https://programming.dev/c/asklemmygrad@lemmygrad.ml)
- [memes@lemmygrad.ml](https://programming.dev/c/memes@lemmygrad.ml)
@ -52,6 +64,7 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [us_news@lemmygrad.ml](https://programming.dev/c/us_news@lemmygrad.ml)
- midwest.social
- [therightcantmeme@midwest.social](https://programming.dev/c/therightcantmeme@midwest.social)
- [usa@midwest.social](https://programming.dev/c/usa@midwest.social)
### NSFW
@ -69,7 +82,11 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [streetmoe@ani.social](https://programming.dev/c/streetmoe@ani.social)
- [thiccmoe@ani.social](https://programming.dev/c/thiccmoe@ani.social)
- lemmit.online
- [lesbians@lemmit.online](https://programming.dev/c/lesbians@lemmit.online)
- [nsfw_caption@lemmit.online](https://programming.dev/c/nsfw_caption@lemmit.online)
- [retroussetits@lemmit.online](https://programming.dev/c/retroussetits@lemmit.online)
- [taboocaptions@lemmit.online](https://programming.dev/c/taboocaptions@lemmit.online)
- [tiktokthots@lemmit.online](https://programming.dev/c/tiktokthots@lemmit.online)
- lemmy.world
- [fitmoe@lemmy.world](https://programming.dev/c/fitmoe@lemmy.world)
- [nsfw@lemmy.world](https://programming.dev/c/nsfw@lemmy.world)
@ -166,17 +183,21 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [futanari@lemmynsfw.com](https://programming.dev/c/futanari@lemmynsfw.com)
- [gay@lemmynsfw.com](https://programming.dev/c/gay@lemmynsfw.com)
- [girls_in_diapers@lemmynsfw.com](https://programming.dev/c/girls_in_diapers@lemmynsfw.com)
- [girlsdrinkingcoffee@lemmynsfw.com](https://programming.dev/c/girlsdrinkingcoffee@lemmynsfw.com)
- [girlsfrontlinensfw@lemmynsfw.com](https://programming.dev/c/girlsfrontlinensfw@lemmynsfw.com)
- [girlshowering@lemmynsfw.com](https://programming.dev/c/girlshowering@lemmynsfw.com)
- [girlsmasturbating@lemmynsfw.com](https://programming.dev/c/girlsmasturbating@lemmynsfw.com)
- [godpussy@lemmynsfw.com](https://programming.dev/c/godpussy@lemmynsfw.com)
- [gonewild@lemmynsfw.com](https://programming.dev/c/gonewild@lemmynsfw.com)
- [gonewildcd@lemmynsfw.com](https://programming.dev/c/gonewildcd@lemmynsfw.com)
- [gonewildstoriesgay@lemmynsfw.com](https://programming.dev/c/gonewildstoriesgay@lemmynsfw.com)
- [gravure@lemmynsfw.com](https://programming.dev/c/gravure@lemmynsfw.com)
- [hairy_men@lemmynsfw.com](https://programming.dev/c/hairy_men@lemmynsfw.com)
- [hausofkillahxrs@lemmynsfw.com](https://programming.dev/c/hausofkillahxrs@lemmynsfw.com)
- [hentai@lemmynsfw.com](https://programming.dev/c/hentai@lemmynsfw.com)
- [hentaibdsm@lemmynsfw.com](https://programming.dev/c/hentaibdsm@lemmynsfw.com)
- [highfantasysmut@lemmynsfw.com](https://programming.dev/c/highfantasysmut@lemmynsfw.com)
- [Hotinfluencers@lemmynsfw.com](https://programming.dev/c/Hotinfluencers@lemmynsfw.com)
- [hugeboobs@lemmynsfw.com](https://programming.dev/c/hugeboobs@lemmynsfw.com)
- [ifyouhadtopickone@lemmynsfw.com](https://programming.dev/c/ifyouhadtopickone@lemmynsfw.com)
- [indiangirls@lemmynsfw.com](https://programming.dev/c/indiangirls@lemmynsfw.com)
@ -187,6 +208,7 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [leggins_gonewild@lemmynsfw.com](https://programming.dev/c/leggins_gonewild@lemmynsfw.com)
- [makenzieraine@lemmynsfw.com](https://programming.dev/c/makenzieraine@lemmynsfw.com)
- [masturbationgonewild@lemmynsfw.com](https://programming.dev/c/masturbationgonewild@lemmynsfw.com)
- [MeasuringTapesAndRulers@lemmynsfw.com](https://programming.dev/c/MeasuringTapesAndRulers@lemmynsfw.com)
- [milaamour@lemmynsfw.com](https://programming.dev/c/milaamour@lemmynsfw.com)
- [milkjugs@lemmynsfw.com](https://programming.dev/c/milkjugs@lemmynsfw.com)
- [music_playlist@lemmynsfw.com](https://programming.dev/c/music_playlist@lemmynsfw.com)
@ -210,6 +232,7 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [proneboneanal@lemmynsfw.com](https://programming.dev/c/proneboneanal@lemmynsfw.com)
- [public_flashing@lemmynsfw.com](https://programming.dev/c/public_flashing@lemmynsfw.com)
- [pussy@lemmynsfw.com](https://programming.dev/c/pussy@lemmynsfw.com)
- [rave_nsfw@lemmynsfw](https://programming.dev/c/rave_nsfw@lemmynsfw.com)
- [rearpussy@lemmynsfw.com](https://programming.dev/c/rearpussy@lemmynsfw.com)
- [rearviews@lemmynsfw.com](https://programming.dev/c/rearviews@lemmynsfw.com)
- [redhead@lemmynsfw.com](https://programming.dev/c/redhead@lemmynsfw.com)
@ -250,6 +273,8 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [realistic@nsfwaiclub.com](https://programming.dev/c/realistic@nsfwaiclub.com)
- [stable_diffusion@nsfwaiclub.com](https://programming.dev/c/stable_diffusion@nsfwaiclub.com)
- [threesome@nsfwaiclub.com](https://programming.dev/c/threesome@nsfwaiclub.com)
- reddthat.com
- [Hentai@reddthat.com](https://programming.dev/c/Hentai@reddthat.com)
### Bot Communities
@ -365,7 +390,10 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [necoarc@lemmy.smeargle.fans](https://programming.dev/c/necoarc@lemmy.smeargle.fans)
- [okbuddyretard@lemmy.smeargle.fans](https://programming.dev/c/okbuddyretard@lemmy.smeargle.fans)
- lemmy.ml
- [communism@lemmy.ml](https://programming.dev/c/communism@lemmy.ml)
- [manga@lemmy.ml](https://programming.dev/c/manga@lemmy.ml)
- lemmy.zip
- [gaming@lemmy.zip](https://programming.dev/c/gaming@lemmy.zip)
- lemy.nl
- [economie@lemy.nl](https://programming.dev/c/economie@lemy.nl)
- [films@lemy.nl](https://programming.dev/c/films@lemy.nl)
@ -378,12 +406,19 @@ Users can subscribe to a hidden community to remove the hidden effect status of
- [wetenschap@lemy.nl](https://programming.dev/c/wetenschap@lemy.nl)
- metacritics.zone
- [books@metacritics.zone](https://programming.dev/c/books@metacritics.zone)
- news.abolish.capital
- [china@news.abolish.capital](https://programming.dev/c/china@news.abolish.capital)
- [latam@news.abolish.capital](https://programming.dev/c/latam@news.abolish.capital)
- [pravda_news@news.abolish.capital](https://programming.dev/c/pravda_news@news.abolish.capital)
- [videos@news.abolish.capital](https://programming.dev/c/videos@news.abolish.capital)
- radiation.party
- [technews@radiation.party](https://programming.dev/c/technews@radiation.party)
- selfhosted.forum
- [homelab@selfhosted.forum](https://programming.dev/c/homelab@selfhosted.forum)
- [homenetworking@selfhosted.forum](https://programming.dev/c/homenetworking@selfhosted.forum)
- [main@selfhosted.forum](https://programming.dev/c/main@selfhosted.forum)
- sh.itjust.works
- [asslips@sh.itjust.works](https://programming.dev/c/asslips@sh.itjust.works)
- ttrpg.network
- [daily_rpg_blog@ttrpg.network](https://programming.dev/c/daily_rpg_blog@ttrpg.network)
- zerobytes.monster