MediaTech Law

By MIRSKY & COMPANY, PLLC

HTML5 Unintended Consequence? Getting Around Apple In-App Sales Restrictions.

One unintended consequence of the accelerating popularity of HTML5 for mobile app development is an ability to skate past Apple’s App Store restrictions on in-app sales.  So I put this question to Piotr Steininger of Tapangi Consulting:

There’s talk out there about being able to use HTML5 to get around Apple’s App Store ban on charging for in-app purchases.  In other words (I think), somehow HTML5 allows content producers to get around this problem by making apps (and other things) downloadable directly through web browsers.  So … how is it that HTML5 allows getting around this issue?

Some background: Apple announced a policy change earlier this year, specifically in Section 11.14 of its App Store guidelines,

Read More

Trademarks: Apple Still Fighting “Video Pod”

Sector Labs, a California company that makes a smartphone-size video projector, filed a federal trademark registration in 2003 for the name “video pod”.

Apple, Inc. challenged the registration, filing an opposition to Sector Lab’s registration with the U.S. Patent and Trademark Office.  Apple claimed (among other things) that Sector Labs’ “video pod” “is extremely similar to Apple’s [“iPod” trademarks]”, “consists in part of a significant portion of [iPod] and the entirety of POD, which consumers use as an abbreviation to identify and refer to Apple’s iPod mark and products”, and that Video Pod “covers a device that is or will be used to transmit video for entertainment and other purposes” – much like Apple’s iPod.

Apple’s legal position is that Sector Labs registration would cause source confusion, namely a likelihood of confusion among consumers as to the source of the two companies’ products, and trademark dilution.  Or in other words, “video pod” would dilute the value of Apple’s iPod franchise by reducing the exclusive association in the marketplace of “pod” with Apple and its ubiquitous iPod.

Read More

Twitter API and Legal Issues for App Developers

Much has been made lately of tension between Twitter and its outside developers.  The issues stoking the fire are less legal issues than business issues brought to front-burner by two particular factors:

(1) The maturity of Twitter as a development platform, or in the words of Ryan Sarver of Twitter, “In the early days, all the clients except Twitter.com were built out by ecosystem companies, mainly because Twitter was so focused on keeping the lights on.  But we learned that in order for us to really grow, we had to start taking over that core experience.” (quoted in the NY Times, 7/17/11).

(2) A reported Federal Trade Commission inquiry into the relationship by the , which has (in some views) caused Twitter to re-think its liberal open-door policy when it came to permitting outside development on its platform.

An excellent story and accompanying podcast on this subject appeared in the NY Times last week, written by Claire Cain Miller.

Bottom line: Twitter is seeking to control the applications that control access to Twitter, meaning desktop and mobile, and leaving the field open to enterprise applications, usability applications, analysis and similar applications.

Certainly the business reasons seem pretty clear, in that Twitter seeks to control core functionality – and the development of that core functionality – of the mother ship.  Although it is not terribly surprising that that strikes some critics as cynical, see for example here (“Twitter, just be honest: ‘The only way we can figure out how to make money is same ol’ display ads and we need to own the client for that.’”)

There are legal issues here, namely the ability of the platform to restrict access to its API.  As Claire Miller and others have noted, part of the problem for Twitter is that developer expectations may have been artificially inflated.  But there is more.  The FTC hint of antitrust scrutiny may be causing Twitter some heartburn about its historical open-ness.  Some analogy from two unrelated contexts: In trademark law, the concept “use in commerce” requires confirmation of continued public use of a registered trademark every 5 years or so.  In real property law, a property owner’s failure to restrict public access to property – and thus demonstrate its private claim – can, under some circumstances, support a court’s granting a permanent public right of way.

