Develop Bugs

[Request] allow original poster to close his own thread and delete double posts...NOW

Please allow posters to close their own threads and delete double posts. It's ridiculous not to have this feature!!!
What is so harmful about us closing our own threads?
I think it is beneficial, for example:
1) OP feels harassed: closes thread
2) OP learns that there was already another, more prominent thread of the same issue: closes thread
3) OP wants too closes his upcoming software update but doesn't want to read other's post issues that he has fixed on the next version.
etc...
Why can't we close our own threads? Delete our own posts?
For ***sakes look at these threads:
http://forum.xda-developers.com/showthread.php?p=4120834#post4120834
http://forum.xda-developers.com/showthread.php?t=535393&highlight=deleted
If you aren't going to implement this then atleast tell us why in the world we can't delete our posts!
Here is my previous thread posted at the wrong forum:
http://forum.xda-developers.com/showthread.php?t=535157

After reading Mike´s post it is clear that the best and easyest way is to click on the red button asking an experienced Mod to do the action, otherwise it can be a democratic chaos...
Just my opinion.

mikechannon said:
It sounds obvious that you should be able to delete your own posts. However, it can cause chaos! Once you create a thread you do not own it, particularly if other users have contributed posts to the thread.
Click to expand...
Click to collapse
I agree, Just because you posted a thread, doesn't mean it's your thread. This is a community with no personal ownership of posts or threads.
mikechannon said:
Deleting the first post in a thread deletes the whole thread. This could be a long running thread with many posts and pages. To allow this thread to suddenly vanish because the OP deletes the first post can upset many contributing users.
Click to expand...
Click to collapse
Mike Speaks from Experience here.
mikechannon said:
However, it's relatively easy to have the odd post removed by clicking on the report post (red triangle) that appears on all posts. All you need do is say something like "please delete my double post" or "delete my post it's in the wrong forum" etc etc
Click to expand...
Click to collapse
Once again I reinforce Mike's statement. The Mods are here to assist you, please make use of our services.
mikechannon said:
There are also a couple of other fiddly reasons why it's best for a Mod to delete posts - one is that a Mod can also move the post to Trash. You may not know that deleted posts are still visible to Mods and leaving them kicking around forums makes things look very messy to Mods even if other users see a nice tidy board. Another reason not to allow user delete is that a very few users could use this to cover up "provocative posting" or just to cause trouble with other members. (You can imagine for example, that a ROM thread suddenly disappearing because the cook is bored with it could lead to lots of frustration amongst users and extra work for Admin and Mods.)
Just use the report icon or contact a Mod - quick and easy
Mike
Click to expand...
Click to collapse
Just basically report to mods is the summation here.

Got a question about deleting a post:
Once a post is deleted, then all posts after it in the same thread will be changed a post#. E.g, if post#2 is deleted, then post#3 became #2, #4 become #3 etc. But if the original post#3 is cross-linked to another thread using the 'view single post' function. In such a case, will the cross-link url address be updated accordingly?

The link will be to the deleted post, no re-shuffle will occur.
The URL is showpost.php and p=4153097 ("p" is the post number, not the thread number, that will be "t").
Here is one I deleted from this thread : http://forum.xda-developers.com/showpost.php?p=4153097&postcount=6
As a moderator, I can see deleted posts. Try that URL above
Dave

In the above case, seems you deleted the whole thread.This is the url you pointed:
http://forum.xda-developers.com/showpost.php?p=4153097&postcount=6,
And I can not access these:
http://forum.xda-developers.com/showpost.php?p=4153097&postcount=5
http://forum.xda-developers.com/showpost.php?p=4153097&postcount=7
My question is for example in this thread we are talking in,
if you deleted this post: http://forum.xda-developers.com/showpost.php?p=4121794&postcount=3.
But I already crosslinked this post (next one to the deleted) with this url: http://forum.xda-developers.com/showpost.php?p=4132664&postcount=4.
So my above url will become this post, is that right?
BTW, sometimes I can see the contents of deleted post from a google search result.
Edit: Ok, seems I got it, you said no re-shuffle. That means if #3 deleted, , #5 is still #5, so there is no influance on crosslink address of posts. Thanks.

