27 réponses à ce sujet

[Jessica Merizan]

Angrywolves wrote...

harsher moderation ?
That would apply to EVERYONE.
shrugs.
Ignore, blocking features, someone hired to be an actual mod who devoted time to it, merging duplicate threads, those steps would have fixed 90% of the issues imo.

We have full time moderators actually. They came on this past May. The BioMod#'s. 

The Read Only transition is happening today. We are NOT making Projects read only due to valid and incredibly well stated reasoning brought up by stakeholders of that feature in this tread. Unlike some people have stated, I don't believe the majority is always right.

For those of you interested, we started gathering feedback on a future BioWare Community site last September. This thread was posted in each of the major subforums:
http://social.biowar...14081744-1.html

We also posted it to Facebook, Twitter, Reddit, and external gaming sites. The feedback we got from that survey as well as our own market research and my work in community management guided our judgements. We also use robust telemetry/analytics data that gives us a lot of feedback. That's how I know that less than 2% of our total registered users (not time spent which some people have interpreted and argued that it takes little time but actual users) are interacting with the features that we will be making Read Only. Again, you will still be able to see what has already been posted, just not create new content. 

Some changes of course are due to our technical limitations in the short term, from which Jesse and I are not planning on walking away. We hope to have in place a better PM solution for the future for instance.

I will endeavor to be as transparent as possible, but again, most of the cloak and dagger language isn't PR writing copy for me (they'd probably have done a better job lol) or us trying to save money and not wanting to tell you, but rather that the development cycle is fluid and fragile. Until things are 100% locked, it's difficult to speak about. 

In some cases, however, as with Projects, when you don't like a decision we have made and you can articulate it rationally and with support, we're happy to see if there are any adjustments we can make. 

[Jesse Reid]

Hey everyone, the read only changes are now live for Blogs, Albums, and Polls. If you notice anything out of the ordinary in Projects and Groups please let us know as those should still work as they normally would.

[Jessica Merizan]

Tarot Redhand wrote...

Jessie first thank you for not messing with the photos in groups. I just tested it with a picture I meant to upload anyway for the group that I lead and it still works. However, quoting you -

We also use robust telemetry/analytics data that gives us a lot
of feedback. That's how I know that less than 2% of our total registered users (not time spent which some people have interpreted and argued that it takes little time but actual users) are interacting with the features that we will be making Read Only.

This use of of your analytics gives a distorted view on the way that albums were actually used on here.  What would happen is that someone wanting to illustrate what they were talking about in a thread would upload a picture to their album and then using the share link that is visible when you view the picture full-sized, they would copy the UBB code for embedding into their post. Heck I even made a tutorial for those on the nwn section who didn't know how to use this feature. What this means in practice is that while traffic in the Albums section would appear to be low, viewership of the actual images would be as high as the popularity of the thread the image was embedded in. Making telemetrics a poor measure of the actual usage of Albums.

TR

To reiterate. It's not about traffic, it's percentage of actual users who are making use the feature overall out of all registered users. Traffic is not really a consideration. Moreso however, is the amount of spam and off-topic (aka non BioWare gaming content) related usage of the features we determined to make Read Only.