@cmuratori @Dravorek ...if specific code is required for interoperability (like a lock-out code), it isn't copyrightable.
-
-
Replying to @taradinoc
@taradinoc@Dravorek But that is talking about _using_ the API. Copyright _the API_ is about who can _implement_ that API.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@Dravorek And I don't see why some other part of the software would be copyrightable, but not that.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@Dravorek Like, I can copyright the "inside" of my program but not the "outside" of my program??1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@Dravorek And this is especially ridiculous considering that _UI_ is copyrightable! So the interface to a human is!1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@Dravorek But now the interface to another computer would not be? That makes absolutely zero sense.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Dravorek The human interface isn't an interop requirement, because users can learn another UI...1 reply 0 retweets 0 likes -
Replying to @taradinoc
@cmuratori@Dravorek ...but the API is an interop requirement, because you can't run (say) a POSIX app without implementing POSIX.1 reply 0 retweets 1 like -
Replying to @taradinoc
@taradinoc@Dravorek How can users "learn another UI"? You can't use Windows without learning Windows.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@Dravorek You can't use Photoshop with a "different UI" than Photoshop. The interface _is_ a critical element of the design.2 replies 0 retweets 2 likes
@taradinoc @Dravorek I really don't see how it is any less copyrightable than anything else.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.