eheh, sure. But XML is just a syntax and RSS is just a semantic. If I have no tool that reads RSS and does something good with it for me, it's useless data. Well-formed and valid, but still useless.
<smirk size="big"/>
Gosh stefano, you ought to try this: http://xml.apache.org/cocoon -- there is a "slashdot" example in there that I think is RSS based and I'm sure it could be
adapted...
I emphasize *to me* because I don't run RSS feeds, nor have *any* intention of doing it since newsfeeds don't go along very well with my off-line habits (mine and those of million others throughout the world which aren't as lucky as many here).
Unlike good old asynchronous email.
I switched to gmane.org for most things...
I am not convinced this is a good idea.... Might be a great tool for spamming or exploiting sendmail.....
Hmmm, pretty damn good point, didn't think of this one.
Could be wrong... I'm kinda a paranoid administrator...
Yeah, well, I'm no system administrator and definately not paranoid these days but I think I know enough about email to question if this is a real security concern or just paranoia.
I don't think it's possible to write something in a wiki, get it picked up, sent to a mail list, infect a sendmail of some sort simply by receiving the message (we use qmail, so no problem from our side, I'm concerned on the mail list subscriber receiver end) and do something nasty.
If that was possible, then a normal spam flood would do as much damage.
The only thing I see is people abusing the wiki to place shameless plugs of themselves that get submitted to the mail list.
But email doesn't really change the picture there.
So, call me liberal but I think we have more to loose than to gain in not allowing diffs forwarding to the mail lists.
I'm pretty sure that authentication and "direct" mail notification are mutually exclusive, I'm happy to be proven wrong... but let me paint you a picture...
I don't think I get your point, Andy. What is this different from direct diff emailing?
andy = ConvertToHappySpammer(andy); //Andy == object
Script script = andy.writesScriptToScreenScrapeAndInteroperateWithWiki();
List emails = EmailListFactory.generateList("http://google.com";);
Iterator i = emails.iterator();
int x = 0;
while(i.hasNext()) {
String emailaddy = (String)i.next();
String seedContent = "";
String pornAd = getPornAd();
WikiPage page = script.createPage("GetYourPornHere" + convertNumberToString(x), seedContent);
script.setEmailNotification(emailaddy, page);
script.setPageContent(page, pornAd);
x++;
}
Isn't that cool?
With the scripted batch approach with the settings stored in a CVS committer controlled file, this wouldn't work... To set up notification you'd have to
have access to CVS. Granted you could still spam the list by creating pages, but thats much less fun than spamming whomever you want....
An admin controlled system would also work... But then one would need volunteer admins interested in doing that... ;-)
As I said, I'm not advocating against it, I'm just saying that we need email nofication also.
And thats fine if someone contributes the patchs, I'll happily apply them...
That wouldn't be me. I'm happy to do maintenance and patches but no development on wikis... Too boring and most of the features requested, I don'tIts highly feasible, I just don't know how "wise" the facilities provided are (letting someone say "sure mail this out to here" seems dangerous...) The above suggestion is probably more secure, easy to implement, etc.
I'll let the more sys-adm-savy people take a shot there.
plan on using...
-andy
