For the Lost fans / addicts out there…
The same gold car involved in accidents with Locke, Michael, and Kate.
The question is whether it was
- the same “real” car
- their memories being manipulated
- a deliberate non-plot related joke
- a coincidence / oversight
What do you think?
One Trackback
The mysterious Pontiac Bonneville
The mysterious Pontiac Bonneville
15 Comments
Awesome find.
No link? Or did you find this yourself?
I think it’s just an “easter egg”, something the producers always talk about. But it could be played out into the ethos of the show, like Ethan being the driver since he did say he was, “traveling the world”.
No, I heard it somewhere (at least the Kate and Micheal parts), and then heard the Locke one somewhere else, so I went and found the screen caps and pieced them together. I forget where I originally heard someone talking about it though.
When you say Ethan, do you mean Desmond?
It could be an easter egg, but my current theory is that it is a subtle hint that their memories are slightly manipulated, influenced or tainted by an external force. There are many other clues that alude to this sort of thing in a lot of the flashback sequences.
I am debating over whether to start a separate Lost blog, because there are a whole bunch of random things I’ve noticed and theories I’ve got, but I don’t want to post them all on here because then the Lost posts would start to outnumber all the others.
that reminds me, can i set up multiple wordpress blogs (with separate templates/content) with a single db (without using categories), or do i need to create a separate db for each?
Yeah, I meant desmond.
N: If you want a multi user install there is Wordpress MU. I’m sure you could just use that for what you are planning but if you want to do more then one install, regularly, just change the DB _prefix and you would be set to install as many WP sites as you want running separately.
Oh yeah, I rather see lost posts then the political rants.
haha, i was gonna say the same thing about lost vs. politics.
and i don’t even watch the show!
Re: The multiple blogs - you can have as many different wordpress instances as you want, all pointing to the same database, distinguishing the tables with different prefixes like Dan said. It gets a little messy though, so I would only recommend that if you were limited to only one mysql database by your provider. Keeping them in separate DBs makes for more manageable backups, etc.
yeah, i know it’s not the best case, but one is what i’ve got to work with
thanks for the advice, btw
yeah lost posts are way better, i haven’t seen esp 11 yet, it didn’t download right but i am soooooo hooked i wish it was on dvd already!
you don’t happen to have downloaded esp 11 and 12? i kept trying to and it never turns out right!
I don’t remember, but I’ll check. I watched those ones live, so I’m not sure.
I’ve had no problems with having multiple blogs in the same DB, I’ve done it from the start and I think it’s actually easier since you only need to update one DB rather then multiple ones. The only problem that I’ve had is when some plugins ignore the prefixes, and just install new tables w/o the designated pre_. but then you could use those same tables on multiple blogs if the plugin is activated, this was actually a benefit because I was using a spam plugin and when I blocked it on one blog, since the tables were shared it was blocked on the others as well.
Anyways, I actually recommend it on blogs that don’t have a lot of traffic so the DB can handle it and Backing up is easier, contrary to what JB says.
It’s mostly a matter of preference, but most times best practices are to not share a single database across multiple applications. There are several reasons for this, but one of them is (as I’ve mentioned above) more manageable (I didn’t say easier) backups. This means that if something goes wrong in one application and you have to restore (which is the whole point of making backups), it’s a lot better if you don’t have to also either restore everything (including unrelated applications) or pick out only the stuff for those particular tables you need. There are also some performance benefits in not having everything in one huge DB, but that would not come into play in most blogs.
The one advantage is for the shared spam or stat tracking databases, but you can always alter those to use their own databases (separate altogether from the blog databases). I’m actually planning on doing this for SK2 and the stat tracking systems I’m using now, because the sometimes those tables can get pretty huge, and I’d rather have them in separate databases just for sizing purposes (for backups, etc.).