No objections and still no actions? Or I am missing something?
Objections aren't what's keeping features from being implemented.
Lack of support/enthusiasm by the appropriate people, and lack of code are.
Lack of praise of a feature by the powers that be is essentially an objection.
As a pmdev
il, if I don't support a feature, i'm not gonna be inclined to implement it.
Unless somebody champions a feature, it's never gonna happen.
Now, given the availability of xml tickers,
you may just want to implement this, like
davorg did it once (but he lost the code -update:- and he forgets he ever wrote it;)).
I also think blakem may have done it, althought I can't find a link.
Turns out blakem crated bivnn.cgi -- an alternate interface to newest nodes (you might also be interested in Perlmonks Threaded Article Viewer).
update: dammit. I continually keep confusing davorg with mirod.
For some reason, they are forever linked in my head. And this is like the 3rd time I did this (I even had davorg convinced he wrote this thing -- sorry dude).
See (crazyinsomniac) Re: /msg me for new nodes in a thread I noded in and mirod also said:
mirod says I think it was called the perlmonks threaded interface or something, but it was a CGI thingie, so even if you used it the script was on my machine. I tried using Google but I can't find it I'll try to rewrite it
mirod says no, I have lost everything in the crash (and I feel so dumb for it :--( I could try rewriting it though, I am away from home and I have a little time locked in my hotel room this week
I just acquired the best of Tesla ;)
|MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"|
|I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).|
|** The third rule of perl club is a statement of fact: pod is sexy.|