Last.fm and similar platforms provide intentional discoverability for people who care enough to put in the work. Only radio and Spotify have provided the unintentional discoverability that I crave.
FWIW, my workflow with git is to stage changes I want to keep after every prompt. Then I can discard changes in the working area after a bad prompt or stage individual changes before discarding from the working area. Works really nice for me.
There is a world of difference between shipping a feature, and shipping an api that anyone can use to ship a feature. It is such a normal progression to make an api and dogfood it internally, iterate until you have something you feel comfortable supporting indefinitely, and then expose that api publicly. It is not reasonable, IMO, to require that every feature you ship has an API that is ready for public consumption.
Granted, Apple generally doesn't do that last part unless forced. I think some kind of timeline on the DMA requirements would be more reasonable. e.g. you have two years to make a feature publicly accessible before fines start accruing.
I have had an excellent experience with the OhSnap grip. https://ohsnap.com/products/snap-grip It is significantly smaller than the popsocket and adds a strong magnet which can attach your phone to magnetic surfaces. It looks flimsy, but I've had it two years and even moved phones and it shows no signs of breaking.
One easy way to accidentally give Claude permission to do almost anything is to tell it that it’s allowed to run “find” without confirmation.
Claude is constantly searching through your files and approving every find command is annoying.
The problem is, find has a --exec flag that lets it run arbitrary bash commands. So now Claude can basically do anything it wants.
I have really been enjoying Claude in a container in yolo mode though. Seems like the main risk I am taking is data exfiltration since it will has unfettered access to the internet.
> Third-party publishers "cannot rely on the ATT framework to comply with their legal obligations," so they "must continue to use their own consent collection solution," the French agency said.
This absolutely sounds like a problem caused by the law and not apple. Apps can’t rely on the prompt for legal authorization (presumably because it is filtered through apples apis?) and must therefore ask themselves.
The only two solutions I see to this is either Apple can’t prompt which means they can’t protect the user or the law can change to accept the prompt as authorization to track.
A code comment can tell you why the code is the way it is, but it shouldn’t tell you why it changed. That’s what commit messages and/or PR descriptions are for.
Yes, people are only confused because they think it means cheapest, which is ultimately a failing of Apple branding but doesn't really make much sense to me.
Could you elaborate on why? The companies I have worked for have pretty much all used domain.com for marketing and app.domain.com for the actual application. What's wrong with this approach?
I've been curious about Kagi as a search engine for a while now and this seems like a good time to try, given that I already pay $20/month for ChatGPT.
The thing stopping me currently from trying this or Claude is I rely on the Opt+Space shortcut with the ChatGPT mac app.
Are there any other options for a native mac app with integration as good as the ChatGPT app?