alias_sqbr

I was tagged by anghraine. Do it if it looks fun!
( Read more... )

How to use html to create a spoiler tag (108 words) by sqbr
Chapters: 1/1
Fandom: No Fandom
Rating: General Audiences
Warnings: No Archive Warnings Apply
Additional Tags: Meta, Guide, tutorial, HTML
Summary:

Here's an example of the sort of 'cut' you can create with this html:

Content note: CONTAINS A SURPRISE!

BOO! IT'S ME, THE HIDDEN DETAILS!!

I wrote this aimed at people wanting to add spoiler cuts to AO3 summaries etc, but the same code works on dreamwidth and a bunch of other places.

NOTE: Turns out the content under the cut is displayed in full to subscribers. Good thing I tested it before posting anything people might find upsetting!

I saw someone post a screenshot tutorial on twitter, thought about testing it then writing an image description, and then went, wait, now that I've written this test work, why not just use it as an example for other people?

It's the same code I already posted about that works on dreamwidth, but it hadn't occured to me you could use it on the AO3, and apparently they only just implemented it for summaries.

Meme from shadaras: How big are your fandoms? List them in order of the number of works posted for them at AO3.
( Read more... )

Via sanguinity and muccamukk, an AO3 meme using NUMBERS to find your 'average' works on the ao3.

( Method )

( My results )

fictional_fans posted: Singular Within Multitude: Creating a Personal Archive on AO3

I'm not sure I'll do this but it hadn't occurred to me as an option, and offers a bit more control.

An Archive Of Our Own (AO3) is an archive for fanworks. Any work posted there needs to be given a title, a fandom, a rating (from "General Audiences" to "Explicit", with the option to pick "No Rating"), and warnings. Here's the AO3's guide to using warnings, note that it deals with some possibly triggering subjects.

Note these two cases in particular:

Choose Not To Use Archive Warnings
Use this if warnings may apply but you don't want to use them.

No Archive Warnings Apply
Use this if AO3 warnings don't apply to your content

These are not the same! But the specific differences can be muddy.

From A Moving Forward PSA for everyone using AO3 by kkglinka:

“No Archive Warnings Apply” means the fic is PG13 at worst, probably fluff, totally safe.

“Choose Not to Use Archive Warnings” is the polar opposite. It’s a glaring Enter at Your Own Risk billboard. It means: a shitload of warnings apply but I ain’t telling because this story requires shock value. It’s very important to read the author’s notes for those fics because they might be using that older format from above.

So I thought this was roughly true, if a bit over-simplistic, then decided to do some rough poking at the AO3, and now I don’t think it’s true at all: as far as I can tell, while works marked "No Archive Warnings Apply" are overall lower rated and "safer" than works marked "Creator Chooses Not To Use Warnings", the difference is small enough to not be much of a useful guide to the content of any given fic.

For example: using the AO3 search, 14% of fic tagged "No Archive Warnings Apply" are explicit, while 16% of those tagged "Creator Chooses Not To Use Warnings" are. A difference, but not a hugely significant one. And under the cut I have a bunch of examples of dark topics which are about half as common amongst "No Archive Warnings Apply" works as "Creator Chooses Not To Use Warnings" ones: a significant difference, but not large enough to make "No Archive Warnings Apply" safe.

My goal isn't to criticise kkglinka, I agreed with them until I ran the numbers (and it is of course possible that I somehow ran the numbers wrong) My goal is to encourage an accurate understanding of how AO3 users use these tags and warnings, and also to have fun playing with numbers because I am a nerd. In the likely event that my own analysis is flawed, I would be interested to hear about it.

And I do agree with kkglinka's final point: if you see something marked "Creator Chooses Not To Use Warnings" you should check the notes and tags very carefully, especially if there's subjects you find triggering. From broader fandom context I suspect kkglinka is pushing back against the situation where someone posts a worked marked "Creator Chooses Not To Use Warnings" that contains major character death or whatever, and a reader(*) gets angry because they think "Creator Chooses Not To Use Warnings" means "No Archive Warnings Apply". And it does not! It means the work could contain literally anything, and if you can't deal with that you shouldn't read it.

So I guess my point is that readers should also check the notes and tags for works marked "No Archive Warnings Apply". If a work marked that way contains major character death etc then yeah, you have a right to be pissed off. But a whole bunch of other stuff is fair game, including porn and other "unsafe" content. Always step carefully.

Content Note: discussion of triggering tags/content
( More rambling along the same lines )

There's been a very Strikethrough-esque purging of accounts on tumblr recently. Apple removed the app because there was too much Inappropriate Content so tumblr used a highly unreliable automated process to remove accounts, and enough people have been hit that's there's a general air of "maybe this is going to be it for me and/or the site".

People have been posting links to their other social media, so! From most to least used:
I'm here(*) on dreamwidth at alias_sqbr and sqbr
Twitter: sqbr
Mastodon: sqbr at im-in.space
Pillowfort: sqbr

And while I'm listing things:
Tumblr: alias-sqbr and sqbr
AO3: sqbr
DeviantArt: sqbr

I also have Serious Game Developer etc accounts but I don't publicly link those to this pseudonym.

(*)Which is to say, I am making this post on dreamwidth, but this line is aimed at those reading the livejournal and tumblr crossposts, because anyone reading on dreamwidth probably knows my dw username already ;)

So I am finally getting around to fixing the NINETY OR SO broken images on my AO3 account. (THANKS PHOTOBUCKET) I settled on Nickpic as a new image host, rather arbitrarily. I've been getting random inconsistent upload errors so I'm not sure I'd rec them, they better not cause me to have to upload everything again.

To make it all feel less like yak shaving(*) I decided to go through from the start and fix up all my old works, since there's a growing list of minor issues like broken formatting I've been meaning to poke at. I am currently one and a half pages in, of nine (eg at about 30 works of 180 /o\)

It's interesting going through everything in chronological order. Right now I'm at April 2010 and past!me still hasn't learned how to format dialogue, but has sort of gotten the hang of chins. Figuring out how long legs are is still a ways in the future. (THEY'RE SO LONG)

A lot of this stuff is not relevant to modern fannish interests (and also...not very good) but I'm going to intermittently post old stuff to tumblr if I think people might enjoy it. I'm still pretty happy with Mafdet Slayer of Serpents, a Stargate comic I did about a Gu'ald cat. Though it's definitely from my pre-understanding-chins period.

(*)A software term I learned from Cam, referring to a large, frustrating and ultimately pointless task. It's easier to spell than sisyphean :)

I love these things, so many numbers! Via torachan, html from Kate.
( Read more... )

Top works by hitcount meme. Some surprises this year!
( Read more... )