Showing posts with label short story. Show all posts
Showing posts with label short story. Show all posts

Monday, 5 December 2011

Real-time Fiction: a Guide


S.Cornish: Time Flies 


This is frontier territory; beyond that line of jagged prose there be dragons.

Using tweets to drip feed the narrative directly to the reader is pretty novel. This is a strange and unfamiliar format, even to me.  Follow it as a reader and you catch the story, blink and you’ll have to scroll back to catch up. Twitter isn’t the medium to simply deliver an existing piece of prose fiction line by line, no-one will want to read that. As a writer it takes some planning to write a story that unfolds in real-time, but it doesn’t need to be difficult or intimidating to do.

What makes any story a good story is an interesting premise, strong believable characters and an engaging narrative. Put this across as a succession of tweets that unfold the story in a fictional real-time and you have a temporal tale.
When setting out to write a temporal story there are a few things worth thinking about.

1. Temporal fiction lends itself to the first person, present tense written as if the narrator/character is sending the tweets. 
2. Give it some structure. Like any story, a beginning establishes the characters and setting, the middle moves the story on from the driving incident/motive and the end brings it to a conclusion along with any consequences. 
3. The story will unfold over several hours or days, so try to pace the delivery of tweets to allow the story arc to work with that, making sure interest is maintained even on the days that are leading up to the major bits of drama.
4. In some respects temporal fiction will work more like a film script or radio play than a short written story. It is worth writing a treatment beforehand to help plan how the story will unfold and how long it will take to do so.
5. Making short plot notes also helps as these are already part way to being tweets in their own right.
6. Note down any extra foibles that occur to you about the characters or situation, these can often be worked into the main story arc for additional interest/drama/comedy.
7. Most likely any dialogue will need to be reported, unless it is addressed directly to the reader. But it isn't the only way, be inventive.
8. Suspension of disbelief should be maintained: if the story had been relying on the character sending tweets on their phone and they get tied up: how are they going to be able to send more tweets?
9. Twitter is a restrictive medium; there are only 140 characters for each tweet (both MS Word and Apple Pages will give a useful character count of any chunk of text you select), avoid having to break a segment of story into more than one tweet. But if it can’t be helped then try to use a device like an interruption to make this seem more plausible.
10. Short snappy delivery of the narrative as reports or recounts is easier to write and read.
11. A one day story may need as many tweets as a five day story, try ensuring there is a tweet every few hours to keep the audience interested. 

If you have any other ideas or thoughts on using twitter as a storytelling medium please comment.
These pointers aren’t rules, they are just things learnt from messing round with the format,
an experimental format. With it, anyone can be a ground-breaker and make up the rules as they go along. Go on, surprise us all.


@TemporalTales is looking for story submissions by new or established writers that can be tweeted over a period of one to fourteen days. Please email stories (.doc .txt or .pages format) to:
muse (at) simoncornish.com
(I’ve used (at) instead of @ to defeat the bots. I’m sure you can figure out how to reassemble it). 

Sunday, 4 December 2011

Temporal Tales




Having got the bit between my teeth with this whole idea of streaming real-time stories through twitter, I've now created a new twitter channel @TemporalTales that will be dedicated to the format, but how is this new way of telling and distributing short fiction through twitter even going to work?


No, the wheel has not been reinvented, experiments in real-time storytelling, like Jeremy Bushnell's Imaginary Year, have been created before, but the demands of the twitter medium calls for a new format to put over the stories in a much more immediate way.
After the successful tweet broadcast of the Bad Hair Daze story in April 2010, I started writing a Christmas story that would be broadcast in December of that year, but workloads being what they are, the broadcast was delayed until this year and @HoBloodyHo will begin tweeting on the 15th December. I’ve been excited getting it all ready and working out the bugs to be able to schedule the tweets. Making a new twitter account for each story has worked for these first two pilot stories, but I’ve realised that to broadcast more stories on a regular basis needs a different solution. Having a tailor made twitter stream for a story looks great, but having to build up a following prior to the story launching is hard work, and most of that following will drift away once the story is over. The idea of a dedicated stream is a much more attractive option, allowing stories to be broadcast back to back (if I can get enough submissions). @TemporalTales has been created to do just that.

The channel is intended to be a platform through which new and established writers can show their ingenuity and writing talent in what is effectively a new format (in the same way that flash fiction is a new format) of real-time storytelling. It also allows links to blogs, books and websites to be placed in the credits that can directly promote the writer to a receptive audience. A supporting blog-based website with an archive will provide additional information about the stories and the writers.
The Temporal Tales twitter account is already up and ready for new followers and will start delivering tales as a channel in the new year. As a test it will be mirroring the tweets from the @HoBloodyHo story, but with a time delay so that the tweets can go at at Eastern Standard Time. The Temporal Tales website and blog are still being designed at the moment, but will up and running before @TemporalTales begins tweeting in anger.

In the meantime we are looking for submissions for new and imaginative stories to deliver when broadcasting begins. Please email stories in .doc or .pages format including a brief outline of what it is about to:

muse (at) simoncornish.com
(I’ve used (at) instead of @ to defeat the bots. I’m sure you can figure out how to reassemble it). 

