this post was submitted on 24 Oct 2025
75 points (95.2% liked)
Open Source
41681 readers
103 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why false? Especially if you have signed NDA. There are certain confidential documents you can only access as an employee at work, like the Airplay protocol. If you work for Apple, memorize the standard, then develop an app for Android which casts audio to Homepod, you're going to get sued.
That's true, the problem with the original statement is that it is too broadly scoped by "knowledge", implying that it is any and all knowledge. If I obtain the knowledge to write a singleton in object oriented programming while at work - even if the concept is applied to a work project, and later use the programming concept of a singleton in my own software, then they can't do shit.
A simpler example that shows that it's too broadly scoped is that if I get trained and certified to use a forklift for a job, and later start my own company and have to use a forklift, there is no precedent for my original employer to come after me for using a forklift in my business operation just because I learned how to use a forklift while I worked for them.
If the knowledge is proprietary or copyrighted or a trade secret and what I do uses any of that, or what I produce is a 1 to 1 product of that, then they can come after me.