As noted in a previous blog, we do plan on getting going with some more changes hopefully near the end of May. Chat got its overhaul this week and we'll be moving through dev changes in the order of importance to the general member base. We've actually kicked through hundreds of adjustments- some you may have noticed, others probably not. However, it recently came to my attention that people have largely stopped reporting technical and usability issues. While we are not able to implement every change and have to be mindful of a budget when we make changes, we do want to make sure the site runs as smoothly as possible for everyone. It's also worth noting that, as browses update themselves, we have to update too, in order to ensure compatibility. So, development on any site is always an ongoing process and we focus our efforts on ensuring the site is compatible with the most common browsers (Chrome, FireFox, Safari, Internet Explorer), and that it works well for most people. There are so many variations in how people use the site, as well as how they access it, that we may never be able to account for every possible situation, and, what would be a fix for one person might ruin the experience of another, so these things will always be a balancing act- what we can do that will make the site better for most people will be the priority.
With all that said, if you come across a glitch or issue, please use the feedback tab or email me directly. Always include as much detail as possible- what was happening, what you were trying to do, what occurred instead, if you got any error codes, as well as your browser, device, and operating system info. Each of us will have a slightly different experience, and I usually need to be able to duplicate an issue before it can get fixed, so the more comprehensive your reports are, the better able I am to get changes made.
I'm going to paste a list of known issues and change requests below. Please take a moment to review the list and add your own comments if you know of an issue not listed here, and, if you have suggestions on how something could work better or be more intuitive, please let me know.
Also, at present, it looks like we need to address most of the Q&A issues first and then make groups work more like Q&A, so those will probably be what we hit next.
Q&A
Question edits are limited to 64 characters, even though initial posts are not. Expand edits. Complete
Comments on mobile devices squish to one side. Fix indents. Upcoming
Bring back questions lost in migration. Complete
Implement “Poster’s Pick,” allowing OP to denote a top answer. Complete
Members lost “delete” button for their own questions- add back in. Complete
Groups
Make group discussions function as much like the main Q&A as possible.
Photos sections in groups don’t allow for member submissions.
Adult network join option doesn’t accept ok.
Notifications for groups do not show name of discussion.
Polls
Unfollow/ Follow poll button needs to be added.
Ability to see how people voted should be added.
Notifications for votes to be added.
Votes to appear in activity feed.
Blogs
Drafts publishes the blog.
Blogs show up five times each in all activity feeds and lists.
Replies have a small font.
Email
The typing box needs the full text editor and should be moved up the page.
General
Site speed (codes to be streamlined after all edits done).
Animated gifs don’t stay animated when uploaded.
Member search and general search don’t work right.
Paste does not work in Dolphin browser on android devices.
Notification links are not standardized.
Activity Feed
The present activity feed only lets you select from groups you own or admin. It should let you choose groups you've joined as well.
It would also be better if the custom feed options let you select entire features, so that if a person wanted to see all the polls and questions, they could. Perhaps a checkbox menu with the features listed, so people can opt-into content feeds by feature. Questions, Polls, Blogs, Groups, photos, videos, etc. A new content only button might be cool too- just showing new main content, not replies.