Right now, Blurt.one is working very well. and I like its colors more than the orange color that characterizes blurt.blog.
I see that they are very similar in their functions. You can try it because my wife uses blurt.one, and she loves it. When I need to go to my wallet or reblurt a post, I use blurt.one
Thanks Ray.
Do you know who created it, and who runs it? It's safe to give them my private key?
I use WhaleVault, which allows me to work with a different key. This is like a vault that stores my keys, and no other person will ever have access to my private keys. That front end is developed and maintained by @tekraze.
Hmmm. Is that not just adding another way your keys can be compromised? How do you know you can trust Whalevault? What if they get hacked, as almost every service eventually does? And my question still remains, how do you know the person/service Whalevault sends the private keys to will keep them secure? Thanks for the info.
Whalevault keeps the keys in local storage only. The code is open source and anyone can access.
The dev is also friendly and supportive and known by everyone here
Thanks
Thanks for the info. As someone who knows nothing about coding or software, I have trouble understanding security issues sometimes.
For example, if the private keys are only stored locally, how does the 3rd party frontend determine that they are legitimate? Does Whalevault check with the blockchain to verify them, and then simply tell the 3rd party "the private key is legitimate"? Or does the 3rd party get access to the keys and do that determination?
Also, if keys are stored locally, isn't that just one more place that the keys are being kept, for a potential security breech? How do we know that hackers can't get into Whalevault?
It's good that the developer is trusted here, that helps a lot.
Hahaha you ask a lot of questions.
If the keys are wrong the transaction will be rejected by the blockchain, so no need to check.
They are stored simply in the browsers storage, unless someone have direct access to your system, nothing can be breached.
My front end is same as the official one, just with UI enhancement as well performance upgrades.The key management is same.
Does that mean your front end allows "self sovereign blog" concept? (censorship of an account on every post by a specific user) Does it use extra algorithms to hide certain people from Trending pages, as blurt-blog does?
I should not probably answer this question. It has been discussed many times, a frontend does not need to have the same features or restrictions. It's up to the operators of the frontend to have some thing or to remove something.
And I can only say, it might have some restrictions, or maybe not. Because things can change over time.
Ohhhh, "it has been discussed many times", I see. Well, thanks for letting me know to avoid Blurt.one!
Yes, you should even avoid blurt in that case
Such an ambassador! What a hero.