[Suggestion] Thread wiki

It is possible to add a "thread wiki" post below the original post?
Eg in slickdeals, you have a common wiki below the OP that people can add stuff
I feel like threads should have things like that...
OP might not have time to update his/her post with relevant info that an another user can add
It might be difficult trying to look through 100 pages of posts to figure out if someone has a similar problem(or through search), while it is easy for multiple people to maintain a common wiki that they can all edit
EG: http://slickdeals.net/f/4803408-Thi...ted-by-users-like-you?p=51265310#edit51265310

paperWastage said:
It is possible to add a "thread wiki" post below the original post?
Eg in slickdeals, you have a common wiki below the OP that people can add stuff
I feel like threads should have things like that...
OP might not have time to update his/her post with relevant info that an another user can add
It might be difficult trying to look through 100 pages of posts to figure out if someone has a similar problem(or through search), while it is easy for multiple people to maintain a common wiki that they can all edit
EG: http://slickdeals.net/f/4803408-Thi...ted-by-users-like-you?p=51265310#edit51265310
Click to expand...
Click to collapse
Interesting idea, not sure how adaptable it would be with the VBulletin software though. It might also be similar in effect to something I hear is going to be rolled out sometime soon, a post rating system so posts with more positive ratings will move to the top, and posts with enough negative ratings will be hidden.
I think though that the OP should either ask the mods to close the thread or hand it over to another user by contacting the forum admin if they don't have time to maintain their thread with important new information.

mf2112 said:
Interesting idea, not sure how adaptable it would be with the VBulletin software though. It might also be similar in effect to something I hear is going to be rolled out sometime soon, a post rating system so posts with more positive ratings will move to the top, and posts with enough negative ratings will be hidden.
I think though that the OP should either ask the mods to close the thread or hand it over to another user by contacting the forum admin if they don't have time to maintain their thread with important new information.
Click to expand...
Click to collapse
I mean small details: like "most commonly encountered problems and solutions", that the OP might have time to add or not
For a dev thread, I rather have the dev (most likely the OP) focus on developing and other people helping out in figuring out problems by common users... users can update the wiki on the un-resolved problems so that the dev can see, without having the dev to read the last 3 pages that were newly posted
you can see in the Slickdeals thread... 179 pages of posts... some of them are "useless" in saying "thanks for the deal", while some people have legitimate questions (like "is this phone quad band") that other users answered 10 pages after their post... having a wiki means common info will be presented clearly without having to dig through the thread, and anyone can update that, not just the OP <--- most important point
EDIT: Slickdeals uses vBulletin too, but customized plugins... there are probably open source plugins out there, just trying to dig through
EDIT2: i guess SD doesn't use pure vBulletin plugins for that... maybe some CMS system

paperWastage said:
I mean small details: like "most commonly encountered problems and solutions", that the OP might have time to add or not
For a dev thread, I rather have the dev (most likely the OP) focus on developing and other people helping out in figuring out problems by common users... users can update the wiki on the un-resolved problems so that the dev can see, without having the dev to read the last 3 pages that were newly posted
you can see in the Slickdeals thread... 179 pages of posts... some of them are "useless" in saying "thanks for the deal", while some people have legitimate questions (like "is this phone quad band") that other users answered 10 pages after their post... having a wiki means common info will be presented clearly without having to dig through the thread, and anyone can update that, not just the OP <--- most important point
EDIT: Slickdeals uses vBulletin too, but customized plugins... there are probably open source plugins out there, just trying to dig through
EDIT2: i guess SD doesn't use pure vBulletin plugins for that... maybe some CMS system
Click to expand...
Click to collapse
I guess the problem really is that the dev thread should not be used for support, but people insist on treating them that way. I think that there should be a "ROM XXXXX Support Thread" in the device Q&A forums and that is where such questions should go instead. Then there would be no problems with the restrictions since user support questions or bug reports without proper logging, details, attempted fixes, etc. would be moved from the dev thread into the support thread if they were able to post them there.