Quoting Rob Diana from Regular Geek, “Twitter also now owns the platform as a whole and must be as reliable as a utility company.  They must provide all of the capabilities that consumers need in the clients.” (emphasis added) A danger for a “public utility” of the information superhighway is creeping expectation of the duties and obligations of public purpose: Loss of commercial freedom, permanent regulatory scrutiny and public stakeholder claims.  It may very well be that Twitter is acting much like New York’s Rockefeller Center, which closes public access to traffic one day a year as a legal “fiction” in order to continue to assert private ownership rights.

Twitter rolled out its new API TOS (“Developer Rules of the Road”) in March of this year.  Rob Diana noted at that time that the announcement may have been – or perhaps should have been – anticlimactic, in that “A basic Twitter client is a terrible idea in today’s ecosystem.”  Wrote Diana:

Unless there is major functionality outside of the existing solutions, a new client is a losing idea. There is a high barrier to entry when we already have third-party clients like Tweetdeck, Seesmic, HootSuite and PeopleBrowser. This does not include some of the other applications that focus on team or brand management. So, by saying not to develop a new client, Twitter has saved us and investors a lot of time and money.

Read More

Dropbox TOS – In Praise of Clarity

Earlier this month, Dropbox spawned a new kerfuffle in internet-land with changes to its Terms of Service (TOS).

The outrage was fast and furious.  A nice deal of blog and Tumblr and other commentary zeroed in on changes Dropbox announced to its TOS before the 4th of July holiday, and in particular how this or that provision “won’t hold up in court”.  See for example J. Daniel Sawyer’s commentary here.

Sawyer was referring to language in the TOS for cloud-server services granting ownership rights to Dropbox or other cloud services.

At least I think that’s what he was referring to, because the Dropbox TOS did not actually grant those ownership rights to Dropbox.  Dropbox’ TOS – like similar TOS for SugarSync and Box.net – granted limited use rights to enable Dropbox to actually provide the service.  Here is the offending provision:

… you grant us (and those we work with to provide the Services) worldwide, non-exclusive, royalty-free, sublicenseable rights to use, copy, distribute, prepare derivative works (such as translations or format conversions) of, perform, or publicly display that stuff to the extent we think it necessary for the Service.

To be clear, if Dropbox actually claimed ownership rights to customer files – and actually provided for the same in its TOS – there’s no particular reason such a grant “won’t hold up in court”.   There are certainly cases of unenforceable contracts – contracts that are fraudulently induced or in contravention of public policy, for example – but a fully and clearly disclosed obligation in exchange for a mutual commitment of service is enforceable.

Read More

Forever 21 – WTF? SLAPP Suit? Trademark Dilution?

A blogger publishing under the name “WTForever21.com” recently got threatened with litigation for trademark infringement by the LA-based clothing retailer Forever 21.

WTForever21.com, a parody site published by Rachel Kane, had prominently disclaimed any affiliation or endorsement by Forever 21.  And as indicated, Kane’s purpose was (some would claim clearly) parody.   Kane was the proud recipient of a cease and desist letter from Forever 21 on April 22 (a copy of which can be found here), which alleged trademark and copyright infringement, unfair competition and trademark dilution.

Without testing the merits of her legal position and, according to several initial reports, not willing to expend the resources to do so, Kane announced that she would pull down her site by June 10th.  Kane then reversed course, and issued a statement last month stating “If the company continues to makes threats that have no basis in law, my attorneys are prepared to vigorously defend me and seek all available legal redress against Forever 21.”  The site is currently live.

Read More

Podcast #10: BitTorrent Copyright Infringement: Trouble for DMCA?

 

Today, I discuss BitTorrents, and a particular case in California challenging the copyright validity of what one service provider is doing.  BitTorrent has been in the (copyright) news lately – and not surprisingly – after the movie studios set their sites on bringing down yet the latest iteration of file-sharing technology.

