(I haven’t confirmed this yet but I think I may have paid for a ten year renewal at some point, which gives you a full decade to lose track of how it’s being paid for.) until it turned out I had it on a registrar with an old email address that I no longer had access to, and the domain was switched into “parked” mode because I had failed to pay for renewal! Short version: while I’ve been paying close attention to the management of domains I’ve bought in the past few years ( datasette.io, datasette.cloud etc) I hadn’t been paying attention to. This site was offline for 24 hours this week due to a DNS issue. Menu items can now also include an optional description, which is displayed below their label in the actions menu. homepage_actions() for actions that apply to the instance homepage.row_actions() for actions that apply to the row page.view_actions() for actions that can be applied to a SQL view.query_actions() for actions that apply to the query results page.Prior to 1.0a12 Datasette had plugin hooks for just the database and table actions menus. Here’s a GIF showing that new button in action across several different pages on Datasette Cloud (which has a bunch of plugins that use it): I decided to turn it into a much more clear button. The cog wasn’t discoverable enough, and felt too much like mystery meat navigation. These were previously hidden behind a “cog” icon in the title of the page-once clicked it would reveal a menu of extra actions. The main theme of these two releases was improvements to Datasette’s “action buttons”.ĭatasette plugins have long been able to register additional menu items that should be shown on the database and table pages. I released two new Datasette 1.0 alphas in the run-up to NICAR: 1.0a12 and 1.0a13. I have a bunch of exciting conversations lined up over the next few weeks thanks to that, with a variety of different sizes of newsrooms who are either using or want to use Datasette.
This time I used a trick I first learned at a YC demo day many years ago: if someone says they’d like to follow up, get out a calendar and book a future conversation with them right there on the spot. I also solved the conference follow-up problem! I’ve long suffered from poor habits in dropping the ball on following up with people I meet at conferences. I got it working just in time for the conference. I need to write more about the latter one: it enables populating tables from unstructured content (using a variant of this technique) and it’s really effective. Alex and I ran a successful workshop on Datasette and Datasette Cloud, and I gave a lightning talk demonstrating two new GPT-4 powered Datasette plugins- datasette-enrichments-gpt and datasette-extract. Weeknotes: the aftermath of NICAR one day ago