mf2112 said:
I guess the problem really is that the dev thread should not be used for support, but people insist on treating them that way. I think that there should be a "ROM XXXXX Support Thread" in the device Q&A forums and that is where such questions should go instead. Then there would be no problems with the restrictions since user support questions or bug reports without proper logging, details, attempted fixes, etc. would be moved from the dev thread into the support thread if they were able to post them there.
Click to expand...
Click to collapse
even in support threads... who would maintain the massive throve of info that many people would ask? the OP(most likely the dev himself who made the thread), or every user who wants to?
example.... if a lot of people post below us, makes it go into 5 pages... someone on page 3 found a plugin that does what it works.... does it make sense for that info to be posted just below my first post by anyone, or is it on me(the OP) to edit my first post "someone on page 3 found this info"?

This is actually an interesting idea. We are busy adding other new features but definitely will keep this in mind. Right now, we do already have a wiki and there is nothing stopping someone from creating a wiki page while adding their thread, and linking to it, but it would be nice to integrate that directly into the page.

bitpushr said:
This is actually an interesting idea. We are busy adding other new features but definitely will keep this in mind. Right now, we do already have a wiki and there is nothing stopping someone from creating a wiki page while adding their thread, and linking to it, but it would be nice to integrate that directly into the page.
Click to expand...
Click to collapse
yeah, but it's definitely not as seamless as having it right below the original post
lemme see if there are any plugins to "stream" that wiki page into a post...

Came here to request this too. And precisely for the same reasons as the OP.
This would be immediately embraced.
I don't understand the "I'm not sure this would be adaptable with vBulletin" comment since slickdeals uses vBulletin.
http://www.qapla.com/mods/showthread.php/309-Wiki-Posts-for-VB4-by-BOP5-BETA

another vote for this.
i have been following a thread about about the development of 4.4 for the hisense sero 7 pro (randomblame, davepmer and others are awesome)
anyway it has a post count of nearly 1,000 and people come in and try the latest build, or just wanting to ask a question about the latest builds. the same questions get asked over and over. i don't really think its the fault of the person asking since who is going to read 1,000 posts just to see if his/her problem has been discussed.

"You may" permits at bottom of page not true?

While trying to get past my 10 post "presumed noob" penalty (I am a professional dev IRL), I tried to reply to a thread where the box at the bottom of the page said that in that particular area I could post replies, but not new threads. As a good netizen I skimmed through the entire 100 pages+ of the thread before pressing reply, only to get an error page which (somewhat indirectly) told my I had no posting rights in that subforum.
This is quite disheartening. Not only are new devs forced to do 10 posts worth of "noob help duty", but the things telling us where we can carry out this penal work seems to be wrong, thus redoubling the penalty for signing up.
What is wrong with this picture?
Is the error page wrong, or the indicators at the bottom of the thread pages?
Either needs to be fixed.
P.S.
The "Is this thread a question" box is another harassment trick. I tried to tick it to indicate this posts needs a reaction of some kind (to fix the bug or explain what I got wrong about the UI), but all I get is a message that general questions belong elsewhere.

[Guideline] Behaviour on XDA

