bashcoder

Fair question. The basic internet email spec has virtually no security features whatsoever, and is completely unauthenticated. Mailing list management software doesn't forge sender information, but rather often retains it and generally trusts incoming headers. Back in the old days, some folks even referred to discussion lists as "reflectors."

The proper usage of SMTP mail headers is outlined in RFC2822 (originally RFC822), and the definition of the headers From, Sender, Resent-From, etc. The rules for specifying sender information are spelled out in 3.6.2. [0]

That said, system behavior also depends on if the MLM software is running behind a mail transport agent that enforces authentication protocols for incoming emails, scans for viruses, etc.

When discussion list owners are concerned about receiving forged posts, they usually use list moderation features so they can ensure emails do not get distributed that haven't been reviewed first. But the biggest problem for MLMs isn't usually dealing with impostors, but rather blocking email-borne viruses and misconfigured auto-responders that could cause bogus emails to get reflected out to subscribers.

The behavior of the outgoing From header from MLM software typically depends on the configuration of the list. Some lists (especially digests) are configured so outgoing messages are "From" the list itself. But most discussion lists are configured to retain the original From line, while clarifying their role as an email proxy through other headers.

[0] http://tools.ietf.org/html/rfc2822#section-3.6.2

Not 1:1, no - thanks for clarifying that. But depending on the content and the indexing, there is a strong correlation between the size of the database and the memory requirements under Mongo DB.

The article states that the initial "Holy s*!" moment was five years ago:

> Over the next five years, Harkema's team applied electrical stimulation to three more paralyzed men...

Yes, and an important limitation stems from this as well.

For a tool like Redis, it's fairly easy for me to accept the limitation that my data size can't exceed available RAM.

But for an indexed document store with full-text query capabilities, it's a lot harder to for me to accept that limitation.

> How does this work as the network scales? If I understand it correctly, every node needs to execute every contract.

Such a network can grow to some extent, but how can it truly scale? There is limited scaling, of course, but node requirements increase as traffic increases, and there is no scalability through distribution of computational resources. So the more work the system does, the stronger each node needs to be.

If the answer to this is, "No problem - we'll just make it more expensive," then the required computational resources could be purchased with the very cryptocurrency that is generated from the system. At that point, it seems to me that the snake eats its own tail.

Regardless, before we declare that there can be any democratization enabled by this tech, I think we need to ask the question, "How does this not transfer even more power to those with the most computational power?"

Put another way, it seems this is tailor-made for Google and Amazon, not an organization of Joe Publics, each with a couple extra GPU's installed. It's still going to be about the "haves" and the "have-nots."

I'm happy to be proven wrong on any of these thoughts. I just think that if we were talking about any other tech, this computational model would not be considered scalable in any meaningful way.

One issue with Deis is that it depends on Chef Server. As an admin, I've happily left that whole model far behind. For me that single dependency is a deal breaker.

Actually the issue was that I was using Google's DNS. When I disabled that, it worked just fine. But thanks for showing me the Chrome trick.

As to the technically correct statement, don't you think that saying a site is a "known malware distributor" is a bit more sweeping than saying something more accurate like "we discovered malware on this site"?

In other words, they are using the same language I would expect to see directed towards sites that have malicious intent and should never be visited.

> First, it's already been unblocked.

It's still blocked for me, with Google branding wired.com as "a known malware distributor."

I was very disappointed to watch in real time as this post was moderated off the HN front page and into oblivion. It happened at 8:46 PM PDT on April 3.

Once it reached #24 on the first page, even as it was gaining points and comments, this post quickly fell several pages.

Yes, we had a few posts on this subject already hit the main page, with one garnering over 900 comments. But especially when we're dealing with an issue with such obvious free speech implications, insightful articles like these should be allowed to run their natural course on HN.

Whatever your beliefs, I'm not sure how this saga fosters either inclusiveness or diversity, and I'm afraid the word community has lost all meaning.

Much success and wisdom to you in your efforts - love the courage, and your eagerness to take feedback.

As to the app, my recommendation is to avoid putting .zedstate files inside the project directories themselves. Instead, keep them in a ~/.zed/ directory. Keeps folks from having to make special .gitignore commits for all of their projects.

I suspect the missing checkmark beside HBO GO is more about putting pressure on HBO than on Amazon. It's got to be just about price and term, with Amazon showing strength by announcing without them.

But when both sides agree on price and ink the deal, HBO will get a premium announcement compared to the others. It will work out just fine.

Not because that was the intent of Stack Exchange, but in my view that's the end result of the generally hostile culture at Server Fault.

Don't get me wrong - striving for excellence requires high standards. But in Meta, their best answer to the question, "How do I ask better questions?" is 1,780 words long.

But visit each site without being logged in, and they both lead with "Anyone can ask a question."

Regardless, the heavy-handed moderation and negative feedback cycle actually means that Server Fault is only meant for seasoned career sysadmins who shouldn't need a Server Fault.

Based on my experience today, I can attest to this. If you purchased recently, they may very well accommodate you.

