Unruly Rambling - pebble tag

Curtail Comment Spam with Pebble CAPTCHA functionality

Sat, 14 Jan 2006 15:33:14 GMT

Over the past month or so, comment spam on my blog has gotten many times worse than in the past. I have been receiving somewhere between 75-200 comment spam messages per week. Because of this, I was forced to enable comment moderation a while back. Unfortunately this isn't a perfect solution since I still must pour through all the rubbish and manually remove them. Thanks to Glenn Smith, I can reduce the number of message's I must look at by using the CAPTCHA functionality he created. Hopefully Simon incorporates this into the next revision of Pebble.

Pebble including Wiki Features! Rock On Simon!!

Fri, 05 Aug 2005 01:36:37 GMT

I agree with Eric's assement of the Blog/Wiki/Forum landscape. While I see the three quite similar I think the Blog/Wiki marriage is a closer fit. Forum's are more of one stop shop for a particular topic. Blog's are kind of a spider web of information from site to site where wiki's are within the same site. To me that makes the most sense. I remember someone saying that Blogs are like usenet with only the people you want to hear from. I guess that means goodbye Trolls.

One application that a few of my friends use is SnipSnap. SnipSnap is a good implementation of what Eric described. It seems Simon is driving Pebble towards that feature set as well. Even though I like the idea of SnipSnap, I much prefer the Pebble interface. With my latest Pebble 1.8 upgrade, I removed my main site and now redirect to my blog. If I want to add any full pages I just use Pebble's static page feature. Here is an example of that. With Wiki capabilities being added, I'll likely drop my JSPWiki installation as well. Im sure migrating all that content will be a pain. Maybe I could help out the cause and come up with a way to automate the migration.

Upgraded to Pebble 1.4.1

Sat, 10 Apr 2004 18:02:36 GMT

First, Id like to say thanks Simon for the addition of using a JNDI mail source. Since my mail server requires pop3 authentication, I was unable to use the email updates feature from previous versions. Like a good user, I opened a jira ticket just after the 1.4 release asking for smtp auth support. Simon responded with jndi support, which is even more flexible.

Now the steps to set this up using JBoss 3.2.3.
1) In the deploy dir, edit the mail-service.xml file with your mail server specific info. i.e. hostname, user, pass, etc. Leave the jndi name as it is java:/Mail

2) Edit the default web.xml that comes with pebble 1.4.1. Change <res-ref-name>mail/Session</res-ref-name> to <res-ref-name>Mail</res-ref-name> so it uses JBoss's default mail service. I chose to do this since I have other apps using this same mail service. You could add an additional one to if you wish. Just remember that when you upgrade to the next version of pebble, you changed the shipped web.xml.

3) Add the jboss specific jboss-web.xml descriptor in the WEB-INF dir. It should contain the following resource entry
<resource-ref>
    <res-ref-name>Mail</res-ref-name>
    <res-type>javax.mail.Session</res-type>
    <res-auth>Container</res-auth>
    <jndi-name>java:/Mail</jndi-name>
</resource-ref>

Thats all there is to it