Some of the issues I discuss are these:

  • What is the BitTorrent file sharing technology? And how is it different from Napster and its peer-to-peer progeny?
  • What are the 2 biggest distinctions between BitTorrent and peer-to-peer and, in particular, BitTorrent’s distributive approach to file-sharing?
  • Why is bitTorrent in the (copyright) news? I will particularly discuss a case in federal court in California, involving Columbia Pictures and other film studios who sued a bitTorrent company called isoHunt, together with its founder, Gary Fung.
  • What were the relevant legal issues in this case? Several important copyright arguments were made, but of most significance were 2 particular issues: inducement of copyright infringement, and the safe harbor for providers of “information location tools” under Section 512 of the Digital Millennium Copyright Act (the DMCA).
  • Why did Google get involved? I discuss how this case was an unusual instance where a court ruled that DMCA safe harbor protection was not available to a provider of “information location tools” who knew or should have known about potential or actual copyright infringement happening on its service.

Please click below for the podcast.

Read More

Startups: Capital Fundraising, Crowdsourcing and Securities Law

“With regulators considering easing fund-raising rules for start-ups …” a recent Wall Street Journal story began, “social-networking sites that link entrepreneurs to large pools of donors are gearing up for a boom.”

First, the background.  Federal and state securities laws govern the sales – including the solicitation of sales – of securities, affecting all efforts to raise capital for startups.  This includes any public efforts to raise money, and includes raising small or large amounts of money.  Generally, sales and solicitations of sales of stock require compliance with SEC and various state securities law, and more particularly the registration requirements of those laws.

Read More

BitTorrent Copyright Infringement: Trouble for DMCA?

BitTorrent has been in the (copyright) news lately – and not surprisingly – after the movie studios set their sites on bringing down yet the latest iteration of file-sharing technology.

2 great background sources on what BitTorrent is and how it works can be found here and here.  In short terms, BitTorrent is a file sharing technology, different from Napster and its peer-to-peer progeny in that it draws down pieces of large data files from multiple computers – rather than single computer to single computer peer-to-peer – based on a “community” structure of participating individual users.  The two biggest distinctions are (1) no single source for the compiled total file contributes more than a very small portion of the total file and (2) the distributive structure finesses the constant file-sharing problem of large data transfers demanding large broadband resources.

Why is bitTorrent in the (copyright) news?

BitTorrent is in the news not simply because Netflix’ CEO stated that “we’ve finally beaten bitTorrent.”  (“We”, by the way, presumably refers to Netflix’ full-file streaming capabilities.)

Read More

App and Software Ownership – Misidentification of Value

You go into a conversation from a lawyer’s perspective, expecting the discussion to be all about “ownership, ownership and ownership”.  You might expect app and other software developers to focus on nothing other than ownership.

Many times you’d be wrong.  One problem with ownership: Misidentification of value.

As Dan Berger of Social Tables pointed out, many technology companies aren’t strictly “technology” plays at all, and their value isn’t in their code, but rather in their execution or implementation.

I recently spoke with Eric Gunderson of Development Seed, whose open-source mapping technologies illustrate the same principle of technology execution: In the case of Development Seed’s MapBox, the great strength is speed.  Big data use means great mapping potential, but also means big processing problems.  Big processing problems reward innovative design execution.  If speed of mapping capability and management of data is a priority, ownership is less of a concern than execution and capabilities.  This is true even with proprietary products rather than services.  One might of course say, “Use our system, use our product,” but why should we use it?  The answer is that you do something better than everyone else out there using comparable – and perhaps even identical – technologies.  You wrap it up and package it – and execute it – better and faster.

The coding is valuable, but the greater value is in the execution of the coding and coupling of the organic coding with acquired knowledge from third-party applications and libraries, including (for example) Javascript libraries and other open-source software under GPL, MIT or other licenses.

The code itself may, or may not be open-source, but the value often is in the packaging, in the delivery, in the execution and the support.  In reality, I – the end user – cannot do much with the code itself beyond the immediate and narrow need of my specific use, and that will be without support, without updates, modifications, improvements and all the other benefits from open-source collaboration.  From the developer’s standpoint, the ability to develop products that continue to feed a renewable support business drives further continued product development.