As a guide, stories should be from one day to two weeks in output duration. Please bear in mind the constraints of the medium when submitting stories, @BadHairDaze is an existing example of how a real-time story has worked. More details about @HoBloodyHo can be found here.

Friday, 16 April 2010

The Twitter Short Story -delivery in progress



This is my second blog about twitter, it's getting to be a habit. If anyone has been following my twitter feed, they will be aware that I'm in the process of delivering a story, Bad Hair Daze, via twitter. Yes, I'm doing it to promote my work, come on, I'm not that innocent, but I'm also doing it because I enjoy playing with new formats and exploring how they can be used. (It's how I got into writing software reviews for magazines like Video Age). The question is, could twitter be a viable delivery tool for short, or episodic storylines, or will it remain the preserve of Haiku's and links to news items?

I'm now into my second day as a twitter novelist (Okay, short fiction writer), so far it could best be described as a learning experience. Bad Hair Daze is a romantic comedy, following the day to day life of Zel, a 24 year old features writer on Hair Magic Magazine. The story is written in a form of diary style, with Zel updating the reader about the events in her day in real-time, as a series of tweets. As a writer this has thrown up a number of challenges, the most obvious being twitter's 140 character limit for each tweet. Frustratingly, this also includes spaces, so lots of short words can be just as bad as long ones. The art I needed to learn was to make each tweet: stand alone –without the need to run onto a second–, still have meaning in itself, and still be able to drive the story forward. The second issue I needed to look at was time. Each tweet must be sent at a particular time, to coincide with Zel's day and the events that are apparently unfolding in real-time. For me, apart from that fact that it plays havoc with my concentration, it has meant getting creative with the means of sending tweets. Normally I can use the computer to send tweets, but to tweet when not at home has necessitated the use of my phone to send them through SMS text messaging. There have been one or two technical difficulties to overcome with this; including switching provider, because my original one didn't work with twitter. I'm also the first to admit I'm useless at tapping out text messages on the phone keypad. To get round this, I send the tweets as text messages using Skype, from my computer to my phone, in advance; it is then a simple matter of forwarding each message to twitter at the scheduled time.
All this should have been fine; it worked during my testing, but yesterday's experience highlighted a couple of issues with the use of my phone. The first being that, for no reason a could tell, it split one of my tweets. I sent it as one text, but it appeared in twitter as two consecutive tweets. The second issue (and lesson learnt) is that, the final tweet of the day lost the last word, appearing in twitter as:
'Evelyn stood right next to me in the lift, touched my hair, and said she liked it in this colour, but it would suit me better shorter. C …'. The last word should have appeared as 'Creepy'. What I had failed to take into account was that mobile phones can deliver more than 140 characters, and my tweet was actually 142; an oversight I should have checked before it was sent to my phone. By the time I realised, parked in a lay-by on the A35, there was really nothing I could do.

I hope that I can work around any future glitches, as I will be relying increasingly on my phone during the London Book Fair next week. Just to be on the safe side, though, I think it will be wise to seek out as many wireless hotspots, for my laptop, as I can.

Aside from any technical problems, I hope that the flow of the story will start to come through as the tweets progress and any idiosyncrasies of the medium will be forgiven as merely a kind of realism to the delivery of the story. I still intend to see the story through to it's conclusion on the 30th April, and hope that those who follow it, find it an interesting and engaging way to experience a narrative. It remains to be seen if it will be worth repeating the experiment, although I do have a longer, and more gritty, story which I may deliver towards Christmas. I may even consider writing another episode to Bad Hair Daze, if this one isn't a complete disaster.

Tuesday, 5 January 2010

My Own Deadlines



As a writer and animator, I'm used to working to deadlines but the only deadlines I find myself failing to meet are my own.

Most of the time such things are not an issue. I set an arbitrary date by which I would like to complete a self-initiated task, such as writing a blog, and attempt to work to that. More often than I would like: work, family or other considerations will lead me to revise these self-imposed deadlines. This is fine, unlike my work deadlines, they are meant to be a flexible guide rather than a rigid cut-off point.

But I got caught out by myself recently. I had planned to write a short seasonally themed story in time for Christmas. It was to be delivered via Twitter as a series of tweets spread over a two week period, which I calculated would give me a deadline around the 11th of December. During November I had a great deal of coursework for my MA, I also had a lot of paid work during the first two weeks of December. To consider this story was probably unrealistic, but as is often the case with me, I used it as a pleasurable thing to wind down in the evenings, after a hard day of doing other things. As the deadline approached I still had a small amount of the story to write. I wanted to get the ending working well, tying up a number of threads, but I had altered the story from it's original outline and I felt the ending should also change. Unfortunately, I also had another deadline for my coursework on the same day, as well as an article I'd promised to complete. I realised something had to give.

In short, I missed my own short story deadline. I did consider posting the beginning whilst I was still writing the end; it's not the first time I've had to do that, but in the end I decided to pull the story. Which, in hindsight, was the correct decision; I had not done enough promotional work for the story and I still wasn't happy with the ending. That I didn't meet my deadline, I don't mind at all; I can revise, and improve it ready for next Christmas; I can deliver it with a more relaxed timeframe and, most importantly, I will have a whole year in which to plan how to promote it. I've also learnt that it is better to not deliver something at all than something done badly.