Live Formatting Bug Tester

Back in 2024, I showed a workaround for YouTube adding the actual @ to usernames: https://does-this-work.dreamwidth.org/6464.html. Those workarounds still display correctly on that post.

In the meantime, the issue was fixed (and I didn’t notice). I used the workaround technique today—and the YouTube userheads appear as DW userheads instead. (The links are correct because they’re not userhead shortcuts, but fully formed anchor links).

Internally, DW is interpreting my Markdown from 2024 differently than today.

Markdown input in markdown editor (my default):

---

[@CalamityKim1](https://www.youtube.com/@CalamityKim1) 
is a 20-something woman [… snip …]

[@ExploreOceans](https://www.youtube.com/@ExploreOceans)
features both livestreams [... snip ...] 

I love [@astronauticast](https://www.youtube
.com/@astronauticast)’s 3-5 minute timelapse 
compilations[... snip ...] 

---

Displays as:

---

calamitykim1 is a 20-something woman [… snip …]

exploreoceans features both livestreams [... snip ...]

I love astronauticast’s 3-5 minute timelapse compilations [... snip ...]

---

Proof that the bug has been fixed: when the Markdown input follows the general pattern of @username.sitename:

@CalamityKim1.youtube is a 20-something woman [… snip …] 

@ExploreOceans.youtube features both livestreams [... snip ...] 

@astronauticast.youtube’s 3-5 minute timelapse 
compilations[... snip ...] 

The userheads display correctly:

CalamityKim1 is a 20-something woman [… snip …]

ExploreOceans features both livestreams [... snip ...]

astronauticast’s 3-5 minute timelapse compilations [... snip ...]

When I create a bare link with angle brackets, uppercase letters are transformed into lower case. Can't recreate the problem here when the post just contains a bare link and a markdown link.

For example, problem doesn't show here:

The link is youtube.com/watch/I908J9_u0WE. I have pasted that exact string into all that follows:

When I create a Markdown link [youtube.com/watch/I908J9_u0WE](https://youtube.com/watch/I908J9_u0WE) this doesn't happen youtube.com/watch/I908J9_u0WE

When bare, notice that all the uppercase letters <https://youtube.com/watch/I908J9_u0WE> remain uppercase https://youtube.com/watch/I908J9_u0WE

But see the next post ....

YouTube & Threads usernames now have @-signs in their names, which plays havoc with Dreamwidth’s userheads. For example:

@ElleCordova.YouTube creates ElleCordova

Looks useful (white arrow in red TV box) but when you click through it doesn’t reach the right person, because it's missing the @ at the beginning of their name.

The solution is use the Dreamwidth syntax to make it look right, and then link it to the correct URL.

[@ElleCordova.YouTube](https://www.youtube.com/@ElleCordova)

Yields ElleCordova

I played around with escaping @ and using @ and @ and &#64 and no joy.

Here comes all the things that didn't work:

@ElleCordova from @@ElleCordova.youtube

@ElleCordova from @@ElleCordova.YouTube @@ElleCordova.YouTube from @@ElleCordova.YouTube

@ElleCordova from @@ElleCordova.YouTube @‌@ElleCordova.YouTube from @‌@ElleCordova.YouTube

@ElleCordova from @@ElleCordova.YouTube @@ElleCordova.YouTube from @@ElleCordova.YouTube

Now with raw html

Here's what I typed in the entry title:

I'm @jesse_the_k aka <user name=jesse_the_k> in a post title

Markdown editor: here's what I typed in the entry title

I'm @jesse_the_k aka <user name=jesse_the_k> in a post title

Let's talk about \@everyone and \@here or is it @\everyone and @\here or better yet `@everyone` and `@here` or `@`everyone and `@`here The same stuff wrapped in <pre> tags

Let's talk about \@everyone and \@here 
or is it @\everyone and @\here 
or better yet `@everyone` and `@here` 
or `@`everyone and `@`here

Let's talk about @everyone and @here or is it @\everyone and @\here or better yet @everyone and @here or @everyone and @here

The same stuff wrapped in <pre> tags

Let's talk about \@everyone and \@here 
or is it @\everyone and @\here 
or better yet `@everyone` and `@here` 
or `@`everyone and `@`here

We love Buffy St Marie!

Just paste
https://youtu.be/0v7LlS5Ajs4

As live Markdown link
<https://youtu.be/0v7LlS5Ajs4>

As full link
[https://youtu.be/0v7LlS5Ajs4](https://youtu.be/0v7LlS5Ajs4)

As reference link
[https://youtu.be/0v7LlS5Ajs4][bsm]

Plain paste
https://www.CamelCase.com

As live Markdown link
<https://www.CamelCase.com>

As full markdown link
[https://www.CamelCase.com](https://www.CamelCase.com)

As reference markdown link
[https://www.CamelCase.com][cc]

[cc]: https://www.CamelCase.com
[bsm]: https://youtu.be/0v7LlS5Ajs4

We love Buffy St Marie!

Just paste
https://youtu.be/0v7LlS5Ajs4

As live Markdown link
<https://youtu.be/0v7lls5ajs4>

As full link
[https://youtu.be/0v7LlS5Ajs4](https://youtu.be/0v7LlS5Ajs4)

As reference link
[https://youtu.be/0v7LlS5Ajs4][bsm]

Plain paste
https://www.CamelCase.com

As live Markdown link
<https://www.camelcase.com>

As full markdown link
[https://www.CamelCase.com](https://www.CamelCase.com)

As reference markdown link
[https://www.CamelCase.com][cc]

[cc]: https://www.CamelCase.com
[bsm]: https://youtu.be/0v7LlS5Ajs4

Activated into links with angle brackets https://www.CamelCase.com Activated into links with angle brackets Activated into links with angle brackets https://www.CamelCase.com https://www.CamelCase.com

Plain old text https://www.CamelCase.com Plain old text Plain old text Plain old text https://www.CamelCase.com Plain old text Plain old text Plain old text

Escaped with backticks https://www.CamelCase.com Escaped with backticks Escaped with backticks https://www.CamelCase.com Escaped with backticks

Angle brackets within backticks <https://www.CamelCase.com> Angle brackets within backticks <https://www.CamelCase.com>

Inline markdown links CamelCase Inline markdown links Inline markdown links CamelCase

Reference markdown links CamelCase Reference markdown links CamelCase Reference markdown links

HTML href version with link as anchor https://www.CamelCase.com HTML href version with link as anchor https://www.CamelCase.com

Typical HTML href version CamelCase Typical HTML href version CamelCase

after the code push with the Markdown editor choice — hooray roadrunnertwice

Here’s the <raw-code> version

First let's show it as code `https://youtu.be/wUJJpAjt0uY` Next as a bare link https://youtu.be/wUJJpAjt0uY Then active markdown in angle brackets <https://youtu.be/wujjpajt0uy> Then inline markdown [watch on YouTube](https://youtu.be/wUJJpAjt0uY) Then active markdown as reference with colon space [watch on YouTube][ytlink2] [ytlink2]: https://youtu.be/wUJJpAjt0uY Then HTML encoding itself https://youtu.be/wUJJpAjt0uY Then full HTML YouTube link Then active markdown short links (lowercased as well as u&lc) <https://is.gd/izitan> <https://is.gd/youtubelink> Finally, as embedded

Here’s the <code> version

First let's show it as code

`https://youtu.be/wUJJpAjt0uY`

Next as a bare link

https://youtu.be/wUJJpAjt0uY

Then active markdown in angle brackets

<https://youtu.be/wujjpajt0uy>

Then inline markdown

[watch on YouTube](https://youtu.be/wUJJpAjt0uY)

Then active markdown as reference with colon space

[watch on YouTube][ytlink2]

[ytlink2]: https://youtu.be/wUJJpAjt0uY

Then HTML encoding itself

https://youtu.be/wUJJpAjt0uY

Then full HTML

YouTube link

Then active markdown short links (lowercased as well as u&lc)

<https://is.gd/izitan>

<https://is.gd/youtubelink>

Finally, as embedded

Watch on YouTube

Here’s the <pre> version

First let's show it as code

`https://youtu.be/wUJJpAjt0uY`

Next as a bare link

https://youtu.be/wUJJpAjt0uY

Then active markdown in angle brackets

<https://youtu.be/wujjpajt0uy>

Then inline markdown

[watch on YouTube](https://youtu.be/wUJJpAjt0uY)

Then active markdown as reference with colon space

[watch on YouTube][ytlink2]

[ytlink2]: https://youtu.be/wUJJpAjt0uY

Then HTML encoding itself

https://youtu.be/wUJJpAjt0uY

Then full HTML

YouTube link

Then active markdown short links (lowercased as well as u&lc)

<https://is.gd/izitan>

<https://is.gd/youtubelink>

Finally, as embedded

Watch on YouTube