Re: [backstage] [Fwd: Fwd: Twitter Fever]
On 17 Apr 2007, at 23:47, Nic James Ferrier wrote: Gordon Joly [EMAIL PROTECTED] writes: At 10:31 +0100 17/4/07, Ian Forrester wrote: I think it can scale if they open up the queuing system and stick to charging for SMS's. I think Kosso has the right idea - http://kosso.wordpress.com/2007/03/28/os-twitter-and-services/ How will charging affect packets going through routers? Charging is not necessary... it just has to be designed correctly. Twitter is just in need of horizontal scaling. Split the namespace across many servers and it would scale. No problem. Which is why I don't understand why they're having some problems. Well, I do. It's because they're using rails. If you do that it suggests you don't know what you're doing. [sits back and waits for everyone to explode with rage] Nic, Without being the flag bearer of the rails brigade [1], that they are using Rails has nothing significant to do with their problems - they'd exist with any platform in use. It's fortunate that it's not one that would require rigmarole to upgrade - i'd hate to see twitter having to amend their Volume License Agreement every week. I don't know what the actual technical competence of this list is, but aside from joining-the-dots with mashups, I'm yet to see much which is truly groundbreaking, impressive and unique - which makes this conversation so empty and pointless. It's true: Twitter hasn't really done anything magical, other than connecting mobile, im and web in a tangled mesh of ubiquity. Sure, there are problems - from design to use: bear in mind that the twitter crew's original mantra was for a tool to tell friends where they are and what they are up to (the sort of thing that jaiku et al are really honing in on, by demoting the conversation). So as to your suggestion - adding more servers. It's an easy fix when you have a service generating income. Twitter, currently, does not. Thus who keeps paying for the machines? Who keeps paying for the text messages - twitter's SMS bill is large enough to get the attention of any provider out there. Developers who understand scalability know that it's often a plumbing problem: as soon as one pipe is capped or uncovered, another leak starts. You constantly have to uncover and release pressure until the system is in balance. Right now twitter is struggling because it's run out of compute cycles; next week it may be the database. Twitter currently has a traffic rank in the top 500 websites - and is completely dynamic. Google currently indexes over 220, 000 pages from twitter.com. It's not a trivial problem. Its not something that a few more servers will fix: twitter needs to come up with new architecture such that it can manage the service properly. In reality this means transitioning to a core twitter centric codebase - ie, do exactly as amazon, ebay and others have done: replace the web scripting language they prototyped in and roll their own, where it makes sense. So hop off the language hate bandwagon, because no-one cares. Instead, add something constructive. Sincerely - James Cox [1] Seriously, I really don't give a crap what platform you prefer. - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
At 23:47 +0100 17/4/07, Nic James Ferrier wrote: Gordon Joly [EMAIL PROTECTED] writes: At 10:31 +0100 17/4/07, Ian Forrester wrote: I think it can scale if they open up the queuing system and stick to charging for SMS's. I think Kosso has the right idea - http://kosso.wordpress.com/2007/03/28/os-twitter-and-services/ --- I don't see how twitter can scale And that was one of my first twitter psotings! Gordo - How will charging affect packets going through routers? Charging is not necessary... it just has to be designed correctly. Twitter is just in need of horizontal scaling. Split the namespace across many servers and it would scale. No problem. Which is why I don't understand why they're having some problems. Well, I do. It's because they're using rails. If you do that it suggests you don't know what you're doing. [sits back and waits for everyone to explode with rage] -- Nic Ferrier http://www.tapsellferrier.co.uk Ruby on Rails == Smoke on Mirrors? Gordo -- Think Feynman/ http://pobox.com/~gordo/ [EMAIL PROTECTED]/// - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
James Cox [EMAIL PROTECTED] writes: So hop off the language hate bandwagon, because no-one cares. Instead, add something constructive. Actually, I wasn't on the language hate bandwagon. I was on the frameworks hate bandwagon. Down with rails! Up with some random other thing! Come on! You're not seriously suggesting this thread is any more ill-informed, ridiculous or downright silly than some others are you? -- Nic Ferrier http://www.tapsellferrier.co.uk - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Twitter currently has a traffic rank in the top 500 websites Netcraft rate Twitter at position 46,867 - and is completely dynamic. Google currently indexes over 220, 000 pages from twitter.com. It's not a trivial problem. Its not something that a few more servers will fix: twitter needs to come up with new architecture such that it can manage the service properly. In reality this means transitioning to a core twitter centric codebase - ie, do exactly as amazon, ebay and others have done: replace the web scripting language they prototyped in and roll their own, where it makes sense. So hop off the language hate bandwagon, because no-one cares. Instead, add something constructive. Sincerely - James Cox [1] Seriously, I really don't give a crap what platform you prefer. I started learning about Ruby on Rails. Then I found out it is a framework. So I stopped. Gordo -- Think Feynman/ http://pobox.com/~gordo/ [EMAIL PROTECTED]/// - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
RE: [backstage] [Fwd: Fwd: Twitter Fever]
James Cox [EMAIL PROTECTED] writes: So hop off the language hate bandwagon, because no-one cares. Instead, add something constructive. Actually, I wasn't on the language hate bandwagon. I was on the frameworks hate bandwagon. Down with rails! Up with some random other thing! Come on! You're not seriously suggesting this thread is any more ill-informed, ridiculous or downright silly than some others are you? - There's huge value in Frameworks. No matter what you may think about Rails, you can't call them all bad. :) Ian - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Gordon Joly [EMAIL PROTECTED] writes: I started learning about Ruby on Rails. Then I found out it is a framework. So I stopped. EURGH! You got some ON YOU! Look! there! on your shoulder! -- Nic Ferrier http://www.tapsellferrier.co.uk [Did no one tell you it was exclamation mark day?] - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
On 18 Apr 2007, at 15:38, Nic James Ferrier wrote: James Cox [EMAIL PROTECTED] writes: So hop off the language hate bandwagon, because no-one cares. Instead, add something constructive. Actually, I wasn't on the language hate bandwagon. I was on the frameworks hate bandwagon. my mistake, my rage had built up to overly intense levels such that my cursory edit didn't spot this school boy error. :) Down with rails! Up with some random other thing! Come on! You're not seriously suggesting this thread is any more ill-informed, ridiculous or downright silly than some others are you? No, i'm saying that the signal v. noise ratio has decreased and it's time we should talk about stuff that's really interesting. Such as fixing the bbc's content opacity, or ensuring that I win the lottery this weekend - come on, one of you lot must know who the independent adjudicator is... - james - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
fixing the bbc's content opacity, or ensuring that I win the lottery this weekend - come on, one of you lot must know who the independent adjudicator is... it's a guy called Random, fortunately he doesn't live on this planet. Otu - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
RE: [backstage] [Fwd: Fwd: Twitter Fever]
I would say it needs a good dollop of cash for equipment development and hosting As for languages - have to stress from experience it is good architecture design, people and strategy which leads to performance not anything to do with Languages themselves. Even Application Frameworks ( which do have a habit of being a bit slow ) if they are implemented consistantly then at least a caching layer can be built in front or behind them to scale. Generally the Amazons etc of this world do a code rewrite when they find crunches in the development process - when you scale your development staff from 10's to 100's you have to look carefully at the tools sets, frameworks and processes - and some of the best do happen to be language specific. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Cox Sent: Wednesday, April 18, 2007 3:17 PM To: backstage@lists.bbc.co.uk Subject: Re: [backstage] [Fwd: Fwd: Twitter Fever] On 17 Apr 2007, at 23:47, Nic James Ferrier wrote: Gordon Joly [EMAIL PROTECTED] writes: At 10:31 +0100 17/4/07, Ian Forrester wrote: I think it can scale if they open up the queuing system and stick to charging for SMS's. I think Kosso has the right idea - http://kosso.wordpress.com/2007/03/28/os-twitter-and-services/ How will charging affect packets going through routers? Charging is not necessary... it just has to be designed correctly. Twitter is just in need of horizontal scaling. Split the namespace across many servers and it would scale. No problem. Which is why I don't understand why they're having some problems. Well, I do. It's because they're using rails. If you do that it suggests you don't know what you're doing. [sits back and waits for everyone to explode with rage] Nic, Without being the flag bearer of the rails brigade [1], that they are using Rails has nothing significant to do with their problems - they'd exist with any platform in use. It's fortunate that it's not one that would require rigmarole to upgrade - i'd hate to see twitter having to amend their Volume License Agreement every week. I don't know what the actual technical competence of this list is, but aside from joining-the-dots with mashups, I'm yet to see much which is truly groundbreaking, impressive and unique - which makes this conversation so empty and pointless. It's true: Twitter hasn't really done anything magical, other than connecting mobile, im and web in a tangled mesh of ubiquity. Sure, there are problems - from design to use: bear in mind that the twitter crew's original mantra was for a tool to tell friends where they are and what they are up to (the sort of thing that jaiku et al are really honing in on, by demoting the conversation). So as to your suggestion - adding more servers. It's an easy fix when you have a service generating income. Twitter, currently, does not. Thus who keeps paying for the machines? Who keeps paying for the text messages - twitter's SMS bill is large enough to get the attention of any provider out there. Developers who understand scalability know that it's often a plumbing problem: as soon as one pipe is capped or uncovered, another leak starts. You constantly have to uncover and release pressure until the system is in balance. Right now twitter is struggling because it's run out of compute cycles; next week it may be the database. Twitter currently has a traffic rank in the top 500 websites - and is completely dynamic. Google currently indexes over 220, 000 pages from twitter.com. It's not a trivial problem. Its not something that a few more servers will fix: twitter needs to come up with new architecture such that it can manage the service properly. In reality this means transitioning to a core twitter centric codebase - ie, do exactly as amazon, ebay and others have done: replace the web scripting language they prototyped in and roll their own, where it makes sense. So hop off the language hate bandwagon, because no-one cares. Instead, add something constructive. Sincerely - James Cox [1] Seriously, I really don't give a crap what platform you prefer. - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/ - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
RE: [backstage] [Fwd: Fwd: Twitter Fever]
At 15:48 +0100 18/4/07, Ian Forrester wrote: - There's huge value in Frameworks. No matter what you may think about Rails, you can't call them all bad. :) Ian A framework is a higher level of abstraction. Most of the time, there come a point where you want to poke around under the bonnet and fine tune the engine Gordo -- Think Feynman/ http://pobox.com/~gordo/ [EMAIL PROTECTED]/// - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
At 15:52 +0100 18/4/07, Nic James Ferrier wrote: Gordon Joly [EMAIL PROTECTED] writes: I started learning about Ruby on Rails. Then I found out it is a framework. So I stopped. EURGH! You got some ON YOU! Look! there! on your shoulder! Looks like a framework, smells like a framework, tastes like a framework thank goodness I didn't tread in it! Gordo -- Think Feynman/ http://pobox.com/~gordo/ [EMAIL PROTECTED]/// - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
RE: [backstage] [Fwd: Fwd: Twitter Fever]
At 17:41 +0100 18/4/07, Gordon Joly wrote: At 15:48 +0100 18/4/07, Ian Forrester wrote: - There's huge value in Frameworks. No matter what you may think about Rails, you can't call them all bad. :) Ian A framework is a higher level of abstraction. Most of the time, there come a point where you want to poke around under the bonnet and fine tune the engine Occasionally. But mostly, abstraction is what good engineering is all about. What more is an operating system than a higher level of abstraction from handling memory management and scheduling in your own code? What more is a CPU architecture than an abstraction from a set of transistors? Tim -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Gordon Joly [EMAIL PROTECTED] writes: At 10:31 +0100 17/4/07, Ian Forrester wrote: I think it can scale if they open up the queuing system and stick to charging for SMS's. I think Kosso has the right idea - http://kosso.wordpress.com/2007/03/28/os-twitter-and-services/ --- I don't see how twitter can scale And that was one of my first twitter psotings! Gordo - How will charging affect packets going through routers? Charging is not necessary... it just has to be designed correctly. Twitter is just in need of horizontal scaling. Split the namespace across many servers and it would scale. No problem. Which is why I don't understand why they're having some problems. Well, I do. It's because they're using rails. If you do that it suggests you don't know what you're doing. [sits back and waits for everyone to explode with rage] -- Nic Ferrier http://www.tapsellferrier.co.uk - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
On Monday 16 April 2007 16:09, Richard Lockwood wrote:
I don't need to define any terms. Architecht is not a verb. An
architecht designs things.
Dictionary.com :
–verb (used with object)
4. to plan, organize, or structure as an architect: The house is well
architected.
-- http://dictionary.reference.com/browse/architect
The OED :
http://dictionary.oed.com/cgi/entry/50011562?query_type=wordqueryword=architectfirst=1max_to_show=10sort_type=alpharesult_place=2search_id=UIrM-K0ETDq-310hilite=50011562
architect, v.
To design (a building). Also transf. and fig. Hence {sm}architected ppl.
a., designed by an architect; {sm}architecting vbl. n. and ppl. a.
Usage throughout the centuries: (courtesy of OED again)
1818 KEATS Let. 23 July (1931) I. 219 This was architected thus By the great
Oceanus. [But see ARCHITECTURE v.] 1890 Harper's Mag. Apr. 809/2 We would not
give being the author of one of Mr. Aldrich's beautiful sonnets to be the
author of many ‘Wyndham Towers’, however skilfully architected. 1912 ROSE
MACAULAY Views Vag. viii. 153, I have no sort of interest in the
architecting or building trades. 1913 RALEIGH Some Authors (1923) 3 He has
come out of the prison-house of theological system, nobly and grimly
architected. 1923 Public Opinion 29 June 622/3 A..vague notion that a
building ought to be architected.
Language does evolve. Anyone who has a bugbear with words being used properly
should perhaps check words mean 'zactly[1] what they think they do :-)
Michael.
[1] OED:
http://dictionary.oed.com/cgi/entry/50290881?single=1query_type=wordqueryword=zactlyfirst=1max_to_show=10
'zackly, 'zactly
Repr. a dial. or colloq. pronunc. of EXACTLY adv.
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
On 12 Apr 2007, at 02:12, Nic James Ferrier wrote: Mr I Forrester [EMAIL PROTECTED] writes: I did talk to the twitter guys about this issue. I think from there point of view, they never said twitter was meant to be a real time system. It just behaved like that from the start. They're winding you up. Have you noticed the tricks they're putting in to make you think your updates are going live? When you post the post is added to your list on the client side. It's async-ajaxed to the backend as well. But if you refresh and it hasn't got back yet it disappears from your list. Whoops. I think they know perfectly well how interactive it should be but they've built it wrong and are now playing catch up. Nic, sorry, but this is just wrong. The ajax updates are there to reduce page compute time, not to try and 'trick people' into thinking that it's 'faster'. They really did intend for it to be a status update tool, something people would update 2-3 times a day. However people are using it real time - and a number of bots are posting super frequently (eg, the beeb feeds). So yes, it was architected badly in the first place, but this doesn't mean that they knew what was going to happen - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
I think you'll find that's designed... /personal bugbear Cheers, Rich. So yes, it was architected badly in the first place, but this doesn't mean that they knew what was going to happen - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
On 16 Apr 2007, at 15:23, Richard Lockwood wrote: I think you'll find that's designed... /personal bugbear So yes, it was architected badly in the first place, but this doesn't mean that they knew what was going to happen and how would you define those terms? - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
I don't need to define any terms. Architecht is not a verb. An architecht designs things. Cheers, Rich. I think you'll find that's designed... /personal bugbear So yes, it was architected badly in the first place, but this doesn't mean that they knew what was going to happen and how would you define those terms? - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/ - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
At 01:37 +0100 12/4/07, Nic James Ferrier wrote: Mr I Forrester [EMAIL PROTECTED] writes: How about something longer term? like being able to follow the doctor around during the week? Can anyone follow twitter these days? It's so s l o w . All those UNICAST connections, eh? Gordo :-) -- Think Feynman/ http://pobox.com/~gordo/ [EMAIL PROTECTED]/// - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Gordon Joly [EMAIL PROTECTED] writes: At 01:37 +0100 12/4/07, Nic James Ferrier wrote: Mr I Forrester [EMAIL PROTECTED] writes: How about something longer term? like being able to follow the doctor around during the week? Can anyone follow twitter these days? It's so s l o w . All those UNICAST connections, eh? Lucky you didn't say that on twitter. I'd be reading it next week. -- Nic Ferrier http://www.tapsellferrier.co.uk - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
[backstage] [Fwd: Fwd: Twitter Fever]
This came from a friend of mine today... --- Nearly didn't bother reading the usual Twitter guff... Going Hollywood My friend Greg directs tv shows and films and he's got a new series premiering on FOX this Sunday night called Drive. The show was created by the same guy who made Firefly and stars the same lead actor, Nathan Fillion. Greg is going to do Twitter-style director's commentary during the premiere. Follow along if you like, just text FOLLOW FOXDRIVE to 40404 or visit the foxdrive profile page: http://twitter.com/foxdrive But this is smart. --- When I first read it, I thought FOX were doing this. But it actually looks like Nathan Fillion is doing it off his own back? Anyway, I wanted to gage people views, if this was good or bad use of twitter? For example how would you guys feel if you could follow a commentary while watching Dr Who or a different commentary on a live sporting event? How about something longer term? like being able to follow the doctor around during the week? Cheers, Ian Forrester - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Mr I Forrester [EMAIL PROTECTED] writes: How about something longer term? like being able to follow the doctor around during the week? Can anyone follow twitter these days? It's so s l o w . I think the beeb is missing a trick in not doing something like the dath vader/luke skywalker twitters. A dr and a dalek would be cool marketing. And when you need to do some spicy baddie marketing, say to introduce the master, the dalek could be a friend of a twitter feed for that event. -- Nic Ferrier http://www.tapsellferrier.co.uk - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Nathan Fillion and the entire ex Firefly cast are really genuine and engaged people. I don't know if I will be watching the first season of Drive though - twitter or not. Tim Minear (the creator) has created 3 shows for FOX in a row. Each one canceled in season 1 (Firefly - with Joss, Wonderfalls and The Inside). If it survives season 1 then I will go... purchase it from iTunes :) Chris On 4/12/07, Mr I Forrester [EMAIL PROTECTED] wrote: This came from a friend of mine today... --- Nearly didn't bother reading the usual Twitter guff... Going Hollywood My friend Greg directs tv shows and films and he's got a new series premiering on FOX this Sunday night called Drive. The show was created by the same guy who made Firefly and stars the same lead actor, Nathan Fillion. Greg is going to do Twitter-style director's commentary during the premiere. Follow along if you like, just text FOLLOW FOXDRIVE to 40404 or visit the foxdrive profile page: http://twitter.com/foxdrive But this is smart. --- When I first read it, I thought FOX were doing this. But it actually looks like Nathan Fillion is doing it off his own back? Anyway, I wanted to gage people views, if this was good or bad use of twitter? For example how would you guys feel if you could follow a commentary while watching Dr Who or a different commentary on a live sporting event? How about something longer term? like being able to follow the doctor around during the week? Cheers, Ian Forrester - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/ -- Chris Saad Faraday Media - For Audiences of One Touchstone - Are You Paying Attention?
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Nic James Ferrier wrote: Mr I Forrester [EMAIL PROTECTED] writes: How about something longer term? like being able to follow the doctor around during the week? Can anyone follow twitter these days? It's so s l o w . I did talk to the twitter guys about this issue. I think from there point of view, they never said twitter was meant to be a real time system. It just behaved like that from the start. I think the beeb is missing a trick in not doing something like the dath vader/luke skywalker twitters. A dr and a dalek would be cool marketing. It could also be informative, educational and of course highly amusing ;) And when you need to do some spicy baddie marketing, say to introduce the master, the dalek could be a friend of a twitter feed for that event. Indeed, your thinking what i'm thinking :) - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] [Fwd: Fwd: Twitter Fever]
Mr I Forrester [EMAIL PROTECTED] writes: I did talk to the twitter guys about this issue. I think from there point of view, they never said twitter was meant to be a real time system. It just behaved like that from the start. They're winding you up. Have you noticed the tricks they're putting in to make you think your updates are going live? When you post the post is added to your list on the client side. It's async-ajaxed to the backend as well. But if you refresh and it hasn't got back yet it disappears from your list. Whoops. I think they know perfectly well how interactive it should be but they've built it wrong and are now playing catch up. Indeed, your thinking what i'm thinking :) Well. We are both brilliant. And cultured. And good looking of course. -- Nic Ferrier http://www.tapsellferrier.co.uk - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
