First of all, you’re implying it runs latest Windows - but Windows 11 shipped a few years ago.

Second - not really a fair comparison. 18 years ago the iPhone didn’t even exist. And the oldest model (17 years old) had really weak hardware. 4GB of storage, 128MB of RAM, and the CPU was an order of magnitude slower than current spec CPUs (it was also 32 bit - and 64 bit ARM is a completely new architecture - similar to the failed Itanium).

Even if it was supported, it would be a horrible experience.

It just hasn’t hit that Twitter-level critical mass of users

Twitter used to be bigger than it is now and it also used to have less spam. So clearly size isn’t the problem.

The problem with twitter is Musk fired all the people who spent their day figuring out how to hide (or just delete) shitty content.

ChatGPT 4 was a little reluctant and asked for more details… when I refused to give any I got:

API requests are usually encrypted with SSL and protected against unauthorised use with something along the lines of a JWT: https://jwt.io/

Breaking through the SSL might be possible, if the developer doesn’t pin certificates, but you don’t know the secret used to generate the HMAC signature (blue section of that website), then you can’t simulate the API request. And the secret shouldn’t be sent over a network connection.

You could probably access the secret with enough work, but it would be a lot of work. You’d have to do it separately for each app. And the developer can change the secret whenever they want. The developer will change the secret at the slightest hint of anything like this being used with their app. And possibly also take additional steps to keep it from being accessed (e.g. store it in the Trusted Platform Module or equivalent on Android/iPhone). Even the CIA can’t access that - it’s mostly intended for payment processing and protecting data on a stolen phone, but there’s nothing stopping a weather app from using it to prevent unauthorised access to their API (weather data is very expensive, and often billed per API request).

Running the real app on a real phone though… basically nothing an app developer can do to stop that.

Arc has uBlock installed by default. So that’s not a differentiator between the two.

it’s just never used or enabled in the software by default

…and most people who own those devices have never heard of IPv6 and don’t know how to enable it. They just won’t be able to access your website. If Amazon dropped support for IPv4, there wouldn’t be anything i’d be able to do to deal with the fall out. I’m not going to send a technician to every single home of every customer I have. What I could (and would) do is move all my stuff off Amazon.

It was a few minutes after takeoff so they were still over a populated area. Hardly surprising that it was found… also if it landed on grass I’m not surprised it’s undamaged.

In short: The per message AES key is derived from the contacts public RSA key.

Erm that’s not how it actually works. Though in your defence, “in short” is pretty hard to achieve here.

The real headache though isn’t encrypting the messages. It’s making sure that only the intended recipient has the decryption key for your message. That’s where E2EE messaging gets complex and frankly Apple doesn’t do the best job.

It’s theoretically possible with iMessage, especially in a nation state level attack, for a compromised device to be one of the recipients your encrypted message is sent to. Wether “theoretically” is “actually in practice” happening is hard to judge, because nation state attacks are normally hidden by court mandated disclosure suppression orders.

The way Signal is architected, it wouldn’t be possible to comply with a court order like that. Unfortunately that means some Signal based messaging services will be forced to exit the UK since laws coming into effect next year will give them no other choice. It’ll be interesting to see if signal based services (like Google RCS) also walk or will they weaken their encryption in order to be able to comply.

The fact at least one nation state is passing laws that force “encrypted” messaging services to have the vulnerability that iMessage has is a pretty strong smoke signal that attacks like that are happening…

Apple’s current market valuation is $3 trillion.

AFAIK it is if you message someone else who uses Google’s RCS.

If you message someone with regular RCS - no encryption.

Oof that’s bad.

Although it should be noted that in well designed apps this should only be metadata. The push notification should just tell the phone that “content is available”, which will power up the CPU, launch the app in the background, download your actual message/etc, decrypt it, and finally put a notification on the lock screen.

Metadata is obviously useful to law enforcement, but unless the app is really poorly written they shouldn’t be getting your actual notification alerts. Those should be E2EE and therefore can’t be disclosed.

Unfortunately the notification system does allow messages to be sent without encryption. Perhaps they should remove that feature.

No… When you send a “blue bubble” photo on an iPhone the file size is around 1.5MB. When you send a “green bubble” photo I think they’re resized down to less than 300KB.

