Thread:がか/@comment-24851773-20171129200219/@comment-26091666-20171216023744

Hi, I'd like to chime in on this discussion for two reasons: With that said, I would like to start off with all these response are of my own personal opinion.
 * 1) It creates an unified discussion instead of having to bounce ideas back and fourth between both our message walls.
 * 2) My reasons are virtually no different to がか as some of these were discussed with other admins of this wikia.

Without a suitable wikitext/code replacement functionality is a huge blow to our needs. To push forth a feature that has no code support isn't an ideal way forward when considering that mobile devices themselves are also advancing at an alarming rate. KC (KanColle) the game is also available for mobile devices and it too has a certain requirement that would enable near desktop-like features. In fact, they're moving towards HTML5 adoption which enables even more rich content. On Fandom side, the pushing for Discussions without any suitable form of code support is a huge drawback in terms of what it can actually provide.

I'd like to see the ability to highlight + pin discussions implemented globally before it is tried on this part of wikia. We have ongoing limited-time functions known as events, etc and with the way Discussions work it will only push the more crucial Discussions down. Not to mention that it is possible for older Discussions to be reignited again come years ahead in time after it has been adopted. On Forums, these are better known as "necroposting", and would only push it towards the top of the list considering how Discussions operates. Without a feature to disable necroposting would require involvement from local (KC wikia) staff.

Last but not least, on a personal note I like to point out that we have had issues with spammers. It is not acceptable (personally) to have Discussions be littered with spam content and only to have either local staff or VSTF to deal with the matter come seasonal events for instance. Currently, we're using AbuseFilter extension which automatically deals with the spam content well before it gets to be seen on the actual site itself. Spam content is not the only issue we have and again without a way for AbuseFilter (or some other suitable replacement other than manual intervention) is personally unacceptable.

I want to also point out that what I stated here are really just some of the few issues with this overall adoption progress. Whether it be migration or to just simply have it enabled.