WHAT IS OCCUPY WETPAINT ?

This wiki is set up to bring attention to Wetpaint, the company, about their failure to support the Wikis on Wetpaint platform.


Video Producers Needed
Occupy Wetpaint wiki is seeking a couple of good videographers to create a Youtube video to voice our concerns about Wetpaint and its community. Please send a message to me for more details.


ISSUES OF CONCERN

Starting around August 2010 to present, the Wikis on Wetpaint platform have deteriorated to a point of almost being a toil to do the most simplest of tasks.


Features that had no problems now are demonstrating flaws.

1. Tables are now ridden with stupid unexplained issues. Copy and paste returns the cursor to the beginning of the table or to the beginning of the content area of a page. This is frustrating if working with a lot of content being pasted into the bottom of the table. One must scroll back to the bottom of the table to continue editing.

2. Fonts not being able to change away from 12 pt size. And the clear attribute function does not work in the easy editor.

3. Attributes (cell color changes) are being lost or being duplicated from the previous attribute

4. Lack of communications with Wetpaint.

5. Our sites are being spammed with fake profiles. There needs to be a better Captcha security process in place to slow down the spammers. See the Asirra Example page on Splats2 for an example of what could be done.

6. During the slowness problem with our wikis, up to present date, the Group Messaging system has been down. Still no word of acknowledgement from Wetpaint on Wetpaint Central about the issue.

***See Outstanding Issues page for more details.

Great News


March 9, 2012
"Alex Weinstein here, Director of Technology and Product at Wetpaint. Following up on our commitment to improve the loading speed and uptime of the Wikis, we’ve just finished the deployment of the new, powerful database server.

In our tests, the Wiki platform was significantly faster and more stable. Please comment on this thread and let us know whether your experience with the platform has improved. We’ll continue monitoring this thread, as well server-side metrics, closely.

Thanks again for your patience. We’re excited to restore the quality of service you have come to expect."


March 6, 2012


USE THREADS HERE TO FURTHER DEFINE ISSUES YOU ARE HAVING WITH WIKIS ON WETPAINT

This site will remain intact. It will be a conduit for an open communication between the users and Wetpaint. This will offer Wetpaint a single source to view the issues without having to wade through many threads on Wetpaint Central.

This site will highlight outstanding unresolved issues occurring on our wikis. The wiki will outline and demonstrate any issue that we are faced.

It will not cater to the development of features that do not exist at present. The wiki will not entertain any suggestions for HTML or CSS coding additions for use by the users. Suggestions are welcomed and will not to be deterred. There are many talented users amongst us, who may have a solution to a suggestion that does not require changes to Wetpaint's code.

It will however list issues that have crept into the product via previous upgrades, specifically those that occurred after the attempt to bring a compatibility with Google's Chrome browser.