While certainly drastically better than before, it still fails at so many of the basics. I use primarily in the car, when need to be hands free. My requests are almost always say, "Directions to Starbucks". Which Starbucks.. and proceeds to list multiple then have to remind it each and every time the one first one... the one closest to me.. the one always go to... etc. So then try to do Directions to Starbucks (Town Name) (that I'm currently in, and still asks did you mean this one or this one, or everyone in a while will say did you mean City (state I'm in), aka the one down the street or did you mean that city but in another state a hundred miles away that you have never gone to. Those types of things always happened with old Siri and persist with new Siri. But now almost always when asking for reminders etc, before it would handle fine, not it says did you mean "what I said), or swapping out word for another someone similar word, etc. The problem before was it had essentially no memory or ability to learn about me. With LLMS thought that would finally change, but it has not ing general. I can say call John. And it will say did you mean John (the one you call every day for the past decade) or do you mean the John, you have never called but is in your contacts from High School? ChatGPT is amazing, and knows me and never makes any of those mistakes but of course is less integrated than Siri can be. Here's for hoping with the new LLM foundation Siri will be able to grow more quickly, but right now, it is the dumbest of the bunch. I get they don't want it to be a full chat bot, and I'm ok with it being more limited, but if it's going to be limited to a certain domain, such as control the home, setting alarms, reminders, directions, it should be absolutely rock solid at that.
Why don't you just say which Starbucks you want to go to? Or even better if you go there all the time and it's the closest one to your home, just remember the way
"clunkiness of ChatGPT is stark. The whole desktop ChatGPT vs Codex switch is dumb. The chat vs work switch is dumb. ChatGPT projects vs Codex local vs Codex cloud projects is mega dumb. I need to make 10 choices each time I want to start or continue a chat. Just give me one chat that orchestrates all of it in the background." This times a 100x. Every step forward seems 2 steps back. The sidebar is jungle, and trying to find chats is tough, trying to remember if its codex or chat, a local one or remote, and that chat ones can't be put in a codex projects and countless other issues that make it a nightmare. While I can they are working on improving the mess to at least presumably get rid of the Chat vs Work toggle, I haven't heard anything that eventually it will just be one, where we can just toggle how it responds it, vs being limited on it can be organized and searched.
"Project" for remote connections are local to the device they are created on. So if you create a project on your laptop for a remote server with a session in it, and want to access that same connection on your phone with the same project folder structure and session grouping, you need to manually recreate the project on that new device and add the session.
And you cannot mix local and remote sessions in a single project. So if you need to do anything locally for a remote project, get in the habit of naming projects things like "Project Foo [Local]" and "Project Foo [Dev]".
Seems to me like they just copied Claude's distinction of Cowork because it sounded better to enterprises but it should never have been pushed to the userbase.
And you accidentally end up asking Astra Max what time the game is tonight or something stupid like that and it still has to finish and burn credits up
Started using whatcable.uk app. Been amazing at finally knowing cable speed, but also device max speeds, and everything in between, without having to carry around one of those digital dongles with more limited use.
There's a PLIST entry possibly relevant to it in
`~/Library/Preferences/com.apple.networkserviceproxy.plist`
I couldn't figure out how to get any changes to reflect but maybe it's a good pointer towards a solution?
EDIT: Reading into this, looks like they're very intentional about not allowing arbitrary enable/disable calls to it, likely to prevent a hostile entity from switching it off on unsuspecting users. The systems setting calls an XPC into a daemon that makes a web request, then validates the response from the API to update the PLIST structure.
> hostile entity from switching it off on unsuspecting users
I agree it's likely to prevent third parties from messing with the setting, but not hostile third parties specifically. Think of a VPN app or file sharing browser extensions who might want to disable the relay "to be helpful".
Because a truly hostile entity capable of changing local settings can already obtain the device's real IP and also capture traffic, the two things private relay is meant to prevent. There would be no point. If anything it might increase the odds of detection.
Apple often plays a game where they blend security and business interests, but represent it only as a security interest.
They own the OS and could do for private relay like what they do for screen recording: when it's in use, overlay an unhideable visual indicator that it's that it's in use. Make it visually obvious when it turns off.
Have you tried recording UI events in Automator and saving it as an Application? Then you could execute the .app via script. I haven't done this but in theory it should work.
On newest iOS this didn't work for me. But it did work for my friend who has a slightly older iOS version. I imagine it's probably related to the difference in areas we're physically in rather than anything on Apple's side.
Yes, a bit of a mess. As the only practical way for most to use is with a password manager. So essentially, all your accounts still have a real password, just you enter that into your password manager app. So if your device is every compromised and someone has your master password then you are screwed.
And of course, passkeys on most all sites don't really improve security since someone can just choose to login with user/pass instead since presumably very few sites allow you to have just passkey.
Also if you use a password manager you may get locked into using that platform. Or ideally using a third party one but then having to pay a subscription, or using an open source option that is not ideal for the average person.
If one uses a passkey as intended and without a password manager and the site truly only supports logging in via your passkey, for all the touted benefits of passkeys, that would be a nightmare if a person loses access to their device, etc.
In Safari (macOS Beta), none of the pictures load. In dev tools shows 403 error for all. If view the image urls directly shows "It appears you don't have
permission to access this page.
403 Error. Forbidden." in a stylized font. Content blockers are "not" enabled. Able to replicate in Private window too. In Chrome however, images all load normally, also able to view the image urls directly. Very odd. No VPN and Private Relay is "off". Very unusual, will have to do some more digging assuming this is just affecting me and not others in Safari on latest macOS beta.
Update works in latest Safari Tech Preview, so assuming some cache/cookie/etc issue even though again affects Private mode.
Tried switching a while back. It's like Safari but with so many little UI improvements that make it so much more enjoyable but while still feeling like something Apple would design. Alas didn't use long as lack to many things such as no native Apple Pay support (have to use iOS or scan a code etc), or 2fa email/sms auto fill, private relay support, doesn't fully support 1Password, and so on. Most all of which because of Apple limitations but still little things that I value more than the better UI. However, far more important than all of that is so many sites didn't work. With Chrome you know a site will work, with Safari you know a lot may not, but with Orion it was an enormous number of sites that continually ran into issues and unlike Safari too many to keep reporting or find work arounds. All the benefits of Safari make it worth the downside of some sites not working properly, but the benefits of Orion over Safari for the massive number that didn't work right was certainly not worth it for me. Which was all unfortunate since the Orion team is doing everything they can essentially on their end. Hopefully they have a large enough niche to stick around and offer even modest competition for the big players.
I am using Orion on Mac and iOS for a few years now and I cannot disagree more.
If a site works on Safari but not on Orion it is mostly due to ad blockers etc. Just flick the compatibility mode and it works. I have not encountered a single case where this did not fix it.
Also for a while now Apple Pay works, Apple password manager works, autofill works.
reply