It can be difficult to search through dozens of threads to find out whether a particular glitch has already been mentioned by other Hubbers.
I would like to see (permanently) a sticky forum thread where Hubbers can report whatever problem is happening currently and check with relative ease to see whether others have reported the same thing. Here, I'm not talking about suggestions for improvements, upgrades, new ideas, etc. - just actual problems.
Obviously, it would get full and unwieldy at some point. The solution to that that I would suggest would be to decide on a maximum number of posts (or pages), close the thread when it reaches the maximum, and open a new one. - Still easier to search, IMO. - OR, as a second option, a time period could be the factor for choosing when to close the old one and open a new one. A week? Longer? Shorter? (Staff should probably select the time length.)
Does anyone else think this is a good idea?
It wouldn't help, people don't look at the sticky threads that are there now.
Owww. That sounds like defeatism.
I have seen some sticky threads receive hundreds of posts, and it seems to depend on the topic.
I don't believe that what I suggested would completely do away with the matter of multiple threads reporting the same technical problems, but I believe it could be a big step towards making the process more efficient. As a matter of fact, melbel's suggestion sounds like a great one. Hubbers could check first to see whether their issue has been noted by staff, before opening a new thread.
With any attempt at a solution, there would probably be some period of learning the system. But I believe either of these suggestions would be an improvement over the free-for-all arrangement we have now.
QM, thanks for your contribution. I'm uncertain about your suggestion right now, because it seems to me to open up the possibility of throwing hundreds of tickets at the engineers. However, I realize that the staff are in a better position to evaluate the potential of that idea than I am.
Actually, I think it would be better to have a whole different section for problems.
"Tickets". People can open a ticket about a problem, add to other tickets, file them under different sections (hub, forum, affiliates etc) and staff can close them when the problem is fixed.
Or maybe a sticky created and edited by the staff as "known bugs"
by Lionrhod 9 years ago
There are a lot of us who haven't been feeling safe on the forums. They've felt stalked, harassed and browbeaten.Sadly, some folks go with the letter of the law, but not the spirit of it in their posts.For an excellent post on why we need Forum Moderators, check out what Makingamark says here...
by Kate Swanson 10 years ago
I just noticed that Matthew replied to a question from a Hubber and immediately closed the threadThere used to be an unspoken policy on the forums - a thread was only closed if things got too heated and unpleasant. I hope that policy is not going to change, for several reasons. For one thing,...
by x 5 years ago
Why do I say that? Because I'm guessing something happened that motivated HP to include this in the HubPages Weekly:*Start*What Are the HubPages Forums for? Are There Any Rules?The Forums allow the community to complement each individual Hubber’s talents and interests. We hope they provide a living...
by Laurel Rogers 11 years ago
Now I have nothing against Nincomp, that sweet lil pony who started a wildly successful thread so very long ago-http://hubpages.com/forum/topic/15440#top...But, folks, don't you think we're acting somewhat like lemmings in search of the unattainable cliff without a ledge?Seems to me that we,...
by Tina 14 years ago
I was just curious. I have not seen a lot of hubbers that have been here at Hubpages for over two years..perhaps they are too busy hubbing away!
by Judi Brown 10 years ago
I know it's been suggested before, but please reconsider allowing threads concerning sites posting stolen content to be stickied.Just today there are several threads regarding the same sites, people cross-posting and getting mixed up on which site is being discussed. It's not surprising; the...
Copyright © 2024 The Arena Media Brands, LLC and respective content providers on this website. HubPages® is a registered trademark of The Arena Platform, Inc. Other product and company names shown may be trademarks of their respective owners. The Arena Media Brands, LLC and respective content providers to this website may receive compensation for some links to products and services on this website.
Copyright © 2024 Maven Media Brands, LLC and respective owners.
As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.
For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy
Show DetailsNecessary | |
---|---|
HubPages Device ID | This is used to identify particular browsers or devices when the access the service, and is used for security reasons. |
Login | This is necessary to sign in to the HubPages Service. |
Google Recaptcha | This is used to prevent bots and spam. (Privacy Policy) |
Akismet | This is used to detect comment spam. (Privacy Policy) |
HubPages Google Analytics | This is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy) |
HubPages Traffic Pixel | This is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized. |
Amazon Web Services | This is a cloud services platform that we used to host our service. (Privacy Policy) |
Cloudflare | This is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy) |
Google Hosted Libraries | Javascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy) |
Features | |
---|---|
Google Custom Search | This is feature allows you to search the site. (Privacy Policy) |
Google Maps | Some articles have Google Maps embedded in them. (Privacy Policy) |
Google Charts | This is used to display charts and graphs on articles and the author center. (Privacy Policy) |
Google AdSense Host API | This service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy) |
Google YouTube | Some articles have YouTube videos embedded in them. (Privacy Policy) |
Vimeo | Some articles have Vimeo videos embedded in them. (Privacy Policy) |
Paypal | This is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy) |
Facebook Login | You can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy) |
Maven | This supports the Maven widget and search functionality. (Privacy Policy) |
Marketing | |
---|---|
Google AdSense | This is an ad network. (Privacy Policy) |
Google DoubleClick | Google provides ad serving technology and runs an ad network. (Privacy Policy) |
Index Exchange | This is an ad network. (Privacy Policy) |
Sovrn | This is an ad network. (Privacy Policy) |
Facebook Ads | This is an ad network. (Privacy Policy) |
Amazon Unified Ad Marketplace | This is an ad network. (Privacy Policy) |
AppNexus | This is an ad network. (Privacy Policy) |
Openx | This is an ad network. (Privacy Policy) |
Rubicon Project | This is an ad network. (Privacy Policy) |
TripleLift | This is an ad network. (Privacy Policy) |
Say Media | We partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy) |
Remarketing Pixels | We may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites. |
Conversion Tracking Pixels | We may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service. |
Statistics | |
---|---|
Author Google Analytics | This is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy) |
Comscore | ComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy) |
Amazon Tracking Pixel | Some articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy) |
Clicksco | This is a data management platform studying reader behavior (Privacy Policy) |