Re: [Openpacket-devel] OpenPacket demo comments

[Jacob H. <ha...@gm...>]

Well, may I suggest that now is a good time than ever to start a
SVN/CVS server for the site?  I could host the site and SVN for
development.  Then give access to developers who would like to work on
feature requests / bugs.

We could also have the SVN repo on sourceforge and/or google.  Not
sure if David is ready to do such a thing or not.  But I would
definately like to help with some of these features and/or design.

Jake

On 8/4/06, Richard Bejtlich <tao...@gm...> wrote:
> David -- phenomenal job.  These are my immediate comments as I try the site:
>
> -- Love the RSS feeds!
>
> -- I assume people can't access the URL for an unapproved feed (say
> http://roach4.no-ip.org:8000/viewfile/25 if 1-24 are already approved)
> ?
>
> -- When approving traces, can there be some sort of "approve with
> comment" or "disapprove with comment" instead of just Y or N?
>
> -- It would be helpful for moderators to be able to review a
> Moderation History log to see who made what decisions, and when.
>
> -- We need a "remoderation" feature.  A moderator might make a
> mistake, or miss something.  So we'll have to be able to remove a
> trace, or maybe add it in later.
>
> -- When browsing files, it would be nice to have a Rating based on
> user feedback.
>
> -- Each trace should have a counter showing number of downloads, if possible.
>
> -- Could you set some kind of marker on the trace indicating if the
> trace was  sanitized during upload or not?
>
> -- When browsing files, sorting on various columns would be cool.
>
> -- It would be neat to make trace uploader IDs a linkable feature that
> would show all traces uploaded by that user ID.
>
> -- When looking at individual traces, the trace uploader ID is
> currently a link to their email address.  I would prefer removing that
> to foil spammers.  It would also be good to instead link to a page
> built for the individual user.  Maybe that page would also list all of
> their uploads, as mentioned earlier?
>
> -- I'm starting to wonder how best to organize these traces.  We
> probably want some means of letting users indicate their idea of what
> the trace is.  We probably want the moderators to make the final
> determination.
>
> -- We might want to stick with really generic categories, like
> "normal," "suspicious," "malicious," or "unknown."
>
> -- Are you saving any information about the traces once your parser
> reads them?  For example, is it possible to search for traces
> involving IP X or port Y or protocol Z?
>
> -- We may have to end up having the traces available mainly via
> queries.  In other words, trying to define rigid categories might be
> doomed.
>
> -- I'll have to develop some disclaimers, FAQs, etc.  I also need to
> work on sponsors.
>
> This is really awesome.  I think having this concrete site will help
> us answer lots of questions.
>
> Thank you,
>
> Richard
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Openpacket-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openpacket-devel
>