Ok, basically this thread is meant to inform the DOs and DON'Ts on XDA, and also how to do certain things. I started this thread as I have noticed that there has recently been an influx of posts that fail to serve their intended purpose well (e.g. asking for help, bug reporting etc.) Also I hope that this thread will serve to at least provide a general guideline.
Rules
1. No stealing of ROMs.
Ok, this is quite obvious but I thought it would do well to just explain what this is so that some of you don't accidentally steal someone else's ROM. What this means is:
You are not allowed to publish a ROM that you didn't create yourself. What this means is simple -- you are not allowed to publish on the web any ROM that you:
a. have not compiled from sources yourself AND that you haven't added in your own code to
b. have ported from another device WITHOUT permission from the original ROM developer
c. have cobbled together from already-published work (take parts from different ROMs and combine them for a hybrid ROM without adding in your own original code)
The following kind(s) of ROM(s) are exempt from this rule:
a. Stock ROMs with/without modifications
++++++++++++++++++++++++++++++++++++
If you contravene the above rule, it will mean that you have stolen a ROM. If you wish to publish a ROM that breaks the above rule, you have to OBTAIN THE PERMISSION of the developers of the parts (be it scripts, ROMs, mods etc.) that you used in your ROM. Furthermore, in your ROM thread, you must give proper credits to the devs whose work you used and also link back to the original ROM.
If your ROM is simply someone's ROM with cosmetic changes (e.g. different theme and/or a few scripts added in), you must do the above and also post it in the Themes and Apps section as an update.zip that only changes the parts of the ROM as needed.
Lesson is simple: If you want fame on XDA, learn how to compile your own ROM sources and don't simply soft-mod -- usually many people inadvertently steal someone else's ROM this way.
##############################################################
Guidelines:
1. Don't post any non-development related stuff (bug-reports ARE development-related so feel free to post them though) -- it only serves to spam up the thread and hinder development. Posts like "This ROM is great", "this ROM is fast and the best I've used" and "Thanks for this awesome ROM" or, god-forbid, "This ROM sucks" etc are hardly informative, development-supportive, and have no purpose. You might feel good after posting this, but honestly it just serves to annoy others that are trying to locate something in the thread. So don't post this, PLEASE .
2. No ETAs. Please, do not post stuff like "When will the next release come along... can't wait!", "When will you fix XXX bug" and similar questions AT ALL. The ROM will be released when ready, and as above this only spams up the thread. If you are that impatient, I suggest you flash back to stock 2.1, no disappointments and is definitely the most stable .
3. Provide as much detail about your bug as possible. This is by far one of the most common problems. Posts like "my WiFi isn't working", "there's xxx when I yyy, please fix!" are really useless. There !re 1001 possible reasons why your WiFi isn't working, and why blahblahblah happens. To be actually helpful and have a greater chance of having your problem rectified, provide the following:
ROM you are on
Kernel you are using
Paraphernalia you have installed (e.g. Scripts like Supercharger, swap, OC frequency etc)
(If possible) How to replicate your issue
What steps you took to rectify the problem (if any)
Your logcat and dmesg
ON TERMINAL EMULATOR
How to get logcat output saved as a file called logcat.txt on your sdcard:
Code:
su
cat /dev/log/system > /sdcard/logcat.txt
And for dmesg to be saved as a file named dmesg.txt on your sdcard
Code:
su
cat /proc/kmsg > /sdcard/dmesg.txt
or for last dmesg after odd shutdown
Code:
su
cat /proc/last_kmsg > /sdcard/lastdmesg.txt
Flaming and trolling:
1. Refrainkfrom using personal insults as much as possible like "you are dumb", "how stupid can you get", "you are a noob" etc. This is the precursor to an unnecessary flame war. Try and be polite instead like, " you are new, so you may not know this, but blahblahblah". You were a noob once, so try and treat noobs as you would have wanted others to treat you when you were a noob.
2. Don't continue flaming. If someone posted something that flames something, don't flame back. Just report the post and sit back and relax. Continuing the post will just feed the troll and make things worse. You might get punished too.
3. Mind your language. Use English on XDA always, if you can't, include an English translated version of your original text and post it along with your original text. Also, never ever use vulgarities on XDA -- it's a surefire way to get infracted. Don't post any racist/political posts either. XDA is for mobile phone discussion and development, not for expressing your extremist/whatever views about...
_______________________________________________________________
Q&A
1. Use the search tool first. You are just one of over 4 million members on XDA, and it is very likely that your question has been asked and answered already. Search before posting any question to avoid spamming the forums. Remember, you are likely to get an answer faster this way, and this also prevents you from being flamed if your question has been asked before
2. Don't be demanding. People do not have an obligation to do things for you, hence don't demand quick answers, insta-fixes, or a detailed step-by-step guide. It just shows how much you actually bothered to search for answers first and also people will be less likely to answer to you.
3. Post questions in the Q&A forums. Just because the DEV and General forums get more traffic doesn't mean that you should post them there. Again, your question will most likely be answered faster in the Q&A forums and you won't get flamed either.
4. Don't revive old threads and answer them. Recently I have seen users who answer threads 2 days+ old that have been resolved already. Their answer is usually a paraphrase of one of the answer posts above. Then they put in a "Please hit Thanks if I helped". Thanks for answering, but no thanks for spamming and trying to get thanks for free.
++++++++++++++++++++++++++++++++++++++++++
Miscellaneous
1. Hit the Thanks button whenever you feel like posting Thanks instead. This reduces the amount of spam on the forums and is a good way of showing your appreciation for the person that helped you. Generally XDAers have a thanks limit of 8 per day, so use them wisely! (Unlimited on Tapatalk/XDA app apparently). At the same time, don't be a Thanks hunter -- someone who actively posts only for Thanks. Please, it is not some sort of "prestige meter", and anyway people can clearly see that you are a thanks hunter and will treat you as such.
2. Use the Report feature. If you see a post that breaks the XDA rules, report the post. Many people that I see just flame the rulebreaker on the thread instead of reporting and allowing a moderator to deal with things. Remember, moderators are not Gods that know whenever some person breaks a rule, so Report posts to help them along.
3. Think, search, then discuss, not the other way round. Only then will a constructive discussion start. Unfortunately, many people just post without thinking, resulting in flaming and general unpleasantness on the forums. XDA is a place where individuals from around the world gather to discuss and develop on mobile phones, so let's keep it that way :highfive::victory:.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
==========================================================
Credits goes to SpyderX for the post. Original link is here.

