Can't the government do the same with cryptocurrencies though? They can also "arrest the criminal and return the stolen cryptocurrencies". Not very practical 99% of the time though...
Maybe these operations will incorporate solar + battery storage into their systems if they want to stay alive... Be less efficient and less productive, but be legal, environmentally and socially responsible (sucking this much power from the public system is not responsible), and still profit.
I have no ties to the FreeBSD project or its foundation, but it seems very cheap for companies that profit billions of dollars yearly to only donate $25k to projects and foundations that support part of the software backbone of their infrastructure... Regardless of regulatory barriers, if this got a bit more exposure it could actually be a PR liability, IMO...
>but it seems very cheap for companies that profit billions of dollars yearly to only donate $25k to projects and foundations that support part of the software backbone of their infrastructure..
That's the free rider problem, one that the GPL (and the AGPL) was designed to avoid.
It's true that many of those companies which use FreeBSD wouldn't touch a GPL codebase (and all the more so an AGPL codebase), but that't the point - while some chose FreeBSD because it's fast/stable (NF and WhatsApp), others chose it because they don't have to contribute back.
At some point we have to acknowledge that our modern technological society relies on having a common, free foundation of tools available to everyone. Sometimes really big companies will get more value out than they put in, but so does everyone else and that's kind of the point of a foundational tool.
All of this free, open, etc. software works in part because of a "pay it forward" approach to the community. If people shame big users for not "paying back" enough, rather than finding more productive means of encouragement, the whole system of free tools becomes less tenable because future users will pick other tools that don't have PR risk attached.
That is literally the IRS's job. IRS funding at the margin directly increases or decreases tax revenues, because they have more or less resources to spend pursuing tax evasion.
Well if they contract out the chain analytics work to the most connected firms, I wouldn't be surprised if we found out that russian hackers are the ones behind helping americans launder their bitcoins/ether…
Maybe Equifax has some engineers working on this right now for them!
The trend is towards KYC compliance and automatic sharing with tax authorities. I assume after a while very few countries will tolerate exchanges not complying.
...and what exactly will they do about it? The question is about decentralized exchanges. Countries may choose not to "tolerate" whatever they wish, but the internet is under no compulsion to tolerate shortsighted countries.
They can prosecute the operators of those sites, not like it didn't happen in the internet before. Usually some things survive, but at the cost of extra hurdles (e.g. only accessible via tor, but even there, some people got busted through bad opsec).
You mean the operators of web front-ends which provide access to the exchange? I suppose that's possible. But I don't know how long that will even be the main way that people access them.
They would need to regulate every ISP in the country to block the protocols, and then go after every website just using those protocols under the hood (and most of these would not be in the USA).
I can't see that ever happening especially because these protocols would have non currency uses as well.
Regulate people using handcranks to power portable transmitters transmitting information at variable frequencies to be received and picked up by those who know of beamforming and antenna design.
I totally acknowledge that there are pros and cons for both dynamically and statically typed languages. (We could start a 10 page discussion here. But I've been there before, perhaps you have too, how about we save our energy? ;)
For the latest and greatest 10 pages about that; just search for the the Hickey 10 year Clojure (rant-ish in places) talk and the Haskell community responding to it.
Python has optional typing support in the standard library since version 3.5. Granted, not type _checking_, but that is offloaded to external tools like mypy[0].
I feel that gradual typing offers the best of both worlds: rapid prototyping, but also the strictness of types where you need it.
What about a Password Manager combined with 2FA? A bit of redundancy in case your master password is somehow compromised, so that you can individually still change each websites' passwords and store them in a new password manager with a different master password. The same applies if your 2FA device is stolen, you may store their recovery passwords on a separate password manager that isn't accessed as often.
What kind of "2FA"? SMS 2FA is not secure. Stand-alone device for every single service? Secure, but acquiring one is not so simple and not every service provides them.
And do you really need to bother with multiple passmanagers at that point? Just store accounts you don't care about in one.
For accounts you really care about, you should make strong unique password yourself and use stand-alone 2FA device.
