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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|