blosxom-devel Mailing List for Blosxom

Brought to you by: kscaldef, xtaran

blosxom-devel — List for discussions around development of blosxom.

You can subscribe to this list here.

2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (7)	Oct (10)	Nov (5)	Dec
2006	Jan	Feb	Mar	Apr	May	Jun (23)	Jul (21)	Aug	Sep (1)	Oct (3)	Nov (1)	Dec
2007	Jan (3)	Feb	Mar	Apr	May	Jun	Jul (12)	Aug (166)	Sep (163)	Oct (59)	Nov (23)	Dec (14)
2008	Jan (3)	Feb (4)	Mar (24)	Apr (14)	May	Jun (9)	Jul (61)	Aug (2)	Sep	Oct (2)	Nov	Dec (12)
2009	Jan (5)	Feb	Mar (3)	Apr	May	Jun	Jul	Aug (1)	Sep	Oct	Nov	Dec
2010	Jan	Feb (1)	Mar (1)	Apr (1)	May	Jun (1)	Jul (3)	Aug	Sep	Oct (3)	Nov	Dec
2011	Jan	Feb	Mar	Apr (7)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2012	Jan (1)	Feb	Mar	Apr (2)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (6)
2013	Jan	Feb	Mar	Apr	May (3)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

1 2 3 .. 27 > >> (Page 1 of 27)

Re: [Blosxom-devel] I have a problem with entries_timestamp plugin

From: Matthijs K. <mat...@st...> - 2013-05-03 18:30:42

Hi Z24,


> I am moving my website from a hosting provider to a new one
> (host-ed.me). I uploaded all my files to the new hosting server,
> including plugins/state/.entries_index.index and when I visit my site
> all the posts get May 1st 2013 as posting date (the upload date)
> instead of the timestamp stored in .entries_index.index, then
> .entries_index.index is updated with the May 1st 2013 timestamp.
Perhaps the path of the files changed? The .entries_index.index file
contains full paths, so if those changed you'll have to manually update
them in the index (after re-copying the file from your backup, since all
the old /wrong paths will have been removed from the index during the
first request).

Gr.

Matthijs

Re: [Blosxom-devel] Net::Akismet and feedback plugin

From: Eric L. <eri...@ff...> - 2012-12-26 11:50:28

Hello,

I'm using Frank Hecker's feedback plugin too. On my side, I don't use 
any moderation at all (less I do, more I'm happy and, also, as 
visitor I don't like blogs, forums, guestbooks, any kind of spaces 
where posting is not in real time - the impression of being on a 
controlled/managed/fake/unreal space).

The way I go is just to limit possibility to comment during two weeks 
: it's not very nice, but it seems to work ; spiders and others 
automated software used by all Black Hat marketers have stopped to 
target my blogs from the point I've added this time limitation. 
Nevertheless, I think your way, Martin, sounds smarter :) Did you 
sent your MOD to Emanuel ?