Any photo larger than that won’t be delivered by some carriers. Also while iMessage photos default to HEIF format - the same compression algorithm as Blue Ray videos - MMS uses JPEG which doesn’t have a target file size feature. All you have is the width/height in pixels and an arbitrary “quality” scale.

To guarantee your photo will never be over 300KB you need to set the width/height/quality to a number that will often be under 100KB… and that’s what Apple does.

Android has a size setting, and you’ll get a delivery failure error if you set it too high for the recipient’s carrier… a lot of carriers do support larger photos… But Apple doesn’t bother with that - they want it to “just work”. Which means 100KB for green bubble photos.

The reality is quality is always going to suffer - converting an image from HEIF to JPEG is a bad idea - it’ll never look anywhere near as good as the original no matter what resolution or quality the compression is set to.

Also… iPhones don’t even take ordinary photos… by default every “photo” is a short video. When you send those to another iPhone, they get the video. Green bubbles either get a still image or worse a 100KB five second video.

https://caniuse.com/?compare=firefox+120,and_ff+119&compareCats=all

If you scroll down past the browser version checkboxes (I’ve ticked the right ones for you) and list of features FireFox supports, you’ll find a very long list of web features that don’t work (or don’t work properly) in FireFox.

Some of them are pretty important features and there are sites that use them. Pretty sure Google Sheets uses the Filesystem stuff for example - it “works” in FireFox but not as well as in Chrome.

What this article is about is unless FireFox’s marketshare trend reverses, websites are going to stop including workarounds specifically for FireFox users. They’ll just let the site be broken in that browser.

No, what this means is sites might start adopting features like PassKeys - a major browser feature that works in every browser except FireFox and one where you just might not be able to access the service, at all, unless your browser has support.

(Passkeys are a replacement for passwords - essentially the idea is to take the technology commonly used for second factor authentication and use it as your “first factor” instead)

I find it hard to believe “not responding to an email” is consent. I mean they can write that in an email but there’s no way they could hold you to that in court.

I don’t see how government vs private makes any difference.

A baby isn’t capable of informed consent, so their DNA shouldn’t be collected unless it’s required for some medical reason (and then the sample should be immediately destroyed and no records kept).

If an adult, however, wants to voluntarily give these folks a DNA sample… well that’s their choice. I’m not surprised it ended poorly.

What would they diagnose?

Combustion Engine? Don’t have one. Transmission? Don’t have one. Emission Control System? Don’t have emissions. Spark Plugs? Nope. Fuel System? No. Exhaust? No. Alternator? No. Battery charger? you can see that on the dashboard. Starter motor? Nope. Battery Status? Also on the dashboard. Vehicle speed… on the dash. Engine idle… no. Air Flow Sensor? No air flow. Intake Manifold Pressure… no intake. Throttle position… only really relevant if you have a clutch or torque converter which EVs don’t have (you would notice, very quickly, if the throttle position detected pressing the pedal when you’re not pressing it in an EV…

That’s the list of standard ODB-II diagnostics. Some cars do more than that, but those are the ones they have to do. And none of them are relevant.

For me Twitter died shortly after Musk took over. It’s fitting that he renamed it - because it’s not the same place anymore.

Speaking as an Australian we’re also not super great at embracing the whole renewables thing

Erm… Australia has the more rooftop solar (32% of households) than any other country in the world and one state (south Australia) already has enough wind turbines to cover 100% of their overnight power consumption when the weather is favourable - with more being deployed (not to mention their grid is connected tot he rest of the nation, which is also investing in wind and hydro, so if it’s windy somewhere else that’s good enough).

We’re also moving pretty fast into hydrogen… in part because we have more power than we can use, so selling it (in the form of green hydrogen) makes sense.

We also have a dying but massive fossil fuel industry, and they spread a lot of FUD… but the reality is those power companies aren’t price competitive with renewable and never will be. They have no future and they’re just trying to delay the inevitable as long as possible.

Everyone thought that would happen with Huawei. What actually happened was a whole bunch of major countries banned Huawei imports and a lot of the ones that allowed them in are having second thoughts. Germany, for example, is in the early discussion phase to remove Huawei equipment (which is already deployed) from their cell network.