rsanders

She could say that all humans should be forcibly rendered sterile before puberty and it still wouldn't be hurting anybody. It's a terrible idea, of course, and I don't much care for it.

http://mxtoolbox.com/SuperTool.aspx?action=spf%3astate.gov&r....

"No SPF records found"

Looks pretty spoofable.

The life of a data frame has become pretty complicated. Along the way it may pass through one or more layers of virtualization, one or more layers of network-specific mangling like iptables doing filtering and NAT, and a combo of the two in OS-based virtualized networks connecting VMs and containers both intra- and inter-host.

Pushing more of the stack into hardware is probably a good idea for single-tenant datacenters that can deploy a lot of e.g. Redis appliances, but those of us just renting capacity in the cloud are going to suffer from Amdahl's Law if you can only accelerate the part of the system adjacent to real hardware NICs.

They do run Linux...in a VM. What's wrong with that?

You don't need to be using serializable isolation to face blocking or deadlocks. So-called "deadlocks" really aren't that bad when they are detected and all but one of the competing transactions are failed. You just catch the error and retry.

Every one of hp's posts in this thread have been informative. Many of them were written as responses to cries arising from the mob with pitchforks and torches, but that doesn't reduce their utility. Given that both the original article, and your comment, made much of the "ASCII binary protocol", explaining the apparent contradiction certainly raised the signal to noise ratio here.

I believe the issue is that new parameters wouldn't be accessible without a library update.

I'd much prefer 500GB for the same price that I can use to share our collected documents with one or two people in my immediate family without having to pay for the same space again for each of them. Dropbox for Business is too expensive, Dropbox Pro is too individual.

Dropbox Family, please!

Look on the bright side; it's good news for the people with the content-creation skills. It isn't as though the ever-increasing complexity of software has had a negative effect on the industry.

What alternatives with well-vetted crypto would you recommend for non-life-threatening personal use?

My Clojure app originally written to run on EB worked with no issues. The problem was with an old, sprawling "monorail" Rails app that needed a very specific system configuration, including running a daemon or two in addition to the web app itself. I can't remember all the individual issues, but the .ebextensions directory was getting pretty big and complicated.

I finally gave up when I ran into bugs in the Rails provisioning scripts that only appeared on initial deploy (or re-deploy; I forget). I had to patch and overwrite them, which was very brittle, and it was just easier to use Chef to spin custom AMIs exactly as I wanted them.

Having Docker be the common "configure a system to your app's needs" mechanism shields me from all these details about how EB works, and that's exactly what was needed.

This is excellent news. I have a rather complicated app which I fought tooth and nail to get working on Elastic Beanstalk. The provisioning scripts were just too buggy, undocumented, and full of bad assumptions.

I have a couple of apps running perfectly under EB. This neatly solves my main issue with it.

Syncing files is pretty much Dropbox's core business. Of all the things to worry about them getting right, that one wouldn't concern me.

The kernel does quite a lot of work to prevent user-space programs from doing stupid stuff to each other, or to at least ameliorate the impact of such stupidity. One of the Unix philosophies has always been to prevent a runaway program from rendering the system inoperable.

systemd has apparently elevated itself somewhat above the typical "user space" level, but it's still not a bad idea to harden the interface between systemd and the kernel where possible.

I may well misunderstand how Social Security works. However, the point of my comment is that it's hardly the only system to which one might contribute funds, incurring some future obligation of (re)payment on the part of that system, which is later discharged using funds that were most recently in "someone else's pocket".

Either it's a trivial point that applies pretty broadly outside of SS, or you meant something more significant and I'm interested in knowing what that is.

You never get your money back out of a bank; you get somebody else's money, if there ever even was physical money involved. And you never step in the same river twice. I think that's all splitting metaphysical hairs.

How is a signal generated by something owned by me, located inside my private residence, intended for use inside my house by my family and guests only, considered "publicly broadcast"? Are cordless phone transmissions publicly broadcast? Baby monitors? Burglar alarms? Home automation devices? Bluetooth headsets?

What good is the experiment if nobody uses it as though it were "real"?

Why do you assume that any coins were in cold storage? That's just another unverifiable assertion.

Yes, it is a substantial generalization, or perhaps a sentence not carefully crafted to withstand nitpicking.

In my job I do the very thing you describe. That said, I'm spending a lot more of my day preparing for the more likely risks, rather than the ones I can just dream up. I doubt many people here are posting from their bomb shelters full of emergency food and water rations, antibiotics, radiation treatments, either.

My point is that I could forgive the first lapse. Fool me once, and so on. But Mt. Gox had their precarious position quite expensively demonstrated to them. A competent management team would have made security and fraud management their top priority nearly 3 years ago when they were last caught with their pants down. It's hard to see them as victims in this because they were so negligent in their responsibilities to their customers.

I couldn't agree with this more. It's human nature not to prepare for a theoretical risk. But once it's happened to you, and to many others in the same industry, it's just foolishness not to invest in prevention.

I imagine there's also a bit of outsider-preference going on here. There's no lack of people who could have been hired to implement controls and audits that would have easily caught a slow leak of coins, but they're part of the Obsolete Fiat Economy and thus irrelevant. "Dunning-Krugerrands", indeed.

In the US, capital losses can be applied to capital gains without any such limit. Perhaps you are thinking of the amount of carried forward cap loss that can be applied to offset ordinary income.

DEVONthink Pro Office doesn't have the beauty of Doo or a name that's even remotely decent from a marketing point of view, but it is a workhorse of a doc processing engine. And it even syncs between multiple computers and Dropbox for your own private cloud.

The only thing I'm missing now is an Android "client" for it.

Who do you think is listening to your quiet signal? Who is supposed to care?

By "lists", you mean "linked lists as implemented with pairs"? What's the practical difference between lists and the seq abstraction (immutability aside)? It's true that Clojure provides a lot of data types, but none that would be unfamiliar to a CL programmer. And you can handle all of them more or less like lists, and as a bonus you can use the same set of functions to do so.

I would think that the immutability of these data structures would be a bigger difference, both conceptually and in the difficulty of porting CL code into Clojure.

That doesn't make any sense. They aren't changing the price on subscriptions you already paid for.

Giant rewrites don't have the best track record of success. Other than language aesthetics, what would be the justification for undertaking that enormous cost and risk? I despise PHP but I wouldn't make that call.

The mutual non-disparagement did not appear to be part of the original agreement, and was only mentioned as a possibility. Such agreements are usually asymmetric in who benefits and who bears the responsibilities, and the company dangles the severance pay to put itself in the superior position. I've never heard of a company offering any such thing, at least not as a standard part of a layoff offered to all affected employees.

Emergency room care is not the same as free kidney transplants.

Indeed. Now name all the other Lisps and Schemes in wide use that are based on immutable data structures.