> I don't think MB makes them like they used to anymore.
You guessed correctly. The 1980's W124 was one of those cars that would keep going and going. Mechanically great, with a galvanized chassis and bodywork that made it also pretty rust resistant.
The 1993 version of the W124, supposed to be an "improved" remodeled version of the original car, was a worst car in every aspect. It rusted, the plastics were cheaper, etc.
The follow-up, the W210, is the model that cost MB dearly. Through cost-cutting and greed, they lost a huge chunk of the taxi market. The car itself was also an absolute rust-bucket piece of cr*p, the interior was also worst, with the whole woes compounded by crappy electronics.
MB as a brand hasn't really recovered from that. The engineering excellency, attention to detail, and engineering pride that made those W123/W124 almost unkillable is lost, and won't be found again.
It is implicit, in the same way that in a modern car you expect electric windows and air-conditioning (yes, back in the day, those were premium extras)
> port her cellphone number to a VOIP provider that does support receiving SMS from shortcodes over wifi
That's generally a great solution – unless the company she's dealing with is one of those that don't send SMS-OTP codes to VoIP numbers for seCuRiTy reasons, or demand that the number is somehow "registered in her name" (which many smaller carriers apparently don't do).
I really wish that were illegal. A phone number is a phone number.
> she turned on wifi calling on her phone. now she could receive SMS messages from friends and family, but 2FA codes still weren't coming through.
Interesting, I was under the impression that SMS over IMS was implemented transparently to external senders. But given what a hack the entire protocol is, I'm not really surprised.
Completely different beasts. One is P2P, the other is A2P
> port her cellphone number to a VOIP provider that does support receiving SMS from shortcodes over wifi
That's generally a great solution – unless the company she's dealing with is one of those that don't send SMS-OTP codes to VoIP numbers for seCuRiTy reasons, or demand that the number is somehow "registered in her name" (which many smaller carriers apparently don't do).
I really wish that were illegal. A phone number is a phone number.
> she turned on wifi calling on her phone. now she could receive SMS messages from friends and family, but 2FA codes still weren't coming through.
Interesting, I was under the impression that SMS over IMS was implemented transparently to external senders. But given what a hack the entire protocol is, I'm not really surprised.
European speaking. For completeness:
Financial directive PSD2[1] allows to use an SMS as a 2FA only because there is an KYC already done for that number (anon SIM are no longer allowed in the EU)
Also note that the 2FA is not the OTP code you receive. This code is just a proxy for probing "something you have", with the "something" being the phone number which, again, is linked to a physical person/company.
I have commented this several times, but as of today, SMS is the only 2FA method that can be easily deployed at scale (all demographics, all locations, compatible with all mobile devices)
[1] https://en.wikipedia.org/wiki/Payment_Services_Directive
- Is the big bang theory the scientific consensus on the origin and evolution of the universe ?
- What are the alternatives ?
The classic "fun" TSR use-case was to make an app that installs an interrupt vector to decode mouse hardware "events" directly from the RS232 port before exiting via 0x21h, so that DOS screen would display a pointless "native" mouse cursor that doesn't do anything :)
When I say mouse cursor, I mean an ASCII block character with the blink bit on.
I implemented a password protected access to A:
Last I checked, you can't run mail servers on typical cloud providers (like Azure, Oracle) and cheap VPSs are almost guaranteed to have "dirty IPs" (used for spam and thus blacklisted).
* No affiliation