They're definitely on the theater side of security. I've got locked out of my account multiple times for no reason.
Furious the second time, I sent a crafted image of an invalid ID to check if they actually even care. It seems they don't, as the account got unlocked all the same.
That doesen't seem like some fundamental restriction, but rather a compromise we're always willing to make. 30ms is not noticeable, so we don't try to lower it and sacrifice something else.
Even the super slow ones like on kindle, are _choices_ that have been made in favor of something else. a second to turn a page on a book isn't unbearable
The worry is that something in a link will cause the program to behave in unpredictable manner. At best it would crash, but it could do much more damage if given the chance.
I don't know Golang, so I can't definitely confirm or deny any intricacies it may or may not have. Though as mentioned by others, it seems to essentially be a wrapper for a webpage
In addition of being quite bad in latency, a single block also cannot hold a lot of transactions. You'll always have to store the mass of transactions somewhere else, which takes away from the purpose of blockchain in the first place.
I think the title is quite misleading. The article says
>the City regulator the FSA is concerned that crypto investment firms could be overstating potential payouts or understating the risks from investing in bitcoin and products related to the digital currency.
Wouldn't it be better to call it "are cyrpto investment firms a scam?" ?
I'd say it's bad design to have everything important in the open just because it's behind a firewall; it's got a huge blast radius when something goes wrong.
Securing your services regardless of where they are in the network should be go the go to