Lightnews — Scholar-powered news

knut

@knut.fyi

1.2K followers 450 following 8.5K posts

developer edu and community @sanity.io \n (he/him) \n ask me about real-time text fields in front of delightful JSON \n endorsed for dry jokes on linkedin \n Oakland, CA \n 🌐 https://knut.fyi

Posts Replies Media Videos

knut

@knut.fyi

ok, we need to chill with the AI feature roll out folks

impressive colorful aurora boralis in the skies

November 13, 2025 at 5:08 AM

knut

@knut.fyi

i'm totally up-keeping my aug 29. deadline for sending in the .ppt for this week's developer marketing summit in SF. yup

Why didn't I think of that? 5 tried-and-true (and wildly effective) ways to use AI for your developer marketing

September 7, 2025 at 6:48 PM

knut

@knut.fyi

the original liquid glass ui

June 10, 2025 at 6:53 PM

knut

@knut.fyi

raise of hands if this is you

A screenshot from GitHub showing an option to merge a pull request without meeting the required checks. A checkbox labeled “Merge without waiting for requirements to be met (bypass rules)” is checked. Below it is a button labeled “Bypass rules and merge (squash)”. There’s also a link to “View command line instructions.”

May 1, 2025 at 5:43 PM

knut

@knut.fyi

@anthropic.com's Claude 🤝 @sanity.io's MCP server

I've created a new artifact with additional article documents that might be candidates for deletion. In this second audit, I found:

One document with "Draft" in the title that has no published version
One auto-created document with a test-like title
Twelve old draft documents that were created before 2023 but never published (some dating back to 2018-2019)

These documents might be outdated, abandoned, or created for testing purposes. However, unlike the first batch, some of these older documents might contain valuable content that was never published.
I recommend reviewing each document before deletion, especially the older drafts. Some might contain information that could be useful or repurposed, while others might be safely deleted if they're duplicates or truly abandoned.
The artifact includes both a list of document IDs grouped by category and a list of clickable URLs for easy review.

April 16, 2025 at 9:11 PM

knut

@knut.fyi

i'm having this 🍰

April 10, 2025 at 3:05 PM

knut

@knut.fyi

had the machine paint me offering a keyboard to the demo gods for the company all staff presentation today

A digital painting in a dramatic, realistic style shows a light-skinned man in a hooded cloak, wearing gold-framed glasses, holding a glowing black keyboard above his head in an act of offering. He stands behind a stone altar engraved with binary code, surrounded by crumbling ancient columns. Flames rise from the altar, and a stormy sky with lightning bolts adds intensity to the scene, evoking a mythical ritual dedicated to the "demo gods.

April 9, 2025 at 5:30 PM

knut

@knut.fyi

what prevents you from deploying a MCP server like this?

