Useful angolizer features

1. first study angolizer and understand what data already are existing IN the present angolizer process.
most data are already in one form or another extracted but unused

2. make sure you have a top-end linux platform to compile - use a purely commercial version - i.e. redhat or novel/suse linux. you will definitely have a fully working linux installed on your professional laptop - multi-boot

3. angolizer

first those things of very special value as site-promotion tool / add-ons

feature list

• a top x list of URLs well formatted in validated RSS2 as RSS feeds. x to be defined in config file. this also needs to define file extension of files to consider for the top list and an exclude list for any URL to be excluded


• a low x list - the lowest traffic URLs - with or without RSS output. this is intended as feedback of files that might need review, re-editing or SEO. x to be configured, exclude list needed, etc


• an output of RSS feed subscribers / viewers by channel and by subscriber sites such as MyYahoo, myGoogle, myMSN, etc. some of may be all leave IN THE LOG a daily dump of access data. that need to be extracted separately from the access_log and displayed in a table and or graphic. a typical fingerprint yahoo drops once or several times daily looks like the sample below.


• accumulation of data into a mysql table for later re-use. such data are all IP ever on site, all countries ever visited, any referrer, all bots. later why- some hosts may want to trace back any hackers IP for example or have a multi-year graphical output of access key-data. the script would need to auto-create a mysql db and auto-configure for its use.


• google sitemap still needs lots of improvement - as of now it is useless on a mixed site static / dynamic content. a single run to create G sitemap needed extensive manual reviewing and correcting making it all in all a wasteful tool useless for professional use. hence i have dumped using g sitemaps. once G sitemaps are created cleanly - thy also need to be converted into yahoo sitemap format and html format and any other future format that some other SE may come up with.


• all data very definitely need to be stored over more than one year to have seasonal comparison data at hand at least over 3-4 or more years - while some visual details may be dropped into a db - some visual graphs like the present graphs may just be needed for future ref - for example compare Dec 2004/2005/2006 to predict 2007 .. etc


• yearly or multi-year sum of individual selected files such as a particular URL or a particular file ( eBooks, etc to show the total nr of downloads per title - configured in config file.

all in all i belief it is about time to upgrade angolizer to a format that includes an upgraded x86_64 / x86_32 version in C as now in combination with a well configured mysql db to store data that might be re3used for various future data analysis variations

currently such yahoo data for feed subscription dropped into my daily access_log files look like

66.218.65.27 - - [02/Oct/2006:01:51:58 -0400] "GET /love_blog/modules/mod_rss/rss.php/2.0 HTTP/1.0" 200 10646 www.kriyayoga.com "-" "YahooFeedSeeker/2.0 (compatible; Mozilla 4.0; MSIE 5.5; http://publisher.yahoo.com/rssguide; users 206; views 5326)" "unknown"

while yahoo's testing RSS bot below since months is crippled and gives NO result:

66.94.237.181 - - [02/Oct/2006:01:58:20 -0400] "GET /love_blog/modules/mod_rss/rss.php/2.0 HTTP/1.0" 200 10646 www.kriyayoga.com "-" "YahooFeedSeeker Testing/2.0 (compatible; Mozilla 4.0; MSIE 5.5; http://publisher.yahoo.com/rssguide; users 0; views 0)" "66.94.229.197"

currently since about may most of yahoo RSS stuff is more or less down anyway.

other RSS sites also download feeds and drop data back into access_log file - formats have to be found first to filter and create proper output

conclusion

OS projects are NO short term projects for a few months !!
OS is like creation - a life time or LONG term commitment to optimize, to debug and to improve on and on. currently what happened to angolizer NEVER should happen - to be dumped after a few weeks - should NEVER have been happened but is proof of total lack of commitment for the wellbeing of others or all creation!

currently some have had problems in compiling angolizer on x86_64 platforms - i had severe problems due to lacking dependencies and missing libs and finally solved them somehow but could never repeat that process again. since quality oriented users run more and more x86_64 platforms such as my dedicated server and my ferrari 4005WLMi - a modern SW MUST run on both - old 32 bit and current 64 bit processors flawlessly.

top to bottom may be priorities in above "feature list"
there certainly might be much more if a serious beginning is done.

any OS project also needs a homepage - sourceforge.net is NO real option as it leads to a total LACK of identification of the current coders with their project. once you start an OS project you have a responsibility - just like a Guru who starts to teach and guide people home!!! a responsibility to perform, to bugfix, to maintain, to improve, ...

love and bliss

hans