It's perfectly safe to plug stuff into any socket that is compatible.
I've told this story before on these forums, but it's good enough to tell again in reference to this comment.
Almost 30 years ago now, I worked as a computer lab staffer at the local university in a variety of computer labs scattered around the campus. The main lab had hundreds of desktop computers in it and used an automated sign up system by the front desk to assign available computers when users left. It worked a lot like the waiting list at the DMV ... sign in and wait for your ID to pop up on the screen in the waiting area telling you where to go. Computers would get assigned to specific users waiting in line and the IDs would show up on the screen of each computer out in the lab.
Some people didn't like to "participate" in that system and would try to "jump the line" by just wandering out into the lab, find a computer with no one sitting in front of it, sit down and shove their disk into the drive ... thinking that would give them control over the computer or something (
"non sequitur, your facts are uncoordinated").
So when the lab was busy and there was a waiting list for open computers, there would always be some student looking panicked coming to the lab staff desk saying that they couldn't get their disk (always a zip disk) out of the computer.
We staffers would just look at each other knowingly and silently acknowledge which one of us wanted to go out onto the floor to "solve" this problem.
I would open up a drawer that held my "usefully bent paper clip" tool that could be inserted into the pinhole of the zip drive to force it to manually eject a zip disk ... and dutifully followed the distressed student out onto the floor to find the computer in question. Invariably, I would arrive to find a screen blinking the ID of a different user than the owner of the zip disk "trapped" in the drive. Since the zip disks were the first to work on a software eject system for hardware, you needed to be logged into the computer to command the ejection from the desktop ... which wasn't available while the computer was locked and awaiting a different user to log into it in order to get to the desktop.
Seeing the situation (that I already knew would be the case before arriving), I would simply ask the person who fetched me if the ID blinking on the computer screen was their ID (it wasn't, it never was), proving that they hadn't paid ANY attention before plopping down and shoving their disk into the machine. I would then use my "usefully bent paper clip" tool in the pinhole of the zip drive to force the manual eject. I pulled the disk out of the drive before SLOWLY handing over the disk to the student while saying in my best "authoritative lecturer of idiots" voice:
"In computing, as in real life ...
make SURE that you are WELCOME ...
before inserting something."
Because the lab was busy whenever this happened, ALL of the computer stations nearby to this little drama would be occupied ... and I pitched my voice deliberately to carry ... which ensured that EVERYONE nearby heard what I said while handing over the zip disk to the student who thought they could "jump the line" and not wait to get a computer while the lab was busy. Invariably, I heard stifled laughs, guffaws and even the occasional giggle from guys and girls nearby, because these were college kids ... and the Life Lesson™ I was teaching obviously applied to more than just zip disks getting shoved into computers without so much as "by your leave" arrogance.
It took a while after the start of each semester, but the number of "zip disk trapped in computers" incidents definitely dropped off during the course of each semester. I'd like to think that a little gentle (but not entirely subtle) public shaming of people with more entitlement than sense helped to tamp down the "enthusiasm" that some students had for jumping the queue for the waiting list in that computer lab.
![Cool :cool: :cool:](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)