*Grown folx zone🔞* I Tumblr while Black every day. 🙋🏽♀️He's a spicy, award-winning ‼️🫶🏽 Gemini nerd, a helluva actor, a DJ who will work for a pint of Guinness (or Murphy's), an iconique Versace model, and so much more. I swoon over him and his characters here, and Peaky Blinders in general. My other fandom blogs: @brownskinsugarplum76 (Led Zeppelin) and @iggy-licious (Iggy Pop). Fics on these blogs, and @goldd-pineapple for aesthetics. Here? Check my pinned master list or search # fkmarrycilllibrary.
Tumblr ate my original post, which only exists as a reblog that I can't edit. 😫😭😭😭 So, welcome to take two 🎬🎬…
Here are my stories for Cillian and some of his characters, also tagged #fkmarrycilllibrary. The most recent stories are listed first for each category.
These are mostly, but not all, smutty reads, noted by this handy symbol: 🔞.
I typically write one shots and drabbles, rather than chapter stories. Character stories are pretty true to canon, unless otherwise specified. Unless otherwise specified, RPF stories are AU in the same way--Cillian is single, with no kids.
I tend to not take requests, only because I am not the fastest of writers, and I don't want to leave anyone hanging. 🙃 But do send an idea if you have one--I've sometimes dropped everything to pursue a juicy idea. I'm chaotic like that. 😉
For more of my work, check out @brownskinsugarplum76 for Robert Plant (Led Zeppelin) stories, and @iggy-licious for Iggy Pop stories. We love a niche music fandom. 🥰
Last, please check for my perpetual reading list by searching #cillianwriterfam .
Thanks for stopping by and reading! Please feel free to comment or reblog! ❤️
Cillian RPF
🔞One Shot: Weekend in Bed
🔞One Shot: Pre-Gaming (Cillian x reader)
Cillian kiss drabble
Tommy Shelby, Peaky Blinders
🔞One Shot: A Small Favor (Tommy x reader)
🔞One Shot: At Ease (Tommy x OC)
One Shot: The Promise of Spring (Tommy x Lizzie)
🔞One Shot: Bad Things (Tommy x May Carleton)
Jackson Rippner, Red Eye
🔞Touch Me Tease Me Collection, Part 1 (Jackson x OC)
This tool is optional. No one is required to use it, but it's here if you want to know which of your AO3 fics were scraped. Locked works were not 100% protected from this scrape. Currently, I don't know of any next steps you should be taking, so this is all informational.
Most people should use this link to check if they were included in the March 2025 AO3 scrape. This will show up to 2,000 scraped works for most usernames.
Or you can use this version, which is slower but does a better job if your username is a common word. This version also lets you look up works by work ID number, which is useful if you're looking for an orphaned or anonymous fic.
If you have more than 2,000 published works, first off, I am jealous of your motivation to write that much. But second, that won't display right on the public version of the tools. You can send me an ask (preferred) or DM (if you need to) to have me do a custom search for you if you have more than 2,000 total works under 1 username. If you send an ask off-anon asking me to search a name, I'll assume you want a private answer.
In case this post breaches containment: this is a tool that only has access to the work IDs, titles, author names, chapter counts, and hit counts of the scraped fics for this most recent scrape by nyuuzyou discovered in April 2025. There is no other work data in this tool. This never had the content of your works loaded to it, only info to help you check if your works were scraped. If you need additional metadata, I can search my offline copy for you if you share a work ID number and tell me what data you're looking for. I will never search the full work text for anyone, but I can check things like word counts and tags.
Please come yell if the tool stops working, and I'll fix as fast as I can. It's slow as hell, but it does load eventually. Give it up to 10 minutes, and if it seems down after that, please alert me via ask! Anons are on if you're shy. The link at the top is faster and handles most users well.
On mobile, enable screen rotation and turn your phone sideways. It's a litttttle easier to use like that. It works better if you can use desktop.
Some FAQs below the cut:
"What do I need to do now?": At this time, the main place where this dataset was shared is disabled. As far as I'm aware, you don't need to do anything, but I'll update if I hear otherwise. If you're worried about getting scraped again, locking your fics to users only is NOT a guarantee, but it's a little extra protection. There are methods that can protect you more, but those will come at a cost of hiding your works from more potential readers as well.
"I know AO3 will be scraped again, and I'm willing to put a silly amount of effort into making my fics unusable for AI!": Excellent, stick around here. I'm currently trying to keep up with anyone working on solutions to poison our AO3 fics, and I will be reblogging information about doing this as I come across it.
"I want my fics to be unusable for AI, but I wanna be lazy about it.": You're so real for that, bestie. It may take awhile, but I'm on the lookout for data poisoning methods that require less effort, and I will boost posts regarding that once I find anything reputable.
"I don't want to know!": This tool is 100% optional. If you don't want to know, simply don't click the link. You are totally welcome to block me if it makes you feel more comfortable.
"Can I see the exact content they scraped?": Nope, not through me. I don't have the time to vet every single person to make sure they are who they say they are, and I don't want to risk giving a scraped copy of your fic to anyone else. If you really want to see this, you can find the info out there still and look it up yourself, but I can't be the one to do it for you.
"Are locked fics safe?": Not safe, but so far, it appears that locked fics were scraped less often than public fics. The only fics I haven't seen scraped as of right now are fics in unrevealed collections, which even logged-in users can't view without permission from the owner.
"My work wasn't a fic. It was an image/video/podfic.": You're safe! All the scrape got was stuff like the tags you used and your title and author name. The work content itself is a blank gap based on the samples I've checked.
"It's slow.": Unfortunately, a 13 million row data dashboard is going to be on the slow side. I think I've done everything I can to speed it up, but it may still take up to 10 minutes to load if you use the second link. It's faster if you can use desktop or the first link, but it should work on your phone too.
"My fic isn't there.": The cut-off date is around February 15th, 2025 for oneshots, but chapters posted up to March 21st, 2025 have been found in the data so far. I had to remove a few works from the dataset because the data was all skrungly and breaking my tool. (The few fics I removed were NOT in English.) Otherwise, from what I can tell so far, the scraper's code just... wasn't very good, so most likely, your fic was missed by random chance.
Thanks to everyone who helped with the cost to host the tool! I appreciate you so so so much. As of this edit, I've received more donations than what I paid to make this tool so you do NOT need to keep sending money. (But I super appreciate everyone who did help fund this! I just wanna make sure we all know it's all paid for now, so if you send any more that's just going to my savings to fix the electrical problems with my house. I don't have any more costs to support for this project right now.)
(Made some edits to the post on 27-May-2025 to update information!)
Gonna pass this around once more with an addition!
Here is a tool that can be used to poison your current and future AO3 fics if you would like to reduce the chances that your work will be useful to scrapers in the future. You can thank the lovely @all-hail-trash-prince for writing the code and for making it more accessible to those who don't know how to run code.
Here is me doing a very brief runthrough on the current version of the tool (as of this reblog).
I'm not saying you have to use this tool. I'm just boosting it as one potential path forward for those who want to reduce the quality of their fics for future scrapers without reducing the quality for readers on AO3, including those using screen readers to narrate your fics. You can choose to use it for zero fics, one fic, some of your fics, or all of your fics. Entirely up to you if you want to do this.
Poisoning your fics now does not undo nyuuzyou's scrape. The data, while a little less accessible now, is still out there in a few locations. There's no undoing that, and there will always be a copy of the fics scraped by nyuuzyou. Poisoning your fics is a method to protect you from future scrapes. The protection doesn't reduce the risk that you will be scraped, but it highly increases the chance that the scraper will not be able to use your fic for anything useful, including AI training. There's no surefire way to protect your fics short of not sharing them at all, but this tool provides the best balance I've seen of protecting them from unwanted use and still allowing you to share with real readers.
And once more for anyone who hasn't caught it yet: I am not directly affiliated with AO3. This is a third party tool that you may choose to use or may choose to ignore.
Happy birthday to our intelligent, talented, gorgeous fandom bby. I respect his talent, I adore the adventurousness he displays as a creative person, and I admire his conviction on what makes a well-lived life, and his desire to defend it at all costs. His music taste is chef's kiss, too, as is his low-key fashionisto vibe. He's the spicy, nerdy weirdo that we deserve. 😌 I'm glad I got into him, and I'm glad I found my Cillian buddies here on Tumblr. 🫶🏽
Donatella Versace stepping down truly marks the end of an era.
She was one of the first major fashion figures to embrace Lewis Hamilton, long before he was in his fashion bag, inviting him to events, dressing him, and even attending the 2017 Fashion Awards together.
