Thanks for reporting this. It looks like it's not the link that is broken, but the rendering of presentation itself. If you go here: https://talks.golang.org/2012, these three:

• concurrency.slide
• tutorial.slide
• waza.slide

are all broken.

cc @dmitshur

Hello @Aju100, welcome to the Go project! Happy New Year, and thank you for identifying this problem!

I believe that the problem is that the slides might not use the godoc format, and might be outdated, so perhaps we should modernize them. @robpike, it would be an honor for you to perhaps take a look at concurrency.slide which you created for that iconic talk, otherwise I can take a look and mail the fixes. Also cheers @dmitshur!
Thank you.

EDIT: I hadn’t seen @ALTree’s analysis (perhaps typed concurrently) but yes, what @ALTree said (thanks and Happy New Year @ALTree)

@odeke-em @ALTree thank you and Happy New year.

I believe @rsc has a tool for this.

There is a command for this, present2md, but there are a couple of problems with it; the parsing of caption commands is broken in some conditions and comments are not retained. These will result in incomplete translation of tutorial.slide and waza.slide. There is also a problem for dot commands without a previous blank line which won't affect any of the decks listed above.

All of these are addressed in existing CLs:

• https://go-review.googlesource.com/c/tools/+/260897
• https://go-review.googlesource.com/c/tools/+/260898
• https://go-review.googlesource.com/c/tools/+/260899

Change https://golang.org/cl/284392 mentions this issue: content/2012: prevent present from misinterpretting comment as title

@robpike Does this talks server need to be bumped? It is still serving text that is broken, and with titles that come from text that was removed; both of concurrency.slide and tutorial.slide are titled "This is a file." on the 2012 directory view but these lines were removed.

@kortschak That is expected, the talks server needs to be redeployed. There's some work that needs to be done. We'll look into doing it possibly next week. (Edit: This is done by now.)

"Expected," no. "Unfortunate," yes. The deployment process has rotted, it seems, and needs to be repaired. It will take a few days.