This particular cable is more intended for connecting to a stereo + charger, so those would be close together.
I'm mainly using it with one of these stereos, but it would be good in a car too:
If you want to connect headphones+charge, the dongle style adapters may be a better fit:
Though you could use a usb or aux extension on either of the shorter ends of the first cable I showed if you wanted too.
Yup, that's what it's for.
For months, masked individuals with no police agency markings have been leaping out of unmarked vehicles that have no licence plates, refusing to identify themselves in any way, then kidnapping people off of the streets; and not one of them has faced any true resistance.
What the fucked has happened to America. Is "hey don't do that", really all you've got???
Admittedly I was very stuck in the 'I hate phones not having Aux' camp because I preferred wired headphones for the longest time.
I was given some fairly poor wireless headphones and was pleasantly surprised by those, so I bought a good quality set myself. Now I've gotten so used to being untethered from my phone while listening to music, or podcasts, etc that I don't think I'd go back to wired headphones while mobile.
That just leaves stereo systems, portable speakers, vehicles and the like. All of those, instead of carrying around or leaving an aux-aux cable, swap that for a usb c to aux cable.
Or even one of these:
As OP said, more space for battery. It's also one less opening to waterproof. It took me a good long while, but I've come around to agree a headphone jack just isn't worth the extra space it takes up. It's not worthless, but there's better ways to use the space.
I bought a y-shaped cable for exactly this the other day.
Usb c on one end, aux and usb a on the other end.
I know it's much easier said than done; but I just wish the world as a whole would put more effort into diplomatic relations instead of just bombing eachother into 'compliance'.
We don't all have to like each other and work together; but if we could stop burning each others houses down, that'd be great.
Hopefully that's not an unpopular opinion...
As nice as that would be, the unfortunate reality is that's just not a realistic solution. You can't put the cat back in the bag, so to speak.
The technology is already known; If everyone agreed to disarm, each party would just be even more worried about nations potentially ignoring that agreement and their now lack of defense against it.
The biggest reason I'm not all that concerned about Iran having nukes is the fact that so many nations are already nuclear armed. The use of nuclear weapons is so hated globally that they can only really be used in defence. If any individual nation chose to use their nukes offensively, the inevitable response from everyone else would mean the decision is suicide.
If Iran acquired nukes, then used them on say, Israel; America at the very least would turn Iran into a nuclear wasteland. I'm sure there are other nations that would join in, even if just on principle.
https://en.m.wikipedia.org/wiki/Iran_nuclear_deal_framework
As far as the NonProliferation Treaty goes, they are threatening to leave it, but haven't actually yet.
The rest of the world says the same about America.
'Terrorist' isn't a way of life, it's the perspective of those against you.
In the last couple of weeks, I've started getting this error ~1/5 times when I try to open one of my own locally hosted services.
I've never used ECH, and have always explicitly restricted nginx to TLS1.2 which doesn't support it. Why am I suddenly getting this, why is it randomly erroring, then working just fine again 2min later, and how can I prevent it altogether? Is anyone else experiencing this?
I'm primarily noticing it with Ombi. I'm also mainly using Chrome Android for this. But, checking just now; DuckDuckGo loads the page just fine everytime, and Firefox is flat out refusing to load it at all.
Firefox refuses to show the cert it claims is invalid, and 'accept and continue' just re-loads this error page. Chrome will show the cert; and it's the correct, valid cert from LE.
There's 20+ services going through the same nginx proxy, all using the same wildcard cert and identical ssl configurations; but Ombi is the only one suddenly giving me this issue regularly.
The vast majority of my services are accessed via lan/vpn; I don't need or want ECH, though I'd like to keep a basic https setup at least.
Solution: replace local A/AAAA records with a CNAME record pointing to a local only domain with its own local A/AAAA records. See below comments for clarification.
I've started noticing this icon more and more: usually on comments with no downvotes. What's it mean?
What makes it a bad cable?
This is the only audio cable I've needed/wanted for a phone in around 5 years. (note, the picture is just an example of the style, not the exact brand I happened to purchase)
For years I refused to even try wireless headphones/earbuds because I was stuck on hurdles like battery life, Bluetooth reliability/range, or the possibility of losing one; but once I actually gave some a try, particularly a good quality set, I honestly couldn't be happier and have come to prefer them over wired headphones quite significantly (specifically for mobile devices). It was genuinely a mental hurdle more than anything. Once I got off my high horse, stopped hating wireless headphones mostly on principle, and realized they actually fit my needs perfectly; I've found the only place I want/need both aux and power connections is at a non-bluetooth stereo.
So now, when I want to charge while playing music at a stereo; this cable is perfect, providing power to the phone and audio to the stereo without some bulky dongle hanging off of your usb c port wearing it out. Since switching to wireless headphones, and buying one of these cables, I have had no desire for anything else.