Writing is often filled with tropes – preconceived ideas that both the writer and the reader bring to the story. If I say “Fairy Godmother,” you probably come up with an image of a nice older woman, perhaps plump and Disney-esque. If I say, “Vampire,” you probably imagine a pale man with fangs and a big black cape.
Those are tropes; kind of like stereotypes, but much broader in that tropes can be about places, events, genres of writing. If I say, “Christmas,” you probably picture a lot. of the same images as I would.
For this assignment we were asked to redefine a fairy tale trope of our choice. I chose trolls.
Everyone who tried to visit the lakeside town of Midland had to pass over the troll bridge. Everyone knew the troll didn’t like people entering Midland. No one understood why.
The studious troll was pretty close to finishing his Ph.D. dissertation on the pending ecological collapse of his lake. Not being allowed to own property in Midland – thanks to a speciesist town council – forced him to live outdoors.
He’d discovered that the curve of the stone bridge best amplified the free wifi from the local pub. So there he lived, trying to protect his research from further contamination, from the annual influx of drunk tourists.
First he’d tried stopping traffic and handing out pamphlets at the bridge, but the illiterate tourists just crumpled them and chucked them all along the shoreline.
Then he’d tried iconographic ‘no fishing’ signs at all the popular fishing holes. They’d been vandalized.
So, now he played to the stereotypes. Hey, if they’re gonna label you an angry troll anyway, why not be one?
Be among the first to be informed when TAU CETI comes out. Just sign up for our newsletter and as an added thank you, we’ll send you a free, subscriber-exclusive collection of short stories.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
You can find more information in our Cookie Policy and .