{"id":236,"date":"2004-05-18T09:21:38","date_gmt":"2004-05-18T13:21:38","guid":{"rendered":"https:\/\/www.goer.org\/wordpress\/now_with_advanced_html_technology"},"modified":"2004-05-18T09:21:38","modified_gmt":"2004-05-18T13:21:38","slug":"now_with_advanced_html_technology","status":"publish","type":"post","link":"https:\/\/www.goer.org\/Journal\/2004\/05\/now_with_advanced_html_technology.html","title":{"rendered":"Now With Advanced HTML Technology"},"content":{"rendered":"

It always has seemed kind of silly to discuss markup<\/a> so often, and not allow people to use inline links in their comments, for crying out loud. So I’ve opened up a small subset of HTML elements. The new system allows links and a number of inline elements such as <em><\/code> and <code><\/code>. I would have liked to open up elements such as <pre><\/code> and <blockquote><\/code>, but… eh. It’s a long story. Anyway, the upshot is that instead of saying,<\/p>\n

\n

Evan, your “commentary” on <marquee> and <blink> (https:\/\/www.goer.org\/HTML\/examples\/htmlhorror1.html) was in *wretched* taste.<\/p>\n<\/blockquote>\n

you can now say,<\/p>\n

\n

Evan, your “commentary<\/a>” on <marquee><\/code> and <blink><\/code> was in wretched<\/em> taste.<\/p>\n<\/blockquote>\n

How exciting! I almost opened up the style<\/code> attribute, so that you all could chew me out in large, red Comic Sans MS. But bold will have to do.<\/p>\n

Aaaanyway. Since this entry is so short, here are a few amusing physics links I’ve collected over the last few days.<\/p>\n