# intellectual property Published articles for intellectual property. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Intelligence is yours. Let's keep it that way. DevFeed: [Intelligence is yours. Let's keep it that way.]() Original publisher: [Read original article]() Author: Paddy Srinivasan Published: 2026-09-14T21:11:13Z Content type: opinion Language: en Sources: [DigitalOcean]() Topics: [Open Source](), [Software](), [PostgreSQL](), [React](), [GitHub]() Tags: [agents](), [competition](), [github](), [infrastructure](), [intellectual-property](), [kubernetes](), [models](), [mysql](), [news](), [open-source](), [opencode](), [postgresql](), [react]() ### AI overview The article argues that founders should retain ownership and control of their companies' intelligence rather than depend on a single intelligence provider. It advocates an Open Intelligence movement built from open-source models, agents, harnesses, data technologies, and infrastructure, drawing comparisons with the adoption of Linux, PostgreSQL, MySQL, Kubernetes, and other open technologies. ### Source excerpt Intelligence was yours. A founder's intellectual property, business logic, differentiation, their intelligence, was once theirs alone. You built it, you owned it, and no tools/platform vendor stood between you and your customers. This is no longer clear. It is starting to look like it is "theirs." Intelligence can now be manufactured: the models, the agents and the harnesses that drive them, and the compute they run on. Providers who own all these can produce the application, and the differentiation, in every industry. That power runs the risk of becoming increasingly concentrated in a handful of companies. The race for the application layer is not about interfaces or go-to-market; it is a fight over who owns the intelligence layer itself. We have seen this before but we must act before its too late. Linux started behind Unix and Windows and now runs most of the world's servers. PostgreSQL and MySQL started behind Oracle and now underpin most new software. Kubernetes arrived after proprietary orchestrators and made them irrelevant. Each began less capable and won anyway: builders could see inside it, run it anywhere, and never had to ask permission. The same is happening now. Open weight models have repeatedly reached the frontier this past year. Open harnesses like OpenCode have grown to tens of trillions of tokens a day. Hermes reached more than 200,000 GitHub stars in five months, a milestone that took React a decade to achieve. Along with the near total adoption of open source data technologies, this collection of open technologies power an Open Intelligence movement. Open Intelligence restores the order. It returns to founders ownership of what makes their companies theirs. Founders should be free to build without tying their future to a single intelligence provider: their choice of agents, harnesses, data technologies, models, and infrastructure, with open source transparency, control, and competition keeping every layer honest. The stakes go beyond business. ## Trump Administration takes down Tetris clone after company warns it takes copyright violation 'very seriously' DevFeed: [Trump Administration takes down Tetris clone after company warns it takes copyright violation 'very seriously']() Original publisher: [Read original article]() Author: Bryant Francis Published: 2026-09-09T15:36:38Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [arcade](), [browser]() Tags: [browser](), [games](), [intellectual-property](), [trump]() ### AI overview The White House removed Build the Wall, a Tetris-like browser game, days after The Tetris Company said it was not involved and took copyright infringement seriously. The reason for the removal is unknown. ### Source excerpt Build The Wall has been knocked down. ## The Walt Disney Company and OpenAI reach landmark agreement to bring beloved characters to Sora DevFeed: [The Walt Disney Company and OpenAI reach landmark agreement to bring beloved characters to Sora]() Original publisher: [Read original article]() Published: 2025-12-11T00:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [OpenAI](), [API](), [ChatGPT](), [Generative AI](), [Responsibility & Safety](), [responsible-ai]() Tags: [ai](), [api](), [chatgpt](), [generative-ai](), [images](), [intellectual-property](), [openai](), [product](), [safety]() ### AI overview The Walt Disney Company and OpenAI announced a three-year licensing agreement allowing Sora to generate user-prompted short videos featuring more than 200 characters from Disney, Marvel, Pixar, and Star Wars. Disney will also use OpenAI APIs and ChatGPT, invest $1 billion in OpenAI, and collaborate on responsible AI that protects users and creators. ### Source excerpt Disney and OpenAI have reached an agreement to bring more than 200 Disney, Marvel, Pixar and Star Wars characters to Sora for fan-inspired short videos. The agreement emphasizes responsible AI in entertainment and includes Disney's company-wide use of ChatGPT Enterprise and the OpenAI API. ## Image replacement in Canva designs using reverse image search DevFeed: [Image replacement in Canva designs using reverse image search]() Original publisher: [Read original article]() Author: Sam Jacobs Published: 2025-01-28T09:05:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [Machine learning](), [Image](), [Requirements](), [Database](), [recommendation systems]() Tags: [backend](), [database](), [design](), [embedding](), [frontend](), [image](), [intellectual-property](), [machine-learning](), [models](), [requirements](), [search]() ### AI overview Canva describes comparing image embedding models to build a scalable reverse image search system for replacing images in designs. The proposed system considers subject, color, tone, positioning, background, emotion, and aspect ratio while supporting IP-safe search across more than 150 million images. ### Source excerpt Qualitative comparison of image embedding models to power a scalable similar-image replacement system for Canva designs. ## Intellectual Property Guideline DevFeed: [Intellectual Property Guideline]() Original publisher: [Read original article]() Published: 2020-02-23T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Windows](), [Development](), [Microsoft](), [free software]() Tags: [copyright](), [developers](), [free](), [intellectual-property](), [legal](), [microsoft](), [open-source](), [os](), [policy](), [react](), [reactos](), [win32](), [winapi](), [windows]() ### AI overview The ReactOS Project's intellectual property guideline explains copyright, patent, trademark, and related legal issues relevant to project development. It provides definitions and policy guidance for developers and potential contributors, while stating that it is not legal advice. ### Source excerpt Preface The ReactOS™ Project is an international group of developers whose goal is to create a work-alike version of the Microsoft Windows operating system. In light of recent activity in the free software world relating to copyright and patent concerns, the administrators of the ReactOS Project feel that a general guideline would be helpful for developers and potential contributors. For questions regarding this guideline, please e-mail Colin Finck. Please note that none of this should be construed as legal advice, as any sort of warranty regarding the project's products, or anything else save a statement of policy on the part of the project. ## Job negotiation for programmers: the basic principles DevFeed: [Job negotiation for programmers: the basic principles]() Original publisher: [Read original article]() Author: Itamar Turner-Trauring Published: 2019-11-27T00:00:00Z Content type: opinion Language: en Sources: [Itamar Turner-Trauring]() Topics: [Development](), [Open Source]() Tags: [article](), [career](), [intellectual-property](), [job](), [legal](), [open-source]() ### AI overview An article about negotiating salary, benefits, and work arrangements when starting a programming job. It presents four principles--viewing employment as a negotiated relationship, gathering knowledge, negotiating from a position of strength, and using appropriate tactics--and illustrates them with a story involving salary and intellectual-property terms affecting open-source work. ### Source excerpt You need to negotiate at a new job: for your salary, or benefits, or my personal favorite, a shorter workweek. You're not sure what to do, or how to approach it, or what to say when the company says "how much do you want?" or "here's our offer--what do you say?" Here's the thing: that final conversation about salary might be the most nerve-wracking part, but the negotiation process starts much much earlier. Which means you can enter that final conversation having positioned yourself for success--and feeling less stressed about it too. The way you can do that is following certain basic principles, which I'll be covering in this article. I'm going to be focusing on salary negotiation as an example, but the same principles will apply when negotiating for a shorter workweek. In particular, I'll be talking about: An example from early in my career when I negotiated very very badly. The right way to negotiate, based on four principles: Employment is a negotiated relationship. Knowledge is power. Negotiate from a position of strength. Use the right tactics. The wrong way to negotiate Before moving on to the principles of negotiation, let me share a story of how I negotiated badly. During my first real job search I interviewed at a company in New York City that was building a financial trading platform. They were pretty excited about some specific technologies I'd learned while working on Twisted, an open source networking framework. They offered me a job, I accepted, and my job search was over. But then they sent me their intellectual property agreement, and I actually read legal documents; you should read them too. The agreement would have given the company ownership over any open source work I did, including work on Twisted. I wanted to ensure I could keep doing open source development, especially given that was their reason for hiring me in the first place. I asked for an exemption covering Twisted, they wouldn't agree, and so we went back and forth trying to reach an agr ## History and effective use of Vim DevFeed: [History and effective use of Vim]() Original publisher: [Read original article]() Published: 2019-07-19T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [Vim](), [Unix](), [systems](), [Command-line interface]() Tags: [article](), [blog](), [effective](), [history](), [intellectual-property](), [legacy](), [plugins](), [posix](), [systems](), [vim]() ### AI overview An article on Vim's historical development and effective use. It traces the editor's lineage from QED through ed, ex, and vi, and encourages readers to study Vim's core functionality, use plugins thoughtfully, and rely less on pre-packaged vimrc files. ### Source excerpt 2019-07-19 This article is based on historical research and on simply reading the Vim user manual cover to cover. Hopefully these notes will help you (re?)discover core functionality of the editor, so you can abandon pre-packaged vimrc files and use plugins more thoughtfully. To go beyond the topics in this blog post, I'd recommend getting a paper copy of the manual and a good pocket reference. ## Keeping Track of Open Source Software Licenses DevFeed: [Keeping Track of Open Source Software Licenses]() Original publisher: [Read original article]() Author: taylor@goteleport.com (Taylor Wakefield) Published: 2016-10-18T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Open Source](), [foss](), [Software](), [open-source-security]() Tags: [acquisition](), [advice](), [customer](), [foss](), [intellectual-property](), [open-source](), [open-source-software](), [saas](), [signing](), [startup]() ### AI overview This article explains why startups and enterprise software teams should track open-source software licenses early. It describes the legal and business risks that can arise during acquisitions or major customer deals, recommends reviewing licenses and watching for copyleft terms, and suggests scanning code with a script and consulting a lawyer. ### Source excerpt It might be mundane and boring but keeping track of your FOSS license usage can save you from a big headache at the least opportune time. ## Intellectual Property: Ideology vs Practicality DevFeed: [Intellectual Property: Ideology vs Practicality]() Original publisher: [Read original article]() Published: 2013-12-14T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [GNU General Public License](), [free software](), [Code](), [Software]() Tags: [apache](), [cost](), [free](), [free-software](), [intellectual-property](), [open-source](), [os](), [react](), [reactos](), [reuse](), [source](), [win32](), [winapi]() ### AI overview The article argues that the GPL's ideological goal of preserving users' rights to modify and extend software also creates obligations for developers who reuse GPL-licensed code. It contends that the resulting source-disclosure burden can make developing a separate solution or choosing a more permissive license such as Apache or BSD more practical. ### Source excerpt The thing that people need to keep in mind when discussing the GPL is that it was created to achieve an ideological and political goal, namely that users of software should have the right to modify and extend the software as they see fit. To achieve this goal, the GPL seeks to ensure that the source code is always available and that reusing the source code in question comes without any restrictions save for what the GPL itself imposes in order to ensure this " ## Intellectual Property: Fundamentals DevFeed: [Intellectual Property: Fundamentals]() Original publisher: [Read original article]() Published: 2013-11-15T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [GNU General Public License](), [free software](), [Open Source](), [ReactOS]() Tags: [free](), [free-software](), [intellectual-property](), [open-source](), [opinion](), [os](), [react](), [reactos](), [win32](), [winapi]() ### AI overview The article explains common misunderstandings about intellectual property, focusing on how the GNU General Public License applies to free software and open-source projects. It discusses source-code access, GPLv2 and GPLv3 provisions, relicensing, and when software constitutes a derived work, with ReactOS as context. ### Source excerpt Intellectual property is something way too many people like to talk about without actually understanding the nuances of the laws supporting them. While I could easily go on and on about these misconceptions, I'll focus primarily on those that relate to free software and open source, of which there are plenty. Some of the more prominent ones include incorrectly claiming what is and what is not a GNU Public License (GPL) violation and the notion that companies should "