This post originally appeared on the Shapeways blog.

Spring is in the air, and that means that it is time for a few policy updates here at Shapeways.  This blog post serves as a summary of those changes.  As a reminder, if you want to go deeper you can always check out the archived versions of specific policies in order to compare them to the current one.

The biggest update is to the Shop Terms and Conditions.  These terms were last updated in 2012 and, as you can imagine, Shapeways has evolved significantly since then.  In addition to the Shop Terms update, this update includes much smaller fixes to the general Terms and Conditions, the API Terms and Conditions, and the Content Policy.  We are also bringing our content policy precheck program out of beta.  I’ll detail all of the changes below.

Shop Terms and Conditions

These are the terms that govern shop owners on Shapeways.  This update overhauls the format so that it makes a bit more sense, and updates some of the policies.  It also takes steps to simplify the terms.  Since you need to have a regular Shapeways account in order to open a shop, it tries to incorporate terms from the standard Shapeways Terms and Conditions by reference instead of repeating them again in the Shop terms.

For example, instead of having a big section on content rules, the new terms incorporate the existing Content Policy.  That should reduce confusion by just having one content policy that governs the entire site and make the terms a bit more concise and easier to read.

While the payment terms remain largely the same (we pay your markup if it is over $30 on the 15th of each month) there are a few additions designed to clarify policies and address issues that have emerged over the years.

One of the most important changes is to highlight the importance of providing us with correct PayPayl information for an account that can receive transfers from the United States or the Netherlands.  Failure to do this can cause all sorts of problems, so we wanted to make sure that there was ample warning in the terms that you need to do that in order to receive  your markup.

Another change is adding rules about how we handle markups on orders that later get returned or rejected.  Sometimes a model is returned because we did not print it correctly.  In those cases we will continue to reprint the models at our expense and send shop owners their markup.  However, sometimes a model is returned or rejected because of an error on the part of the designer.  We are currently exploring the best way to handle those situations.  It is likely that in at least some of those cases we will not pay the designer a markup if the return or rejection stems from errors that they made.

The changes to the terms give us the ability to begin testing rules governing what happens when a product is returned due to designer error.  The process of exploring options will take some time, and we will strive to do it in an open, inclusive way.  Expect to hear more about the process soon.  Until we roll out a more formal tests, designers will at most receive warnings that their model was returned due to what we believe to be their error.  To put it another way, we will not begin withholding markups for returned or rejected models until we have new rules in place.

Most of the rest of the changes are relatively small.  We added a reminder that some tax authorities require us and/or our payment processors to report data on accounts with gross payments over $20,000 and 200 transactions.  We also did a better job of linking the indemnity and product liability sections of the shop owner terms with the general site terms.  At the end we made it explicit that we may change the terms from time to time.

Finally, we linked the confidentiality terms in the shop owner terms to those in our privacy statement.  Hopefully that will give all users of the site a  more uniform set of expectations in terms of privacy on the site.

Terms and Conditions

As I noted at the start of this post, in addition to an overhaul of the shop terms and conditions we also made some updates to other policies on the site.  In addition to fixing some typos in our general terms, the update has two substantive additions.  These are actually clarifications of existing policies that we wanted to make even more clear in the terms.  Remember that these apply to all users, not just shop owners.

The first is what happens when a model violates the content policy. The terms now make it clear that if a model violates our content policy we will refuse to print it and issue you a refund.  If we catch the violation after we print the model, we will not ship you the model and may not issue you a full refund.

We are pairing this with removing the content policy precheck program from beta.  You can email  content-precheck@shapeways.com if you are worried that a model might run into trouble with our content policy.  Even if your model is incomplete – or even just an idea – we will do our best to give you guidance about how our content policy applies to you.

The second update to the general terms a clarification as to what happens when you remove a model from Shapeways.  The terms now make it clear that we may continue to use the model as part of our internal education and testing process. This is largely because we use user models to develop testing benchmarks that need to be consistent over time.  However, you can still always email customer service when you remove a model and request that it also be removed from internal testing.

API Terms and Conditions

The updates to the API Terms and Conditions are relatively modest.  In addition to some minor typos, the terms now make it clear that developers using the API are responsible for all fraud and chargebacks related to their use.  Since the API developer is in the best position to design their application in a way that avoids these sorts of fraudulent charges, it seemed only fair that they are responsible when someone uses the application fraudulently.

Content Policy

