You can subscribe to this list here.
2003 |
Jan
(24) |
Feb
(226) |
Mar
(150) |
Apr
(103) |
May
(101) |
Jun
(83) |
Jul
(80) |
Aug
(27) |
Sep
(48) |
Oct
(2) |
Nov
(17) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(11) |
Feb
(67) |
Mar
(53) |
Apr
(60) |
May
(79) |
Jun
(17) |
Jul
(6) |
Aug
(13) |
Sep
(14) |
Oct
(6) |
Nov
(13) |
Dec
(161) |
2005 |
Jan
(37) |
Feb
(31) |
Mar
(82) |
Apr
(119) |
May
(30) |
Jun
(5) |
Jul
(3) |
Aug
(9) |
Sep
(7) |
Oct
(14) |
Nov
(1) |
Dec
(10) |
2006 |
Jan
(32) |
Feb
(18) |
Mar
(12) |
Apr
(14) |
May
(10) |
Jun
(5) |
Jul
(1) |
Aug
(17) |
Sep
(21) |
Oct
(6) |
Nov
(27) |
Dec
(16) |
2007 |
Jan
(4) |
Feb
(6) |
Mar
(18) |
Apr
(1) |
May
(33) |
Jun
(6) |
Jul
(16) |
Aug
(12) |
Sep
(12) |
Oct
(9) |
Nov
(17) |
Dec
(31) |
2008 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
(29) |
May
(11) |
Jun
(7) |
Jul
(21) |
Aug
|
Sep
(3) |
Oct
(22) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
(5) |
Mar
(4) |
Apr
(8) |
May
(8) |
Jun
(9) |
Jul
(6) |
Aug
(2) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
2010 |
Jan
(16) |
Feb
(6) |
Mar
|
Apr
|
May
(27) |
Jun
(5) |
Jul
(2) |
Aug
(9) |
Sep
(1) |
Oct
(35) |
Nov
(5) |
Dec
|
2011 |
Jan
(18) |
Feb
(3) |
Mar
(18) |
Apr
(18) |
May
|
Jun
(4) |
Jul
|
Aug
(5) |
Sep
|
Oct
(3) |
Nov
(13) |
Dec
(9) |
2012 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
(38) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(9) |
2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(6) |
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: will <wi...@bl...> - 2003-01-25 16:39:31
|
I fixed up categories so it's all pretty now. When doing that I noticed that if you browse by category, you only get the max number of entries as specified in the ini file. I was wondering if it'd be a good thing to add a max override on the url like the flavour. Something like this: http://www.bluesock.org/~willg/cgi-bin/pyblosxom.cgi/dev?max=26 In this case, we would show 26 entries. Would that be a good idea, or not? My concern is that old entries won't be viewable if we spill over the max. Of course, I guess it prevents people from pulling _all_ your entries. I don't know if that's good or bad, though. How do other *blosxom things handle this? /will -- whatever it is, you can find it at http://www.bluesock.org/~willg/ except Will--you can only see him in real life. |
From: Wari W. <wa...@ho...> - 2003-01-22 15:26:02
|
As some of you know, I was thinking of doing plugins that will touch a makeshift db to tell a cronjob what to do later. Don't listen to me, it wasn't me putting on my unix administrator cap :) This should not be a job of pyblosxom. I mean, why get pyblosxom to notice when a cronjob can do the noticing. What the program in your control, make it a command line program, cannot access the command line, allow web access to it, with a password or something. A little python script can be a cgi, a command line program and a cronjob (to run quietly). Actually it does not have to be a python script but where's the fun in that? :) Using plugins similar to Will's load() style plugin, I will pass an object containing py config variables, as well as a list of what blogs changed or is new to pyblosxom. The plugins then do what they need to do. What are the areas the plugins can help? Off the hat, I can think of, 1. static page renders, 2. pingbacks, 3. trackbacks or 4. what ever feedbacks that needs to be 'activated' on new entries. 5. Weblogs.com and blo.gs ping, or wherever users might want to ping to notify a new blog entry. 6. external uploads to webservers (blog locally, publish globally) 7. Backups 8. Web site cleanups My hat's empty now :) You can see how useful this can be, and I have not even started on anything yet :) So what do you think? Do I sound like rambling? :) Is this a good idea, or something I should scrap? Do you have task ideas out off your hats? |