FanFiction Library

The FanFiction Library is a Discord Server for fanfic recommendations. Feel at home in our awesome and diverse community of fanfic readers and writers! https://discord.gg/fanfictionlibrary

[transformativeworks]

"Deprecated Fandoms" Spam Bot Alert!

If you get a comment that says AO3 is "deleting works to conserve server space", that is a Spam Bot. There is no such thing as "deprecated fandom content", nor is there any limit on the number of works that can be posted to a fandom tag (regardless of how "popular" it is). AO3 has not changed its content policies. We are committed to upholding our founding principle of maximum inclusiveness of fanwork content, and will only remove content that violates the AO3 Terms of Service. While non-fanworks are not allowed on AO3, we consider both original works and real-person fiction to be fanworks. Please don't listen to anyone telling you otherwise.

Unlike the previous round of art spam, so far these comments have all been from guests, so our advice for handling them is different! We're working on filtering these comments out, and flagging them as spam is how you can help. Read more below the cut!

To help train our automated spam-checker to block similar guest comments in the future:

If the comment is on your own work: 

Note: The "Spam" button only appears when viewing a guest comment directly on your work. This is because the AO3 comment inbox is merely a copy of the work's comments – deleting a comment from your AO3 inbox does not delete the comment from the work itself.

Go directly to the comment on your work, either by clicking on the link in your email or in your AO3 inbox.

Click on the "Spam" button to mark the guest comment as spam and remove it from your work. 

That's it! You don't have to do anything else.

If you see comments like these on someone else's work: 

Feel free to let the creator know the comment is from a bot and that they should mark it as spam. 

You can also report the comments as botspam via the Policy Questions & Abuse Reports form linked at the bottom of every page on AO3. 

If you are reporting multiple guest comments, please submit only one report and include all comment links in your report description. (You can get the direct link to any comment by clicking the "Thread" button on the comment, and then copying the URL of that page.)

AO3's Policy & Abuse committee (PAC) does not pre-screen content on AO3; they only investigate if they receive a report. All reports are reviewed by PAC volunteers, who are real human beings. You don't need to worry that your or anyone else's fanworks will be taken down due to a baseless report or a mass-reporting campaign. 

If PAC were to determine that you had violated the TOS, you would receive a notification of the violation via the email address associated with your AO3 account—not via comments, social media, or any other method. 

[fanfictionlibrary01]

hi! id be interested on joing your discord server, but unfortunately your server is not accesible to me for some reason? i completed all the steps but nothing's showing up. im bookworm3691

Hi there!

Please try the link in the bio of this account. If that doesn't work, please direct message us!

[ao3org]

Errors Accessing AO3

We are continuing to investigate reports of slowness and errors when trying to load AO3, including errors saying that AO3 is down.

Refer to our status page for more information.

Posted: 19:38 UTC 01 March, 2026

[ao3org]

AO3 is currently down. We do not have an estimated return time currently. We're looking into it with one of our third-party support providers and will update when we have more information. Thank you for your patience!

Refer to our status page for more information.

Posted: 20:35 UTC 01 March, 2026

[transformativeworks]

Harassment Spam Bot Alert!

Date posted: November 12, 2025

AO3 has recently seen a rise in guest spambot comments making false accusations about work creators or other users. For example, they may claim that a particular user is discriminating against minorities, trying to hide the fact that they use AI, or are at risk of having their works stolen or deleted.

These comments often copy existing AO3 usernames in order to make their accusations seem more legitimate. They may also try to lure people onto other platforms (similar to the art commission scam), or use fake links that actually lead to pornographic images.

As always, we recommend that you do not click on any suspicious links or give your contact information to scammers. Instead, simply mark the comments as spam or report them so that the Policy & Abuse committee can remove comments left by these spambots.

Learn how to recognize them and what to do below the cut!

How to recognize this kind of spam:

The comments come from guests, not logged-in users.

The comments may start with praise for you and your writing, trying to lull you into a false sense of security. Or they may claim that you are a bad writer, trying to make you too upset to realize that the comments are fake.