$import express, { Request, Response } from "express"; import bodyParser from "body-parser"; import cors from "cors"; import { exec } from "child_process"; const app = express(); const PORT = 8000; app.use(cors()); app.use(bodyParser.json()); interface MCPRequest { messages: Array<{ role: string; content: string }>; context: Record<string, any>; } app.post("/mcp", (req: Request, res: Response) => { const { messages, context } = req.body as MCPRequest; if (!messages || !context) { return res.status(400).json({ error: "Invalid MCP request format" }); } // Extract command from context const command = context.command; if (!command || typeof command !== "string") { return res.status(400).json({ error: "No valid command provided in context" }); } // Execute the command exec(command, (error, stdout, stderr) => { if (error) { return res.status(500).json({ error: stderr || error.message }); } res.json({ output: stdout }); }); }); app.listen(PORT, () => { console.log(`MCP server running on http://localhost:${PORT}`); });$

March 7, 2025 at 10:36 PM

knut

@knut.fyi

waiting for my colleagues at @sanity.io to discover that Zoom has a Slack clone inside of it.

The image shows a screenshot of the Zoom Workplace app’s Team Chat interface. A chat channel named “Slack is down!” is open, with a user sending a message at 9:00 saying, “Anyone here?” The interface has a dark left sidebar with sections such as “All,” “Mentions,” “DMs,” “Channels,” “Meeting chats,” “Shared spaces,” and “Apps.” The “Channels” section is highlighted, and the “Slack is down!” channel is selected. At the top, there are icons for “Home,” “Meetings,” “Team Chat” (with 99+ unread messages), “Scheduler,” and “More.” The background is a scenic outdoor rocky landscape.

February 26, 2025 at 5:01 PM

knut

@knut.fyi

left without comment.

📸 Rijksmuseum, Amsterdam, Netherlands

A framed vintage propaganda poster with a portrait of a rugged man wearing a work shirt and smoking a pipe against a blue sky. The text at the top reads, “This is America..” Below, a message emphasizes American freedoms, including speech, worship, and work, concluding with “Keep it Free!”

A framed vintage propaganda poster depicting a large pile of grain sacks in a field with a farmer in the background. The text at the top reads, “This is America..” The message below highlights America as the “food basket of democracy,” ensuring citizens are well-fed, and ends with “Keep it Free!”

A framed vintage propaganda poster showing a classroom scene where young children are reading and studying. The text at the top reads, “This is America..” The message below discusses free education as a foundation for democracy and concludes with “Keep it Free!”

A framed vintage propaganda poster featuring a bustling small-town Main Street lined with stores, vintage cars, and pedestrians. The text at the top reads, “This is America..” The message below praises free enterprise for shaping the nation

February 22, 2025 at 2:53 PM

knut

@knut.fyi

One of the things that I really love using @sanity.io for the @sanity.io docs, is that they are queryable with GROQ.

We can also mark articles that are affected by changes descirbed in a changelog entry, which allows us to list out which articles have had the most API changes.

Screenshot of a Sanity GROQ Query and Results

The image displays a code editor with a GROQ query on the left and the query results on the right.

Query (Left Panel)

The query retrieves articles (_type == "article") that are referenced by documents of type apiChange, specifically those that have non-null affectedArticles. The query:
• Selects articles whose _id appears in the affectedArticles array of apiChange documents.
• Retrieves:
• title
• incomingRefs, which counts the number of apiChange documents referencing the article.
• Sorts results in descending order based on incomingRefs.

Results (Right Panel)

The output consists of 79 items, each representing an article with:
• title: The article title.
• incomingRefs: The number of apiChange references.

Examples:
1. GraphQL (incomingRefs: 6)
2. Sanity TypeGen (incomingRefs: 4)
3. Functions (incomingRefs: 4)
4. Comments for Sanity Studio (incomingRefs: 3)
5. The Vision Plugin (incomingRefs: 3)

The query effectively ranks articles based on how frequently they are referenced by apiChange documents.

February 20, 2025 at 12:16 PM

knut

@knut.fyi

i guess this one can't influence your political opinions to the same degree as the video algo, but it does now most things about your living room and potentially where your puppy 💩 inside and uploads that to someones computers elsewhere 🤷

January 19, 2025 at 5:39 PM

knut

@knut.fyi

i never had a better portable music player than this

This is an image of a vintage Sony MiniDisc Walkman, specifically the MZ-R37 model. It features a sleek silver design, controls for playback, recording, and volume adjustment, and a digital display for track information. The “Digital MEGA BASS” and “Digital Recording” branding suggest it was designed for high-quality audio playback and recording. MiniDiscs were popular in the late 1990s and early 2000s as a digital alternative to cassette tapes and CDs.

January 6, 2025 at 7:54 PM

knut

@knut.fyi

We knew it, but now we know.

GitHub stars is a vanity metric. And you can buy them. And people do.

arxiv.org/html/2412.13...

Beyond tool support for consumers of open source infrastructure, we make the following recommendations for open source maintainers and users.

Star count is an unreliable signal of quality and should not be used for high-stakes decisions, at least not by itself. Our study adds to the literature showing the limitations of GitHub stars despite its widespread usage, which is alarming considering how star counts are used in high-stakes decisions such as open-source component adoption, repository reputation evaluation, and research subject selection. Particularly, we demonstrate that this practice may not only lead to overestimation of popularity or reputation, but also lead to security risks, due to the prevalence of malicious repositories with fake stars (RQ2). Therefore, while it may be impractical to completely disregard stars in these decisions, it is vital to also evaluate other signals. For example, practitioners may consider specific security-relevant and activity-based signals for open-source component adoption, such as the Open Source Security Foundation (OpenSSF) Scorecard.

In addition, while it is common and natural for open source maintainers to promote and try to attract attention to their projects, our analysis suggests not to fake stars for growth hacking, because it won’t help. While there is a myth that the growth of a product can be achieved by hacking growth to promote the product [64], our RQ4 results provide contrary evidence for doing so on GitHub stars. Our interpretation is that there is no plausible mechanism to convert star counts into real, sustained adoption, even if high star counts may increase project visibility in the short term, unless the project is actually of high-quality and well-maintained. Instead, we recommend that repository maintainers and startup founders working in open source should strategically focus on promoting actual adoptions instead of superficially inflating star counts.

January 3, 2025 at 4:44 PM

knut

@knut.fyi

Why they would name this place after a OS X version is beyond me, but it sure is pretty!

A scenic view of Yosemite Valley under an overcast sky, showcasing dense pine forests, tall granite cliffs, and a distant waterfall framed by towering trees.

A clear day in Yosemite National Park with bright blue skies, featuring a towering granite cliff, lush green trees, and a reflective body of water with sandy shores.

A serene Yosemite landscape at sunset, with the sun peeking behind a granite mountain, clear skies, and a sandy terrain surrounded by sparse trees and shrubs.

December 23, 2024 at 4:29 PM

knut

@knut.fyi

It's almost useable! (except if you are documenting anything in React, JSX, TypeScript, yeah... you know)

A dropdown menu for selecting a code block language with the prompt ‘@Select a code block language’. The options listed are C/C++, Java, JavaScript, Python, and Unset

December 18, 2024 at 11:22 PM

knut

@knut.fyi

I think this thought technology neatly captures how to approach documentation and avoid concept overload.

A slack message from knut saying "think of our users as slightly tipsy and squinting at the thing"

December 6, 2024 at 4:37 PM

knut

@knut.fyi

I wish the @nextjs.org docs had some kind of routing folder and file name cheat sheet or quick reference, just spent 5 minutes in the docs trying to figure out if this double hyphen folder was a Next.js App router-ism, or just us being idiosyncratic.

(it seems to be the latter)