A combination of desktop-grade mandatory access controls mediated by launch services through TCC, built-in restrictions with the quartz compositor and the ubiquitous use of hardened runtime means the expectation on macOS is that an application generally does not have access to everything. No cross-application memory access, logs with private information scrubbed even locally, keylogging restricted to a small subset of apps you choose to have the capability, screen scraping limited to the app itself and the global menu bar along the top, etc. In Golden Gate, they're even blocking access to application data directories per-app, starting off with a blacklist approach with the later goal in future versions to make everything fully isolated using whitelisting.

Different OS, different security model to the UNIX tradition the moment GUI apps are used.

If it is x86 hardware then slap on ChromeOS Flex until 2034 and by then someone will have recreated it as just Chromium atop the equivalent of matchbox window manager but using Wayland instead

Try running a Loki Games installer and watch it fall over because head and tail are no longer compatible with themselves without using random, obscure environment variables to try and restore the original default behaviour. That is just the tip of the iceberg for backwards incompatible changes internal to "old" utilities which do in fact still receive regular changes.

My only complaint with Canonical's approach was pushing half and half into an Ubuntu LTS, which was clearly a terrible idea to anyone watching, but now they're stuck with it, I'm sure they'll learn from it.

Idiots will be idiots but thankfully not all countries have judgmental idiots trying to punish other idiots. But hey, that is what brainwashing about so-called freedoms you have in principle which you do not actually have in practice does to people.

If over here we imprisoned people for admitting they did drugs while pregnant, then people would just outright refuse medical treatment when they need it due to a lack of trust. Instead, if people admit to it, we get them free help and support so they can deliver a healthy child, and if later on in the term it turns out that thereâ(TM)s damage done, then a medically-assisted termination of the pregnancy can still occur if two doctors assess the evidence and sign off on it.

WPA Enterprise has this covered. The certificate check occurs during the connection, prior to authentication. Procedurally generated credentials could be printed on to your tickets in advance, designed to work both at airports and during flights.

Considering that just about every website which facilitates any kind of public facing user-to-user communication is what politicians call social media (which would also technically include Slashdot, decades old random PHPBB forums and sites like Newgrounds) I think all this blaming of social media instead of naming and shaming the specific commercially operated websites responsible for the tragedies, needs to end.

Otherwise, if we are going to blame anything and everything, the argument might as well be microplastics.

The law says children cannot purchase or be sold cigarettes, which is not the same thing as saying children cannot smoke. Likewise, with this law, it is perfectly legal for children to use social media, it is just illegal for the companies to target children and have to provide a means of proving that they do something to try and stop children using their services.

Teenagers still experiment with cigarettes, light drugs and start drinking somewhere around the age of 15 like they should and politicians can keep on making a big fuss out of things which simply are not problems to distract from actual real world problems. Like social media.

IMHO, Mozilla should start competing with the rest of the ad blocking browsers, and commit to fully integrating adblock-rust explicitly for that purpose. They should tell the truth they've always been too scared to tell (for fear of losing income) which is that enshittification is unstoppable without going nuclear on the rampant commercialisation of the open Internet, and that people are going to stump up the necessary funds to enable Mozilla to deal with it.

The threat of using DRM to counteract such a move is a complete paper tiger, since it would ruin all the smart device integrations (especially on TVs and older games consoles) which can't be easily updated in the process, as well as break essential enterprise security scanning techniques to the point where it would relegate all but the most banal of entertainment-related services to obscurity.

It's time for management to be brave and grow a pair.

Action cams are what people typically go with for that use case. Better quality video and audio with better runtimes for a fraction of the price, enabling folks to add them to helmets, handlebars/chest and more for multiple angles. These Meta glasses are actually worse than Google Glass and have greater cloud dependence. Maybe the only saving grace will be longer support than Google provided.

Britain has a historical defence pact with Ukraine, which unlike Russia, it is actually honouring. An inconvenient truth is that without the very defence pact formed as part of the Budapest Memorandum (which resulted in Ukraine relinquishing its nuclear arsenal and the UK being duty bound to provide aid) every major Russian city would have probably been (very legitimately) nuked in self-defence by now. Thankfully, it's just a bunch of drones sabotaging Russian national infrastructure, and it could all end tomorrow if Russia was willing to actually honour what it too had originally promised instead of trying to play a failed game of conquest.

Likewise, it was Russia's leadership which created the "Ukrainian Nazism problem" that it's complaining about by spearheading a violent uprising in the mid-2010s which turned fringe groups into recognised militia (e.g. Azov) who are now perceived as heroes of the people seen as acting in the best interests of the Ukrainian majority. It isn't just Ukrainians but also Jews, Muslims, Greeks, Crimeans, disgruntled Russians and Belarusians who all ended up uniting under the same banner that was originally considered to be Nazi-adjacent. The irony is that both the problem and the resulting "denazification" all happened in the blink of an eye, and now those so-called "Neo-Nazis" will be forever remembered for protecting Ukraine from an invasion by an evil Russian dictator called Vladimir Putin.

If I was Vlad, I'd be pulling out and claiming the military operation to be a success before integrating all those volunteer North Koreans into Russian society.

At this point, webmasters should accept very short lived client TLS keys signed by neutral third parties who take care of the proof of humanity on their behalf. Since security requirements for most websites are low, even places like libraries could issue them if needs be, and webmasters could choose how many or how few authorities they trust. The standard could be used creatively such that Valid To field is used purely as an limiter for initiating trust for the first time, providing convenience to users while making it easy to ban any bots which somehow slip through by banning a trusted entity or even a whole country if they are found to be on the fiddle.

Every URL is sent to Microsoft with Optional/Full telemetry enabled when you don't use InPrivate Browsing and that includes your GDID. You can observe this in the Diagnostic Data Viewer, and as it's full URLs (not just domains) Microsoft knows every little search query too. Even if you scale back to security-only telemetry, Microsoft still receives full URLs (not just domains) not via diagnostic telemetry data but instead via Microsoft SmartScreen, and AFAIK that still includes a unique device identifier, with the legitimate reasoning being for their Intelligence Graph to identify malicious endpoints between sessions.

Likewise, all the telemetry related to the running of programs is queued and uploaded with Optional/Full even if no crashes occur, as well as diagnostic logs relating to software installs/updates, so Microsoft can see what devices have been running, when and for how long. All of that can be correlated once law enforcement is involved because they can subpoena third-parties to nab access logs which allow for the use of statistical analysis to reidentify the user.

All of this is legit, but the problem is that Microsoft abused our trust by violating their own Privacy Policy, since they claim not to identify people, but clearly did in this case.

Microsoft tied the device ID to the person, then looked up the telemetry associated with the device to work out how the device was used, then sent all that data to the feds, despite their privacy policy stating that device identifiers will not be used to identify people.

We must not forget this. They lied.

Publish a book, a song, a movie, or even a play, and you are legally required to make copies available to national libraries for archival in the countries you opted to publish them in, along with copies of accompanying scripts, manifests and documentation. Members of the public then have a right to access those copies for education and research purposes. DRM be damned there as well, as the library is freely allowed to use the analog loophole to break it when it gets in the way of legitimate archival.

Software developers and video game publishers should not get any special treatment here, and if scripts and manifests are not off limits, then source code and technical documentation should not be either. Thereâ(TM)s zero reason members of the public should be prevented from independently studying how any published work functions, irrespective of whether they have even purchased a private copy of their own. That is how it has always worked before and that is how it should continue to work in the modern day.

Might also be worth noting that no other guardrail for anything allows alleged harmful output to occur before trying to claw it back like they are Alex Jones lawyer.