@DamienPetrilli Those are the ones I have experience with. Sounds like many of the others are failing because they rely on S3.
Surprised how long this S3/SES outage is lasting.
@FastSpring Any update on this?
@Gok That is an improvement. But I think it still tries to interpret days/times/intervals in the following text.
@Gok In other words, I think transcription should be harder than parsing simple commands, but Siri finds it easier because it’s so complex.
@Gok And it can already do that hard part well enough.
@Gok In theory, it should be easy to enter a “reminder mode” (easy part) and then it would have to transcribe what I say (hard part).
@Gok I guess I didn’t explain very well. I mean in the context of my example, making a reminder, there is no “understanding” to be done.
@Gok I think transcription is the easy part—because I can see on the screen that it usually gets it pretty close. Interpreting it is harder.
@McCloudStrife Right. Essentially 100% accuracy in 1996. More accurate, faster, and with far less hardware than the Newton.
@McCloudStrife I thought they should have done the Graffiti approach initially but had hope. That was 5+ years ago.
@McCloudStrife No, I don’t use recurring reminders or the Reminders app; just a front-end to OmniFocus.
@McCloudStrife That could work even without turning anything off, if it could be more modal or put the keywords at the beginning like Alexa.
@McCloudStrife I wish I could turn Siri off for everything except Reminders, which would then be super reliable.
@McCloudStrife I believe it’s still impossible to do a local music search with Siri enabled; before this worked offline and was faster.
@timohetzel What happens to the app ecosystem for the rest of us if they lose the pros?
@nickheer The iCatch is more similar to MagicGrips. But the one that I used actually covered the whole puck mouse, including the button.
@rgriff That would be my guess.
@rgriff I’m not sure about that. I’m seeing Shift on a VM where I don’t think I’ve ever relaunched Finder or changed Show Library Folder.
@zcichy Such an unforced error.
@peternlewis I’m seeing this, too. This will break lots of stuff.
@ScooterComputer Hmm, I haven’t heard any other reports of that.
@etresoft I’m all for it. More consistent with the other commands. Just wonder why it happened when it did.
@dougscripts No, I just verified that in 10.12.0 and 10.12.1 it was Option.
@mcelhearn It also looks like sometime in 10.12.2 or 10.12.3 they got rid of the View Options checkbox to always show the Library folder.
@mcelhearn There wasn’t.
@mcelhearn And now there’s a keyboard shortcut: Command-Shift-L. Not sure about 10.12.2.
Opening user Library folder from Finder’s Go menu: on 10.7-10.12.1 you hold down Option key, but on 10.12.3 you have to hold down Shift.
@joely Cool. BTW, seems like there’s a new issue in 10.12.3 where PDFView delivered in notifications has a nil window…
@futurekennysf Sorry, I don’t have any further info on this.
@speisert Yes, and I like the way it handles notes. Lighterweight than Markdown.
@speisert Right, I use TaskPaper format for notes/records. OmniFocus for projects and to-do lists.
@speisert I used TaskPaper itself for several years. Last few years, I’ve been using the TaskPaper format in BBEdit and Editorial.
@speisert I’m not. I was happy that Omni changed the clipboard format back to regular text.
@joely I don’t think so, and Apple probably doesn't want you shipping their binary.
@leebennett Oh, for me it’s happening spontaneously every hour or so, not after rebooting.
@isaiah A basic filename search shouldn’t use an index.
@leebennett So do I, but the problem occurs on the MBP internal display, which uses Apple’s default calibration.
Simply opening the Color tab of the Displays pref pane fixes the color. The correct color profile is already shown as selected.
Flux uninstalled, its profiles deleted, internal MBP display still auto-auto-changes color periodically.
Why does Finder still fail to find files by filename, even in non-hidden folders?
@dafacto Sorry to hear that. I’m still seeing issues like this, too.
@cookednick No problem. I can edit it if you want.
Not yet. :(
@nickheer Yep, meant to quote your last paragraph. Thanks!
@lapcatsoftware Yep. Still using WebObjects internally…
@lapcatsoftware As to the three possibilities, remember that the official line was that Carbon would have feature parity and be 1st class.
@lapcatsoftware At this point there would be a huge cost to Apple’s reputation if they abandoned Swift. There’s no precedent like this.
@DanFrakes I saw this for months with Flagged; rebuilding helped, but only temporarily. Finally did clean install, seemed to fix. ¯\_(ツ)_/¯
@Kentzo No, haven’t heard about that.
@DanFrakes You may need to rebuild the database and/or Spotlight.
@lapcatsoftware GC had at least two fundamental problems: iOS and maintaining dual mode frameworks. Is there anything like that for Swift?
@lapcatsoftware It’s not about what Apple says. It’s about whether what they’re evangelizing actually makes sense now and in the future.
@lapcatsoftware They totally would if they had a good reason, but I don’t think they do.
@grynspan Right, but that wouldn’t be too complicated to understand, just probably not advisable.
@lapcatsoftware Yeah, that’s the big question. Granted, it did sell a lot in those years.
@grynspan Agreed, but there’s a lot of ground between “easily understood” to “you have no idea what your code is doing.” And can document it
@grynspan Until someone decides to invoke it n times?
@laxdude What do you mean? Unable to switch over to what?
@nickheer Yeah, looks like I ran the wrong script on that text. Thanks!
@petermaurer Good thing there’s no Cocoa Print Manager.
@dancounsell Makes sense. Wonder if you keep getting revenue in that case.
@dancounsell So you could subscribe for one month, get all the apps, unsubscribe, and keep all the current versions?
@olebegemann Except that the Discourse user experience is much worse than e-mail.
@fzwob It sounded like they thought they were fixing a big problem by locking it down, but I don’t know how to evaluate that claim.
@fzwob rather they prioritize fixing the compiler/editor bugs that I hit daily. But it’s another thing to actively prevent 3rd party efforts
@fzwob Yes. The Xcode one is particularly frustrating. They clearly don’t have time to make a plug-in architecture. And personally I would
@fzwob Yes, that is a problem.
@fzwob I agree to an extent, but some of this is probably stuff that Apple would like to do, and other stuff is structurally hard for them.
@mulle_nat Yes, but must be something non-local. Git says the .m file hasn’t changed since November. Xcode 8.2 installed in December.
Why does the Clang static analyzer suddenly find new problems when neither Xcode nor the code has changed recently?
@grynspan Incidentally, I’m successfully using this as a workaround for 29958269.
@grynspan Not yet. I think it must have regressed because found sample code online that successfully treated it as a URL.
So kPasteboardTypeFileURLPromise is documented as being a UTF-8 encoded file URL, but it seems to actually be a file path.
@mmunz The compiler/highlighter also seems to be much more crashy when dealing with Obj-C headers.
@jgordonshare So many newer, spiffier apps to do this, but I still prefer OmniDiskSweeper.
@lapcatsoftware I would like a stat like “percent of time product worked correctly.”
@joely Agreed. :(
@joely I don’t know. Wasn’t expecting any new APIs, just fixes.