You are viewing a single comment's thread from:
RE: This is a Test. Sort of. Mostly...
@peak.moderator, the failed postings have when I have been logged in via Steemconnect. I can use all the SteemPeak features; save drafts, insert photos, format text... but when I click to publish, that error message shows up.
It did NOT show up here because (i'm thinking) this was a super simple and short post with no graphics footers and so on. But I don't know.
This is a pretty important issue for me, because I want to completely move away from using the terms "Steem" and "Steemit" when describing what I do to fellow bloggers who could become community members... I just want to be able to say "I'm blogging on a site called Steempeak."
Well we are looking for name suggestions of a url that doesnt have to include steem. :)
Also we are trying to get a handle on some errors happening because of different nodes we use and for sure some steemconnect stuff that has been bothersome. We may just make our own steemconnect type option
I'm thinking it may be something really simple like a conflict of some sort... maybe you can't have the Keychain extension installed while also using other ways to validate posts and transactions? Beats me... I'm not a techie.
I really SO like Steempeak, however... I used to work in the usability and human factors department of a Fortune 500 hardware OEM, and Steempeak has — at least to my eye — by far the best usability and intuitive interface of any of the front ends. So that's why you guys should be promoted and the best entry point for regular humans to access the blockchain.
Well still plenty of work yet to do but thanks for the vote of confidence
@peak.moderator, as a follow up to this issue, it appears we have isolated the original issue. Not sure if it tells you anything, but I thought I'd pass it along.
My wife and I often use the same laptop... we've been using the "switch user" to move between accounts; when we completely log out and then long back in as the other user, the problem does not happen. So, we have at workaround, at least.