The comments may accuse you or another user of promoting discriminatory beliefs, deceiving fans, or similar behaviors that might cause other people to shun or harass the accused individual. They may claim that they checked social media to find that the accused user is "brazenly sharing hateful content" or "bragging about using AI".

The comments are often pleading or angry, asking you to "stop lying to your readers", "don't remove the AI prompts from your work", or suggesting that you "consider adding more diverse characters" to "repair the trust you've lost with your audience".

So far, these comments have all been from guests. Our advice is to flag them as spam to better filter them out.

To help train our automated spam-checker to block similar guest comments in the future:

If the comment is on your own work:

Go directly to the comment on your work, either by clicking on the link in your email or in your AO3 inbox.

Click on the "Spam" button to mark the guest comment as spam and remove it from your work.

Note: The "Spam" button only appears when viewing a guest comment directly on your work. This is because the AO3 comment inbox is merely a copy of the work's comments – deleting a comment from your AO3 inbox does not delete the comment from the work itself.

If you see comments like these on someone else's work:

Feel free to let the creator know the comment is from a bot, and that they should mark it as spam.

You can also report the comments as botspam via the Policy Questions & Abuse Reports form linked at the bottom of every page on AO3.

If you are reporting multiple guest comments, please submit only one report, and include all comment links in your report description. (You can get the direct link to any comment by clicking the "Thread" button on the comment, and then copying the URL of that page.)

[transformativeworks]

As of December 2025, bots have also left guest comments harassing users by:

threatening to report you/your fic to the authorities or your employers

alleging security concerns like your email being compromised or spyware on your computer

claiming that they know your address and are going to visit you at your house

saying that you will die alone and unemployed over the holidays

What these bots claim is not true. These accusations do not mean your work will be deleted or that your accounts are insecure. We recommend that you mark these comments as spam following the instructions in our previous post.

These examples also do not represent the full range of harassment comments that you may receive. We will continue to try and keep you updated about trends; however, please note that the exact wording the bots use will continue to evolve.

If you're not sure if something is a spambot comment, you're welcome to contact Policy & Abuse for assistance. Refer to the original post for more information!

[transformativeworks]

As of January 2026, bots impersonating legitimate users have increasingly left guest comments harassing other users by:

claiming that they know where you live

alleging to have seen you in person

threatening to meet you face-to-face

saying that they posted your personal information (name, address, etc) online

What these bots claim is not true. These comments are likely intended to alarm you into replying.We recommend that you mark these comments as spam following the instructions in our previous post.

These examples do not represent the full range of harassment comments that you may receive. We will continue to try and keep you updated about trends; however, please note that the exact wording the bots use will continue to evolve.

If you're not sure if something is a spambot comment, you're welcome to contact Policy & Abuse for assistance. Refer to the original post for more information!

[ao3org]

AO3 will be down for about 15 hours starting at 08:00 UTC on January 21 (what time is that for me?) while we make some improvements to searching bookmarks and series, including:

adding the ability to search, filter, and sort bookmarks by word count

making sure bookmark search results are correct when you use tags containing letters and numbers

preventing series blurbs from listing tags that were only used on draft works

preventing series blurbs from listing tags used on restricted works for guests

updating series bookmark search so it only searches the tags on works you can access

Please follow our status page for updates.

[ao3org]

Starting 24 hours from now, AO3 will be down for about 15 hours.

[ao3org]

AO3 will be going down for about 15 hours of maintenance at 08:00 UTC (what time is that for me?).

Posted: 20:06 UTC January 20, 2026

[ao3org]

AO3 downtime starts in one hour! We expect it to last about 15 hours.

Posted: 07:01 UTC January 21, 2026

[ao3org]

15 hours of AO3 downtime have begun! We'll keep you updated on any changes.

Posted: 08:12 UTC January 21, 2026

[ao3org]

AO3 is back sooner than expected!

Posted: 18:40 UTC January 21, 2026

[fanfictionlibrary01]

AO3 is back online!

[ao3org]

AO3 will be down for about 15 hours starting at 08:00 UTC on January 21 (what time is that for me?) while we make some improvements to searching bookmarks and series, including:

