Thanks for the tips here. Could you elaborate on Carla? I tried Googling around but didn't mind much detailed information. I work on Lyrebird so could be helpful as you say.
.app packages are merely the binary with assets and a bunch of metadata for code signing, entitlements, icons and locales. If you "Show Package Contents" there's not much to them.
This implementation sounds better. Though for me I still have to manually input a code from the Duo app (that doesn't auto refresh after code entry since it's not time based).
The openness of this approach will allow for great recall potential with GPT models when we eventually get them running locally. Dave Winer has already been experimenting with this (admittedly not locally) based on his large backlog of blog posts and has found it effective[1].
I've considered this too, sometimes it will divulge information from the rule list and instantly follow it up by letting you know that it's confidential and that it will not tell you what it just told you.
See also Paul Haddad's situation[1] (creator of TweetBot):
> I really want an official public statement. We have a large number of sub. renewals for year 3 of Tweetbot coming up in a couple of weeks. If we're permanently cut off I need to know so we can remove the app from sale and prevent those. Which obviously I'd rather not do.
The Stadia closure has left a controlled leak of fascinating internal Google projects. First it was cdc-file-transfer, "born from the ashes of Stadia," now it's the internal Worm Game used for testing that "the Stadia team spent a LOT of time playing." Love to see it.
I am stunned by how close this description aligns with my thinking. I think that reading and prior consideration are fast fading in this industry for the reason you put so well, "everyone is used to learning by doing."