Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Through the years I have "tasted" several website hosting companies; none of them had Markdown available in their support-ticket-systems (if all any formatting method available). Why is it? What's...
#4: Question closed
by
Alexei
·
2021-05-15T18:48:43Z (almost 3 years ago)
#3: Post edited
by
Alexei
·
2021-05-15T18:45:52Z (almost 3 years ago)
Why most hosting providers support ticket systems allow text only (no formmating)?
- Why most hosting providers support ticket systems allow text only (no formatting)?
#2: Post edited
by
Alexei
·
2021-05-15T04:57:04Z (almost 3 years ago)
Replaced title with a clear question
A common phenomenon: Website hosting providers develop support-ticket-systems as formatless
- Why most hosting providers support ticket systems allow text only (no formmating)?
#1: Initial revision
A common phenomenon: Website hosting providers develop support-ticket-systems as formatless
Through the years I have "tasted" several website hosting companies; none of them had [**Markdown**](https://en.wikipedia.org/wiki/Markdown) available in their support-ticket-systems (if all any formatting method available). Why is it? What's so problematic for hosting providers to let their customers comfortably format their support tickets (which is extremely important in cases of complicated problems and can save time and energy for both sides)? Is there some information security reason for such a support-ticket-system development paradigm?