Actually, you are doing it wrong, I made the same mistake so many times before. Say for this video
* , you have to put in the random character code. The you is taken out to stop the video from showing up.
[[tube:h3WO_oxH4rg]] it right, while [[tube:watch?v=h3WO_oxH4rg&feature=feedbul]] is wrong.
edited 5th Jul '11 9:06:44 PM by nuclearneo577
That's because the code is borked in that post. Instead of [youtube:2gk4OglvB-o], it's [youtube: https://www.youtube.com/watch?v=2gk4OglvB-o
] (only with double square brackets instead of singles.)
The space between the colon following "youtube" alone is enough to break the coding. But then it's combined with the standalone-link markup. The parser tries to read that, gives up in confusion, and dumps you to the youtube home page, because that's the only part it can figure out.
If there are more of those that you know of,let me know what posts they're in, because the only way to fix it is to open the post for editing before the parser figures out that it doesn't understand what you want.
edited 5th Jul '11 9:57:45 PM by Madrugada
That glitch with the full link becoming a redirect is a really serious one that needs to be fixed, though.
Also I've been having a problem with the embeds autoplaying if I pull a page with embeds out of my history, like if I click a link in the same tab and then return to the thread.
Fresh-eyed movie blogThat isn't a glitch. It's markup that is done wrong by the poster. Calling it a glitch and expecting it to be fixed is like blaming the car maker for the fact that you backed into a tree.
The youtube embed markup is simple: [[ youtube:videoidnumber ]] (without the spaces, of course)
What's causing the problem is markup like this: [[ youtube: http://youtube:videoidnumber
]]. See the difference? The server thinks it's a direct link. The markup is telling the software to do two different things at once: "make an embed of this video", and "Link to this offsite page".
And I really shouldn't have to say this, but I'm going to anyway: Anyone who does this on purpose, for any reason, will be banned. Permanently.
edited 19th Jul '11 2:46:37 PM by Madrugada
Okay, an exploit then? I don't necessarily want it fixed so that the user doing it wrong gets the intended result, just something in there to catch that so it won't do it with that mistake.
Fresh-eyed movie blogIt seems that it's still happening.
edited 23rd Jul '11 9:38:46 PM by CentralAvenue
Heapers’ Hangout

They automatically take you to You Tube's front page now, making navigation of threads a pain.
Could this be remedied?