Last on the list of updates is the Content Policy.  The biggest change, which I already  mentioned above, is that we are bringing the content policy precheck out of beta.  Besides cleaning up some typos (by the way, feel free to let me know when you see typos in our policies….), the only other change is to make our preferred way of receiving copyright takedown notices more prominent.  Sending emails to content@shapeways.com is the best way to get a takedown request processed efficiently, and now that email address is more obvious on the page.

Thus concludes the spring recitation of the Shapeways policy updates.  As always, if you have any comments, questions or concerns, feel free to put them in the comments below, email them to me at mweinberg@shapeways.com, or tweet at me @MWeinberg2D.

This post originally appeared on the Shapeways blog.

Last week Shapeways participated in the fifth annual 3D/DC conference.  3D/DC is an event held by the nonprofit advocacy organization Public Knowledge (full disclosure: I used to work there) designed to connect 3D printing with policymakers in Washington, DC.

The world of 3D printing has evolved a lot since the first 3D/DC, and the conference has evolved right along with it. The first 3D/DC (video highlights here) was primarily focused on introducing 3D printing to policymakers and introducing policymakers to 3D printing.  Most attendees of 3D/DC in 2011 had barely ever heard of 3D printing, and may never have even seen pictures of 3D printers.  Similarly, the 3D printing community itself was largely unfamiliar with the policy world and had never even thought about trying to set up a meeting with a Member of Congress.

Fast forward to 2016.  Everyone may not have seen 3D printing first hand, but panelists didn’t have to begin every conversation with an explanation of what 3D printing was.  As a result, after a day of private meetings with Members of Congress and their staff, the public day of 3D/DC could focus on the application of 3D printing to important areas of policy.

Public Knowledge’s Courtney Duffy did a fantastic job of bringing new perspectives and areas of focus to the event this year.  The first panel, on 3D printing and STEAM education included Shapeways’ own Lauren Slowik.  Lauren is our point person on connecting the educational and arts community to Shapeways, so she was able to bring an applied perspective to the conversation.  She was joined by two kids who live 3D printing and STEAM education, John (age 11) and Becky (age 15) Button, along with Sophie Georgiou of Morphi and Joseph Williams of Perris Union High School District.

That first panel set the tone for the rest of the day by talking less about 3D printing for 3D printing’s sake, and instead focusing on how 3D printing integrated into issue areas such as the environment, workforce development, social impact, and the arts.  These panels, which brought together diverse perspectives from both inside and outside of government, were possible because 3D printing has expanded well beyond its original group of enthusiasts.  As we here at Shapeways see every day, many of the most exciting applications of 3D printing comes from people who care less about how 3D printing works and more about what 3D printing can do.

While a policy conference in Washington DC would not be complete without policy panels, 3D/DC is not complete without its culminating reception.  Although many more people have heard about 3D printing in 2016 than in 2011, there are still plenty of people who have never experienced it in person.  The reception and demonstration gives policymakers a chance to see 3D printing and talk to the people behind the printers in a less formal atmosphere.

This reception has evolved over the years as well.  As more and more local community groups, libraries, and maker spaces grow up across the country, 3D/DC can draw on a vibrant local 3D printing scene to demonstrate at the reception.  As a bonus, staffers and policymakers who live in the Washington, DC area can walk into 3D/DC and walk out with information on how to join a local hacker space.  Over the long term, a cadre of wonks who have deep first hand experiences with 3D printing will make sure that 3D printing policy coming out of Washington is created with a nuanced understanding of the technology.

You can check out more about this year’s 3D/DC by searching #3DDC2016 on twitter.  I’ll also try to update this post with a link to videos of the panels as soon as they are up.  In the meantime, you can learn more about what Public Knowledge is doing to help advocate for good 3D printing policy here.

Last week Sparkfun ran a piece on their blog called “FaKey Makey” taking a deep dive into what appears to be an unauthorized derivative of the popular MaKey MaKey hardware accessory.  Briefly - and I commend the entire thing to you - it concludes that a product called the MC2 Circuit Beats manufactured by MGA Entertainment is a derivative of the MaKey MaKey that fails to give MaKey MaKey credit as the source of the idea.  

In addition to the really impressive forensics work in the post, the incident serves as a nice opportunity to reflect on the limits of open source hardware licensing.  It may also help highlight why the Open Source Hardware Association is moving towards a certification model and not an approved license model.

But first…