My point being, the OP lists four methods by which he thinks crowdfunding can work (pre-order plus reward, equity, debt, and donation).

Each method has its own set of concerns for regulatory issues, requirements for qualified investors, upside potential, tax implications, etc.

My point is that there may be other possible options, and I point to Safe as a good example of how VC can innovate and remove friction from raising startup capital.

It's possible that new investment instruments, such as YC's Safe [0] which removes the friction of convertible notes by offering warrants for future equity, could facilitate this sort of thing.

[0] http://blog.ycombinator.com/announcing-the-safe-a-replacemen...

Well, I think the crux of my criticism is that I'm not sure there actually is a real professional market for e-ink devices.

Very good - then don't you also share my skepticism about this as a viable product?

The first meetings I had about Que was actually with Hearst, if I recall. The Plastic Logic play was backed by content providers seeking a new channel, including Barnes & Noble. The Sony play is backed by a hardware provider seeking a new channel. So producers have this need, but what about customers?

I find myself having the same three doubts I had back in the day:

1) Nobody cares if a screen is flexible for these particular product applications (especially for the Que, which mounted flexible display tech in a rigid form).

2) It's a solution in search of a problem. Who is clamoring for this device at market scale? Even for a specific vertical?

3) Haven't we learned that these devices need the support of a broader ecosystem? That developers need to find opportunity in a platform for it to succeed, and that requires a certain critical mass? How is that going to happen serving a niche vertical market?

Interested in your thoughts.

Agreed. In fact, all of the myriad secondary costs and benefits from commerce are already accounted for when you have a market that trades the currencies themselves.

I should hope it doesn't work that way, because under section 117 of the Copyright Act I'm allowed to keep an archival copy. [0]

[0] http://www.copyright.gov/help/faq/faq-digital.html

This tech, and that business plan, is nothing new. Plastic Logic aimed squarely at the professional market with a flexible e-ink reader that debuted at CES 2009. [0]

It hasn't worked out so well for them. I visited their booth in 2009, and they showed a large flexible screen housed in a rigid case. It was to be the advent of flexible e-ink, and the beginning of a new era. Eventually, their announced content partners fell through, and despite an initial splash it never really materialized.

Plastic Logic did launch in the US, but shut down their US ops in 2012. [1] They are still a going concern, however, and still focusing on the business market.

[0] http://www.slashgear.com/plastic-logic-que-wireless-ebook-re... [1] http://www.ft.com/intl/cms/s/0/1a08be60-9eba-11e1-9cc8-00144...

In fact, without specifying anything else, a Rails app deployed to Heroku will default to using webrick. Consequently, at Waza 2013 they revealed that webrick is the most used server at Heroku, and is 3x more popular than Thin. [0]

[0] http://www.slideshare.net/heroku/heroku-secrets-waza-2013

Sure - and I think Sony e-readers were even among the first to allow side-loading of non-DRM ebooks.

The problem is the economics. There just haven't been financially successful examples of standalone readers, and Sony has been no exception.

Amazon can offer cheap Kindles because they can sell ebooks onto the devices directly and make money from content. Apple can charge more for their books because people are bought-in to their iPad investment, and because competitors have to pay Apple 30% to sell directly on to an iOS device.

Sony, meanwhile, continues to fail to bring an integrated value proposition to the market. Everything with them involves friction, compared to the competition. Last time I was at CES, I couldn't even find a Sony reader in their booth.

Meanwhile, today I get an email from Sony saying that their Reader store closed on March 20, and that it has ceded its customers to Kobo, which spawned from Canada's Chapters Indigo. [0]

While this tech may be notable, Sony continues to have a fatally misaligned device/content strategy.

[0] http://www.kobobooks.com/SonyMigrate

I'm not, but I'm watching several of the Github repos and doing fresh EC2 installs and tests whenever they release a new version. I'm very much a fan of the project, but I would not use it in production at this point.

CoreOS is still alpha, which is exemplified in this release, which requires a fresh install and isn't upgradeable from the previous release with their auto-update feature.

Also the team is still working out where to put things, filesystems, and how to best integrate etcd, networkd, systemd, etc., with their fleet system for a fully automated, auto-scalable, auto-discovering, self-healing clustering system. All that stuff has come a long way in recent weeks, and I'm very glad to see a distro geared towards both Docker and clustering.

It's a pretty impressive system. If you're interested in their architecture, here's a YouTube video worth watching: "Marco Cecconi The Architecture of Stack Overflow - Developer Conference 2013" [0]

[0] https://www.youtube.com/watch?v=OGi8FT2j8hE

To make matters worse, people who get this news while wearing an Oculus Rift headset can't even do a proper facepalm.

Github is good because it adds value and removes friction.

Well, I'm a Salt user and I was communicating with Matt during the writing of his book. During that time he certainly gave Salt a solid, fair evaluation. He also spent a lot of time hanging out in #salt IRC asking key questions, and answering some as well.

So I would suggest that it's natural and OK for someone's evaluation process to yield a favorite (apparently in Matt's case, it's Ansible), without it becoming a "religious passion."