Marcin is a hero – his attention to detail and enthusiasm are infectious; whether he’s writing about abandoned rail infra in SF, obscure movies (Sneakers!) or vintage typography. This is a gem showcasing (interactively! with VMs in your browser!!) the evolution of Mac preferences UI.
Join me on a journey through the first twenty years of Mac’s control panels.
“No, I don’t use LLMs for writing the text on this very blog, which I suspect has now become a default assumption for people reading an article written by an experienced LLM user. My blog is far too weird for an LLM to properly emulate. My writing style is blunt, irreverent, and occasionally cringe: even with prompt engineering plus few-shot prompting by giving it examples of my existing blog posts and telling the model to follow the same literary style precisely, LLMs output something closer to Marvel movie dialogue. But even if LLMs could write articles in my voice I still wouldn’t use them due of the ethics of misrepresenting authorship by having the majority of the work not be my own words. Additionally, I tend to write about very recent events in the tech/coding world that would not be strongly represented in the training data of a LLM if at all, which increases the likelihood of hallucination.”
“Secretive is an app for storing and managing SSH keys in the Secure Enclave. It is inspired by the sekey project, but rewritten in Swift with no external dependencies and with a handy native management app.”
So this is a new approach… No longer allowing password based auth for the DB root solves a whole lot of possible security snafu’s, but at the expense of some friction in learning ‘the new way’
The idea with the new set-up is that you shouldn’t be using passwords at all.
What’s especially relevant is the contents of /usr/share/doc/mariadb-server-10.0/README.Debian.gz on Ubuntu 16.04:
“Scripts should run as a user have have the required grants and be identified via unix_socket.
So it looks like passwords should no longer be used by applications.”
Not just to save your 4G data bundle, but also great to squeeze the most out of a crappy Wi-Fi hotspot when abroad (or on the ‘Wi-Fi in de Trein’ in NL). By blocking large background transfers like CrashPlan, Box and Google Drive, the limited bandwidth is all available for your foreground tasks!
Smart companies are starting to build solutions with a “mobile native” assumption:
This change, from building on mobile ‘first’ to really leveraging what a billion or so high-end smartphones can do in 2016, reminds me a little of the ‘Web 2.0’ products of a decade or so ago. One (and only one) way you could characterize these is that they said: ”you know, we don’t necessarily have to think about Lynx, and CGI scripts, and IE2, and dialup. We’ve evolved the web beyond the point that tags were controversial and can make new assumptions about what will work, and that enables new ways to think about interfaces and services.”