There are some practical approaches you can try, but I see two basic difficulties with your core idea.
...I look to a node and discover that it needs to be studied. I give the ID to the supost program, and it fetches the node and show me,...
That suggests a solution based on heuristics about authors and titles and the tree of replies, but prevents decisions based on the content.
The larger problem is that you want machine evaluation of human expression -- understanding of speech. That holy grail has been drifting just out of reach for a very long time.
PM does have XML feeds, including 'newest nodes', so heuristics like I mentioned are possible in limited bandwidth.
After Compline,
Zaxo
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.