|
|
|||
|
|
||||
|
Problems, Questions and Suggestions The WebRing.com System Overview This page provides a listing of some of the problems, suggestions and questions related to the WebRing.com system.
Summary
After some suggestions that one be created, WebRing.com hosted a forum that, at first, seemed to be for the proposal of proposed enhancements to the system. Listed on the home page of WebRing.com as "Proposed Enhancements", the actual name of the forum is "RingMasters of WebRing.com". Unfortunately, while the forum does report changes which have been made to the system, it does not seem to post proposed enhancements so that they can be discussed. In addition while problems and issues, as well as questions and suggestions, are frequently posted in the "Manager's Forum", members who are not managers do not have access to those messages. There was, once upon a time, another "Wish List", but it is gone too. There no longer seems to be any public, system maintained database to track such items. Finally, I find myself frequently posting problems, issues, questions and suggestions and, if only for myself, I need to track them. For that reason, I have created this page. Whose Are These? This is not an official page. This is not an official list. The objective is to track those problems and suggestions that catch my interest. Most are problems and suggestions that I have posted. A few are based on problems and suggestions posted by others which caught my interest. The list is not comprehensive by any means. There are problems, questions and suggestions which I have not captured. In addition, the "history" is not here. Many, many, many problems and suggestions made through the years have been addressed. This list does not reflect those. In the interest of credit, I've tried to create links to some of others' posts in various forums. But, the decision to list them here is mine. The choice of words is mine. The organization is mine. Ultimate, these are my responsibility. If you wish to give credit, give it to others. If you wish to assess "blame", toss it my way. Corrections and Suggestions If you have any questions or suggestions, or if you just want to point out a typo, feel free to write me. The Problem List
The Suggestion List
Problems Problems: Failures of the system to perform as documented, or, in the absence of explicit documentation, as reasonably expected. P-1. Custom Navbar Colors Processed Incorrectly References Background 1. For this test, use a standard WebRing.com Navbar. 2. Click "Navigation Code". 3. You are now on the page to "Customize Navigation Bar". 4. For the Outline Color, click the Radio Button to 'Enter Hex Color Value" and enter a code of #FFDDDD. 5. For the Link Color, do exactly the same thing: click the Radio Button to 'Enter Hex Color Value" and enter a code of #FFDDDD. 6. For the Text Color, do exactly the same thing: click the Radio Button to 'Enter Hex Color Value" and enter a code of #FFDDDD. 7. Click Preview 8. You will see the navbar with very faint pinkish-brown outlines, text and links. 9. Click Finished. 10. Click on Color Scheme. 11. Click on Navigation Code. 12. You are now back to the page to "Customize Navigation Bar". 13. Notice that the navbar appears correct --- as you left it. 14. However, also note that the Radio buttons you clicked are not clicked. 15. Change the background color. Doesn't matter what. Just change it. 16. Click Preview. 17. Note it changes. And all looks good. 18. Click Finished. 19. Click on Color Scheme 20. Click on Navigation Code. 21. You are now back to the page to "Customize Navigation Bar". 22. Notice that the navbar is incorrect . All of your custom colors for the Outline, Text and Link are gone . This is a problem. Problem Summary The system does not correctly set the Navbar Maintenance input screen when custom colors are used. The result is that a Ringmasters choices of custom colors may be destroyed by the system. Possible Fix Whenever custom colors are used, the system should pre-select the radio buttons for the custom colors. P-2. System Navigation After Work on Navbars References Background When you have finished work on your webring Navbar and click "Finished" you end up in a "limbo". Even though you have "left" the Navigation Code section of management, the "Navigation Code" item on the menu is still black so you can't go back to the Navigation Code section. Problem Summary A navigation menu item should only be blacked out if you are "in" that section. In these circumstances the "Navigation Code" item is blacked out and unavailable even when you are no longer "in" that section. Possible Fix Re-enable the "Navigation Code" menu item on the page following completion of work on a Navbar (the page you get after you click "Finished"). The general URL of this page is: Related Suggestion Suggestion S-4 also relates to navigation issues during Navbar maintenance. P-3. Form Text Fields Improperly Set As Textarea References
Background When a form is created on a webpage, a field can be set as "text" or as "textarea". Text is for a "one line" field (e.g., name, ID, password, color, URL) Textarea is for "multiline" data (e.g., comments, html code, email text, etc.) On WebRing.com, on two different forms, fields which should be "text" are improperly set as "textarea". These forms are:
Problem Summary Form fields that can functionally only accept one line of data are improperly set as textarea fields to accept multiple lines of data. Possible Fix Change these fields to type "text" to eliminate the multiline possibility. P-4. Lack of Alt Text for Key Graphics References
Background International accessibility standards require that all significant graphic on a web page use alt text to identify that graphic. These standards are particularly important for all sight impaired users. These standards include:
More information is available here:
Currently, if a webring logo is specified for a WebRing.com webring, no alt text is assigned to that graphic on the hub/list page. Problem Summary The Hub/List page does not assign alt text to the webring logo. Possible Fix 1. Permit the ringmasters to write such alt text. 2. Default such alt text to the name of the webring, but permit the ringmaster to override this text to more correctly comply with accessibility standards. (NB: use of the name of the webring as the alt text would be "better" than no alt text at all, but it does not meet the standards. Custom written alt text is required to describe adequately the picture as required by the standards.) P-5. System Shows Suspended Members But Then Denies They Exist - RESOLVED References
Resolved This problem has been resolved by a system change noted here. My testing has confirmed the change. Background User britfeldweimaraners posted this problem about her specific webring http://m.webring.com/hub?ring=webfehler. The original post was 26.Mar.2005. As of 16.Apr.2005 it is still an error. This webring shows suspended members. They were suspended because they are using the HTML version of the code. When britfeldweimaraners attempts to send them a message about the problem, the send return page says:
The ring is Private, not listed in the directory or search, and is closed to new members. Problem Summary Even though the system shows suspended members, when you try to email them, it denies they exist. Questions Questions: Questions of significance asked of or about WebRing.com. No questions are currently documented on this page. Suggestions Suggestions: Ideas for improvements of the WebRing.com system. S-1. Notice About Serving Images Off Other Servers References
Background When a you (a manager) clicks on "Edit Ring Logo", you go to a page that says (in part)
I like that this notice "names names" to help new ringmasters recognize some of the services which cannot deliver their graphics. Similarly, when you click on "Navigation Code" and then "Navbar Logo" you go to a page that says (in part)
Suggestion Incorporate the the server specific language first quoted above (which mentions Yahoo, Geocities, FortuneCity, et. al.) on all other pages (e.g., the navbar page noted above). Benefits Ringmasters, particularly new ringmasters would be reminded more than once and would more quickly realize that their graphics cannot be served off of all external servers. S-2. Improve Ring Homepage Setting References
Background On the Edit Global Settings page, there are two fields:
The advantage of entering the Ring HomePage Site is that a link to this site will appear at the top of the Hub/List page with the label "Ringmaster's site". The advantage of using the Ring HomePage URL is that the page need not be the Ringmaster's page within the webring. This permits the Ringmaster to have separate (a) membership pages and (b) home pages. But, there is a problem. When you use the Ring HomePage URL instead of the Ring HomePage Site , the system does not create a link on the Hub/List page to the referenced home page. Suggestion If the Ringmaster uses a Ring HomePage URL , place a link on the Hub/List page. Place it in the same "line" as the current links to the Ringmaster Profile page and Ringmaster's site. A possible label might be "Home Page". Benefits This would permit Ringmasters to have (a) a member page and (b) a separate home page page and (c) to have a link to the home page on the Hub/List page. S-3. Management Display of the Navbar Logo References
Background When you click "Navigation Code" in the management section (to be able to adjust your navbar) , the system does not tell you whether you currently have a logo. If your current navbar code uses the logo, you will see it below in the navbar sample. But if your current navbar code does not use the logo, you will not know. Suggestion Show the logo at the top of the page, perhaps at a "reduced" size(e.g., 50 x whatever) just as a guide as to whether a logo has been uploaded at all, and if so, what it is. Benefits Ringmasters could see the navbar logo currently stored on the system without the need for the navbar to be using the logo. In addition, if a the logo were being uploaded, the system would display the results of that upload allowing the ringmaster to confirm that the upload was successful, even if the navbar was not using a logo at the time of the change. S-4. System Navigation After Navbar Logo Upload References Background After uploading a new navbar logo, the system "leaves" the management section for working with the navbar and returns to the "display" of the members of the webring. It is not possible to immediately see whether the logo was uploaded correctly nor is it possible to see the effect of the upload. Suggestion After the uploading of a new navbar logo, the system should return to the "general" Customize Navigation Bar page (http://x.webring.com/wrman?custnavbar&ring=whatever) Benefits This change would confirm that the graphic uploaded correctly and it would also permit immediate work on the navbar code if desired. Related Suggestion Today, to confirm that the upload occurs, it is necessary for the navbar to be set to use the logo. It would be more easily confirmed, even if the navbar is not set to use the logo, if Suggestion S-3 is adopted. S-5. Adding Hub/List Page URL to Emails References
Background Like most who own/operate webrings, I receive emails from my members. They arrive saying something like ...
Suggestion Add the URL of the Hub/List page of the webring in question (e.g., http://h.webring.com/hub?ring=poetic2). Benefits It would speed responses to the emails and improve service to our members. S-6. Increase and Standardize Form Field Sizes References
Background The pages used to customize administrative emails have large, easy to use form fields.
These is larger than the form fields on many other pages.
Suggestion Increase (and possibly standardize) the form field sizes across the system allowing more characters in width (e.g., 72 characters of width) and more rows of text (e.g., 18-20 rows of text data). Benefits Increased user friendliness, increased ease of use of the data forms and a consistent look and feel across the WebRing.com system. S-7. Sort Webring List By Age of Pending Memberships References
Background WebRing.com suggests that webrings with "old" pending memberships should be attended to. It feels so strongly about this that if a ringmaster fails to attend to pending memberships for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend to "old" pending memberships it sends Property Seizure Notices via email to advise the ringmaster. In addition, I believe that older pending memberships should be processed first. That is, those who apply first should be processed first. This processing concept is called FIFO (first in, first out). At the present time, the only tool available to a ringmaster to facilitate FIFO processing are the emails sent upon application to the webring. Suggestion Add a sort function to the ringmasters list of webrings to be able to sort the list based on the order of the oldest pending application. Benefits Ringmasters would be able to process applications on a FIFO basis, attending to the oldest applications first. This would be particularly useful if a ringmaster was prohibited from managing his webrings for a brief period (e.g., through sickness, travel or technical issues). When the ringmaster returned, he could immediately begin processing the oldest applications first, working back toward newer applications. S-8. Property Seizure Notices Should Disclose Risk of Property Seizure References Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. Property Seizure Notices #2 and following include this text
The first Property Seizure Notice does not include this text. Suggestion Include the referenced text in the first Property Seizure Notice. Benefits The risk of property seizure by the system would be more fully disclosed to ringmasters at every step of the Property Seizure Notification process. S-9. Property Seizure Notices Should Disclose Specific Management Errors and Possible Errors References Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. Property Seizure Notice #1 specifically identifies what the system considers to be the standards violation. If there are multiple issues, it identifies those. However, subsequent Property Seizure Notices (numbers 2 and following) just list the possibilities and do not list the specific "infraction". Suggestion All Property Seizure Notices should include:
Include this information in the first Property Seizure Notice as well. Benefits Ringmasters may, for a variety of reasons, not receive one or more of the Property Seizure Notices sent by WebRing.com. Full disclosure in all Property Seizure Notices will increase the likelihood of error resolution by the ringmaster. Further, full disclosure in all Property Seizure Notices will increase awareness of the possible standards violations which could lead to property seizure by the system. S-10. Improve Ability To Manually Suspend Members with Automated Management System (AMS) Enabled References
Background Ringmasters who use the Automated Management System (AMS) may still need to suspend a membership. However, such suspensions are not for "code" issues, but relate to other problems (e.g., lack of links from the site into the webring, questionable content, inappropriate site description, links to adult sites). Because code is not the problem, if such a suspension is made without disabling AMS for that particular member, the system will automatically activate that member. For this reason, every suspension also requires turning off the AMS for that site. Suspending and turning off AMS can be complex. For example, if the site was found through a search, then turning off AMS requires searching again to find the site to suspend it. Suggestions 1. Provide an option that the ringmaster can set to have the system automatically turn off AMS for all manual suspensions. 2. If #1 is not possible, add an additional button that will suspend and turn off AMS in one click. Benefits The ability to more easily manage a webring will decrease ringmaster frustration, improve the WebRing.com image and increase the routine management of the webrings in the system. S-11. Add Web Based Message to Explain Manual Suspension References
Background Whenever you manually suspend a member, the member should receive an an email explaining the reason. But, there are a wazillion things that can go wrong with email. Regardless of whether the member receives the notice or not, it would be helpful to have a web based method to tell a member why his site is suspended. Suggestions Provide a simple text field of a couple hundred characters that
Currently, when a member visits the hub page, the "Edit Site Info" link appears in the left column. That serves to tell the member that they are a member as well as providing a link to edit their details. Add to that left column display, the site status (active, suspended, passing, fail, etc.) and, if applicable, the text field explaining the "reason". For example, the left column might say
(In this example, "You have adult links on your site" would be the text entered by the ringmaster at the time of suspension.) Benefits Members visiting the hub page would more quickly know the status of their site in that particular webring and, in the case of suspension, the specific reason for that suspension. S-12. Change Label Currently Shown as "Hits" References Background The column labeled "hits" on the "Top 30 Rings" list (and probably other lists as well, are not hits. Instead, then they are the results of some calculation the WebRing.com system does. Suggestion Change the label from "hits" to something else. "Hits" has a meaning. But the numbers shown, while derived in part from "hits", are not hits. Benefits Less confusion and "truth in labeling". S-13. Place the Join Instructions Field in the Left Column of All Join/Management Pages. References Background On the "Process New Sites" page and the "Manage Members" page, the left column is wasted. It currently says:
That hasn't changed in a wazillion years. A better alternative, acknowledged by "system" is to place the new Join Instructions field into that left column. Suggestion Replace the current text in the left column of all Join/Management pages with the new Join Instructions field. Benefits As ringmasters manage their webrings, they will have, immediately on those management pages, descriptions of the exact purpose of their webring as well as their own summaries of the restrictions they might impose on memberships. And, as noted above, the "system" acknowledged this benefit. S-14. Check for Mismatched Codes in Custom Navbars References
Background After the Yahoo! debacle, WebRing.com added a delightful feature: the ability to customize the HTML code for the navbar. While this is a great feature, it sometimes has unintended consequences. One reason is that ringmasters make unintended errors in the HTML. A common one is "opening" a code or tag but failing to "close" the code or tag. For example, they may open a division (<div>) but not close the division (</div>). Or they may not close a table or a font specification. Suggestion Implement a simple check for unmatched codes or tags. For example, each of the opening codes could be counted and compared against a count of the corresponding closing codes. Benefits While such a simple check would not ensure that the HTML code would be properly structure and would not ensure that the code would actually "work", it would help to prevent some of the more egregious code errors, particularly those which have cascade effects on the entire stack. S-15. Include Specific Clarifying Information for All Unanticipated Page Redirects References Background When a ringmaster commits a transgression of WebRing.com policies, the system may choose to redirect that member to a page other than the one expected. For example, the system may redirect you if you have "too many" emails in your account. Suggestion All redirects based on a policy transgression should include a clarifying message and, if possible, a link to more information. For example, if the system decided to redirect a member to a page because of "excessive" emails, a message should indicate the reason for the redirect and link to a page offering more information. The information should include the specific criteria required to eliminate the redirect (i.e., the trigger level). Benefits Ringmasters would more immediately understand what is going on, management would improve and there would be fewer queries to support forums and help resources. S-16. Identify and Explain All System Modifications of Ringmaster Specified Webring Data References Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. When the system triggers some of these Property Seizure Notices, it also resets some webring specific data. For example:
In addition, the system may reset webring specific data for a variety of other reasons. Here are three more examples:
Suggestion The WebRing.com system should identify and explain all system modifications of ringmaster specified webring data (e.g., application expiration time, navbar code, etc.). Such identifications and explanations should, at a minimum:
Benefits Ringmasters would immediately know what data was changed and why. Currently it may take days or weeks to realize the system has initiated a data change. Additionally, ringmasters would be directly encouraged to correct the problem. This would improve the public image of WebRing.com and improve overall webring management by ringmasters. S-17. Implement Web Based Property Seizure Notices to Supplement the Email Notices References Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. One reason these property seizures can happen is that ringmasters may not receive the emails. For example, if the WebRing.com mail servers become listed on any of the SMTP blacklists, that email mail not reach the ringmaster. Or, if the WebRing.com email is constructed using phrases or techniques that major spam filters (e.g., SpamAssassin) consider "spam like", that email may not reach the ringmaster. Neither of these possible occurrences are the "fault" of the ringmaster, but both may prevent proper notice of the pending property seizure. In addition, things which trigger action by WebRing.com (e.g., leaving applications pending for months), may not bother some older ringmasters. Suggestion WebRing.com should implement a simple, web-based, Property Seizure Notice to supplement email notices. Whenever a ringmaster logged in, the ringmaster would be advised of the pending threat of property seizure even if the email notices were erroneously diverted. This notice should include a one-click link to a page showing all webrings being threatened with property seizure. The webrings should be listed in order of threat, beginning with those requiring most immediate action to avoid property seizure and ending with those still having the most time before property seizure. This web-based notice should not preclude the ringmaster from attending to other webring business. That is, it should not be a "block", but rather a constructive notice. The web-based Property Seizure Notices should not be attempted via pop-ups. Pop-up blockers, such as those now standard in Internet Explorer, will prevent pop-ups from being seen. Benefits Ringmasters who do not receive the Property Seizure Notices via email or who may generally receive the emails but who do not receive one particular email, would be advised of the issue with their webring. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-18. Document the Conditions which Trigger Property Seizure References Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. I am unaware of any page on the WebRing.com site which provides a clear, concise, cogent, comprehensive list of the conditions which will trigger property seizure. Suggestion 1. Expedite a full documentation of the conditions which will trigger property seizure and publicize this list to increase compliance by ringmasters. 2. Reference this documentation in all Property Seizure Notices. 3. Note all changes to these conditions on the WebRing.com status pages such as http://dir.webring.com/h/status20050112. Benefits Preventative action to prevent the conditions would be increased. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-19. Document the Property Seizure Process References
Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. I am unaware of any page on the WebRing.com site which provides a clear, concise, cogent, comprehensive documentation of the process of this property seizure. Suggestion Expedite a full documentation of the property seizure process. Benefits Preventative action to prevent the conditions would be increased. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-20. Improve the Email Address Verification Process References
Background The WebRing.com system has implemented a web based email system. In order to maximize the use of this system, the members need to authenticate/validate their email address. Since that introduction I have coached numerous individuals having problems. In many cases the problem seems to be the inclusion of a trailing space in the email which is then transferred into the validation field. Suggestions 1. Alter the outgoing validation email to remove the trailing space and terminate the line immediately after the validation code. 2. Alter the incoming process to "trim" the authentication code (i.e., remove both leading and trailing spaces) before comparison, thus eliminating trailing as an issue. Benefits These changes would reduce member problems with this function and reduce the contact load on support S-21. Provide for a Second Email Address for Property Seizure Notices References
Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. One reason these property seizures can happen is that ringmasters may not receive the emails. For example, if the WebRing.com mail servers become listed on any of the SMTP blacklists, that email mail not reach the ringmaster. Or, if the WebRing.com email is constructed using phrases or techniques that major spam filters (e.g., SpamAssassin) consider "spam like", that email may not reach the ringmaster. Neither of these possible occurrences are the "fault" of the ringmaster, but both may prevent proper notice of the pending property seizure. In addition, things which trigger action by WebRing.com (e.g., leaving applications pending for months), may not bother some older ringmasters. Suggestion Provide for a second email address for Property Seizure Notices. Ringmasters could specify this second email address (e.g., an account on another server, or a friend's account) as a "backup" for the critical Property Seizure Notices. Benefits Ringmasters would have a backup against the many technical issues which might prevent the delivery of a particular email. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-22. Increase Disclosure of the Importance of the Registered/Verified External Email Address for Property Seizure Notices References
Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. One reason these property seizures can happen is that ringmasters may not receive the emails. For example, if the WebRing.com mail servers become listed on any of the SMTP blacklists, that email mail not reach the ringmaster. Or, if the WebRing.com email is constructed using phrases or techniques that major spam filters (e.g., SpamAssassin) consider "spam like", that email may not reach the ringmaster. Part of the problem may be that new ringmasters do not understand the critical importance of the registered/verified external email address. These ringmasters may register an email address for the sole purpose of becoming "verified" but never actually check the registered address. Suggestion Improve the description of the purpose and importance of the registered/verified external email address. More clearly explain that this address will be used for all critical notices including possible Property Seizure Notices, as well as user banning and similar system actions. The page http://a.webring.com/cgi-bin/info would be one place for such a notice. The page http://a.webring.com/cgi-bin/info?screen=infowrmail already a similar notice, but it can be improved. Benefits Ringmasters would be less likely to ignore their registered/verified email address. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-23. Provide an Option for Property Seizure Notices to Go Both to the External Email Address and Also the WebRing.com Mail System References
Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. One reason these property seizures can happen is that ringmasters may not receive the emails. For example, if the WebRing.com mail servers become listed on any of the SMTP blacklists, that email mail not reach the ringmaster. Or, if the WebRing.com email is constructed using phrases or techniques that major spam filters (e.g., SpamAssassin) consider "spam like", that email may not reach the ringmaster. Neither of these possible occurrences are the "fault" of the ringmaster, but both may prevent proper notice of the pending property seizure. In addition, things which trigger action by WebRing.com (e.g., leaving applications pending for months), may not bother some older ringmasters. Suggestion Provide an option for the Property Seizure Notices to be directed both to the external email address and also to the WebRing.com Mail System. Set this option as the default when the feature is implemented and when new memberships are created. Benefits Ringmasters would have a backup against the many technical issues which might prevent the delivery of a particular email. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-24. Copy All Property Seizure Notices to Webring Helpers References
Background WebRing.com has "standards" for the maintenance of webrings. Although these "standards" are not formally disclosed anywhere, if a ringmaster violates these standards for "too long", WebRing.com will seize the webring and transfer ownership to another ringmaster through a process called "adoption". To alert the ringmaster to the need to attend violations of these "standards", the system sends Property Seizure Notices via email to the ringmaster. One reason these property seizures can happen is that ringmasters may not receive the emails. For example, if the WebRing.com mail servers become listed on any of the SMTP blacklists, that email mail not reach the ringmaster. Or, if the WebRing.com email is constructed using phrases or techniques that major spam filters (e.g., SpamAssassin) consider "spam like", that email may not reach the ringmaster. Neither of these possible occurrences are the "fault" of the ringmaster, but both may prevent proper notice of the pending property seizure. In addition, things which trigger action by WebRing.com (e.g., leaving applications pending for months), may not bother some older ringmasters. Suggestion Send copies of all Property Seizure Notices to designated webring helpers. Benefits Ringmasters who designate helpers to assist with management would have backup for all critical management issues which trigger Property Seizure Notices. Ringmasters would have a backup against the many technical issues which might prevent the delivery of a particular email. Corrective action would be expedited and property seizures would be reduced. Claims of "I did not know" would be reduced. Management would improve as would the public image of WebRing.com. S-25. Allow Helpers to See Webrings for which They Have Been Designated as Helper References Background Ringmasters can designate "helpers" for their webrings. However, there is no way for helpers to see a system page showing all webrings for which they are designated helper. Suggestion Provide a way for helpers to see all webrings for which they have been designated as helper. Benefits Faster maintenance of webrings, reduced delays addressing problems and an improved public image for WebRing.com S-26. WebRing.com System "Staff" Should Identify Themselves Uniquely References
Background When the WebRing.com system "staff" post to forums, they use common login IDs and do not uniquely identify themselves. It is difficult to identify who said what. Suggestion WebRing.com system "staff" should uniquely identify themselves, either by using unique IDs or by signing emails. (NB: if pseudonymity is desired, a "nickname" or "handle" may be used as a signature.) Benefits Forum readers would know who is saying what. S-27. Add Option to Sort Members by ID References
Background While the current Manage Members page offers a variety of selection options, it offers no sort options. One sort option that would be useful is to sort by member ID. Suggestion Add an option on the Manage Members page to sort by member ID. Benefits This would permit a ringmaster to see all the memberships each member had in the webring. S-28. Change Management Function Results Pages References
Background When working on WebRing.com management functions, many of the functions "complete" by returning to a general page displaying a member list. While this isn't a big deal on DSL, on dial up it is a bit slow. Also, it increases the bandwidth load for the system. As ringmaster perform management functions, this is frequently unnecessary. For example, I frequently perform management in groups, approving members, suspending members, deleting members, updating messages, changing the descriptions and join pages, and updating the navbar. As I click from function to management function I really don't need to see the member list until I am finally done. It might (maybe) be worth changing this (or providing a configurable option) so that within the management functions it just returns a page with the management menu (and, of course, a link to return to the member list). Suggestion Provide an option to let ringmasters have the system complete management functions by returning to a page that just shows the management menu and does not display the entire member list. Benefits Faster page updates for ringmasters on dialup and a reduced bandwidth load for the system. S-29. Modify the Email Field on the WebRing.com Mail Configuration Page References
Background The Email Field on the WebRing.com Mail Configuration page at http://o.webring.com/cgi-bin/info?screen=infowrmail does not currently have an explanation that changing that field requires revalidating the email address. That is, the external email address on the Account Settings page and the external email address on the WebRing Mail Configuration page are not two separate email addresses, but are the same email address. Changing this email address without re-verifying may prevent system emails from being sent to the email address. Suggestions 1. Add explanations to the Email Field on the WebRing.com Mail Configuration page, or 2. Eliminate the ability to modify the external email address from the WebRing Mail Configuration page and direct the user to the Account Settings page for all such changes. Benefits Users are less likely to change their email address and not realize that it requires a new verification.
S-30. Change Text on Management Settings Page: References
Background The Management Settings page has a setting labeled
However, as the system has clarified it does not actually expire (delete) pending submissions. It only expires (deletes) pending submissions without PASS or PASS_L status. Suggestion Change the wording to read:
(In addition, if the ringmaster has specified that PASS_L is equivalent to "fail", the system should automatically expire (delete) them as well.) Benefits The current wording is misleading. The new wording would be more correct. S-31. Implement Some Form of Acknowledgement/Tracking of Support Requests References
Background Currently, when a help request is sent to WebRing.com support, there is no acknowledgement that the request was received, no way to know how long it will take to address and no way to know when follow-up would be appropriate. Suggestion When a help request is sent to WebRing.com support, provide some form of acknowledgement and tracking. This might include:
Benefits WebRing.com customers would be less likely to duplicate requests. In addition they would have a better experience during their help request process, improving the public image of WebRing.com. S-32. Implement a "Reconfirm Suspension" Button References
Background WebRing.com has decided that suspending members which "pass" is bad, so bad that if you do it for too long they will seize your webring and give it to someone else. The current "solution" is to: a) activate the member, being careful not to send a message b) re-suspend the member, again being careful not to send a message Suggestion Implement a "reconfirm suspension" button. This button would enable a ringmaster to tell the system that yes, the ringmaster DOES want to keep this member failing even though the site "passes". Benefits When WebRing.com sends a Property Seizure Notice because the member is suspended but "passes", the ringmaster could just go in and click the "reconfirm suspension" button to say "yes, I know, and I want it that way." Ringmasters could more easily comply with the policies of WebRing.com resulting in fewer seizures, fewer dissatisfied ringmasters, less discussion about such items in the forums and an improved the public image of WebRing.com. S-33. Check the "Suspended Sites" Calculation and Clarify the Messages References Background WebRing.com has decided that suspending members which "pass" is bad, so bad that if you do it for too long they will seize your webring and give it to someone else. However, there is some public confusion about the exact calculation algorithm used to determine what is "too long". One Property Seizure Notice says:
Another Property Seizure Notice says:
Neither notice is precise. In addition there is at least one report in this forum that the calculation may be flawed. This report suggests that a member who has been suspended as failing for a month, and who then becomes "passing" on a Friday, may be reported under this algorithm because the algorithm measures the time from suspension instead of the time from "passing". Suggestions
Benefits The exact nature of the policy would be clear and all references to the policy would be precise and match. Ringmasters could more easily comply with the policies of WebRing.com resulting in fewer seizures, fewer dissatisfied ringmasters, less discussion about such items in the forums and an improved the public image of WebRing.com. S-34. Clarify Messages About "Unsatisfactorily Low Navigation Ratings" References Background WebRing.com has decided that having "an unsatisfactorily low navigation rating" is sufficient cause to seize your webring and give it to someone else. One of the Property Seizure Notices uses this language:
However, this notice does not indicate what constitutes an "unsatisfactorily low" rating. The notice is not precise. Suggestions
Benefits The exact nature of the policy would be clear and all references to the policy would be precise and match. Ringmasters could more easily comply with the policies of WebRing.com resulting in fewer seizures, fewer dissatisfied ringmasters, less discussion about such items in the forums and an improved the public image of WebRing.com. S-35. Have the Code --ssnbcode-- Work in the Approval Email and All Other Emails References
Background The substitution code --ssnbcode-- works in the Application Email to deliver the recommended SSNB Code to be placed on the member's web page. However, in the Approval Email, this substitution code is not evaluated and replaced. This substitution code is also not evaluated and replaced in other emails (e.g., emails sent to individual members or selected members). Suggestions Have this substitution code available for evaluation and substitution in the Approval Email and in all other emails as well. Benefits Having substitution codes consistent across the system will improve the ability of ringmasters to properly use the substitution codes. This will reduce both member and ringmaster issues, reduce discussion about such items in the forums, reduce support requests for such items and improve the public image of WebRing.com S-36. Stop Modifying Ringmaster Specified Webring Data on Voluntary Transfers References
Related Suggestion Suggestion S-16 also relates to the system changing ringmaster specified data. Background Whenever one ringmaster transfers a webring to another ringmaster, the the system resets some webring specific data. For example:
Suggestion Do not make these changes. Benefits I have suggested in another item (S-16) that the WebRing.com system should identify and explain all system modifications of ringmaster specified webring data (e.g., application expiration time, navbar code, etc.). However, for these particular modifications which result from a voluntary transfer from one ringmaster to another, my suggestion is that the changes not be made at all. While changes may be appropriate for system initiated and managed changes, I am unable to identify any system need to execute such changes for a voluntarily initiated transfer. Further, in a variety of cases (e.g., a transfer to permit "baby sitting", or a transfer from one ID to another of the same ringmaster) such changes actually work to the detriment of the webring. They must be recognized and changed back, increasing the work of the ringmasters and the system bandwidth load. Eliminating these changes would permit ringmasters to transfer webrings "intact". This would improve overall webring management by ringmasters and would eliminate an unnecessary annoyance. S-37. Allow One Time BCC Copy of Emails to the Ringmaster References
Background The WebRing.com system provides a feature to enable a ringmaster to receive copies of emails. By clicking "Customize Emails" on the management toolbars, the ringmaster can turn on BCC copying of the emails for:
Once this option is set, the ringmaster will automatically receive a "BCC" copy of these email. Suggestion Add an additional option on the send page for some of these emails to specify a "one time" BCC to the ringmaster. This would include:
This option could be added as a checkbox in the same location as the checkboxes for "Save as Default Email" and "Do NOT send email this time ONLY". Benefits These emails are sent by ringmaster "clicks". Currently if the ringmaster wants a copy of just the one email, s/he must change the specification to provide a copy, then send the email, then unclick the option. The ability to get a "one time" BCC copy would simplify this process.
Articles About the WebRing.com System
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