Some quick background may be helpful.  The MaKey MaKey is a clever bit of hardware that lets you use all sorts of physical objects as input for your computer.  If you are itching to turn those bananas in your kitchen into a piano or use the walls of your living room to control a video game character, the MaKey MaKey is a good place to start.  

It is also open source hardware, which means MaKey MaKey makes things like their schematics available under a CC (in this case attribution, share-alike) license.  

For the purposes of this post I’m going to assume that everything in the Sparkfun article is true and that MGA 1) made something that can trace its lineage back to the MaKey MaKey, and 2) failed to give MaKey MaKey attribution for that history.  Keep in mind that either of those could be incorrect.  I’ll do my best to update this post if I become aware of evidence to the contrary.

Moral/Social Issues

The moral and social issues surrounding open source hardware, derivatives, and attribution can be complex, so I’m going to skip over them here.  Instead, I’m going to focus on the legal and licensing aspects of what happened here. Specifically, did MGA - the company that made the derivative product - violate any licenses?

Does the New Board Violate MaKey MaKey’s License?

Spoiler: I don’t think so.  But I’ll go deeper than that.

MaKey MaKey puts out its schematics under a CC license.  It is important to understand what that really means.  A CC license is a copyright license and can only control the use of works that are protected by copyright.  In this case, the schematics are covered by copyright.  However, this does not mean that the MaKey MaKey itself is covered by copyright. In fact, as a functional object, it is not protected by copyright (there are some clever lawyer arguments that one could use to chip away at this simple statement, but in the interest of clarity I’m just going to work under that assumption).  That means that the license on the schematics are irrelevant to the object itself.

What does that mean?  If you copy MaKey MaKey’s schematics without giving MaKey MaKey attribution, you have infringed on their copyright.  However, if you just decide to copy the MaKey MaKey itself, the license they attached to their schematics requiring attribution doesn’t matter.  You have no legal obligation to give MaKey MaKey anything.

Even if MGA copied MaKey MaKey’s schematics, as long as they kept the attribution on the schematics they probably did not have any obligation to give attribution on the product itself.

Is it Bad that MGA Can Copy MaKey MaKey?

I don’t think that it is.  The fact that hardware can be copied is a feature, not a bug, of IP law.  

Unless MaKey MaKey had a patent on its core functionality, the fact that MaKey MaKey is open source hardware doesn’t really have an impact on MGA’s ability to copy it.  While the schematics  may have made it easier, the Sparkfun post suggests that a determined copier probably could have figured out what was going on without them.

On the flip side, I’d be willing to bet that MaKey MaKey’s openness has helped it grow a community and a market.  I also suspect that this benefit outweighs whatever “cost” making it easier for copiers to access schematics imposed on them.

This incident also serves as a reminder that hardware is open by default.  If you’ve even been frustrated with copyright restrictions, this world of open by default can feel liberating and loaded with possibilities.  If you have ever reverse engineered a piece of hardware without asking permission from the manufacturer first, you understand what that openness means.

Finally, remember that openness goes both ways.  The same legal structures that make it hard for MaKey Makey to protect its core functionality with IP makes it hard for MGA to protect whatever improvements they have come up with.  Even if MGA does not release the schematics, it is likely that MaKey MaKey can reverse engineer them and incorporate them into a future version of MaKey MaKey. (note: maybe do not do this without first talking to a lawyer).  To me, that’s an example of how the openness ecosystem in hardware can extend well beyond a core group of open source hardware devotees.  

Would A Different License Change This Analysis?

I don’t believe so. The core challenge remains that you need a work protected by copyright as a “hook” for any restrictive copyright license.  Even a non-commercial restriction on the schematics probably would not stand in MGA’s way.  (side note: would downloading a copy of the schematics in order to make a commercial product based on those schematics - as opposed to commercially selling the schematics themselves - violate a non-commercial CC restriction?  I don’t know but I’d argue against it).

Would an Open Source Hardware Certification Help in this Situation?

Yes and no.  As I hope this post makes clear, one of the reasons that the Open Source Hardware Association is looking towards certification is because copyright-based hardware licenses can leave a lot out.  Those exclusions can come as a surprise to the people who are using the license.

A certification will not directly prevent someone from making an unattributed derivative of a piece of hardware.  Of course, in many cases, neither would a license. The open by default nature of hardware makes that sort of condition very hard to enforce without patents.