Also, Kevin, just a thought (maybe clever, maybe not - don't know:) : 
from the point of view of a lot of "autosubmitters" (I mean all kind 
of tools used by a lot of marketers), a successfull posting is when 
the form action has been well ran (ie. POST request succeeded). So, 
they don't check resulting page to be sure the post really appears 
afterward. These automates are not aware of the moderation and, by 
that way, doesn't stop their bad job (mass submission) because of 
moderation, while they stop-it if there's not any possibility to 
submit (ie. send request running form action). So - if what I say 
here is pertinent - any way which will block submission after request 
would be less efficient than the one which do-it before. Just a thought !

Have a good day
Eric / ffh-lab.com

At 02:42 26/12/2012, you wrote:
>When I last looked at using Frank's feedback plugin, I found the Akismet
>functionality didn't work, as Akismet now also requires an IP address
>and user-agent of the comment submitter to be provided, and the feedback
>plugin wasn't providing that info when doing an Akismet query.
>
>I've gone down a slightly different path, with the following mods to the
>feedback plugin:
>-reject the comment if it contains more than 3 instances of http://
>-added a checkbox to the comment form that the submitter must enable to
>specify they are human
>and have found they have significantly reduced the amount of comment
>spam I was getting on my blog.
>
>regards,
>Martin.
>
>Kevin Walzer wrote, On 26/12/2012 9:33 AM:
> > I'm using Frank Hecker's feedback plugin
> > (http://hecker.org/blosxom/feedback) for comments at my blog. While the
> > plugin works well, especially its moderation features, I find that it
> > does not seem to do a very good job of filtering out spam, even when I
> > enable the optional Net::Akismet functionality.
> >
> > I have an Akismet API key, and doing some basic testing of the module
> > with my key suggests that it works in identifying spam--but my mailbox
> > is flooded with moderation requests for comments that turn out to be
> > nothing but spam--literally dozens per day.
> >
> > Any idea what the problem might be? Is it possible that the Akismet bits
> > are turning away a lot of spam, but a lot is still getting in? (I know
> > Aiksmet isn't perfect.) What I've done as a workaround is to check for
> > URL's in the comment field, and mark those as spam (since all the spam
> > appears to come from linkbots). That seems to be helping, but it also
> > isn't the way things are supposed to work. Any suggestions are appreciated.
> >
> > --Kevin
> >
>
>------------------------------------------------------------------------------
>LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>Remotely access PCs and mobile devices and provide instant support
>Improve your efficiency, and focus on delivering more value-add services
>Discover what IT Professionals Know. Rescue delivers
>http://p.sf.net/sfu/logmein_12329d2d
>_______________________________________________
>Blosxom-devel mailing list
>Blo...@li...
>https://lists.sourceforge.net/lists/listinfo/blosxom-devel

Re: [Blosxom-devel] Net::Akismet and feedback plugin

From: Martin P. <mp...@ma...> - 2012-12-26 02:12:38

When I last looked at using Frank's feedback plugin, I found the Akismet 
functionality didn't work, as Akismet now also requires an IP address 
and user-agent of the comment submitter to be provided, and the feedback 
plugin wasn't providing that info when doing an Akismet query.

I've gone down a slightly different path, with the following mods to the 
feedback plugin:
-reject the comment if it contains more than 3 instances of http://
-added a checkbox to the comment form that the submitter must enable to 
specify they are human
and have found they have significantly reduced the amount of comment 
spam I was getting on my blog.

regards,
Martin.

Kevin Walzer wrote, On 26/12/2012 9:33 AM:
> I'm using Frank Hecker's feedback plugin
> (http://hecker.org/blosxom/feedback) for comments at my blog. While the
> plugin works well, especially its moderation features, I find that it
> does not seem to do a very good job of filtering out spam, even when I
> enable the optional Net::Akismet functionality.
>
> I have an Akismet API key, and doing some basic testing of the module
> with my key suggests that it works in identifying spam--but my mailbox
> is flooded with moderation requests for comments that turn out to be
> nothing but spam--literally dozens per day.
>
> Any idea what the problem might be? Is it possible that the Akismet bits
> are turning away a lot of spam, but a lot is still getting in? (I know
> Aiksmet isn't perfect.) What I've done as a workaround is to check for
> URL's in the comment field, and mark those as spam (since all the spam
> appears to come from linkbots). That seems to be helping, but it also
> isn't the way things are supposed to work. Any suggestions are appreciated.
>
> --Kevin
>

Re: [Blosxom-devel] Net::Akismet and feedback plugin

From: Kevin W. <kw...@co...> - 2012-12-26 01:39:28

On 12/25/12 8:33 PM, Kevin Walzer wrote:
> I'm using Frank Hecker's feedback plugin
> (http://hecker.org/blosxom/feedback) for comments at my blog. While the
> plugin works well, especially its moderation features, I find that it
> does not seem to do a very good job of filtering out spam, even when I
> enable the optional Net::Akismet functionality.
>
> I have an Akismet API key, and doing some basic testing of the module
> with my key suggests that it works in identifying spam--but my mailbox
> is flooded with moderation requests for comments that turn out to be
> nothing but spam--literally dozens per day.
>
> Any idea what the problem might be? Is it possible that the Akismet bits
> are turning away a lot of spam, but a lot is still getting in? (I know
> Aiksmet isn't perfect.) What I've done as a workaround is to check for
> URL's in the comment field, and mark those as spam (since all the spam
> appears to come from linkbots). That seems to be helping, but it also
> isn't the way things are supposed to work. Any suggestions are appreciated.
>
> --Kevin
>

Just for the record, here is the additional spam check, around line 1021 
in the plugin:

     # TODO: Add other useful spam checks.
     return 1 if  ($$params_ref{'comment'} =~ /http/);

And here's the change to the built-in comment form, around line 1466:

html commentform \n<form method="POST" 
action="$blosxom::url$blosxom::path/$blosxom::fn.$blosxom::flavour">\n<table><tr><i>URLs 
in comment text will be treated as 
spam.</i></tr><tr><td>Name:</td><td><input name="name" size="35" 
value="$feedback::name_preview"></td></tr>\n<tr><td>Web Site 
(optional):</td><td><input name="url" size="35" 
value="$feedback::url_preview"></td></tr>\n<tr><td>Comments:</td><td><textarea 
name="comment" rows="5" 
cols="60">$feedback::comment_preview</textarea></td></tr>\n<tr><td><input type="hidden" 
name="plugin" value="writeback"><input type="submit" name="submit" 
value="Preview"></td><td><input type="submit" name="submit" 
value="Post"></td></tr>\n</table></form>


-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com

[Blosxom-devel] Net::Akismet and feedback plugin

From: Kevin W. <kw...@co...> - 2012-12-26 01:33:29

I'm using Frank Hecker's feedback plugin 
(http://hecker.org/blosxom/feedback) for comments at my blog. While the 
plugin works well, especially its moderation features, I find that it 
does not seem to do a very good job of filtering out spam, even when I 
enable the optional Net::Akismet functionality.

I have an Akismet API key, and doing some basic testing of the module 
with my key suggests that it works in identifying spam--but my mailbox 
is flooded with moderation requests for comments that turn out to be 
nothing but spam--literally dozens per day.

Any idea what the problem might be? Is it possible that the Akismet bits 
are turning away a lot of spam, but a lot is still getting in? (I know 
Aiksmet isn't perfect.) What I've done as a workaround is to check for 
URL's in the comment field, and mark those as spam (since all the spam 
appears to come from linkbots). That seems to be helping, but it also 
isn't the way things are supposed to work. Any suggestions are appreciated.

--Kevin

-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com

Re: [Blosxom-devel] Enthusastic blosxom user

From: David M. <pa...@fr...> - 2012-12-19 08:18:13

Greetings.

The lists get little traffic anymore, but I for one am still listening.

I recently revived my Blosxom-powered blog:
http://papa.motd.org/cgi-bin/blosxom.cgi

I am by no means an expert, but after examining a large number of blog
engines, Blosxom can still not be beat for shell integration and overall
simplicity. Too bad some of the plugins are withering away from bit rot.

Good to see you doing nice work with Blosxom on your sites.


-- 
David Meyer
Takarazuka, Japan
http://papa.motd.org/cgi-bin/blosxom.cgi
pa...@fr...


-- 
David Meyer
Takarazuka, Japan
gopher://sdf.org/1/users/papa/ | http://papa.sdf.org/nexus/
pa...@sd...

[Blosxom-devel] Enthusastic blosxom user

From: Kevin W. <kw...@co...> - 2012-12-18 15:49:47

Hi all,

I hope these lists have at least a bit of traffic, and that I'm not 
posting to a ghost town. I just wanted to thank y'all for taking up Rael 
Dornfest's work with Blosxom and continuing to maintain the package.

I mention my use of blosxom in this blog post:

http://www.smallbizmac.net/blosxom.cgi/2012/12/18#blosxom

I've been using blosxom for years, after switching from 
http://pivotx.net, which is much heavier to install and configure. In 
fact, I use bloxsom on four separate blogs:

http://www.smallbizmac.net/blosxom.cgi
http://www.codebykevin.com/blosxom.cgi
http://www.wtmobilesoftware.com/blosxom.cgi
http://www.kevin-walzer.com/blosxom.cgi/

I just find it wonderfully configurable, easy to set up and use, and 
it's flexible enough to be updated with a modern responsive design 
engine as well.

I'm actually still using the ancient version of blosxom (2.0) that I 
downloaded from Rael's site back in, I guess, 2006? I haven't updated 
because I saw no reason to. How does the current version at SF improve 
on the older one?

Thanks again,
Kevin
-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com

[Blosxom-devel] released Blosxom::Header

From: Ryo A. <ryo...@gm...> - 2012-04-26 16:14:51

Dear Blosxom developers,

I released Blosxom::Header 0.3 which represents $blosxom::header.
I also implemented tie() interface:

  tie my %header, 'Blosxom::Header';

Though there are so many Blosxom clones,
we shouldn't forget Blosxom originated from Perl implementation.
It's time to investigate what Blosxom is more precisely.
I believe Perl one should be the best of them :)

Sincirely,
Ryo

[Blosxom-devel] release Blosxom::Header soon

From: 穴澤亮 <ryo...@gm...> - 2012-04-02 03:21:17

Dear Blosxom developers,

I roughly illustrated how Blosxom::Header should work here:
https://github.com/r-anazawa/p5-Blosxom-Header/tree/master/t

In short:

 {
     package blosxom;
     our $header = { -type => 'text/html };
 }

 use Blosxom::Header;

 my $h = Blosxom::Header->new;
 my $value = $h->get( 'foo' );
 my $bool  = $h->exists( 'foo' );

 $h->set( foo => 'bar' );
 $h->delete( 'foo' );

 my @cookies = $h->get( 'cookie' );
 $h->push( 'foo' );

 $h->header; # same reference as $blosxom::header

I will release this module on CPAN.org soon. (currently, just my idea)

See also:
https://metacpan.org/module/Blosxom::Header

I'm waiting for your comments or suggestions :)

Sincerely,
Ryo

[Blosxom-devel] Blosxom::Header - Missing interface to modify HTTP headers

From: Ryo A. <r-a...@sh...> - 2012-01-30 11:15:37

Dear Blosxom developers,

I wrote a  Perl module which provides plugins writers the interface
to modify HTTP headers.

I requested for reviews on PrePAN.org.
https://prepan.org/module/3Yz7PYrBNy

I'm waiting for your suggestions or comments.

-- 
Ryo Anazawa
r-a...@sh...
https://github.com/r-anazawa/