eric B. wrote: > Being a rather new to ASSP, I will take a look at the interface as well and > point out where I find/found it unclear. Maybe someone else will be able to > pick up on the thread afterwards for additional clarification. Overall, > however, I have to say that in general, I didn't find the descriptions > confusing, as much as I found I was missing a document / instructions that > explain how everything ties together. On its own, each description was > rather clear, once you understood what the general concept of the parameter > was for. An immediate example I can think of is something like the red > list. The descriptions for the different redlists options are clear, but > the whole concept of the redlist is/was still a bit hazy, and thus I needed > some clarification (I'm still a bit grey on it, but I have a better > understanding at the moment).
Clarification on the features and how they work together is a problem right now. Even with all the documentation and people here it took me a bit of thinking to wrap my head around some of the features when I first installed ASSP. > I think either building a more complete FAQ, or even better some form of a > flowchart (I know this is going to be very complex) that explains the > processing might be more helpful. I think a flowchart existed in the > original ASSP doc pages, but isn't complete based on today's featureset. The problem with flowcharts and ASSP is that they become extremely complex and hard to layout. I've tried :) I sidelined that project a while back and currently the only ones that made it to the wiki are the Delaying and general layout flowcharts. > The other thing that I think can be extremely useful to newcomers (again, > like myself), would be an example set of real-world values for the config > files. I know Fritz was kind enough to provide a whole bunch of screen > shots a month back or so when I had asked (thank you so much), but if we > could take that kind of information and provide it either in the ASSP > package itself, or as a startup-example-config package, that might go a long > way. Especially for people who - a) don't know what settings are "good" > settings, b) who are rusty with regexs, etc. Agreed, we need a "recommended settings" article with suggestions and solutions for common needs that people look to ASSP for. As for Regexs they are still something of a mystery to me, but are becoming clearer over time, something that went into detail about what they are and how they work would be nice for reference. > Finally, something else that would be great (long term again), would be an > ability to share / communicate with others the lists/regexs that people use > for blacklists, no-delaylists, spam/script-bombs, etc.. Given that those > are lists that need to be kept up-to-date, etc, a way to communally share > them would probably be useful. Wiki? non-sourceforge forum perhaps? Kevin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
