When Is The Transaction Error When Publishing A Post Going To Get Fixed?

I don't usually vent on Steemit but I have a gripe that I can't contain anymore. Since around the time of Steemfest posting a post on Steemit shows a transaction error when you hit the publish button.

The post does get published and opening your blog on another tab in your browser and refreshing the page shows the post is live.

Image credit

For seasoned Steemit users, this is a temporary problem that I'm sure will get fixed. However, for a new Steemian they are getting very confused.

Almost everyone that I have signed up to Steemit who are currently active has sent me a message that reads something like this.

Hey, @luzcypher, I'm trying to post on Steemit and it says I have a transaction error. What do I do? Did I break it?

To which I respond explaining what I mentioned above.

This is not good for the platform and needs to be addressed. I have spent hours over this last month explaining to people who signed up because of me how to work around this and it seems silly that a team of people at Steemit has not fixed this yet.

One of the reasons I made this post is to save me time explaining this to people. Now I will just send them a link to this post.

Surely you can see how this gives a bad impression and especially a bad first impression. I'm not going to promote Steemit or sign any more people up until this is fixed because it reflects badly on the platform.

Imagine getting a group of 50 people together to introduce them to Steemit (a scenario I'm sure is happening all over the world as we speak) and all of them are excited because all week they have heard from the 10 people I have already signed up to Steemit just how great it is.

I gather them together and walk them through making their first introductory post and as soon as they hit the publish button for the first time they get a transaction error.

Now imagine the look on their faces as you explain to them that this is just a temporary error and here is how you fix it. The excitement seems to have drained from their faces replaced by confusion as they smile politely thinking; what the fuck?

I understand we are in beta and things like this will come up, but this seems like something that should be a priority and I have not seen any updates or gestures reassuring us that it is being addressed.

First impressions really set the tone for how a user interacts with the platform and my reputation means something to me. I'm a diehard Steemian and can promote like a boss, but until this is fixed I'm in a holding pattern as far as any immediate site promotion goes.

Is this too much to ask? That the post publish button works properly.

Come on guys, really? Am I the only one who thinks this is important?

Is anyone doing anything about this?

It seems like it's important enough not to put it off. Is someone working on it?

How many users do you think Steemit is losing while we wait for this to be fixed?

The other thing that really bothers me about these types of issues that don't seem to be clearly communicated to the community is that people will now have to make a post, as I have done, about this issue asking what is being done about it.

Now Google is going to eventually index all these posts talking about the problems with Steemit. In publishing, this is called bad publicity and it's the last thing Steemit needs is users complaining about every issue that comes up with the platform indelibly and ad nauseam when one post from the Steemit team could have informed everyone about the issue and status.

These problems will now come up anytime some new user searches Google about Steemit and the impression they will get is that no one is doing anything about them. Why else would so many of the users be making posts about the same problem?

** End of rant **

Please, the fine, hardworking people on the Steemit technical team, please fix the transaction broadcast error on the publishing button when you publish a post. Thank you.

Related Posts

Originalmusic Tag Is Missing Again - Where Has It Gone? --- by @luzcypher