1. TC Disrupt Hackathon part 2 - Miniprinter hack

    Miniprinter is a little hardware hack to make legal contracts more portable and cute. I took a thermal printer (a tiny printing device normally incapsulated in cash registers to print receipts) and I “hacked” into it to make it print what I wanted.

    To do this, I used an open source prototyping platform called Arduino. Arduino’s circuit board is connected to both the printer and by computer. Once the circuit is set up, Arduino does all the programming work. Relying on a couple of Adafruit’s Arduino libraries I was able to make a short sketch on Arduino and print this contract on a 2.25” roll of paper! Here’s a video of it (ignore the black screen and drama following the fall of the Miniprinter!)

    This is only the first prototype: Miniprinter 2.0 will be portable, connected to the internet, and will play Game of Thrones theme in 8-bit while printing. It will become the ultimate accessory for the modern lawyer!

    This is a cool yet simple hack: it was my first Arduino project and you just need a couple of wires to make it yourself. Just get a thermal printer and an Arduino starter kit, and plug in the code below!

    // this sketch works with Arduino 1.0 only
    #include "SoftwareSerial.h"
    #include "Adafruit_Thermal.h"
    #include "qrcode.cpp"
    
    int printer_RX_Pin = 2;  // this is the green wire
    int printer_TX_Pin = 3;  // this is the yellow wire
    
    Adafruit_Thermal printer(printer_RX_Pin, printer_TX_Pin);
    
    void setup(){
      Serial.begin(9600);
      printer.begin();
    
      printer.doubleHeightOn();
      printer.justify('C');
      printer.println("Contract for hackers \nwho hate contracts");
      printer.doubleHeightOff();
     
      
      printer.println("This agreement is between Hacker01 and Hacker02. We agree as follows:\n1) Each of us, individually, is free to use any programming concept shared, discovered, or created during the TC Disrupt Hackathon 2012.\n2) Each of us hereby grants a full, non-exclusive, free license to the other to use any code or binaries from the above project. This means that each of us, individually, is free to use anything we create for the project above as part of a separate larger project with a significant amount of additional functionality.\n3) In the event that the project above is successful, we'll take reasonable efforts to come to a new agreement with the goal of creating a separate entity to manage and develop the project further");
     
      
      printer.justify('L');  
      printer.println("Signatures:\n_______________\n_____________");
      
      printer.inverseOn();
      printer.println("This minicontract is legally binding, don't lose it! Execute it online for free by scanning the QR code below");
      printer.inverseOff();
    
    
      printer.printBitmap(135, 135, adaqr);
      printer.println("Docracy.com");
      printer.feed(1);
    
      printer.sleep(); //Tell printer to sleep. MUST call wake before printing again, even if reset
      printer.wake(); //Wake printer.
      printer.setDefault(); //restore printer to defaults
    }
    
    void loop(){
    }
    

  2. Our TechCrunch Disrupt Hack: Kickli.st!

    Kickli.st!

    As Docracy was born at the TechCrunch Disrupt Hackathon in NYC last year, we were excited to return last weekend for a day of hacking. We worked on a small and simple service that we really wanted to exist, and the result our hacking is Kickli.st!

    The motivation for Kickli.st is that mailing lists are great, but they tend to deteriorate over time as the list starts to get spammed, or unsavory members arrive and lower the overall quality of conversation. Kickli.st combats this phenomenon by providing mailing lists with three simple concepts:

    1. The only way to get added to a list is to be invited by an existing member.
    2. Members can easily vote that an email sent to the list sucked, resulting in a strike being given to the author. If that user accumulates just two strikes, they are kicked off the list!
    3. Of course, that same user can be invited back by another member. However, when somebody gets kicked off the list, the member who invited them also gets a strike!

    We think that these rules will help maintain the quality of postings… either that, or lists will simply self-destruct, which would at least be exciting! The entire interface (creating mailing lists, voting against messages, inviting new users, etc.) is handled via email, making it very accessible from any type of device.

    It was the perfect bite-sized one-day hack, and we think it will be useful as well. We’re starting to create some fun (YET DISCIPLINED) mailing lists with Kickli.st, and you should too: head on over to the site to sign up, after which you can create your own lists via the email interface.

  3. We had a great time at TechCrunch Disrupt; both the Hackathon part on the weekend, and the main event during the week. See above for some company photos, courtesy Quotidian Ventures, who hosted a great “Startup Village” at the event, including the photo booth, ping pong tables an even an inflatable meeting room!

  4. Hacks, Docs and 1 year review

    I can’t believe that it’s been a year since we started Docracy at the TechCrunch Disrupt Hackathon.  As we get ready to do it all over again this Saturday, I think back to an important quote from 4AM last year: “I’m never doing this again.” A lot has happened in the last year, including Docracy now being our full time job which is pretty awesome and crazy when I think about it.

    One thing we wanted to do last year was work with some new people we would meet at the event. Ultimately we decided not to because we didn’t know who would end up owning the idea once the haze of the weekend had cleared. If you’re worrying about this yourself, you actually have a few good options now on Docracy. Here’s a quick summary of some of them:
    1. Agree to open source everything you work on. Just start a project on github and put a license of your choice in there. Awesome, somewhere a dolphin just smiled.
    2. Agree that everyone on the team gets to use the code for whatever they want. This is the simplest option for code you want to keep private, and you don’t want to split up ownership of some imaginary entity. You can always agree to form a company later once you figure out who’s going to actually do some work instead of getting drunk and fighting about PNG files (true story). A simple doc for this situation is: https://www.docracy.com/5211/contract-for-hackers-who-hate-contracts
    3. Finally, maybe you’re a little further along and actually want to define the relationship and get started for real. Take a look at Seedcamp’s Founder Collaboration Agreement: https://www.docracy.com/103/founder-collaboration-agreement and also a branch that doesn’t split equity https://www.docracy.com/234/the-revised-collaboration-agreement
    If you have any questions just ask them in the related document discussion, someone will be along to help out. And if you’re going to the hackathon, come find us and sign our legally binding t-shirts! Or just check out our hacks before we fall asleep in our chinese food.

    More hackathon related documents can be found in our hackathon bundle, for example:

  5. Quotidian Ventures: Get To Know... Docracy →

    The folks at Quotidian Ventures interviewed Matt! Click on the title to read the full thing, it’s pretty funny! 

    qventures:


    Why you care:


    Starting (and running) a company can lead to reams of paperwork. Docracy aims to make the paperwork in your life free, trustworthy, and collaborative, so you can minimize your legal bills and maximize your ability to handle the other 999 things on your plate.

  6. The standard of standards

    We’re the proud new hosts of three highly standardized contracts from KIIAC:

    Why do we like these documents? Because their level of standardization was objectively measured against a statistical model—the clauses that anchor these documents are actually the clauses most commonly used in contracts drafted by flesh-and-blood lawyers.

    In other words, if you are a stats nerd or a contracts nerd or any other type of nerd, keep on reading.

    There are two ways to establish any type of standard, legal standards in particular. The first is “top-down”: an authority (usually the government or a particularly influential industry association) pipes up and decrees: “Folks, this is the standard form for this type of contract. You all shall use this from now on, so we all execute the same thing.” Everybody answers “Amen” and a standard is born.

    The second is “bottom-up”: a particular contract becomes relatively popular due to its characteristics. Maybe it’s more fair, more clear, more complete. Or maybe it’s just shorter or simply easier to get. More people start adopting it because they like it, and a virtuous cycle is set into motion. Eventually, the contract becomes so common that people sign it without even reading: they already know what’s inside. These “natural standards” are the most powerful, and maybe even the most fair, as they are shaped by market forces.

    Figuring out how to automate this second type of standard agreement is the goal of Mr. Kingsley Martin. It’s pretty hard to describe his software, KIIAC, in plain English, but I’ll do my best.

    KIIAC is leveraged on the fact that most legal language is already pretty standard. Transactional lawyers have been using each other’s language for centuries, in the process of drafting contracts and improving clarity and enhancing legal protections. But now we have machines.

    By applying statistical metrics to document comparison, KIIAC identifies commonalities and divergences among contracts and homes in on the specific clauses where those divergences are most likely to occur. Note that Kingsley’s objective is actually to help lawyers draft contracts more efficiently–but in the process of building his engine, he wound up identifying these standard contracts, which we’re delighted to be hosting.

    Thanks to the almighty power of statistics, Kingsley can put any contract into the KIIAC machine and tell you how standard it is by comparing it to what others have signed in real life. How cool is that?

    Even cooler, now that the standards are on Docracy, you can work directly on those: customize and sign the most standard document ever. Finally, the phrase “this clause is very standard” has a real meaning. Thanks to Kingsley for open-sourcing this incredible material. If you want to know more, check out KIIAC and the Contract Standards website.

    Happy signing!

  7. Get a contract, get paid (Reloaded)

    Today we dedicate our weekly blog post to a seriously good cause: helping independent professionals getting paid for their work.

    Our friends and neighbors at Freelancers Union are bravely promoting a new piece of state legislation called The Freelancer Payment Protection Act – which would legally protect freelancers from clients who do not pay their dues. If a client doesn’t pay you, you’re now forced to take unreasonable and expensive efforts just to get what you’re rightfully entitled to. In the worst cases, taking action is so expensive that you just give up on getting paid. And it’s not a small amount: Freelancers Union estimates that in 2009 alone, New York State’s self-employed lost $4.7 billion due to client nonpayment, and the state lost $323 million in tax revenue.

    fppa

    Did it happen to you? Add it to the World’s Longest Invoice and support the campaign!

    This new legislation, if passed, will bring new legal tools against “deadbeat clients”, enabling the self-employed to file complaints with the New York State Department of Labor, which will investigate the claim. Victims may be able to receive 100% of what they’re owed, plus attorney’s fees and interest on the amount owed. You can learn more here.

    Never forget that, as our attorney friends at BklynLegal say, if you don’t have a written contract the only one who gets paid is your lawyer. Start using Docracy to ink your deals: it’s free and we have some good templates to start from!

  8. Feature Friday - New Editor, Sign Again

    The last few weeks have seen dozens of small enhancements and improvements on Docracy, but there are just two new features we’ll focus on in this edition of the celebrated blogging phenomenon known as Feature Friday:

    New Editor

    New Editor Toolbar

    The document editor has been vastly improved. The key new feature is that you can now insert a field into the doc simply pressing the orange, left-most button in the toolbar. Fields are important as they allow a signing user to fill in specific contract details such as dates, amounts, time limits, etc. Field details can include default values and even a method of automatically filling in standard contract values (i.e., today’s date, names of the parties involved, addresses).

    New Field Editor

    Sign Again

    Sign Again Feature

    This next feature is a simple one, but really handy. A user can now sign a new contract based on a copy of an old one. Simply review an old signed contract and click the Sign the Document Again link. The fields are already filled in exactly as before, and any custom edits are preserved. Simply adjust the document fields to the new situation, indicate the new recipient, and the document is ready to sign.

  9. Hack that contract!

    Docracy is the platform for BLIP’s legal hackathon, happening now at the Brooklyn Law School. Alongside the main theme (hacking SOPA draft and make it better) we are running a “contract hack”. We are inviting everybody to “hack” an existing contract on our site.

    We picked real-life contracts and published them on Docracy.com, and we challenge all hackathon participants (and anybody who is up for the task) to make them better and more useful. Turn the contract into a template, a standardized, legally solid agreement, simple to read and understand. Pull it apart and make it as simple and as generic as possible. The best effort will win a Kindle Fire!

    How to participate in the Hacking Contracts Contest

    What: You have four different agreements to choose from as a starting point, of different levels of difficulty (you can compete in one or more category and hack more than one contract). The starting documents are:

    How: Use Docracy’s branching function to create your version of the contract you chose. Work on it as much as you need, and make it public when it’s ready.

    Judging criteria: Docracy’s team (John, Matt, and Veronica) will select the winning edit at the end of the event according to the following criteria:

    • Readability (use of formatting, plain English, no redundancies)
    • Standardization (ability to distinguish boilerplates from relevant business clauses, use of form fields, adaptation to e-signing)
    • Awesomeness (general quality of the final draft)

    When: You have 2 weeks from today (i.e. until Sunday, April 29) to branch one of more of the documents above.

    Prize: We will deliver to the winner a shiny new Kindle Fire!

    If you are at BLIP’s Legal Hackathon today, come at our workshop in room 602 after lunch to learn more about our contract quest!

  10. Welcome to the first Legal Hackathon

    Blip

    Next Sunday, April 15th, we’ll be at the first BLIP’s (Brooklyn Law School Clinic) Legal Hackathon, a.k.a. #HackTheAct. This hackathon is an experiment in democratic legal drafting. Prof. Jonathan Askin and his team want to prove that motivated and skilled citizens are better legislation drafters than political staff in D.C. More than hundred lawyers and techologists will meet up at Brooklyn Law School. Their quest? To write a better version of SOPA, the contested legislation proposal that tried to enhance the protection of intellectual property on the internet.

    Docracy will provide tech support to the hackathon by allowing participants to “branch” (make a copy) of the original Act and work on their own version. They will be also able to use Docracy’s “merge” function to work collaboratively during the following days, embedding comments into a final proposal that will be submitted to the judges. The grand prize is $1,000, so sign up while you still can!

    We decided to support the #HackTheAct mission and philosophy for the following reasons:

    • Docracy’s prototype was built at the TechCrunch Disrupt Hackathon. We believe in creative collaboration, and we think you can build meaningful things in just a few hours. “Hacking” really means using your intellectual skills to tweak existing material for your needs, and this skill is totally applicable to the world of legalese.
    • We think legal information should be more accessible, and we incentivize the sharing of legal knowledge by applying concepts like crowd-sourcing and open-sourcing to law. Docracy was built to make commercial transactions more transparent and efficient, and we believe the legislative process could also benefit from more transparency and efficiency.
    • We care about technology and want to grow in an environment that’s both secure and free, and where intellectual property exists but is not exploited at the expense of society. Only people who know the web very well understand these needs, and we like to think some of them are better positioned to write regulation than professional legislation drafters.

    In support of #HackTheAct, we will invite everybody to “hack” an existing contract on our site. At the #HackTheAct event, we will publish a real-life, IP-related contract taken from the SEC database on Docracy.com. We challenge hackathon participants and anybody who is up for the task to make it standardized, legally solid, and simple to read and understand. Pull it apart and make it as simple and as generic as possible.The best effort will win a Kindle Fire!