I googled a bit and it seems you might be able to run low speed Ethernet over untwisted wires if they are not long.
They aren't exactly in widespread usage yet, though.
--
(ETA: And apparently there are even 100 and 1000 Mbps variants now too [0] -- with lower maximum distances, of course.)
[0]: https://en.m.wikipedia.org/wiki/Ethernet_over_twisted_pair#S...
[1] https://www.gl1800riders.com/attachments/federal-law-motorcy...
Now, as a motorcyclist who has been hit head-on more than once by drivers who swore "I didn't even see him!" -- with the last crash leaving me with multiple broken bones and an inability to walk for several months -- you better believe I now have both a pulsating headlamp and a nice set of loud ass pipes (they're even called "Street Cannons")! on my bike.
I've also lost a non-zero number of friends due to folks who swore they didn't see them.
It's now been eight years since I've gotten hit... so I really am sorry if my headlight or pipes bother you as I pass by but, well, I have loved ones I'd like to see again so I hope you'll forgive me.
--
Anyways, there's a toll-free number on your card. Call it and explain the situation to them. They'll likely re-issue your card and call it a day, unless the specific transactions trigger some sort of "red flag" (although, if that were the case, the fraud department would likely have noticed before you did and already took action).
There are certain types of questions that aren't really appropriate for an "Ask HN". This is one of them.
Still, I'd rather use GitLab ober GitHub.
> This bug was patched by Microsoft in June 2022 ...
> The occupants of a vehicle that is the subject of a police stop may record the encounter if the occupants are not interfering with lawful police actions.
--
On a side note, I encourage everyone to carefully read the actual bill.
There's a lot of intelligent people here on HN but it seems that many of those commenting can't quite comprehend plain English (not as well as I would have expected, at least).
--
These used to be big, expensive, standalone devices (I'd occasionally use one in a previous job). Nowadays, there are portable, handheld units specifically for identifying where a break has occurred and the same, basic functionality is often even built into the gear used at either end of connections (e.g., even the "enterprise" switches -- from Brocade and Cisco -- that I use at home).
---
[0]: https://en.wikipedia.org/wiki/Optical_time-domain_reflectome...
https://onezero.medium.com/my-one-phrase-resum%C3%A9-98776ef...
(Try an incognito window if Medium blocks you.)
That article has a few inaccuracies too, but as the events were over 30 years ago, this can be forgiven.
Read Alan's article and then come back for this followup.
Alan mentioned the "gizmos". He actually originally called them "waldos", named after these:
https://en.wikipedia.org/wiki/Remote_manipulator
I couldn't make sense of that name, so I suggested "gizmo", which seemed fun and more descriptive. That name stuck - for a while. Microsoft later renamed them to "controls". How boring!
I also developed the "gizmo interface", which Microsoft renamed to VBX. (They were really not into fun names at the time.)
It has sometimes been said that Bill Gates was the one who insisted that VB have an extension interface like this. The truth is more subtle. We had the gizmo interface all along. It was obvious that we would need it for our own gizmos, and that we should allow other developers to build their own gizmos.
Apparently, the Microsoft team that turned Ruby+Basic into VB was going to keep the gizmo interface private and only let Microsoft developers use it, at least at first to save time on the schedule. Bill quite rightly saw the power of exposing the interface to outside developers and decided to make it part of the product - just as we had planned all along.
And I built the "event arrows" that Alan mentioned. He originally called an event a "flimsy" (a British term for "lightweight paper used especially for multiple copies"). I couldn't make sense of that name either, so we kicked it around and settled on "event".
This left a problem of what to name the act of sending an event from one gizmo to another. I was familiar with the term "trigger" from SQL, but that didn't seem quite right, and we were into fun names. But I couldn't think of one!
At the time, when I got frustrated with a coding or naming problem, I had a habit of firing rubber bands at my IBM Monochrome Display to shake up my thinking. (Don't try this with a modern flat panel.)
That didn't give me any ideas.
So I decided to fire up a doobie and see if that would help.
As I flicked my lighter and looked at the fire, it all came together:
Fire a rubber band. Fire up a doobie. Fire an event!
AMA, and I will see if I can remember...
> Just WTF were those Microsoft guys smoking when they designed this shit?
<g>
Highly recommend the ICX 6610 in particular. The only other Brocade (Ethernet) switches I've personally managed are the "access layer" FCX switches (in an old position 10+ years ago).