Is there a way to understand how the post approval system works? It was easy to understand initially (new accounts and trust), but just now a post of mine got held for approval and I am not sure how that happens when I was allowed to post comments and stories before?
Are there additional filters or keyword blocks that stop posts and put them in approval queue? Would it be possible to know what these are in advance so that write ups are not wasted.
We have a very limited set of characters and words which result in messages being held for manual approval. This is an anti-spam measure and as such we wonât be sharing the specifics of what may trigger it.
We make our best effort to respond to flags as quickly as we can, and in this case it took just 13 minutes which is extremely reasonable, especially seeing as most of us (myself included) are simply volunteers.
Related to that why does Project Showcase need to apply to the developers role and then post
Why is it not that I make a Project Showcase, Post goes for approval, staff peer reviews and approves or deny and then grant the developers role (mind you only if it is approved the developers role or even right before the approval)?
It just adds more steps than it needs to be and I constantly worry whenever my application has even went through the messages pile or whatever.
(The reason Iâm saying it is relevant enough is that if it was the ladder, posts in Project Showcase would go for approval, if it isnât Iâm more than happy to open a separate thread or you have the consent to move it to another thread)
There is a good reason and and that is that we want developers to have a badge so affiliation is verified but also that any COI in other threads are visible.
It is also a very simple step for people to apply for it and it saves a lot of junk posts on the forum.
I understand that, this is why I said right after or just before the approval the developers badge shall be given.
I donât wanna be waiting god knows how long just to get access and write my project showcase, Iâd rather write it out and leave it alone with no worries till approval and then later after or just before the approval get the developers role. The current system is basically adding friction for no tangible reason, if not it can ruin motivation or cause mood swings (which it did for me, I was excited to write my project showcase only to be disappointed that I have to do this extra step that basically ruined the entire motivation for me).
And as I said I donât wanna get dead worried about the application especially being in messages just suddenly going down with the other pile of messages among other flaws of the approach, meanwhile posting for approval is a win-win situation, I write and leave it alone, and the teams responsible for it gets to (thoroughly) vet and approve/deny at any time and does not have the problem of being in the pile of messages or worrying whenever thatâs gonna even go through. I literally posted a reminder almost a week later (close to a week, 5 days later to be precise) because of how worried I am and I expect to do it for another week and then a month which already a month is ridiculous. If it was a post I would leave it alone.
I also saw you mentioned about how easy, no it isnât exactly easy, Itâs not hard but it isnât easy either, it isnt much in the way of obvious enough especially with the lack of pinned post or otherwise the guideline not instructing you should click the @developers button and then request, and then without any like explaination of the process or otherwise how long it is expected to take. Yeah of course Iâm worried, what if it takes a month which would be kinda ridiculous.
How does that stop astroturfers from jumping on a VPN, creating burners and posting âhey guys, check out this cool new project that I totally didnât createâ in another category like âSite Developmentâ?
If it doesnât, then you just created a system that punishes people for following your rules and rewards those that break them.
At the end of the day, legitimate companies should recognize that following the rules here gives them exceptional marketing, that theyâre rewarded for engaging with discussions rather than just sharing marketing updates, and that if youâre a group of people actively participating here we have a ton of tools to give you recognition, e.g.:
This indicates your affiliation, which is a benefit to our community, but this is also a branding opportunity to feature your brand wherever you post here, which is one benefit to developers.
If youâre a marketer for these companies and look at this forum and think the best way to sell your product is with Reddit-style astroturfing with burner accounts that nobody here recognizes, instead of taking advantage of these systems we provide completely for free on a place online very different from everywhere else, then frankly youâre a giant idiot.
People here know/recognize each other, and as a group weâre almost unreasonably generous with the folks who do appreciate and follow the system, whereas shills without merit are disregarded accordingly, they donât reap ârewards.â
Ahh well that is just impractical for us because join group requests starts a conversation in which wr can ask questions, which is often needed. So i am not im favour of changing this.
Because in the past, one of my posts was dropped in queue with no explanation. I attributed it to being a new account, but the newer interaction caught me slightly off guard.
Sometimes that may hamper the flow of an ongoing discussion. But that answers my question, thanks. Spam is hard to deal with and I do not envy the work moderators have. Marked as answer, thank you again.
cool, why not start a message or dm/email if contact method is available when you wanna question the developer while the post remains pending. And if you donât have any questions, the vetting and approval/denial process continues as is
see there are solutions, while not causing these problems to the one who wants to write a project showcase and be done with.
I wonder when will you realize that the current way to apply then publish is just a slap in the face to those when it couldâve been in my draft already (in the correct category) or waiting for approval
It will be harder to keep an overview really because requests for post approvals will pile up. It will be very impractical for all mods and surely lead to more mistakes.
I honestly also dont see what is the issue with the current process.