Whether or not open-source, Social Tables, like MapBox, can benefit from copyright protection as a “collective work” or compilation, and that protection has meaningful value.  But as Dan Berger of Social Tables is quick to recognize, the copyright protection has less meaning to his potential market than the elegance of his design and the ease-of-use of his execution.   As technologist Piotr Steininger told me recently, referring to SproutCore, with increasing use of open-source, developers – and technology businesses – have realized that “the framework has potential but it can only benefit from open collaboration.  So in a sense the company gives up a product but in return gains a better product by sharing it.”

Read More

Podcast #9: App Development Legal Issues: Open Source, Copyright, API Terms of Use and More


Today, we will discuss the business and, particularly, the legal landscape faced by application (App) developers dealing with mobile platforms (iOS, Android and Blackberry being dominant), including dealing with application interfaces (APIs) when developing based on existing applications, and, of course, client relationships.

I am joined today by Liz Steininger, co-founder of Tapangi Consulting and project manager in the DC Government’s Office of the Chief Technology Officer.  Tapangi Consulting specializes in mobile and HTML5 application development as well as content management.  Liz is also an active member of the DC Tech community and you can find her on Twitter as @liz315.

Some of the issues we discuss today are these:

  • Protecting ideas in early stages of pitching to potential clients.
  • Application developer agreements and API Terms of Use (TOUs).
  • Platform question: As a developer, how do you think about development based on different platform (e.g. Android or iOS or Blackberry) or a specific API?
  • Copyright and “open source” issues, GPL, libraries, use of third-party code.
  • Ownership and Rights Issues
  • Privacy and uses of personal information (PI).

Please click here for the podcast.

Read More

Startup Companies: LLCs vs. S corps, Startup Capital vs. Outside Investors

Startup Structure Question: Why and when are LLCs preferable to S corps and vice versa?

Answer #1: If now or soon contemplating employee stock options and/or bringing in outside investors, then corporation status is probably desirable.  And … you can later convert from S to C.

Answer #2: Otherwise, LLCs are more desirable.

Pass-Through Entities

Both S corps and LLCs are pass-through entities, meaning that income will not be taxable at the company level, but only taxable to the owners.  This distinguishes these 2 entity types from traditional “C” corporations, which must pay taxes both at the company level and later when distributed to the shareholders.

Tax Advantage – S Corps

S corps have one – potential – further tax advantage over LLCs, in the ability to effectively reduce an owner’s self-employment taxes by paying the owner a salary versus dividends.  So, for example, assuming two companies, one an S corp, the other an LLC, both earn $100,000 in income.  The S corp could pay the owner $50,000 in salary, and the $50,000 balance would be deemed dividend income to the owners or owners, and not subject to self-employment taxes.  The salary portion is subject to self-employment taxes, while the dividend portion is not.

Using the same figures for an LLC, the full $100,000 would be deemed income to the owner subject to self-employment tax.

Read More

App Developer Legal Issues: API TOUs, Copyright and Trademark

Our Twitter chat last week with technology and entertainment lawyer Joy Butler highlighted legal issues with app development, including contract issues between app developers and clients, on one end, and intellectual property (IP) and API issues between the app and the intended development platform, on the other end.

Privacy issues become pressing later when the app goes public for end users, although the biggest privacy problems tend to arise when app publishers get tripped up by commitments made in their own end user license agreements (EULAs) or privacy policies, more so than from any violations of privacy laws.  More on privacy and the app/API problems in a separate blog post.

Immediate issues are copyright and trademark, both governed by federal laws, but also governed by API terms of use and similar application development agreements with hosting platforms.  Apple’s software developer kits (SDK) for the iPad and iPhone encompass similar purposes as part of broader packages of developer protocols for use of those APIs.

Read More