adding the ability to search, filter, and sort bookmarks by word count

making sure bookmark search results are correct when you use tags containing letters and numbers

preventing series blurbs from listing tags that were only used on draft works

preventing series blurbs from listing tags used on restricted works for guests

updating series bookmark search so it only searches the tags on works you can access

Please follow our status page for updates.

[fanfictionlibrary01]

#32: FFL Febuwhump 5k Challenge

It's time to bring back a classic - with a small twist! February + Whump = Febuwhump! In this month, we want to cater to angst!

We are doing so by giving you 10 prompts to choose from. You can pick one, or ten. You can write one work or ten. The goal is to write a total amount of 5k words while using at least one prompt. If you write more than one work, then that's fine - but one prompt can only be used once, so only in one of your works. The detailed rules are available in our server's challenge post. You can sign up for the challenge and its respective AO3 Collection there!

If you want to participate in this challenge, or talk about this challenge with others, join our Discord Server!

[fanfictionlibrary01]

Discord Research Survey about AI in Discord

Discord Research is currently performing a survey asking users how they feel about AI being potentially implemented in Discord. We have already shared this in our Discord server as well as the Fanfic Communities Network Discord server, but want to share it here as well. As it is, AI and the possibility that it will be a feature in Discord, is a topic that concerns fanfic communities in my opinion. If our voices have the chance of being heard in this matter, we should use this opportunity to raise them!

The survey: https://discord.sjc1.qualtrics.com/jfe/form/SV_5BGtstVUidXadts

Edit: Just as we were about to post this, the survey apparently closed! Still posting it to share the information.

