ianbetteridge

About

Username
ianbetteridge
Joined
Visits
2
Last Active
Roles
member
Points
269
Badges
0
Posts
11
  • Microsoft blames European Commission for global CrowdStrike catastrophe

    ssfe11 said:
    The EC once again shows how clueless grandstanding politicians can cause havoc. The EC taking lefts and rights from Apple, Meta and now Microsoft. The only way to beat these ignorant folks is to band together and that’s what looks like is exactly happening. Nice!
    It seems odd to come to AppleInsider and find people  repeating Microsoft PR talking points, but here we are. Strange times indeed.

    To understand what’s going on, you need to go back to the 1990s, when Microsoft was unconstrained by any thoughts of antitrust or monopoly law, and spent quite a lot of time and effort decimating the third party software industry. It had a massive advantage over the likes of Novell, Lotus, WordPerfect and the rest because it could create and use APIs that were private, while making second-rate APIs public.

    It could also deliberately break third party software with Windows updates. While “DOS isn’t done till Lotus won’t run” was a myth, the truth was that if an update broke a competitor’s app, that was good news for Microsoft. And they definitely weren't going to go the extra mile to fix something that affected 1-2-3 if it didn't affect Excel.

    Eventually this got the attention of regulators including the DoJ and EC (European Commission). It’s EXACTLY the kind of behaviour that you are absolutely not allowed to do under antitrust law. When you have a dominant position – and no one doubted, or doubts, MS has this in operating systems – you just can’t get away with it.

    In 2004, the EC case was pretty-much over. Microsoft agreed it had been bad, and offered to publish its APIs, and apply a level playing field – which meant its own applications weren’t allowed to use special “Microsoft-only” APIs. Anything Microsoft’s apps could do HAD to be available to others.

    Did Microsoft stick to this agreement like a good little boy? Of course it didn’t.

    So in 2006, a group of software companies complained it to the EC, through a coalition called the European Committee for Interoperable Standards (ECIS). Despite the name, ECIS was largely US companies, including IBM, Adobe, Oracle, and McAfee. By 2007, the EC had investigated and found that yes, Microsoft had failed to live up to its agreements. It got fined, and the EC asked Microsoft to propose new, specific remedies to make sure it didn’t happen again.

    In 2009, those agreements were signed. And in them, there is a specific part – section C (42) – which deals with security software. Now you might get the impression from what Microsoft is saying now, something that’s being repeated by people who can’t be bothered to look up agreements AKA “pundits”, that this mandates kernel level access for third parties.

    Reader, it does nothing of the sort. It simply states that Microsoft has to make available – and document – whatever APIs its own software uses. The company could do what Apple has done and move access for EDR (endpoint detection and response) software out of the kernel. It has chosen not to do this.

    So no, Microsoft hasn’t been “ordered” by the big bad EU to do anything other than stop its old tricks of giving its own applications advantages that no third party could ever have. It hasn’t moved EDR out of the kernel because, at least back in 2009, the Windows kernel was a mess and developing equivalent APIs was going to be expensive.

    Do I blame Microsoft? Not really: Windows is what it is, and keeping it secure is hard. I don’t believe its the platform vendors fault if, using legitimate methods, a third party messes up a patch. That’s entirely down to Crowdstrike.

    But is it the EC’s fault? Absolutely not. Stopping companies like Microsoft from destroying competition not by better products but by leveraging ownership of a platform is exactly the thing antitrust bodies are set up to do. It’s what the DoJ did to IBM in 1956, and without that judgement we would all be still using mainframes from Big Blue.

    avon b7hagarmuthuk_vanalingamihatescreennamesnubuskiltedgreen9secondkox2ronnwilliamlondonstompy
  • Google's RCS messaging is coming to iPhone in 2024

    gatorguy said:

    Following years of pressure from Google for Apple to adopt the presently flawed RCS system within iMessage, Apple has committed to doing so during 2024.

    Android does not have a true equivalent alternative to Apple's iMessage...
    Ummm, yes they do. The equally secure and private Google Messages. Unfortunately, the initial implementation of RCS on the iPhone will not be end-to-end encrypted. Still showing a bit of stubbornness I suppose.

    Keeping the blue bubble/green bubble distinction would be an advantage for Android users using the E2EE Google Messages (Apple users too if they understand what it means) since it will designate the conversation as potentially insecure. But I've been seeing claims the bubbles are going away. I don't know how true that is, as I thought blue and green indicated the level of encryption. 
    It's not stubbornness, it's simply that the extensions which Google has made to RCS which support E2E encryption are proprietary and only available via the closed-source Google Messages app, and with service providers that run their customers' messages on Google (proprietary) Jibe platform. 

    The reality is that Google end-to-end messaging system, while built on RCS, is as proprietary and closed as iMessage. That's why non-Google versions of Android such as Graphene which ship the stock (open source) messages app don't have support for encrypted RCS. If you want that on Android, you and all your friends have to be using Google's closed-off software. 
    gregoriusmauxiowilliamlondonAlex1Nroundaboutnowjas99Anilu_777watto_cobrastrongy
  • Apple's iPhone parts pairing is making the company billions

    Draco said:
    Many of the iPhone's sub-systems like the displays and cameras are highly complex devices that would be very difficult for a third party to duplicate while preserving the quality Apple's customers expect. Some may also contain calibration data that resides in the phone memory and hence that's why you can't swap modules from phone to phone and expect them to work properly. 

    Knock-off batteries and power adapters can also pose a safety hazard to users and I would highly recommend only purchasing the Apple versions of these even if they cost a few bucks more. 

    You're missing the point. This isn't about knock-off parts: it's about parts which come from otherwise dead devices. If a screen is cracked, all the other parts of the phone are likely good and can be reused. But Apple deliberate uses parts locking to prevent anyone from harvesting parts from iPhones (and iPads), in order to increase its own profits.
    muthuk_vanalingamwilliamlondon
  • Apple's iPhone parts pairing is making the company billions

    badmonk said:
    I have news for the NY Times and all the right to repair advocates in this forum but new model cars often require specialized diagnostic software and expertise available only to dealers so cars are not a great example as quoted in their article.

    But you know in these times when everyone is starring at their phones, no one can think of anything but Apple and iPhones and App stores.

    I have used iPhones only since 2007 and have never had a device fail on me (with the exception of a single battery expansion which was repaired).

    The bottom line is that if not abused they are incredibly durable due to their build quality.  My friends that use other devices have produced much more e-waste.

    In all cases I have handed my used iPhones down to family members or resold them on eBay after two to three years of use.

    Cars need that specialist diagnostic software and expertise not because it's actually mechanically required, but because manufacturers deliberately build in VIN-locking and will go after anyone who tries to circumvent it with a DMCA 1201 suit.
    williamlondonjony0
  • Apple's iPhone parts pairing is making the company billions

    Xed said:
    I have no problem with this. I want my Apple product to work exactly as it was designed, and a sub-par part could compromise a lot. For example, what if a camera or Touch ID sensor pays a part in causing the security protections to fail? Data could be lost/stolen and who get the blame? Me as a consumer because I cheaped out? The scond-rate part manufacturer? Or Apple? (hint... one of those three has a lot more money than the other two, and the lawyers know it.) 
    I'm a little torn on this matter. Recently I had a cracked display on an iPhone. I was given the option for a "real" display or a bad Chinese knockoff that will look OK but is really only good for a trade-in or less than ethical resale to another user, I do like knowing that authenticate components are being used.

    The choice isn't between a real part and a bad Chinese knock-off: the choice is between a new Apple supplied part and a perfectly functional part culled from an iPhone which was otherwise dead.

    But Apple says you can't have that perfectly good part and stops you using it through parts-locking. That's not protecting you, it's because Apple doesn't make any money from it. And so that perfectly functioning screen goes into the endless mountain of e-waste, the one which Apple claims to care so much about in its fancy videos.
    muthuk_vanalingamwilliamlondon