allow Suspended users access to Dashboard
-
in view of that and many other similar threads, also left by users who paid Automattic for the such upgrade features as ‘custom domain’ or ‘custom theme style (CSS)’, ‘custom storage space’, etc (e.g. [1], [2]), and also bearing in mind that Automattic Inc. does not provide a refund in any event, including account suspension.
in addition to the original idea of letting suspended users access to the dashboard, where they should be able to communicate with stuff directly and save an XML backup of their blogs, I think they should also be allowed to
- download all their content they’ve uploaded onto .com (docs, images, video etc);
- access to the custom domain control panel, so that they could point their domain to another host;
- access to custom theme style (CSS) editor pane, so that they could take it to another host as well.
besides an e-mail, there also should be a direct fontend to the help desk software used for support ticket tracking (Kayako eSupport) through the Dashboard proper.
the third-party services such as e-mail may and definitely should be used, but mainly as an alerting device and a CC (aiding to backup issue tracking in case if/when it will be required, for instance, as an evidence in the court), rather than a primary communication means. this as well should help in the “lost in the spam replies” cases.
—-
[1] “[closed] Domain Name Issue“ -
My understanding is staff are already looking into ways to deal with users that are potentially in a spot that could get them TOS’ed. If there are people in blatant violation, this really isn’t an issue with what you are posting since they wouldn’t have this issue if they actually read the TOS. Good stuff though Options and maybe discussing this with staff is the best way to have them know your concerns and suggestions.
Trent
-
“To Err Is Human”
Trent, the issue is we’re all mere humans who are prone to errors:
* the ones, who report their fellow bloggers just because they don’t like that blogs for some reasons, and that triggers the Akismet;
* the ones, who write the Akismet algorythm (which may give false positives), and that triggers Mark;
* and apparently Mark, who pushes the button which toggles blog status (actual content retains in the DB — needs checking), himself is a human, having to deal with way too many of such cases.
why do you belive there’re so many splogs on the blog*spot, despite superb spam filtering at the gmail? cause it’s a hard manual labour to remove a blog.
-
True, errors are to be human. No argument there.
* the ones, who report their fellow bloggers just because they don’t like that blogs for some reasons, and that triggers the Akismet;
That is not about suspension of blogs for TOS reasons, but rather spam filtering with Akismet which is a completely different issue.
* the ones, who write the Akismet algorythm (which may give false positives), and that triggers Mark;
Akismet issues once again….different issue.
* and apparently Mark, who pushes the button which toggles blog status (actual content retains in the DB — needs checking), himself is a human, having to deal with way too many of such cases.
Maybe Mark might make the odd error, but when it comes to “nuking” a blog for a TOS issue, I personally doubt that happens in error, but refer to my first statement in this post.
why do you belive there’re so many splogs on the blog*spot, despite superb spam filtering at the gmail? cause it’s a hard manual labour to remove a blog.
Maybe that is the case and maybe they just don’t have anyone to do it manually and check things because they don’t think it is an issue. One can only speculate on the ways of Google ;)
Let’s put it this way, I think this is a good idea that you have here and think that maybe staff would also like to read what you have stated. There is no argument here :)
Trent
-
when it comes to “nuking” a blog for a TOS issue, I personally doubt that happens in error
Even if the content is stolen, libellous, or obscene, does wordpress.com witholding it actually make any difference whatsoever? They can always retrieve it from the Google cache or whatever their original source was. Disabling the dashboard is just a lazy way of making sure people can’t add any more dodgy content (because nobody can be bothered to code a solution which would block posting while enabling other features) and ensuring they head here to blog about their frustrations instead.
-
Good catch Wank! I was actually referring to staff physically hitting the “delete” button in error and not a “system failure”, so to speak. Who knows what the best solution is because “automatic” deletion or action (such as akismet) can have false positives. Human interference is time consuming. Who knows…..
Trent
-
When it comes to these my blog has been suspended types showing up on the forum crying the blues let’s all keep two things in mind.
(1) You get what you pay for and Matt & Co. are not paying the bloggers who do provide support on this forum. We are volunteers.
(2) The restraint that has been demonstrated by volunteers when dealing with these folks seems to be wearing thin. -
If your blog has been suspended, please contact support as directed in the message that appears when you log in. We’ll do our best to resolve the situation. Posting on the forum won’t help, as forum members can’t do anything about your situation.
- The topic ‘allow Suspended users access to Dashboard’ is closed to new replies.
WordPress.com Forums 