"30 years ago this week…something called the World Wide Web launched into the public domain…#CERN owned Berners-Lee's invention and…had the option to license [it] out…for profit. But Berners-Lee believed that keeping the web as open as possible would help it grow…[He] eventually convinced CERN to release the World Wide Web into the #PublicDomain without any #patents or fees."
#AI#ComputerVision#Surveillance#Patents#IP: "A rapidly growing number of voices argue that AI research, and computer vision in particular, is powering mass surveillance. Yet the direct path from computer vision research to surveillance has remained obscured and difficult to assess. Here, we reveal the Surveillance AI pipeline by analyzing three decades of computer vision research papers and downstream patents, more than 40,000 documents. We find the large majority of annotated computer vision papers and patents self-report their technology enables extracting data about humans. Moreover, the majority of these technologies specifically enable extracting data about human bodies and body parts. We present both quantitative and rich qualitative analysis illuminating these practices of human data extraction. Studying the roots of this pipeline, we find that institutions that prolifically produce computer vision research, namely elite universities and "big tech" corporations, are subsequently cited in thousands of surveillance patents. Further, we find consistent evidence against the narrative that only these few rogue entities are contributing to surveillance. Rather, we expose the fieldwide norm that when an institution, nation, or subfield authors computer vision papers with downstream patents, the majority of these papers are used in surveillance patents. In total, we find the number of papers with downstream surveillance patents increased more than five-fold between the 1990s and the 2010s, with computer vision research now having been used in more than 11,000 surveillance patents. Finally, in addition to the high levels of surveillance we find documented in computer vision papers and patents, we unearth pervasive patterns of documents using language that obfuscates the extent of surveillance. Our analysis reveals the pipeline by which computer vision research has powered the ongoing expansion of surveillance."
By the way, nearly all the specimen images we've been creating in the UT collection have been placed in the public domain, and are free to take and use for anything:
A must have, if you want to browse the web without ads, trackers, malware and more. There are other browsers you could use, but with #firefox, you can install add-ons to help you mitigate all the tracking and ads. You can even install desktop only add-ons now, and supporting a engine which is not #chromium (controlled by Google) like every other major browser.
There are multiple forks available on the F-droid if you don't want to use plain firefox. This works on desktop too, I recommend #LibreWolf.
My favorite way of blocking ads, you have control over which domain the app can connect. It works like a VPN, but it does not make any outgoing connection. The bad thing is, if you want to use an actual #VPN, you can't have both at the same time and you need to disable your custom DNS.
I recommend to enable in settings > advanced options > block system apps, and individual domains too. When you open the app for the first time, it asks you if you want to block essential request for the apps to work, I recommend to enable this if you don't want apps breaking.
You android vendor may be killing the app, for this reason is necessary to add the app in the list of apps not be optimized by the system. If this issue keeps happening follow the guide from dontkillmyapp.com (advanced)
A DNS works like a translator, computers are good with numbers, but we are not good at memorizing long numbers. Computers communicate with each other using the Internet Protocol (IP), which are pure numbers. For example, your instance #IP is 104.26.8.209 but is easier to us just type lemmy.world.
A DNS is like a table where it has a relationship between keys pointing lemmy.world to 104.26.8.209, so your computer knows where is the computer is trying to connect.
Let's imagine an app is trying to connect to "https://ads-from.company.com", if you are using a DNS which blocks known domain ads it will redirect that request to "0.0.0.0" which is like sending it to a black hole. There are multiple DNS available, which different purposes, for ads, malware, porn, gambling, etc.
Have in mind that these are not full bulletproof protections, one may work better than the other, and can break from time to time. With popular services with ads, like social media, you could use alternative front-ends to their official client or website.
Here is a list of alternative front-ends and an add-on to automatically redirect to them, you have to use it with a browser and you can add as a shortcut to the home screen, better if it works like a #PWAhttps://libredirect.github.io
There's a website (https://songswave.com) that might have stolen your #music and plan to make money off it without your permission!
I've just found my album "Enjoy the Ride" on there being sold for €4.26.
If your music is on there, you can send them an email at the contacts they've listed on https://songswave.com/pages/view/id/2/ requesting they remove it.
My old Mastodon server is closing, so I'll do a new #Introduction here! I'm a #LawProf at Stanford, researching & teaching about #Patents, #IP, and #Innovation Law. I have a free patent law casebook at patentcasebook.org, and I'm currently working on projects related to university tech transfer, equity in inventorship, patent disclosure doctrine, and medical device incentives. I'm still figuring out the post-Twitter world and am also on #Bluesky.
#AI#GenerativeAI#LLMs#AITraining#GeneratedImages#Copyright#IP: "A lot of early AI research was done in an academic setting; the law specifically mentions teaching, scholarship, and research as examples of fair use. As a result, the machine-learning community has traditionally taken a relaxed attitude toward copyright. Early training sets frequently included copyrighted material.
As academic researchers took jobs in the burgeoning commercial AI sector, many assumed they would continue to enjoy wide latitude to train on copyrighted material. Some feel blindsided by copyright holders’ demands for cash.
“We all learn for free,” Daniel Jeffries wrote in his tweet summing up the view of many in the AI community. “We learn from the world around us and so do machines.”
The argument seems to be that if it’s legal for a human being to learn from one copyrighted book, it must also be legal for a large language model to learn from a million copyrighted books—even if the training process requires making copies of the books.
As MP3.com and Texaco learned, this isn't always true. A use that’s fair at a small scale can be unfair when it’s scaled up and commercialized.
But AI advocates like Jeffries are right that sometimes it is true. There are cases where courts have held that bulk technological uses of copyrighted works are fair use. The most important example is almost certainly the Google Books case."
I've been looking in to cases assigned to Judge Seeger following a few orders refusing TRO's. Of course all the cases I am interested in are Schedule A cases and there are patterns in these cases.
For now though, what a gem, I have just found. This judge is right up there with my current fav.
How many Schedule A cases..? Have those cases made any dent in the amount of counterfeiting? If the answer is no, what is the purpose of
another game of Whack−A−Mole?
#TikToks Daten-Dilemma: Zwischen Innovation u. Überwachung..
.. Datenstaubsauger biblischen Ausmaßes“, der nicht nur auf Basis von Geräte- und Netzwerkinformationen, sondern auch über #SIM-Karten u #IP-Adressen Standortdaten seiner Nutzer sammelt.
The name of late Colombian drug lord Pablo Escobar cannot be registered as an EU trade mark, the European Court of Justice ruled on Wednesday, after his brother tried to lay a claim.The court upheld the decision of the EU's intellectual property office (EUIPO) that refused a trade mark application by Escobar Inc. in 2022....
Just a brief reminder that every #AWS VM/container/etc you give a public #IPv4#IP address to now costs you $3.65/month more than in 2023. AWS charges per IP-address per-hour.
Okay I thought I'd share this recent post here on the #Fediverse. To give it some context, it's an answer to a common question, often a misunderstanding (even by many knowledgeable folks) as to just how we got here.
There's a lot of apples and oranges here. And everyone had a lot of good points made, but your question is simple, and has a very simple answer. I'll endeavor to address that directly, but do need to tend to some of what has already been said.
Scroll down to the tl;dr for the succinct answer of your question
Ethernet, ARCNET, Token Ring, Thick net (RG-59), Thin net (RG-58 A/U), and UTP (Cat 3, Cat 5, and Cat 6 unshielded twisted pair, Etc.) really have zero bearing on your question insofar as IP is concerned. All of these specifications relate to the definition of technologies that, although are indeed addressed in the OSI model which is indeed very much in use to this day,but are outside the scope of Internet Protocol. I'll come back to this in a minute.
It's quite common to say TCP/IP, but really, it's just IP. For example, we have TCP ports and we have UDP ports in firewalling. i.e., TCP is Transmission Control Protocol and handles the delivery of data in the form of packets. IP handles the routing itself so those messages can arrive to and from the end points. Uniform Data Protocol is another delivery system that does not guarantee arrival but operates on a best effort basis, while TCP is much chattier as it guarantees delivery and retransmission of missed packets - UDP is pretty efficient but in the case of say, a phone call, a packet here and there won't be missed by the human ear.
That's a very simplistic high level-view that will only stand up to the most basic of scrutiny, but this isn't a class on internetworking ;) If you just want to be able to understand conceptually, my definition will suffice.
Networking (LAN) topologies like Token Ring, ARCNET, and Ethernet aren't anywhere in the IP stack, but figure prominently in the OSI stack. I'm not going to go into the details of how these work, or the physical connection methods used like Vampire Taps, Thin net, or twisted pair with RJ-45 terminators, but their relationship will become obvious in a moment.
The OSI model unfolds like so, remember this little mnemonic to keep it straight so you always know:
> People Don't Need To See Paula Abdul
Okay, touched on already, but not really treated, is the description of that little memory aid.
> Physical, Data Link, Network, Transport, Session, Presentation, and Application layers (From bottom to top).
The physical and Data Link layers cover things like the cabling methods described above,and you're probably familiar with MAC Addresses (medium access control) on NICs (network interface controller). These correlate to the first two layers of the OSI stack, namely, the Physical (obvious - you can touch it), and the Data Link layer - how each host's NIC and switches on each LAN segment talk to each other and decide which packets are designated for whom (People Don't).
In software engineering, we're concerned mostly with the Session, Presentation, and Application layers (See Paula Abdul). Detailed explanation of these top three layers is outside the scope of this discussion.
The Beauty of the OSI model is that each layer on one host (or program) talks to exclusively with the same layer of the program or hardware on the other host it is communicating with - or so it believes it is, because, as should be obvious, is has to pass its information down the stack to the next layer below itself, and then when it arrives at the other host, it passes that information back up the stack until it reaches the very top (Abdul) of the stack - the application.
Not all communication involves all of the stacks. At the LAN (Local Area Network) level, we're mostly concerned with the Physical and Data Link layers - we're just trying to get some packet that we aren't concerned about the contents of from one box to another. But that packet probably includes information that goes all the way up the stack.
For instance, NIC #1 has the MAC: 00:b0:d0:63:c2:26 and NIC #2 has a MAC of 00:00:5e:c0:53:af. There's communication between these two NICs over the Ethernet on this LAN segment. One says I have a packet for 00:00:5e:c0:53:af and then two answers and says, "Hey that's me!" Nobody else has that address on the LAN, so they don't answer and stop listening for the payload.
Now for Internet Protocol (IP) and TCP/UDP (Transmission Control Protocol and User Datagram Protocol):
IP corresponds to Layer 3 (Need) - the Network Layer of the **OSI Model.
TCP and UDP correspond to Layer 4 (To) - the Transport Layer of the OSI model.
That covers the entire OSI model and how TCP/IP correspond to it - almost. You're not getting off that easy today.
There's actually a bit of conflation and overlapping there. Just like in real life, it's never that cut and dried. For that, we have the following excellent explanation and drill down thanks to Julia Evans:
Layer 2 (Don't) corresponds to Ethernet.
Layer 3 (Need) corresponds to IP.
Layer 4 (To) corresponds to TCP or UDP (or ICMP etc)
Layer 7 (Abdul) corresponds to whatever is inside the TCP or UDP packet (for example a DNS query)
You may wish to give her page a gander for just a bit more of a deeper dive.
Now let's talk about what might be a bit of a misconception on the part of some, or at least, a bit of a foggy conflation between that of the specification of the OSI model and a Company called Bolt Beranek & Newman (BBN) a government contractor tasked with developing the IP stack networking code.
The TCP/IP you know and depend upon today wasn't written by them, and to suggest that it was the OSI model that was scrapped instead of BBN's product is a bit of a misunderstanding. As you can see from above, the OSI model is very much alive and well, and factors into your everyday life, encompasses software development and communications, device manufacturing and engineering, as well as routing and delivery of information.
This next part is rather opinionated, and the way that many of us choose to remember our history of UNIX, the ARPANET, the NSFnet, and the Internet:
The IP stack you know and use everyday was fathered by Bill Joy, who arrived at UC Berkeley in (IIRC) 1974), created vi because ed just wasn't cutting it when he wanted a full screen editor to write Berkeley UNIX (BSD), including TCP/IP, and co-founded Sun Microsystems (SunOS / Solaris):
> Bill Joy just didn’t feel like this (the BBN code) was as efficient as he could do if he did it himself. And so Joy just rewrote it. Here the stuff was delivered to him, he said, “That’s a bunch of junk,” and he redid it. There was no debate at all. He just unilaterally redid it.
Because UNIX was hitherto an AT&T product, and because government contracting has always been rife with interminable vacillating and pontificating, BBN never actually managed to produce code for the the IP stack that could really be relied upon. In short, it kinda sucked. Bad.
So! You've decided to scroll down and skip all of the other stuff to get the straight dope on the answer to your question. Here it is:
> What were the major things that caused TCP/IP to become the internet standard protocol?
The ARPANET (and where I worked, what was to become specifically the MILNET portion of that) had a mandate to replace NCP (Network Control Protocol) with IP (Internet Protocol). We did a dry run and literally over two thirds of the Internet (ARPANET) at that time disappeared, because people are lazy, software has bugs, you name it. There were lots of reasons. But that only lasted the better part of a day for the most part.
At that time the ARPANET really only consisted of Universities, big Defense contractors and U.S. Military facilities. Now, if you'll do a bit of digging around, you'll discover that there was really no such thing as NCP - that is, for the most part, what the film industry refers to as a retcon, meaning that we, as an industry, retroactively went back and came up with a way to explain away replacing a protocol that didn't really exist - a backstory, if you will. Sure, there was NCP, it was mostly a kludge of heterogeneous management and communications programs that varied from system to system, site to site, with several commonalities and inconsistencies that were hobbled together with bailing twine, coat hangers, and duct tape (for lack of a better metaphor).
So we really, really, needed something as uniform and ubiquitous as the promise that Internet Protocol would deliver. Because Bill Joy and others had done so much work at UC Berkeley, we actually had 4.1BSD (4.1a) to work with on our DEC machinery. As a junior member of my division, in both age and experience, I was given the task of, let's say throwing the switch on some of our machines, so to speak, when we cut over from the NCP spaghetti and henceforth embraced TCP/IP no matter what, on Flag Day - 01 January 1983.
So you see,the adoption of Internet Protocol was not a de facto occurrence - it was de jure, a government mandate to occur at a specific time on a specific day.
It literally had nothing to do with popularity or some kind of organic adoption, the erroneously described, so-called demise of the OSI model, or any physical network topology.
DARPA said 01 January 1983 and that's it, and that was it - Flag Day.
Sure, it took a few days for several facilities to come up (anyone not running IP was summarily and unceremoniously cut off from the ARPANET).
And one also needs to consider that it wasn't every machine - we only had some machines that were Internet hosts. We still had a lot of mainframes and mini computers, etc., that were interconnected within our facilities in a hodgepodge or some other fashion. Nowadays we have a tendency to be somewhat incredulous if every device doesn't directly connect over IP to the Internet in some way. That wasn't the case back then - you passed traffic internally, sometimes by unmounting tapes from one machine and mounting them on another.
There was a lot of hand wringing, stress, boatloads of frustration, and concern by people over keeping their jobs all over the world. But that's why and when it happened. Six months later in the UNIX portions of networks we had much greater stability with the release of 4.2BSD, but it wouldn't really be until a few years later Net2 was released that things settled down with the virtually flawless networking stability that we enjoy today.
I own the #copyright for the lectures I give to college students, but for some reason the #FBI has not yet contacted me with offers to prosecute anyone recording all or portions of my lectures without my written permission. I'm seriously considering putting an FBI warning at the beginning of every lecture. I think it might start good conversations about whose interests the cops choose to protect in American society.
What were the major things that caused TCP/IP to become the internet standard protocol?
This had to be addressed, with so many people piling on and choosing that the OSI model was replaced by TCP/IP because it worked better and increased in popularity
DARPA Logo Defense Advanced Projects Administration
Okay I thought I'd share this recent post here on the #Fediverse. To give it some context, it's an answer to a common question, often a misunderstanding (even by many knowledgeable folks) as to just how we got here.
There's a lot of apples and oranges here. And everyone had a lot of good points made, but your question is simple, and has a very simple answer. I'll endeavor to address that directly, but do need to tend to some of what has already been said.
Scroll down to the tl;dr for the succinct answer of your question
Ethernet, ARCNET, Token Ring, Thick net (RG-59), Thin net (RG-58 A/U), and UTP (Cat 3, Cat 5, and Cat 6 unshielded twisted pair, Etc.) really have zero bearing on your question insofar as IP is concerned. All of these specifications relate to the definition of technologies that, although are indeed addressed in the OSI model which is indeed very much in use to this day,but are outside the scope of Internet Protocol. I'll come back to this in a minute.
It's quite common to say TCP/IP, but really, it's just IP. For example, we have TCP ports and we have UDP ports in firewalling. i.e., TCP is Transmission Control Protocol and handles the delivery of data in the form of packets. IP handles the routing itself so those messages can arrive to and from the end points. Uniform Data Protocol is another delivery system that does not guarantee arrival but operates on a best effort basis, while TCP is much chattier as it guarantees delivery and retransmission of missed packets - UDP is pretty efficient but in the case of say, a phone call, a packet here and there won't be missed by the human ear.
That's a very simplistic high level-view that will only stand up to the most basic of scrutiny, but this isn't a class on internetworking ;) If you just want to be able to understand conceptually, my definition will suffice.
Networking (LAN) topologies like Token Ring, ARCNET, and Ethernet aren't anywhere in the IP stack, but figure prominently in the OSI stack. I'm not going to go into the details of how these work, or the physical connection methods used like Vampire Taps, Thin net, or twisted pair with RJ-45 terminators, but their relationship will become obvious in a moment.
The OSI model unfolds like so, remember this little mnemonic to keep it straight so you always know:
> People Don't Need To See Paula Abdul
Okay, touched on already, but not really treated, is the description of that little memory aid.
> Physical, Data Link, Network, Transport, Session, Presentation, and Application layers (From bottom to top).
The physical and Data Link layers cover things like the cabling methods described above,and you're probably familiar with MAC Addresses (medium access control) on NICs (network interface controller). These correlate to the first two layers of the OSI stack, namely, the Physical (obvious - you can touch it), and the Data Link layer - how each host's NIC and switches on each LAN segment talk to each other and decide which packets are designated for whom (People Don't).
In software engineering, we're concerned mostly with the Session, Presentation, and Application layers (See Paula Abdul). Detailed explanation of these top three layers is outside the scope of this discussion.
The Beauty of the OSI model is that each layer on one host (or program) talks to exclusively with the same layer of the program or hardware on the other host it is communicating with - or so it believes it is, because, as should be obvious, is has to pass its information down the stack to the next layer below itself, and then when it arrives at the other host, it passes that information back up the stack until it reaches the very top (Abdul) of the stack - the application.
Not all communication involves all of the stacks. At the LAN (Local Area Network) level, we're mostly concerned with the Physical and Data Link layers - we're just trying to get some packet that we aren't concerned about the contents of from one box to another. But that packet probably includes information that goes all the way up the stack.
For instance, NIC #1 has the MAC: 00:b0:d0:63:c2:26 and NIC #2 has a MAC of 00:00:5e:c0:53:af. There's communication between these two NICs over the Ethernet on this LAN segment. One says I have a packet for 00:00:5e:c0:53:af and then two answers and says, "Hey that's me!" Nobody else has that address on the LAN, so they don't answer and stop listening for the payload.
Now for Internet Protocol (IP) and TCP/UDP (Transmission Control Protocol and User Datagram Protocol):
IP corresponds to Layer 3 (Need) - the Network Layer of the **OSI Model.
TCP and UDP correspond to Layer 4 (To) - the Transport Layer of the OSI model.
That covers the entire OSI model and how TCP/IP correspond to it - almost. You're not getting off that easy today.
There's actually a bit of conflation and overlapping there. Just like in real life, it's never that cut and dried. For that, we have the following excellent explanation and drill down thanks to Julia Evans:
Layer 2 (Don't) corresponds to Ethernet.
Layer 3 (Need) corresponds to IP.
Layer 4 (To) corresponds to TCP or UDP (or ICMP etc)
Layer 7 (Abdul) corresponds to whatever is inside the TCP or UDP packet (for example a DNS query)
You may wish to give her page a gander for just a bit more of a deeper dive.
Now let's talk about what might be a bit of a misconception on the part of some, or at least, a bit of a foggy conflation between that of the specification of the OSI model and a Company called Bolt Beranek & Newman (BBN) a government contractor tasked with developing the IP stack networking code.
The TCP/IP you know and depend upon today wasn't written by them, and to suggest that it was the OSI model that was scrapped instead of BBN's product is a bit of a misunderstanding. As you can see from above, the OSI model is very much alive and well, and factors into your everyday life, encompasses software development and communications, device manufacturing and engineering, as well as routing and delivery of information.
This next part is rather opinionated, and the way that many of us choose to remember our history of UNIX, the ARPANET, the NSFnet, and the Internet:
The IP stack you know and use everyday was fathered by Bill Joy, who arrived at UC Berkeley in (IIRC) 1974), created vi because ed just wasn't cutting it when he wanted a full screen editor to write Berkeley UNIX (BSD), including TCP/IP, and co-founded Sun Microsystems (SunOS / Solaris):
> Bill Joy just didn’t feel like this (the BBN code) was as efficient as he could do if he did it himself. And so Joy just rewrote it. Here the stuff was delivered to him, he said, “That’s a bunch of junk,” and he redid it. There was no debate at all. He just unilaterally redid it.
Because UNIX was hitherto an AT&T product, and because government contracting has always been rife with interminable vacillating and pontificating, BBN never actually managed to produce code for the the IP stack that could really be relied upon. In short, it kinda sucked. Bad.
So! You've decided to scroll down and skip all of the other stuff to get the straight dope on the answer to your question. Here it is:
> What were the major things that caused TCP/IP to become the internet standard protocol?
The ARPANET (and where I worked, what was to become specifically the MILNET portion of that) had a mandate to replace NCP (Network Control Protocol) with IP (Internet Protocol). We did a dry run and literally over two thirds of the Internet (ARPANET) at that time disappeared, because people are lazy, software has bugs, you name it. There were lots of reasons. But that only lasted the better part of a day for the most part.
At that time the ARPANET really only consisted of Universities, big Defense contractors and U.S. Military facilities. Now, if you'll do a bit of digging around, you'll discover that there was really no such thing as NCP - that is, for the most part, what the film industry refers to as a retcon, meaning that we, as an industry, retroactively went back and came up with a way to explain away replacing a protocol that didn't really exist - a backstory, if you will. Sure, there was NCP, it was mostly a kludge of heterogeneous management and communications programs that varied from system to system, site to site, with several commonalities and inconsistencies that were hobbled together with bailing twine, coat hangers, and duct tape (for lack of a better metaphor).
So we really, really, needed something as uniform and ubiquitous as the promise that Internet Protocol would deliver. Because Bill Joy and others had done so much work at UC Berkeley, we actually had 4.1BSD (4.1a) to work with on our DEC machinery. As a junior member of my division, in both age and experience, I was given the task of, let's say throwing the switch on some of our machines, so to speak, when we cut over from the NCP spaghetti and henceforth embraced TCP/IP no matter what, on Flag Day - 01 January 1983.
So you see,the adoption of Internet Protocol was not a de facto occurrence - it was de jure, a government mandate to occur at a specific time on a specific day.
It literally had nothing to do with popularity or some kind of organic adoption, the erroneously described, so-called demise of the OSI model, or any physical network topology.
DARPA said 01 January 1983 and that's it, and that was it - Flag Day.
Sure, it took a few days for several facilities to come up (anyone not running IP was summarily and unceremoniously cut off from the ARPANET).
And one also needs to consider that it wasn't every machine - we only had some machines that were Internet hosts. We still had a lot of mainframes and mini computers, etc., that were interconnected within our facilities in a hodgepodge or some other fashion. Nowadays we have a tendency to be somewhat incredulous if every device doesn't directly connect over IP to the Internet in some way. That wasn't the case back then - you passed traffic internally, sometimes by unmounting tapes from one machine and mounting them on another.
There was a lot of hand wringing, stress, boatloads of frustration, and concern by people over keeping their jobs all over the world. But that's why and when it happened. Six months later in the UNIX portions of networks we had much greater stability with the release of 4.2BSD, but it wouldn't really be until a few years later Net2 was released that things settled down with the virtually flawless networking stability that we enjoy today.
#IP#Copyright#PublicDomain: "2024 has been off to a busy start with the long-anticipated arrival of Mickey Mouse and Steamboat Willie in the public domain. Creators have released new games and stories, including a comic that picks up where Steamboat Willie ends. Comedian John Oliver has been showcasing a “Steamboat Mickey” mascot. CBS Sunday Morning even aired a Mickey-inspired celebration of the public domain featuring an interview with CSPD Director Jennifer Jenkins.
This is just the beginning of Mickey’s new life in the public domain. Next year, over a dozen Mickey Mouse cartoons from 1929 will join Steamboat Willie in the public domain. These cartoons continue Disney’s innovative experiments with synchronized sound and include The Karnival Kid, the first film in which Mickey speaks intelligible words. His first words? “Hot dogs! Hot dogs!”
Like other Disney works, The Karnival Kid builds upon prior public domain material. To attract an audience for Minnie Mouse’s “shimmy dancer” performance, the Karnival barker riffs on a 19th Century tune known as “the snake charmer song.” This melody has also been featured in numerous other Disney cartoons and may be familiar to readers from the scores of additional reuses in works ranging from The Simpsons to Ke$ha’s Take It Off." https://web.law.duke.edu/cspd/newsletter/April2024/
Never enter any information that would qualify as a trade secret into an AI chat bot, regardless of what the terms of service of the chat bot provides.
We Need Smart Intellectual Property Laws for Artificial Intelligence (www.scientificamerican.com)
“One-size-fits-all” regulation will sideline medical and research benefits promised by the advent of artificial intelligence
YouTube can't stop showing me AI deepfake ads (www.spacebar.news)
European court rules drug lord Pablo Escabar's name can not be trademarked (www.reuters.com)
The name of late Colombian drug lord Pablo Escobar cannot be registered as an EU trade mark, the European Court of Justice ruled on Wednesday, after his brother tried to lay a claim.The court upheld the decision of the EU's intellectual property office (EUIPO) that refused a trade mark application by Escobar Inc. in 2022....