That is odd. It’s not what I see:
That is odd. It’s not what I see:
A very poor Lemmy article headline. The linked article says “alleged” and clearly there were multiple factors involved.
Very few people will be able to use it: only iPhone 15 Pro and higher. Most users won’t have a capable phone until their next upgrade in 1-3 years.
Hopefully by then they’ve caught up to where Anthropic, OpenAI, and Meta are today.
I have used the Excel/Word/Keynote formats with iWork and it’s okay. MS Office is the de-facto standard format and recognized by Google Docs, OpenOffice, and of course MS Office.
I don’t think it’s a truly open format like ODF, but you can be sure it’ll be recognized everywhere for a long time.
I use the stock keyboard. It’s terrible, but so are the alternatives, plus there are privacy concerns.
One nice thing I will say is that the word suggestions are actually good in the latest iOS since they are now based on an LLM.
Bit other than thst typing is so inaccurate taht O have to go back and corewxt nearly every word.
Swipe typing showing hello very much either. (Swipe typing doesn’t help very much either.)
deleted by creator
It’s a PR issue not a legal one.
This draft spec was eventually published as RFC 9562. Compared to the previous spec it adds versions 6, 7, and 8, plus best practices guidance.
Basically, there are a bunch of UUID alternatives that arose to fix the problem that UUIDs are bad for use as database keys in large tables (here’s the perspective of MySQL experts Percona). A bunch of these alternatives are actually linked from the RFC, which I haven’t seen done before. Version 7, in particular, is meant to address this use case.
You live in a city, but most of the store chain’s customers live in the suburbs where gas is a major expense and fuel perks are a big incentive to shop at a particular store.
The store isn’t trying to promote fossil fuels. They only care about customer loyalty. Besides (they might rationalize), their customers have to buy gas somewhere so why not from us?
The one that’s not shown: Standalone Passwords app
True, it’s a private (not local) IP. It could easily have connected to a remote system, as their proof-of-concept did.
This code execs cmd.exe
and pipes output to and from a hardcoded IP. That’s pretty weird. What’s running on that IP? How does the extension know something is there?
It looks like VS Code has no review — human or automated — or enforced entitlement system that would have stopped this or at least had someone verify it was legit.
Their findings included an extension that opens an obvious reverse shell.
The Fisker Ocean has solar panels on its roof. It can add 4 or 5 miles a day if fully exposed to the sun.
Not enough to matter. It’s a gimmick.
If you don’t have an EV, you may think that EV owners are worried about range, and they’d welcome any increase. I have not found this to be true.
It’s more like having a car that starts every day with a full tank. You’re never going to burn through that in a single day. Pretty soon you don’t care about range, efficiency, or pay much attention to the battery meter. It only matters if you’re on a road trip, which for me is a couple times a year.
I would not want to give up a nice full-roof sunroof for a few extra miles a day.
Thanks. That’s good to know.
Use this shortcut from Ricky Mondello, the lead for Apple’s password development team.
I get the feeling they wanted to do a Passwords app for some time but needed to get, probably executive-level, buy-in to get it done.
Apple will get bad PR about this: they are “Sherlocking” password managers. 1Password will write a blog post about how this is actually good for them because now password management is mainstream; 3rd party password managers will decide to focus more on the enterprise market; Microsoft will come out with a competing password manager that re-uses the name of a previous product and is bundled with Edge, etc. How it always goes.
Any USB-C headphones work.
This report is from 2016. It’s mainly of historical interest.
All Mac laptops do. And my work Windows PC looks like it has one but the company was too cheap to pay for it, so all it has is a spot that looks like a fingerprint sensor.
It’s nice that this is compatible with Redis clients, and even Redis cluster operations. But I wish they would take this opportunity to make scaling more ergonomic. The Redis cluster mode is a pain to use because certain commands don’t work on a cluster (and developers don’t seem to realize this, leading to implementation issues).
Or they changed the headline and due to caches CDNs or other reasons you didn’t get the newer one.
archive.today has your original headline cached.
Thanks for posting. While it’s a needlessly provocative headline, if that’s what the article headline was, then that is what the Lemmy one should be.