Dear Steemit Developers -- About Our Bug Reports. Help!

Hello Steemit developers!
At the end of this comment is a bug report I left in the middle of another web page tonight.
After doing so, I went hunting around for the proper place to report bugs. It seems I need to go to Github and open an account there, and that some others that have not done so have simply made posts like this one anouncing their bug for any interested party to see and hopefully help deal with the matter.

Sending Steem Inc.'s thousands of clients (Steemit users) to go open accounts at Github broadcasts an unfortunate implicit message and hurts company branding, in my opinion.

Only slightly less bad for the brand are the six-plus posts (most dated "last year") I found tonight where people seem to have decided that the only way they found to report a bug was to make a regular Post (like this one) about it. This does not look great, and here's why.

At any of my web sites, if I wa nt people to report stuff I have a notice that says "If you wish to report/request X click here". On clicking there, a form opens up. They fill out the form and click on "Submit". End of story!

There are some programming geniuses working on Steem and Steamit, as well as amnong the users. I know that they can do the same thing here. Could we have this here please? If it is here aready and I just missed it, I apologize and I will delete my post ASAP.


Here is my comment of tonight, which deals with a problem I had this morning.
"Hello! I apologize for the multiple repetitions of my comments, which occurred this morning. This situation represents a protocol/program bug in the Steamit software.
This bug has one of two forms. (1) The error message about "transmission error" should not be such as to lead the user to believe that the transmission needs to be resubmitted. That is, it needs to be accompanied by additional text telling the submitter what to do. (2) Once the system has a particular submission on board, it should be able to check whether submission is identical to one received a few minutes earlier from the same sender and addressed to the same recipient, and simply ignore it. That is, it hould not allow the message to show up twice on users' screens.
Of course this message does not belong on this page; but I put it here in case someone at this page is in contact with the developers and can alert them to the problem."

H2
H3
H4
3 columns
2 columns
1 column
Join the conversation now
Logo
Center