However, to the extent that people see a Open Source Hardware Association certification as valuable, it can help distinguish the MaKey Makeys of the world from the MGAs of the world.  People value openness - and value it more every day.  If a product like MaKey MaKey can stand up and say that they truly are open, it can - I hope - help expand their market reach.

For now, it seems like MaKey MaKey and the MGA board can coexist.  That’s a good outcome too.  My real interest in this incident is that it gives another excuse to do concrete thinking about how open source hardware and licensing can really work.

Let’s start this post with a lawyerly caveat. Everything on this site is my own personal opinion and should not be attributed to my employer or anyone else.   While that’s always true, this post is super thinking-in-progress-y so it seemed wise to repeat that.  Plus I’m not even a pretend product liability lawyer so keep that in mind.

For many people, IP is the first thing that comes to mind when they imagine ways for 3D printing to get into legal trouble.  It certainly was for me, and I think that’s more or less right.  IP issues are coming first in the 3D printing world.

However, if you give people a few more minutes, the second thing that comes to mind is often product liability.  And rightly so - product liability is a big area of law and 3D printed things can hurt people (because, you know, “things” as a product class can hurt people).

However, thinking about 3D printing and product liability isn’t easy.  Modern product liability law developed along with mass manufacturing and the structure of mass manufacturing is build into its underlying assumptions that ground modern product liability law.  A technology that reintroduces variability, customization, and distributed manufacturing into product design and manufacture runs counter to much of product liability’s worldview. Before you even get to the rules, 3D printing just doesn’t fit into how product liability law sees the world.

Furthermore, product liability is not necessarily prepared for a big shift.  Everyone involved in copyright law has experienced (is experiencing?) a fundamental shift in its practice in the last twenty years.  While that shift has not been as extensive in patent and trademark law, those legal worlds are close to copyright.  At a minimum, that gave them a front row seat to the change.  Like it or not, IP lawyers, policymakers, and advocates are emotionally prepared for seismic change.

In contrast, product liability has been on a relatively stable trajectory for decades. This isn’t to suggest that it has been unchanged - there have been plenty of important shifts and big decisions.  But when compared to an area like copyright its basic assumptions and ordering principles have been remarkably static.  That may mean that the people who make up the product liability policy world are less prepared for a big change.

One way to think about the forces driving these changes is to lay out the contrasting world views of traditional product liability and the new model exemplified by companies like Shapeways.

Traditional Model

• Professional Designers. With modern mass manufacturing, products are designed by individuals or teams with a deep understanding of material properties, tolerances, and  other relevant considerations.  They are trained to anticipate potential use problems and incorporate solutions into the design.
  
• B2B Manufacturing Relationship. Once those designers finish the design, they contract directly with a manufacturer.  The manufacturer understands what they are manufacturing and establishes manufacturing and monitoring processes oriented towards the purpose of the object.
• QA Testing Fit for Purpose.  Because both the designer and manufacturer understand what they are manufacturing and how it will be done, they can collaborate on a testing regime oriented towards the anticipated use of the object.
• Mature Insurance and Contract Umbrella.  Each party is insured and risk is contractually allocated in line with well established industry norms.

New Model

• Designers of Mixed Backgrounds.  While some designers in this new model are trained engineers, plenty of them are not.  Their skill set may have blind spots and shortcomings that they are not aware of and that do not immediately and obviously manifest themselves in their work.
  
• Arms-Length Manufacturing Relationship.  The designs can be printed by a service bureau, but the service bureau does not necessarily appreciate the actual purpose of the object.  The manufacturer uses generic 3D printing processes that are not tailored to the object.
• Lack of QA Testing.  Since the manufacturer does not know what they are printing, they do not create tests to make sure that the finished object is fit for purpose.  Repeatability in 3D printing is not up to the standards of traditional mass manufacturing, so the designer may have a limited understanding of the characteristics of a specific model shipped directly to a customer.
• Immature Insurance and Contract Umbrella.  The process is full of players who may not be insured with an eye towards product liability.  Contracts do not necessarily allocate risk along well established industry norms.

This does not mean that the 3D printing-enabled ability for an individual in their basement to sell physical products to the world is doomed.  Nor does it mean that we should scrap the existing product liability regime because this new model isn’t a perfect fit out of the box.