Other posts mentioning this (you'll find screenshots etc. there too): https://bsky.app/profile/pcperini.com/post/3mbzsd67kfk23

Edit 2: There's a scare going around that the survey was just a scam to grab user-infos and to hack participants' Discord accounts. The survey (we did go through it entirely before posting it anywhere) we shared did not ask for any infos like user id's, tokens, passwords, etc., so we guess that either there was a second survey someone used to actually scam, or that this is fake.

This also supports this: https://bsky.app/profile/snuffbait.bsky.social/post/3mc4fiaxo6c2t

[transformativeworks]

Harassment Spam Bot Alert!

Date posted: November 12, 2025

AO3 has recently seen a rise in guest spambot comments making false accusations about work creators or other users. For example, they may claim that a particular user is discriminating against minorities, trying to hide the fact that they use AI, or are at risk of having their works stolen or deleted.

These comments often copy existing AO3 usernames in order to make their accusations seem more legitimate. They may also try to lure people onto other platforms (similar to the art commission scam), or use fake links that actually lead to pornographic images.

As always, we recommend that you do not click on any suspicious links or give your contact information to scammers. Instead, simply mark the comments as spam or report them so that the Policy & Abuse committee can remove comments left by these spambots.

Learn how to recognize them and what to do below the cut!

How to recognize this kind of spam:

The comments come from guests, not logged-in users.

The comments may start with praise for you and your writing, trying to lull you into a false sense of security. Or they may claim that you are a bad writer, trying to make you too upset to realize that the comments are fake.

The comments may accuse you or another user of promoting discriminatory beliefs, deceiving fans, or similar behaviors that might cause other people to shun or harass the accused individual. They may claim that they checked social media to find that the accused user is "brazenly sharing hateful content" or "bragging about using AI".

The comments are often pleading or angry, asking you to "stop lying to your readers", "don't remove the AI prompts from your work", or suggesting that you "consider adding more diverse characters" to "repair the trust you've lost with your audience".

So far, these comments have all been from guests. Our advice is to flag them as spam to better filter them out.

To help train our automated spam-checker to block similar guest comments in the future:

If the comment is on your own work:

Go directly to the comment on your work, either by clicking on the link in your email or in your AO3 inbox.

Click on the "Spam" button to mark the guest comment as spam and remove it from your work.

Note: The "Spam" button only appears when viewing a guest comment directly on your work. This is because the AO3 comment inbox is merely a copy of the work's comments – deleting a comment from your AO3 inbox does not delete the comment from the work itself.

If you see comments like these on someone else's work:

Feel free to let the creator know the comment is from a bot, and that they should mark it as spam.

You can also report the comments as botspam via the Policy Questions & Abuse Reports form linked at the bottom of every page on AO3.

If you are reporting multiple guest comments, please submit only one report, and include all comment links in your report description. (You can get the direct link to any comment by clicking the "Thread" button on the comment, and then copying the URL of that page.)

[ao3org]

Bookmark creation errors

We are investigating an issue with 500 errors when creating bookmarks. Refer to our status page for more information and updates.

Posted: 05:50 UTC July 3, 2025

[ao3org]

We've found the cause and are working on a fix. We expect to have it ready in a few days.

Posted: 06:52 UTC July 3, 2025

[ao3org]

To apply the bookmark fix, we need to block traffic Cloudflare flags as bot-like, which may also impact some VPNs. If you see the AO3 maintenance mode message, please try again with your VPN off. If needed, we might need to put the site in maintenance mode for everyone.

Posted: 14:35 UTC July 3, 2025

[ao3org]

To fully fix bookmark creation, we will need to put AO3 in maintenance mode for a few hours. We'll be back once the fix has been fully applied.

Posted: 17:05 UTC July 3, 2025

[transformativeworks]

"Deprecated Fandoms" Spam Bot Alert!

If you get a comment that says AO3 is "deleting works to conserve server space", that is a Spam Bot. There is no such thing as "deprecated fandom content", nor is there any limit on the number of works that can be posted to a fandom tag (regardless of how "popular" it is). AO3 has not changed its content policies. We are committed to upholding our founding principle of maximum inclusiveness of fanwork content, and will only remove content that violates the AO3 Terms of Service. While non-fanworks are not allowed on AO3, we consider both original works and real-person fiction to be fanworks. Please don't listen to anyone telling you otherwise.

Unlike the previous round of art spam, so far these comments have all been from guests, so our advice for handling them is different! We're working on filtering these comments out, and flagging them as spam is how you can help. Read more below the cut!

To help train our automated spam-checker to block similar guest comments in the future:

If the comment is on your own work: 

Note: The "Spam" button only appears when viewing a guest comment directly on your work. This is because the AO3 comment inbox is merely a copy of the work's comments – deleting a comment from your AO3 inbox does not delete the comment from the work itself.

Go directly to the comment on your work, either by clicking on the link in your email or in your AO3 inbox.

Click on the "Spam" button to mark the guest comment as spam and remove it from your work. 

That's it! You don't have to do anything else.

If you see comments like these on someone else's work: 

Feel free to let the creator know the comment is from a bot and that they should mark it as spam. 

You can also report the comments as botspam via the Policy Questions & Abuse Reports form linked at the bottom of every page on AO3. 

If you are reporting multiple guest comments, please submit only one report and include all comment links in your report description. (You can get the direct link to any comment by clicking the "Thread" button on the comment, and then copying the URL of that page.)

AO3's Policy & Abuse committee (PAC) does not pre-screen content on AO3; they only investigate if they receive a report. All reports are reviewed by PAC volunteers, who are real human beings. You don't need to worry that your or anyone else's fanworks will be taken down due to a baseless report or a mass-reporting campaign. 

If PAC were to determine that you had violated the TOS, you would receive a notification of the violation via the email address associated with your AO3 account—not via comments, social media, or any other method. 

[fanfictionlibrary01]

New AO3 “Proactive Removal” Bot Comment Scam

There’s a new type of spam circulating on AO3 where "guest commenters" (bots) are warning authors about their fics being in danger of deletion due to being part of older/less active fandoms or being original works.

What is happening? What do we know?

A guest user will leave a generic, flattering comments at the start, praising the author’s story, saying how much they enjoyed it, or how well the characters were written. Then it shifts to a false warning, claiming AO3 is undergoing a “cleanup” of sorts of older, inactive, or “deprecated” fandoms to free up server space.

It states that if the author doesn’t remove their fic themselves, AO3 will delete it and may even ban the author’s account for non-compliance

The comment is also likely imply urgency by saying the supposed cleanup is happening soon and that the author has to take action right away.

The organization behind AO3 has issued a statement that these comments are false. AO3 is an archive, the purpose of the site is preservation and archival, so mass deletions would go entirely against their core mission.

What can you do?

Ignore it. This message is completely false. AO3 does not delete fics based on fandom activity or age, and it certainly doesn’t issue bans for not removing a fic preemptively.

The scam uses a mix of praise and threats to manipulate authors. While the positive opening can understandably disarm authors, please: do not delete your fics. Nothing will be deleted.

Report the comments as spam using AO3's reporting tools, or delete them entirely.

Stay calm. Scams like this are designed to create panic, but rest assured that your works are safe.

Inform others. Share this information with other authors and readers, especially those who may be new to AO3 or unfamiliar with how it works.

Sources:

Various posts online: Tumblr post, Reddit post 1, Reddit post 2

AO3 themself: @transformativeworks on Tumblr

Follow up on updates and new infos in the Fanfic Communities Network!

[fanfictionlibrary01]

Pridemonth 4x3 Challenge

In June, we want to host a challenge fitting for the month of pride. Whether you're a part of the community yourself or not, you are welcome to participate!

The challenge is divided into four (4) parts, with three (3) themes each. Each of the four weeks is one part.

We want you to write one work (oneshot, multichapter, etc. - your call) per week that picks up one of the three given themes of that week. You can also write 3 fanfics per week if you want; the minimum is one per week, so a total of 4 works.

If you want to participate or talk about this challenge with others, join our Discord Server!

[fanfictionlibrary01]

AO3 Data Scraped for AI Training Dataset

What is happening, and what you can do. Check for potential edits with additions at the end of the post!

What is happening? What do we know?

A user going by "nyuuzyou" on the HuggingFace platform uploaded a dataset a few days ago - containing scraped content from AO3. HuggingFace is a very popular platform and widely used for sharing machine learning and AI models/datasets. The scraped dataset includes fics, fanart, and other fanworks - all taken without permission and intended for use in training gen AI models. You can find more information in this Reddit post.

This dataset is one of several compiled from various websites—at least seven in total. While two datasets have been removed, the AO3 one was only disabled on HuggingFace. This means that it’s not downloadable at the moment but still visible. It may also return if takedown efforts end up being challenged/reversed by that user.

Key Details

Scope: On AO3, all content with work IDs between 1 and 63,200,000 has been targeted. The work ID is the number at the end of a work's URL — for example, in https://archiveofourown.org/works/12345678, 12345678 is the work ID. You can find it by simply opening the work and checking the URL in your browser’s address bar. So, if your work falls in that range and is publicly accessible (i.e., not locked and open to everyone, including guests), it’s mostly likely included in the dataset. This dataset is currently disabled on HuggingFace, but that doesn't mean it's gone. It's only a temporary takedown as of now.

Takedown notices have been issued, but this user has also uploaded the dataset to other sites after backlash and partial removal.

There are talks in the discussion forums of potentially moving this dataset to Telegram, torrents, and/or other private channels.

HuggingFace AO3 dataset page

Other distributed sites listed here (as per a Reddit comment)

Currently deleted from ModelScope

What can you do?

Should the dataset return again and you see that your work was affected: file your own DMCA or copyright takedown notice. The uploader, in their own words, "has not agreed to take down the entire repo. At this time, the scraper has agreed with taking down art from the person who owns the copyright. That means each of you will need to request a takedown."

Instructions and a sample CSV template to list your work IDs for removal are provided in this guide. You can find more details in this announcement by PaperDemon.

Lock your works! It would limit visibility to registered users only, and is a very good step to prevent scraping or unauthorized use. To lock all your works on AO3, go to “My Works,” click “Edit Works,” and select all. Then click “Edit” and check the box labeled “Only show to registered users.” Scroll down and click “Update All Works” to apply the change.

⚠️ | Final Notes:

This user has so far shown no signs of stopping and is continuing to redistribute the data across multiple sites, even after numerous takedown requests (read more here). So, we can only recommend to be cautious and beware, lock your works, feel free to make use of takedown notices if you're unfortunately affected, and spread the word to fellow creators.

Follow up on this and get the latest updated in the Fanfic Communities Network (FCN) Discord Server!

If you have more information regarding this - e.g. if works from other sites are affected too - please reach out to us in the FCN!!

Edit (2025-04-26):

The user who has scraped the works has, upon request by another person, posted a way to convert ao3 json to markdown:

https://huggingface.co/datasets/nyuuzyou/archiveofourown/discussions/170

https://gist.github.com/nyuuzyou/b2f83669ad80a22e435728245ebcdf9f

This shows us that nyuuzyou continues to show no signs of taking down the scraped works.

Edit (2025-04-28):

A user warned that even archive-locked AO3 fics were included in a scraped dataset (most likely taken while the scraper was logged in, before they were banned or switched to public-only access). Some public works were missed as well:

https://huggingface.co/datasets/nyuuzyou/archiveofourown/discussions/213#680fcdb76d9e022324a70cf1

Edit (2025-05-03):

Hey everybody, this is a bit late, but the AO3 dataset has been permanently removed from HuggingFace: https://huggingface.co/datasets/nyuuzyou/archiveofourown. While this unfortunately doesn’t prevent it from being shared elsewhere (like torrents) nor does it guarantee any deletion of past downloads and whatnot, having it taken down from a major platform like HF is still a significant step forward. (There is more info about other sites on PaperDemon.)

So please don’t be disheartened—every action counts, and this shows that pushing back and filing DMCAs and copyright notices as appropriate does make a difference. We’ll certainly keep an eye out for more info and post updates here, but thank you again to everyone who helped report, spread the word, or supported the effort. Keep reading, keep writing. ♥️

[fanfictionlibrary01]

Check out the newest edit!

[fanfictionlibrary01]

Comment Challenge (May 2025)

We have a new Challenge for you! This time, the challenge is for writers and readers alike: support your favourite fanfics and fanfic authors by leaving a comment! Often times we want to show our appreciation to our favourite author, but don't know what to say - but as every author will tell you, that's not important, because every nice comment is a good comment!

Rules/Goals:

Within the month of May, leave at least 15 different comments

Be nice- the goal is to appreciate and support, not to bash others

Don't give unsolicited concrit- while well meant, it still includes critique, and some authors might feel discouraged by it. So only give concrit if the author states they are fine with it/ want it!

There are no rules about the length or elaborateness of the comments- no matter how unsure or awkward you feel with leaving comments, the important part is that you do! A small "I liked this, thanks!" is perfectly fine.

If you want to talk about this challenge with others, let yourself be inspired by comments that others have written, and/or track your progress, join our Discord Server!

[fanfictionlibrary01]

AO3 Data Scraped for AI Training Dataset

What is happening, and what you can do. Check for potential edits with additions at the end of the post!

What is happening? What do we know?

A user going by "nyuuzyou" on the HuggingFace platform uploaded a dataset a few days ago - containing scraped content from AO3. HuggingFace is a very popular platform and widely used for sharing machine learning and AI models/datasets. The scraped dataset includes fics, fanart, and other fanworks - all taken without permission and intended for use in training gen AI models. You can find more information in this Reddit post.

This dataset is one of several compiled from various websites—at least seven in total. While two datasets have been removed, the AO3 one was only disabled on HuggingFace. This means that it’s not downloadable at the moment but still visible. It may also return if takedown efforts end up being challenged/reversed by that user.

Key Details

Scope: On AO3, all content with work IDs between 1 and 63,200,000 has been targeted. The work ID is the number at the end of a work's URL — for example, in https://archiveofourown.org/works/12345678, 12345678 is the work ID. You can find it by simply opening the work and checking the URL in your browser’s address bar. So, if your work falls in that range and is publicly accessible (i.e., not locked and open to everyone, including guests), it’s mostly likely included in the dataset. This dataset is currently disabled on HuggingFace, but that doesn't mean it's gone. It's only a temporary takedown as of now.

Takedown notices have been issued, but this user has also uploaded the dataset to other sites after backlash and partial removal.

There are talks in the discussion forums of potentially moving this dataset to Telegram, torrents, and/or other private channels.

HuggingFace AO3 dataset page

Other distributed sites listed here (as per a Reddit comment)

Currently deleted from ModelScope

What can you do?

Should the dataset return again and you see that your work was affected: file your own DMCA or copyright takedown notice. The uploader, in their own words, "has not agreed to take down the entire repo. At this time, the scraper has agreed with taking down art from the person who owns the copyright. That means each of you will need to request a takedown."

Instructions and a sample CSV template to list your work IDs for removal are provided in this guide. You can find more details in this announcement by PaperDemon.

Lock your works! It would limit visibility to registered users only, and is a very good step to prevent scraping or unauthorized use. To lock all your works on AO3, go to “My Works,” click “Edit Works,” and select all. Then click “Edit” and check the box labeled “Only show to registered users.” Scroll down and click “Update All Works” to apply the change.

⚠️ | Final Notes:

This user has so far shown no signs of stopping and is continuing to redistribute the data across multiple sites, even after numerous takedown requests (read more here). So, we can only recommend to be cautious and beware, lock your works, feel free to make use of takedown notices if you're unfortunately affected, and spread the word to fellow creators.

Follow up on this and get the latest updated in the Fanfic Communities Network (FCN) Discord Server!

If you have more information regarding this - e.g. if works from other sites are affected too - please reach out to us in the FCN!!

Edit (2025-04-26):

The user who has scraped the works has, upon request by another person, posted a way to convert ao3 json to markdown:

https://huggingface.co/datasets/nyuuzyou/archiveofourown/discussions/170

https://gist.github.com/nyuuzyou/b2f83669ad80a22e435728245ebcdf9f

This shows us that nyuuzyou continues to show no signs of taking down the scraped works.

Edit (2025-04-28):

A user warned that even archive-locked AO3 fics were included in a scraped dataset (most likely taken while the scraper was logged in, before they were banned or switched to public-only access). Some public works were missed as well:

https://huggingface.co/datasets/nyuuzyou/archiveofourown/discussions/213#680fcdb76d9e022324a70cf1

Edit (2025-05-03):

Hey everybody, this is a bit late, but the AO3 dataset has been permanently removed from HuggingFace: https://huggingface.co/datasets/nyuuzyou/archiveofourown. While this unfortunately doesn’t prevent it from being shared elsewhere (like torrents) nor does it guarantee any deletion of past downloads and whatnot, having it taken down from a major platform like HF is still a significant step forward. (There is more info about other sites on PaperDemon.)

So please don’t be disheartened—every action counts, and this shows that pushing back and filing DMCAs and copyright notices as appropriate does make a difference. We’ll certainly keep an eye out for more info and post updates here, but thank you again to everyone who helped report, spread the word, or supported the effort. Keep reading, keep writing. ♥️

[fanfictionlibrary01]

FFL AU Songfic Challenge

April 2025

In this challenge - a variation from our Sonfic Challenge from exactly a year ago - you get 10 songs, each representing a certain AU type in the world of fanfiction. Your job is to write a songfic that uses one of the songs for your fanfic. (If you want to write a fanfic for each song, you can ofc write 10 fanfics! We're not stopping you :wink:) Since all songs are instrumental, the interpretation is very free, since music affects everyone differently. But: You need to represent your interpretation of the chosen song as best as possible! Alternatively, you can use the son's title or a part of it as a prompt, and write for that, or do that and write for the song itself! Your fanfic must be in the AU setting that the respective song represents though!

The posting for this challenge is from April 7th to April 20th.

You will find the prompts in our Discord Server ;) You can join under https://discord.gg/fanfictionlibrary !

[fanfictionlibrary01]

The posting time for our challenge has begun! 😍🎉

[fanfictionlibrary01]

Do I need to write fan fiction in order to join the server?

Not at all!

Whether you're a fanfic reader or writer, an oldie (/fond) or newbie (also /fond) in fanfics - for you to join our server, you need to be interested in fanfics, that's all 🤗