One of the cool new enhancements to use Perl (via Slash 2.2) is the Message system. You can sign up to get messages when people reply to you, moderate you, and metamoderate you. Currently, you can get those messages mailed to you, or provided via the web site. You can also get the daily news either in headline form as before, or with the text of the articles, mailed to you.
Head over to your message preferences to set it up.
Update: 10/03 18:29 GMT by P : Oh, another new feature I forgot to mention was that you can use URLs now like http://use.perl.org/user/gnat/journal/. Instead of "~user" you can also put "my" for your own page. In place of "journal" you can also put "discussions" to see what discussions the user has created, and "pubkey" to see his public key. And without the "journal/" you go to the user's info page, as before.
use perl can email me whenever one of my 'friends' submits a journal entry to tell me that this content is on the website. What I want to know is, can use perl mail me the actual text of the journal entry? And by this I mean use perl itself, not some extra script that trawls the website (which are out there, and I use, and are very good.)
Re:Again, in english
pudge on 2001-10-03T18:22:57
It is possible... but I would be concerned that the users would give permission for their words to be emailed out. So not only would we have to code the sending, but we would have to code some permission system. Possible, but not right now. Re:Again, in english
acme on 2001-10-03T20:06:35
You're concerned "that the users would give permission for their words to be emailed out". Surely they've given consent for their words to be on a website, and as we all know, whatever is on a website is in full public view and can never be taken away. I don't really see a distinction between the "put on web" "emailed to random people who would have seen it on the web anyway" (apart from driving traffic away from the site and losing banner impressions, of course).
I use the same script as 2shortplanks and of course it broke when you upgraded use.perl.org recently so I wonder if there's a better solution to the one we currently have. A full SOAP interface to slashcode?;-) Re:Again, in english
pudge on 2001-10-03T20:23:14
Well, *you* might not see a disinction, but I have been around long enough to know there *is* a distinction, and some people (though probably not most of them) care what it is. Perhaps I am being oversensitive about it, I don't know. Maybe we can conduct a poll?;-)
As to SOAP, well, a web services interface to Slash would be great. Imagine have a command line program, "useperl-journal", and executing it, which launches your text editor, and then you write your journal, and it sends it off to the web site for you. Web services are nifty. Slash is Open Source... patches welcome! <ducking ...> Re:Again, in english
koschei on 2001-10-03T22:08:00
Hmm. Basically what I was suggesting, only I was removing the need to have any sort of program - email updates could be done while on holiday, perhaps (the signing thing could prove problematic, so some password mechanism could be provided in addition perhaps).
Of course, it would only *augment* a SOAP interface rather than be there instead. Of course, of course.
Re:The inverse operation
chromatic on 2001-10-04T01:31:45
ithought can be used to post to Advogato, among other places. It'd probably be an easy modification.Of course, it probably wouldn't be too difficult to add an XML-RPC plugin to Slash, either. Maybe next week.
Re:The inverse operation
Matts on 2001-10-05T08:27:53
acme has such a thing that he uses. Why not ask him for a copy?