Instead, as I tried to outline in my response to Adam Thierer’s proposal for maker immunity, it means that we are at a moment where it may make sense to rethink parts of the existing product liability regime.  It is worth trying to understand if the goals of product liability  - to create incentives for people responsible for goods to make their goods safer and to compensate people who are injured by goods - can be advanced in a way that does not require every player in the design-build-distribute chain to be a commercially and legally sophisticated entity.  

Obviously it is way to early to know. Hopefully we are in the beginning of that discussion.

By the way, the Minnesota Journal of Law, Science, and Technology had a really great symposium on 3D printing and law in March.  I’d recommend the entire thing if you are interested, but they did an entire panel on product liability where people who actually know product liability work through some of these issues.

This post is mostly a reaction to Adam Thierer’s recent article titled “A Section 230 for the ‘Makers Movement,” although in the grand tradition of reaction pieces it also uses the article as an excuse to write about a few things I’ve been thinking about lately.  It will probably make a bit more sense (or at least be easier to point out what I’m missing) if you read his piece first, although I’ll do my best to summarize it along the way.

The “230″ in his title is Section 230 of the Communications Decency Act, which gives online platforms wide ranging immunity from responsibility for the things their users post on said platforms.  Many people consider it one of, if not the, most important foundational laws for the growth of the internet.  Essentially, this is because it allowed online platforms to let crazy people they don’t know post things for the entire internet to read.  It is the reason, for example, that tumblr isn’t going to do a legal review before letting me use tumblr to post this blog post.  They don’t care what I write because no one can sue them for my degenerate libelous crackpottery.

What Does This Have To Do With “Makers”?

Before Section 230, traditional law treated publishers as responsible for the things that they published.  This made sense when your mental image of a publisher is the New York Times.  The New York Times is exerting a lot of control and review over what gets published in its pages, so it is reasonable to hold them accountable if one of their writers does something crazy.  However, tumblr (or twitter, or facebook, or whatever) doesn’t have the same relationship with its “writers.”  It does not make sense to hold them responsible for what people publish on their platform because they do not exercise any control over that content.  The internet meant that a lot more people were writing for the public and that the old mental model for dealing with that broke down.

You can draw a fairly convincing parallel to the maker movement.  A collection of technologies is allowing more and more people to not only make physical things, but distribute those physical things around the world.  Regulatory models relating to physical things that assume that there are a limited number of people or companies manufacturing and distributing physical objects don’t necessarily apply.  The nature of the new players involved means that traditional legal assumptions may not apply.  That can result in unjust law and crippling (unintentional) inefficiencies.

If that thesis is correct, it is very tempting to look to the internet model - and Section 230 in particular - for the best ways to address this disruption.

Extending Immunity - The Uber Model vs. the Collaborative Model

Obviously talk of immunity for the technologies and platforms that make the maker movement work is highly interesting to me professionally.  After all, my day job is at just one of those platforms.  Similarly, my not-day job is on the board of the Open Source Hardware Association and there are some people who worry about the legal ramifications of releasing a swarm of open source physical objects out into the world.

However, I do have a reflexive concern about any call for blanket immunities for new technologies.  It may not be fair, but some of those are grounded in what might be thought of as the Uber approach to policy.

Uber was faced with a thicket of taxi regulation that threatened their business model. Their initial response was essentially to dismiss those regulations and bulldoze their way through to the market.

For many people this was a highly popular approach, made all the more popular because many of the regulations that were being bulldozed were imposed by government agencies that were captured by the taxi industry they regulated.  The regulations appeared to benefit the taxi industry much more than taxi customers, so many Uber customers quickly sided with Uber over the regulators and did not shed a tear for the lost regulations.

This approach has its appeal.  It can work quickly and radically transform a ossified industry in pro-consumer ways.  But it can also create problems.  One of those problems is that it can alienate potential partners.  But the bigger problem is that the process of bulldozing “bad” regulations can also result in destroying legitimate regulations that have to do with things like encouraging accessibility and protecting users.  This collateral damage isn’t necessarily the intent, but can be very real for users who rely on the regulatory safety net.

There are, of course, alternative models. 

The most obvious is to go back to the concerns that (at least nominally) motivated the regulation in the first place.  Instead of simply saying “this regulation should not apply,” propose an alternative regulatory scheme that achieves the same end goal without whatever negative barriers the existing scheme is creating.  Naturally this assumes that the original goals still make sense, that there is a way to address them without skunking the entire operation, and that someone on the regulator side is interested in having the conversation.  Admittedly, this can also be an excruciatingly slow process.  If it is done well it can leave everyone better off - but that “if” is a big one.

