What Iíd like to do at some point is to build a fulltext Atom feed that uses Feed Thread and Feed History extension elements. You could then read Perlmonks from right inside your aggregator just like on the site, threading and all. (Using Feed History would offset the cost of a fulltext feed by ensuring that aggregators donít need to poll aggressively to avoid missing feed entries.)
(Since theyíre not even completely finished and blessed, there isnít much support yet for these extensions Ė but that would be helped if there were incentives for it in the form of existing consumable data. Which would in turn be a happy side-effect of having a clean static archive of Perlmonks, which IMO is worthwhile all by itself. I always worry a bit about the fact that the years of community knowledge and history that have accumulated at Perlmonks are stored in whatís effectively a closed silo. Be nice to have a copy of it outside the database in a future-proof standard format.)
Makeshifts last the longest.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||