Bougie Girl With Self Esteem To The Sun

I’m 21. I’ve been using Wattpad since I was 11/12. Same thing for Webtoon, the company that I believe sponsors or is partnered with Wattpad, considering some webtoons have novel versions of the comics on Wattpad. If you have any experience with Webtoon and how they censor or regulate content, this isn’t surprising. Webtoon is notoriously horrible when it comes to censorship of anything involving sex or anything mature. I’m talking about forcing artists to censor a character’s ass with fog or steam, full body nudity isn’t really allowed even if it’s sexual, censoring knives, etc.

In my personal opinion, I think Wattpad updated their content guidelines so it more closely matches Webtoon’s content guidelines. Cus, I looked at Webtoon’s and the words they used for some sections are extremely similar to Wattpad’s. I wouldn’t be surprised if Webtoon was a factor in why the guidelines changed. Wattpad has already begun to host novelizations of some Webtoons like the Cursed Princess Club, and it wouldn’t be too shocking if Webtoon was like “Hey, you need to clean up your platform. We don’t want all that smut on it while you’re hosting our webtoon novels.”

Webtoon guidelines are on the left, and Wattpad is on the right.

Again, I wouldn’t be surprised if more novelizations of webtoons come onto Wattpad, and vice versa. They already have a Wattpad profile and a reading list named this:

ao3 doesn't have an app because for it to have an app, appstore will have to approve it first. and if, hypothetically, ao3 needs appstore to approve it, it will also have to abide by appstore's pro-censorship stance and start banning dark and taboo fics, which is against its own core principle of being completely against censorship.

ao3 doesn't need an app. it works more than fine without an app. the reason ao3 can allow dark and taboo fics, the reason it can allow the most disgusting and shockingly vile fics, and be completely against censorship is because it doesn't need appstore's approval. it stands on its own as a non-profit organization with functioning site and a team of lawyers protecting its platform, its users, and every single fanwork on its platform.

everybody say thank you ao3

Some AAVE speakers pluralize 'child' as 'childrens'. People get racist about this ("It's already plural!"), but 'children' actually comes from Middle English speakers doing the same thing: slapping their plural marker on word already pluralized by an extinct plural marker.

To oversimplify: in Old English, 'childer' ('ċildra') was the plural of 'child' ('ċild'). Middle English developed an '-en' plural marker, which we see in 'oxen'. Instead of updating to 'childen', people slapped their preferred '-en' onto the end of 'childer' - so now we have 'child-er-en'. AAVE carries on this tradition with 'child-er-en-s'.

"Pure" language is just impurity obscured by the passage of time.

1. Unpublishing all chapters except an announcement chapter with a link to your alt fanfic site and/or your ao3 username.

1. Unpublishing all chapters except an announcement chapter with a link to your alt fanfic site and/or your ao3 username.

While you can do whatever you want on AO3, it's a lot less common to post the equivalent of oneshot books there. (And we definitely don't call our works "books", regardless of format.)

The reason is that AO3 has much more comprehensive search capabilities. It's far easier to drill down through the metadata to find every single work ever posted with tags X and Y and Z and this ship type and that warning. There's no algorithm. Popularity doesn't matter unless you're sorting by kudos, which is not the default.

So if you strongly prefer to repost a oneshot book as-is, you do you. It's not against the rules.

But if you want your work found by AO3 users, it may make more sense to post each chapter as its own work with headers reflecting the specific ship or tropes in that single section. Having only the most relevant tags on that part makes it way easier to find.

If I love the trope in oneshot #1 but hate the trope in oneshot #3, I'm going to miss all of your work if it's posted as one single thing because I'll be using the exclude filters.

It's fine for a single work to be 100 words (or even 0 words if it's embedded fan art or a fanvid or AMV). Related works can be grouped via series, and the same work can be in multiple series. Related works can also be grouped in a collection or via very specific tags nobody else would be likely to copy. You can also bookmark works and put the bookmark into a collection.

1. Unpublishing all chapters except an announcement chapter with a link to your alt fanfic site and/or your ao3 username.

I don't know why did i do this, but here is the[ code ], I stayed up late working on this, so I hope there aren’t any issues.

mobile:

desktop:

symbols and pngs:

what people without a pfp (1) and guests (2) get as pfp:

​I’ve heard a rumor online that sometimes supermarket strawberries look beautiful but aren't very sweet. Is that true where you live? 🍓

​Anyway, I hope this skin brings 100% strawberry sweetness to your AO3! For this update, I also made custom bookmark icons. I think they look like cute little stamps on the work page! Go ahead and give your favorite fics a special strawberry seal of approval! 🧺✨ Hope you like it!

​🛠️ Installation Guide

​I have uploaded the codes to my GitHub. You will find two files there:

​🍓base: This file contains the foundation code (Base Code).

​🍓🧺✨: This file contains the strawberry color theme code (Theme Code).

​Here is how to use them:

​Step 1: Create the Base Skin

​Open the 🍓base file on my GitHub and copy all the code.

​On AO3, create a new site skin. (You can name it whatever you like, as AO3 skin names must be unique for everyone).

​Paste the copied code into the CSS box.

​Scroll down to the "Advanced" section and check the box for "Parent Only".

​Click "Submit" to save.

​Step 2: Create the Color Theme Skin

​Open the 🍓🧺✨ file on my GitHub and copy all the code.

​On AO3, create another new site skin (again, name it whatever you prefer).

​Paste the copied code into the CSS box.

​Scroll down to the "Advanced" section again.

​Find "Parent Skins" and click the "Add parent skin" button.

​In the input field that appears, search for the exact name you gave to your Base Skin in Step 1, and select it.

​Click "Submit" to save and apply.

​⚠️ Important Note:

If you are using Google Chrome and encounter issues adding the parent skin (e.g., the search box doesn't respond), please try switching to a different browser, such as Microsoft Edge, to complete this step.

​📝 Notes:

​English is not my first language, so please forgive any awkward phrasing or errors in my explanation.

​The image materials used to build this skin were found online. This is a completely free, passion project meant for sharing, and will never be used for any profit.

​The fanfictions shown in the preview images belong entirely to their respective amazing authors. I only used them to demonstrate the skin layout.