Re: The whole point of bitcoin is that it isn't subject to governments.
Why do you (apparently) believe exchanges are required to transfer bitcoin? Do people not use paper money in pubs in China?
91 publicly visible posts • joined 20 Mar 2009
"What’s needed is not a clampdown on encryption — after all, it’s essential for financial transactions and the modern economy... the Home Office has developed sensible proposals that require a judge to give permission before real-time communications can be monitored — ensuring that suspected terrorists can be stopped before it’s too late, while also protecting against the mass surveillance that the public is worried about."
Notice the implicit distinction between needs and wants. He seems believe encryption is only "essential" for banking. The other consideration is lip service to placate the masses. But they do not deserve robust protection from abuse by authority.
"Why should people be paid a salary, yet not contribute and work in some manner (obviously assuming they are able)."
They shouldn't.
But why should they not be paid a dividend for their share of the common wealth of society? We do believe in capitalism, don't we?
Yes, they do, and it's not enough. You excised the comment about diminished capacity, or disregarded it. Perception of the actor is key. A person in such a situation does not consult a lawyer to inquire about local laws. They want to be anonymous, and we want them to report the emergency without delay.
Those who only consider the pitfalls but do not understand the value of anonymous speech need to think harder.
Half-right. "Unlimited", does not mean infinite. It means there is no limit. It means that you can use the available bandwidth throughout the contract period without limit. Aggregate data transfer will be finite. It is the responsibility of the service provider to provide that data transfer accordingly. It is not the responsibility of the consumer to consider the network load implications.
Contradictory fine print is inherently deception.
In flight training I was taught to constantly consider one's options in the event of complete engine failure. This inevitably leads one to consider hypothetical situations in order to be primed for action. One of these is the beach below. Land on the sand, unless it is populated. If there are people, ditch in the water, at considerably greater risk to one's own health. Similar situation with golf fairways vs. rougher terrain, etc.
Maybe I've been planning it wrong?
Correct. Even the most sophisticated autopilot system that includes the capability to land the airplane is only there to reduce the workload of the pilot - in order that the pilot can devote more attention to monitoring the progress of the flight more carefully and assuring safe operation. A machine assumes zero responsibility.
When drivers understand this, so-called self-driving - or whatever we call them - cars will bring a net positive value to us.
The human system works because we correct each others' errors. I frequently adjust for other drivers' moves that are dangerous mistakes, and I know others have done the same for me - obviously more times than I can know.
I wonder how effectively the robot does this. Will we need to go to robot-only roads to each a real safety improvement?
Uber should be playing the role of guide for drivers, arranging for adequate insurance at competitive rates (instead of the crap they try to pull now, leaving drivers exposed). They should be certifying and rating financing services and maintenance facilities. They should be arranging for local ordinance compliance by scoping out localities and easing the path for drivers with individualized guides. They should be offering a background checking service. In the political arena they should be working to harmonize laws across jurisdictions not by fighting regulation but by promoting regulation that is both easier to comply with and that protects their customers and drivers, which incidentally, probably gives them a certain degree of release from liability, aside from a long-term enhancement to their reputation. With a $50B valuation, one might think they could muster the resources to provide real value to the system. It seems they just want to run some servers in racks instead. Leeches.
...is probably valuable enough to apply to less than 5% of student work. Beyond the most rudimentary assessment of spelling, grammar and simple structure, it is nearly useless. Additionally, if students learn to apply the formulaic style that is likely to elicit the best grades from the machine, we are probably doing more harm than good. There is something to be said for ignoring simple, rigid rules and allowing some creativity to flourish. I doubt the application in question is sophisticated enough to strike a good balance. Very likely, there is no balance at all.
Training and education can be seen as distinct and complementary processes.
IBM 360- and 370-series BAL programmers of the 1970s and earlier carried accordion-folded "green cards" that listed all the operations. I had white cards and yellow cards that covered later 370 models like the 370/168, but they were still known as green cards. The summary information all fit on the card and reference to the big manual that actually described how the instructions worked in detail was only occasionally required. The instruction sets of the DEC PDP 11/70 had a distinct flavor (memory addressing and subroutine calling conventions, octal vs. hex, ASCII vs. EBCDIC), and the programming conventions were different but the basic concepts were the same. The IBM Series/1 minicomputer instruction set, for which I coded assembly for several years was relatively byzantine. The equivalent "green card" was actually a booklet, and the full processor manual was a little more useful. I only dabbled with Motorola 6502, Intel 8088 and the like in assembler, but can say confidently that the knowledge is universal and relevant even when working in much higher layers such as say, Scala in a JVM, but less often applicable.
But all this knowledge could be circumscribed well and is limited in scope. There is much more to know in today's environment and I believe the work is even more challenging to do well. We have tools to protect us from the old classic errors, but as creative humans, we will continue to find new ways to screw up. I believe an assembly language experience is worthwhile for any coder.
Apparently backup procedures need a validation component. This is probably application-specific, but certainly practical in most cases, isn't it? Can a backup region be seeded with validation markers that would be corrupted by rogue encryption that the ransomware cannot detect?
When I had T-Mobile (whom I despised otherwise), I liked that part of the deal. My monthly cost was capped, yet I didn't have to worry about service being absolutely cut off either. Throttling might be an inconvenience, but I rarely experienced it, if ever. I don't rely on mobile for serious data transfer. For me, it's for ubiquitous connectivity.
One could argue that the speedtest scheme is reasonable because it enables one to measure capability independent of current throttling state. But then, who is to say what the consumer is trying to measure: potential or actual speed? I know what is more likely, so no, the speedtest site scheme was a slimy fraud.
"Under AQM, the modem and CMTS include software that watches over their buffers, and if TCP is keeping buffers so full that it has an impact on latency, the devices will drop “just enough packets to send TCP the signal that it needs to slow down, so that more appropriate buffer levels can be maintained”.
Reminds me of the Random Early Detection classless queuing discipline, as provided by the Linux tc command. From man tc(8):
red Random Early Detection simulates physical congestion by randomly
dropping packets when nearing configured bandwidth allocation.
Well suited to very large bandwidth applications.
More like an option to change the firmware in the car. I wouldn't choose an alternative, but I would like to change whatever constant needs to be changed to recalibrate and correct the fuel flow metering which consistently under-reports consumption by about 7%. Opening the code up so that any mechanic (not just at the dealer) has full access to functionality? That would be good.
Vaguely recall working on code for a messaging system for Continental Grain on a PDP-11/70 circa 19, uh, 78, maybe. 64KB address space, with another 64KB available in another mode. Very foggy on this...
Then I did IBM Series/1 assembler for a few years. No OS initially, just some utilities called CPS and BPPF. Reboot to start text editor, type disk sector addresses. Reboot to run assembler, similar drill. Debug with membrane keyboard and sixteen bit indicators. Develop a branch banking system. Develop a brokerage trading system. Develop a commincations switch. Get real good with hexadecimal and binary patterns. Ahh... ZZZZZ
Where is the cobweb icon?
I once tried to use OO Calc to view an Excel spreadsheet for the budget produced by a school district. Some incompatibility caused it to display incorrect results. Upon investigation, I discovered that the bug could be considered a feature, and the incompatibility was a matter of interpretation. I posted a problem report to the maintainers' site. The response I received was about ideological purity: how OO does it right, and MS does it wrong. No interest in resolving the compatibility problem.
It was then I realized that MS will maintain dominance for a long time. Very discouraging.