The point of this diversion is mostly to say that I’m a bit wary of simply exempting wide swaths of society from generally applicable rules without some fairly substantial evidence that doing so is necessary and one of the few real options to achieve some legitimate goal.  That’s not to say that it can never make sense - I think Section 230 worked out pretty well - but rather that doing so should usually require a fairly serious consideration of what is lost when granting such an exemption.  

It also means that when thinking about Adam’s proposal the details matter. So let’s get to them.

Models of Immunity

Adam proposes three potential models for immunity: Section 230, firearm manufacturer immunity, and immunity for vaccine manufacturers.

I won’t spend any more time on the 230 stuff.  The firearm manufacturer immunity is interesting.  I’ll be the first to admit that I don’t know a lot about it beyond the fact that Congress passed a law making it hard/impossible to sue firearm manufacturers for tort liability on the theory that they make inherently unsafe products.

Gun politics aside (which is basically impossible in the context of a law involving guns in the US Congress), I’m a bit skeptical that this is a great model for guns or for makers.  One way to think of the purpose of tort liability is to find a way to push an industry towards creating safer products without strangling the industry with regulation.  In that context, I worry that a blanket exception makes it too easy to not move towards safer products in the long run - and “safer products” does not have to mean ‘no more guns’. This is not to say that all tort liability is good.  But I do recognize that it can have a useful role in accelerating the spread of safer products.  The drag that creates for manufacturers can be worthwhile.

The vaccine fund is another interesting example, but one that Adam admits is hard to apply directly here.  The idea is that some sort of government pool of money stands in the place of vaccine manufacturers in cases where vaccines hurt people.  Because everyone benefits from vaccines, in the rare cases when someone is injured by a vaccine it makes sense for everyone to help compensate them.  Removing liability also makes it more likely that companies will step in to manufacture the vaccines and sell them at affordable prices.  The problem when transposing the model to making is that can be quite hard to calibrate the size of the fund or who should be able to hide behind it without more information about the real types of lawsuit threats maker companies are facing.  For better or worse, we just don’t have the data yet.

Areas of Coverage

“Maker stuff” is a crazily broad category, and it would probably be a horrible idea to create some sort of blanket immunity that covers all of it.  Different technologies are different, and the challenges they may or may not present should be dealt with on a more granular level than “it allows people to make and distribute things.”  Easily recognizing this, Adam breaks it down into three categories.

Robots

The proposed immunity is for open robot creators if the robot is under the control of the user or software written by a third party.  The idea is that putting a robot out into the world should not make you liable for every crazy thing that someone might do with the robot.

While I like this theory, I’m not convinced (yet) that existing tort liability is inadequate in this situation.  In at least some cases tort can take into account things like third party or user modifications.  Blanket liability exemptions are a big deal and I’d need a lot of convincing that they are really necessary here.  Imposing liability in nonprofessional makers creates a problem, but it can also bring some benefits.

3D Printing

I obviously have a lot of conflicts on this one.  There would be a clear short term (at least) professional benefit to me if all 3D printing platforms were categorically immune from any claim related to what users do on the site.

That being said, I worry about this sort of exemption as well.  “Many people can use this to make stuff” isn’t necessarily a power specific to 3D printing.  When I think about 3D printing policy, one of my first points is usually to avoid treating 3D printing differently unless you have to.  The fear that 3D printing will be implicated because a user does something stupid or illegal is real, but the answer in those cases is probably to treat it like any other technology.  Creating a special 3D printing carveout should only happen when there is real evidence that there is a 3D printing specific problem that needs addressing.  I’m not sure there is one yet.

Virtual Reality

This section of the post feels more like flag planted than anything else.  It is too early in the history of applied VR to know what may or may not be needed.  Adam seems to view it the same way. I’m glad he raises it, and also glad to see that he doesn’t propose anything specific.

Main Takeaways

I found that this piece made me think a lot about the nature of regulation and liability in the maker context, which is fantastic.  When I approach these questions, I try and start by understanding why the existing rules are there in the first place.  Then I try and formulate an explanation for why a specific technology or application changes the assumptions underlying the regulatory regime.  Only at that point would I start to put forward alternative ways to address the underlying concerns of the motivation (or explain why those concerns are no longer valid) that do not unnecessarily hamper the growth of the new technology.  I’m looking forward to the full length treatment of this issue that Adam promises at the end to see how he approaches it.