Obviously, we have a different understanding of "Quality of Software".
RoS is a software product, with documented functionaliyt. At least, supposed to be. Not a "secret" to be explored. Not a "secret" to be known only by "adepts".
You are missing my point. I was responding to the following statement you made:
And in case, some users complain, that their hotspots do not work, then everybody has to browse this forum to find the solution:
My point is/was that there is NO software that is as complex as Mikrotik that, even with documentation, does not require anyone using it to it's potential to occasionally visit the forums/documentation/other support channels. Anyone who suggests or expects otherwise has unrealistic expectations.
Regarding " not prepared read documentation "...: Sorry, where is the docs about the existance or purpose of /webproxy directory ?
It's here in this forum. It is, in fact, right here in this thread.
In case of proper documentation, the original question of this thread (and a few others) would not have been asked.
Do you use Windows, Mac and/or a Linux OS? Do you ever have to search for answers to questions on those operating systems? Ever used ANY software that did not require you to search for some documentation? Mikrotik has done a very nice job of getting the documentation online (2.9.x series was EXCELLENT, 3.x documentation was lacking until recently). It is not 100% of all functionality, but MOST of it is there. Now, MY question for you...Before you joined this converstation here in the forum, did you look in the wiki for an answer?
Or, in case during SW-installation, this directory would have been created, the original poster of the problem and myself would have seen it and modified error.html ourselves.
So I call it a "Bug" of the installation routine.
First, I don't use web proxy. I do not want my file system cluttered with such a file. So I would call the creation of the webproxy directory a bug if it was there. It works both ways...
Of course, I understand your standpoint. To keep the secrets, to protect your job. Sorry, offending you.
LOL. I'm not offended at all. First, If you think I am out to "keep secrets", you should visit my blog and view other posts I've made here on the forum. Also, visit my mailing lists and see my posts there. NONE of those things will indicate that my intent is to keep secrets. Personally, I get tired of simple questions (such as this thread) and would rather move on to more complex networking applications.
Similar is the discussion about "User errors". One of my customers told me: "There is no such thing like a user error". And he was right. BTW, this customer is from a large international airline ....
No, he was NOT right. I've been supporting end users for too long to believe that statement. I have seen some really stupid user errors. Everything from leaving gear unplugged (and expecting it to work) to the inablility to read what is right on the screen.