After submit, automatically display next report

[C600G]

After submitting the spam report, a great usability and efficiency improvement is to have SC display the next report to process (if there is one, of course!) instead of making the user click on the "Report" link to get the next one.

Especially when SC is slow on reponse, this would save user's time (one long wait instead of two) and reduce the number of web submit requests for the server to process (if I emailed in 10 spam reports, I will have 20 submits - 10 from the "Report" click and 10 from the "Send" click.

(Not sure where to post this - I did not see a "feature requests" area)

[Wazoo]

After submitting the spam report, a great usability and efficiency improvement is to have SC display the next report to process (if there is one, of course!) instead of making the user click on the "Report" link to get the next one.

Especially when SC is slow on reponse, this would save user's time (one long wait instead of two) and reduce the number of web submit requests for the server to process (if I emailed in 10 spam reports, I will have 20 submits - 10 from the "Report" click and 10 from the "Send" click.

(Not sure where to post this - I did not see a "feature requests" area)

You've not described your "subscription type", so here's one shot to try.

You need to go to the web site (URL was in your confirmation e-mail), paste in a spam for processing, but remember to click the box at the bottom and accept the cookie. This first click/box sets you up for the "auto-submit" for your next spam submittal .... repeat this a second time, and look for the new check-box, which will turn on Technical Details ... this puts out some of the resulting parser checks and responses that will better aid you in trying to figure out what went wrong in a parse, do you agree with the findings, etc. ....

[C600G]

Thanks for the reply.

I am not sure what "auto-submittal" is and provides, and I do see "Technical Details" and have had that on for a long time.

You've not described your "subscription type", so here's one shot to try.

Paid spam reporting.

The issue occurs with processing spams emailed in, not pasted into the webform.

After logging in, then click the "Report" link, then view the spam analysis, then click "Send", then see the list of sent email report addresses and another "Report" link if another is waiting for processing. Instead of another report link, I would like to see SC automatically begin analysis of the next one and display it for "Send"ing.

Was I more clear? Does this feature already exist and I do not know how to set it on? I have looked at prefs etc. but saw nothing.

[Jeff G.]

No, that feature doesn't exist. If it did, you would be able to hammer the servers faster.

[jefft]

Was I more clear?  Does this feature already exist and I do not know how to set it on?  I have looked at prefs etc. but saw nothing.

No, the feature is a good idea and it's been suggested before. It doesn't exist yet, though.

JT

[C600G]

No, the feature is a good idea and it's been suggested before. It doesn't exist yet, though.

Thanks for the info jefft. Have there been any thoughts to a publicly viewable feature request list (and allow adding of new ones)? Would prevent repeated posts of previous suggestions and losing them when wanted.

Another idea after that one is to give each user a certain number of points per year to vote on the one(s) they want most? Would help internal planning on what things to add next when ready to consider user input.

No, that feature doesn't exist. If it did, you would be able to hammer the servers faster.

and the server could handle them faster as this change would cut in half for the server the number of requests to process and responses to send! Besides the "not the best" usability of it as it is today, the server initiating to process a request has overhead (not necessarily huge, but some), which consumes resources - resources that could be better spent processing spam reports instead. Reducing the request/response count helps improve the system's capability to handle larger loads.

Another way to say it is crippling usability is not a proper solution to throttle server loads.

Jeff J