Nice copy-paste.
You can at least give credits.
Original thread here by SpyderX.

stamatis said:
Nice copy-paste.
You can at least give credits.
Original thread here by SpyderX.
Click to expand...
Click to collapse
Done.

forum interface not user friendly

I understand the desire to keep the spammers out, but it seems that you went for the brute force approach here.
When I tried to reply to someone's message that contained a link, as new member I was not allowed to do so because my message now contained a link, even though it was only a quote. Fine.
When I wrote a message, filled out the image verification field and clicked on "preview post", I had to do image verification all over again before posting. This is simply annoying and does nothing to prevent spam, it only prevents good user experience and discourages people from previewing their posts. Maybe I don't even need to do the verification when I preview the post, I didn't experiment, but in any case this is a pretty badly constructed interface.
Finally, when I wanted to edit my post immediately after posting, I got a message that new users have to wait five minutes before posting again. Obviously, the restriction doesn't distinguish between posting a new message and editing an old one. Again, in this case it's simply annoying.
Ironically, the forum pages are teeming with flashy advertisements.

biggvsdiccvs said:
I understand the desire to keep the spammers out, but it seems that you went for the brute force approach here.
When I tried to reply to someone's message that contained a link, as new member I was not allowed to do so because my message now contained a link, even though it was only a quote. Fine.
When I wrote a message, filled out the image verification field and clicked on "preview post", I had to do image verification all over again before posting. This is simply annoying and does nothing to prevent spam, it only prevents good user experience and discourages people from previewing their posts. Maybe I don't even need to do the verification when I preview the post, I didn't experiment, but in any case this is a pretty badly constructed interface.
Finally, when I wanted to edit my post immediately after posting, I got a message that new users have to wait five minutes before posting again. Obviously, the restriction doesn't distinguish between posting a new message and editing an old one. Again, in this case it's simply annoying.
Ironically, the forum pages are teeming with flashy advertisements.
Click to expand...
Click to collapse
These are measures put in place only for new users. As you post more, it'll be easier.
It's something we have to do.

Too many new user to do differently.
Inviato dal mio Nexus 4 usando Tapatalk 4