Shellsharks Blogroll - BlogFlock

Miley Cyrus, what's going on? - The Weblog of fLaMEd

2026-08-01T21:35:29.000Z

What’s going on, Internet? I jumped on YouTube and found six new Miley Cyrus videos sitting there waiting for me. Six of them. Was this the rollout of a new album? Why hadn’t I heard about this already?

It wasn’t. They’re just videos for Something Beautiful, last year’s record, and they’re the last pieces of the pop opera film that went with it. I caught the film when it came out last year in the theatre but never came back to the album.

These were all released 17 hours ago, when were they made? Is she just emptying the vault before a new rollout?

Let’s have a quick surf around the web to see what’s going on.

She’s had a big week, is what’s going on. On the 27th she guest edited Wonderland’s summer issue. Next day she signed to Atlantic. Columbia’s done after Endless Summer Vacation and Something Beautiful. Four days after that, six videos.

Turns out it’s just a clear out. Everything left over gets dumped on YouTube.

The next one will be her tenth. Something Beautiful was an experimental album, will the tenth be similar? Who knows. She’s never really made the same record twice. Good for her, but it’s also why I keep going back to my favourites.

Not the new album I got excited about, then. Here are the six new videos.

Something Beautiful never lived up to Plastic Hearts for me, and I kinda just want more of that, but I doubt it. Either way, I’m here for the next era.

Hey, thanks for reading this post in your feed reader! Want to chat? Reply by email or add me on XMPP, or send a webmention. Check out the posts archive on the website.

Open Tabs July 2026 - The Weblog of fLaMEd

2026-08-01T19:36:28.000Z

What’s going on, Internet? If you don’t folllow my Bookmarks through the feed, then here’s the bookmarks from July. Enjoy.

Rant about blogs and the IndieWeb - Dom Corriveau Okay, this one had me in tears. Such a good read.
Your Metablogging is Lame as Hell – Absurd Pirate’s Internet Blog Lol, kinda nodding my head here. Blogging about Bear Blog blogs is becoming a bit of a thing, isn’t it?
don’t let Web nostalgia obscure a positive Web future This has always been something I’m an advocate for. Draw inspiration from the 90s/2000s web, but don’t rely on old and outdated hacks. Take advantage of the capabilities we have today, but don’t go overboard with modern bloat.
Pseudonym as an escape I’ve written about this previously. The pseudonym isn’t hiding; it’s breathing room. Been enjoying not being my IRL name online since 96.
Websites Are Not Going to Die If Google stops linking to websites, it stops being a search engine. Another good reminder to keep the personal website going while corp search eats itself.
The Web Won Because It Got Easier Worth a read for anyone pushing the indie web. Knowing how it all works doesn’t make it easy for the next person.
Netizen Contributing to the internet for the good of it, not for profit. Now I’m wondering what my netizen contributions will be…
The Music Discovery Problem Music discovery takes intentional effort once the algorithm’s gone, and that’s fine. I should write up and document my discovery process.
We need a physical digital music experience Olly’s model already exists in the audiobook world. Libro.fm sends a slice of my audiobook purchases to my local (physical) bookstore.
Hardcore IndieWeb: Run your own website 100% independently for only $0.01/day Great read.
The Overthinkers Guide to rekindle your Blogging Mojo Maybe some inspiration for some of you to start writing again. Sometimes I just cbf writing, lol
List of things I love seeing in personal webspaces A non-exhaustive list of things Folkmoss love seeing in blogs/personal websites.
What should a personal website be? Ratfactor asks about what a website should be. A reflection of yourself, not some idea of what a website is meant to be.
Kevin Boone: Why Idon’t really care if web content is AI-generated Kevin Boone talks about how scepticism should apply to everything online, not just the AI-generated stuff. Trust the source you know, not the medium. It feels like people forget how crap search results have been since 2008 with the rise of “SEO Spam”. Humans have been shit long before AI.
Dirty Little Zine — Free 8-Page Printable Zine Maker Super cool little tool that will help you create simple 8-page zines
What We Lost When We Quit Using Crappy Old Web Forums A fantastic read about forum software all the way from Usenet to Discourse, which is where we ended up at the 32-Bit Cafe, same as every other forum these days. RIP phpBB.
#11: fLaMEd Fury (flamedfury.com) - Wonders of Web Weaving So, I did a podcast. James had me on his podcast to talk about my corner of the web. We got into gaming and TV communities, music, and why the indie web is worth it.

For more, check out the bookmarks archive, and subscribe to the feeds if you want these as they happen.

Hey, thanks for reading this post in your feed reader! Want to chat? Reply by email or add me on XMPP, or send a webmention. Check out the posts archive on the website.

My next experiment - Werd I/O

2026-08-01T17:36:11.000Z

On Thursday, I left my role as Senior Director of Technology at ProPublica, where I led IT, Security, and Engineering. In September, I will begin my John S. Knight Journalism Fellowship at Stanford University. Which means that, during August, I will move with my family back to the San Francisco Bay Area and be based in the vicinity of the Stanford campus.

What can you expect from me?

In August, my writing will likely be more sporadic. From September, I expect to spend more time documenting my research, opening conversations, and being intentional about pushing forward the ideas I’ve always held space for.

My thesis is that community — and open community protocols and platforms — can help build trust, loyalty, and resilience in news. I laid out some of those ideas in The Community-First Software Era. But I’m going into it with an ethos of intentional serendipity, armed with everything I’ve learned about leadership, technology, journalism, and entrepreneurship. I’ll also be armed with everything I will learn with Stanford as a platform. I can’t predict what I’ll emerge with — but I can commit to taking you along with me.

Where else can you find me?

I’m going to endeavor to stick close to Stanford over the next year. I’ve also decided that I won’t get on a plane for the rest of 2026, partially as a challenge to myself and partially as a reaction to some really bad flights earlier this year.

But I’m making an exception for the News Product Alliance Summit in Chicago from October 21-23. Last year I found it to be the most substantive conference about news product and technology I’d been to. I was lucky enough to present two sessions and loved the experience. So I’m back, with Joe Germuska, to talk about how newsrooms can benefit from open technology and protocols:

Proprietary social media platforms have inserted themselves between newsrooms and the things journalism needs to survive: engagement, trust, and revenue. As AI creates new layers of intermediation and puts newsrooms at further risk, building direct relationships with your own audiences has never been more urgent.

Drawing from our combined experience building technology for newsrooms, we'll make the case for open protocols — shared, interoperable technologies no single company controls — as the foundation for a healthier news ecosystem. We'll explore how building on open infrastructure, rather than proprietary platforms, helps publishers reach more people, deepen engagement, and control their own destinies, without losing out on user experience or adding complexity.

I’m hoping to put on more events in California through Stanford, so watch this space.

Can we chat?

This work can’t be done in a vacuum. I want to learn and build alongside people who are doing great work, led by important values.

If anything I’ve spoken about above — or anything I write in this space — resonates with you, I’d love to chat. In September I’ll resume my Open Office Hours and will be available both to chat online and over a coffee for folks who might be in the Bay Area.

A note about ProPublica

I truly loved my time leading tech at ProPublica. The phrase we used internally was that it was never boring: there was always something happening. It was sometimes exhilarating, sometimes frustrating, but it was always done with a community of really great human beings working together towards the most meaningful mission of my career.

That mission runs deep throughout the newsroom:

To expose abuses of power and betrayals of the public trust by government, business, and other institutions, using the moral force of investigative journalism to spur reform through the sustained spotlighting of wrongdoing.

Some newsrooms report. Some observe and have a view from nowhere. ProPublica exists to spur reform, and its impact showcase demonstrates that it succeeds. Every workplace has things to improve or friction to overcome — they’re all works in progress — but it was hugely motivational to be working alongside these incredible people for this incredible reason.

The day after I left, the ProPublica Guild ratified its first contract. It was a long, fraught conversation that had been happening almost the entire time I was at the organization. (My timing is impeccable.) I wasn’t a part of the Guild or manager bargaining, but I couldn’t say anything about it while the negotiation was happening for fear of accidentally interfering with the process.

I’m very glad everyone got there: every worker deserves a good union to support them, and the people who work to publish ProPublica’s journalism – across editorial and business teams – certainly deserve a great deal.

I will be cheerleading for ProPublica forever, and I hope to be friends with the people behind it forever. I’m grateful that I was able to be a part of that community. And if you’re looking for a place to financially support that drives real change, there are much worse places to donate.

Mead Recipe - Smoldering Pear & Star Anise Bochet - Cool As Heck

2026-08-01T14:38:00.000Z

Every month I do some research and get inspired by other brewers and mead makers and try to come up with an interesting mead recipe. Here's my idea for August 2026. This doesn't mean I'll be making it this month, but it's going on the list of things to try, and features some new methods like caramelizing the honey and using Voss Kveik yeast.

This recipe is a bochet. If you haven't tried one, it's mead made with honey that's been cooked until it darkens and smells like toasted marshmallow. The heat changes the chemistry. You get unfermentable sugars and Maillard compounds that give you a natural semi-sweet finish without any chemical stabilization. It's one of the few ways to make a mead that doesn't need sulfites or sorbate to stay sweet.

This batch pairs that caramelized base with dried pear and star anise. The yeast is Voss Kveik, which I keep wanting to try because it ferments hot and fast without producing fusel alcohols. At 86°F it throws off bright orange esters that cut through the richness of the caramel. The dried pear goes in during secondary; fresh pear is mostly water and dilutes the flavor, but dried pear rehydrated in the mead itself gives you a concentrated, honeyed fruit note.

Star anise is the risky one. Two pods, lightly crushed, and you have to taste every three days starting at day seven. It goes from subtle to medicinal fast, and it keeps building in the bottle. I'd rather under-spice and add more next time than overdo it and dump the batch. It can get out of control fast.

The full process is below. Fair warning: caramelizing honey can be the most dangerous thing you'll do in meadmaking. It foams to three or four times its volume and holds heat like napalm. Use a pot at least six quarts, wear long sleeves, and add water drop by drop at first or it seizes into hard candy.

---

Ingredients (1 gallon)

Wildflower honey 3.0 lbs Raw, not buckwheat

Spring water ~0.8 gal Top up to 1 gallon total

Voss Kveik yeast 3 g Lallemand LalBrew Voss

Go-Ferm 3.75 g Rehydration nutrient

Fermaid O 4.0 g total 4 doses, TOSNA schedule

Dried Bosc pears 4 halves Unsulfured

Star anise 2 pods Lightly crushed

Black tea 1 cup Steeped 5 min, cooled

French oak cubes 7 g Medium toast, optional

Process

Caramelize the honey. Cook 3 lbs honey in a 6+ quart pot over medium heat, stirring constantly. It'll foam violently, then subside. Keep going 45–55 minutes until it's deep mahogany and smells like toasted marshmallow and dark caramel. Remove from heat, cool to 180°F, then trickle in 1 cup warm water drop by drop. Add a second cup once it's incorporated.

Build the must. Combine the caramelized honey, 1 cup cooled black tea, and enough spring water to hit 1 gallon. Shake for 2 minutes to aerate. Check OG — you want ~1.112. Temperature should be 85–90°F.

Pitch the yeast. Rehydrate 3 g Voss Kveik with 3.75 g Go-Ferm in 50 mL water at 104°F for 15 minutes. Pitch into the warm must, seal with an airlock, and hold at 85–95°F.

This one is daunting but very interesting and could be a great learning opportunity. I'm excited to try this out, but it might have to wait for next summer.

📝 2026-08-01 15:28: Our new addition to the family, Nelly, has arrived and she's causing havoc already. 🤣 - Kev Quirk

2026-08-01T14:28:00.000Z

Our new addition to the family, Nelly, has arrived and she's causing havoc already. 🤣

Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️

You can reply to this post by email, or leave a comment.

📝 2026-08-01 13:46: Signed up for a Vinted account. My options to "secure my account" were adding a... - Kev Quirk

2026-08-01T12:46:00.000Z

Signed up for a Vinted account. My options to "secure my account" were adding a phone number, or to logout.

I fucking hate this side of the internet. Scumbags.

Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️

You can reply to this post by email, or leave a comment.

Gadget Review: HIKMICRO D02 Thermal Camera ★★★★★ - Terence Eden’s Blog

2026-08-01T11:34:43.000Z

The good folks at Hikmicro have sent me their D02 Infrared Camera to review. It's part of their "Eco" series of thermal imagers - designed to be easy to use around the home and relatively cheap.

Despite the no-fills appearance, it packs in a lot of features which put some more expensive models to shame. It even works with Linux. Shove in a USB-C cable to grab the photos or even use it as a webcam.

All the images you see in this post are unaltered. I haven't optimised them or stripped the metadata; what you see is what you get.

Let's go!

Specs and Pictures

Infrared cameras usually have tiny sensors - the D02 is no different, you get 96x96 pixels of thermal information upscaled to 240x240.

Where the D02 shines is that it also has an optical camera just below the thermal sensor. This allows the camera to combine both the thermal and optical images into one "fusion" image.

Here's an example of the thermal image:

The optical image has a higher resolution - 480x640:

It isn't the highest quality lens in the world, but more than adequate for seeing what's going on.

Once fused, the image looks like this:

With the two images overlayed, you get a reasonably clear photo. The visual shows a good amount of detail and the thermal image shows what's hot.

It mostly works. If you're pointing at something very close to the sensor then you'll end up with a slightly surreal image like this which show the two out of alignment.

Storage is limited to around 2.5GB with no SD card slot. But given that photos are typically less than 150KB, you'll fit tens of thousands on there before worrying about running out of space.

Videos

Videos are a bit bigger, about 12MB per minute in MP4 format. But, again, you'll be able to store a couple of hours of footage on there without worry.

Again, 240x240 upscaled. Good enough for domestic use. No audio. What you see is what you get.

EXIF

There's not much useful EXIF - just the timestamp and camera serial number. That said, all the images and videos are placed in the DCIM folder which should make importing them easier.

Some other cameras provide the "raw" thermal data separately - but that's only really useful if you're doing analysis on the data, rather than trying to spot hot / cold spots.

Features

There are a few other nifty features. You can set a schedule to allow it to take pictures periodically - handy if you use the tripod attachment point to place it in a static location.

You can change the type of thermal image taken - there are various palettes available depending on what you're interested in.

There are various emissivity profiles depending on what you're pointing at:

You can also fiddle with the distance setting depending on how close you are to the subject. There's also an alarm setting to warn you if something is too hot or too cold.

Finally, you can view back the images and videos on the device. Handy if you can't get to a computer and want to show someone what you've spotted.

User Interface

There's a trigger. Press it once to take a photo. Hold it down to start / stop recording. Pretty much idiot proof.

The rest is a bit flimsy. A combined power / select button, a back button, then up & down arrows. The arrows confused me for a while. Press the up one to change the type of photo you're taking, the down one changes the colour scheme.

There's no touch-screen, haptic feedback, speaker, or anything expensive like that.

Linux and Open Source

Works fine as a storage device on Linux, showing up as 0525:a4a5 "Netchip Technology, Inc. Linux-USB File-backed Storage Gadget". True to its word, it shows up as a standard disk.

Most hardware manufacturers from China ignore their Open Source obligations - but not HIKMICRO. There's a rather prominent menu item in the settings screen which lets you scroll through an almost endless parade of software names and their licences. A bonus star for that!

You can also turn on diagnostic logging - that'll slowly fill the disk with log files:

[07-21 14:47:40][pid:477][tid:642][GUI][ERROR][minigui_lcd_dsp_update][line:1393] KEY_OK_MSG minigui_lcd_dsp_update GUI_TM_DATA_CAPTURE...

Probably not overly useful unless you've got a problem.

Webcam

On plugging in the camera via USB-C, the screen gives a choice of "USB Drive" or "USB Cast Screen". Toggling to the screen option transforms the device into 2bdf:017f a "UVC Camera". In theory, you should be able to use it as a standard WebCam and show others what the D02 is seeing. I couldn't get it to work with Chrome or Firefox directly.

Using qv4l2 I was able to open it as an MJPG stream once I set the resolution to 240x320.

For those of a technical bent, here's what v4l2-ctl showed as the available formats:

ioctl: VIDIOC_ENUM_FMT
    Type: Video Capture

    [0]: 'MJPG' (Motion-JPEG, compressed)
        Size: Discrete 240x320
            Interval: Discrete 0.033s (30.000 fps)
        Size: Discrete 320x240
            Interval: Discrete 0.033s (30.000 fps)
    [1]: 'YUYV' (YUYV 4:2:2)
        Size: Discrete 640x256
            Interval: Discrete 0.033s (30.000 fps)

Price

Infrared cameras are annoyingly expensive. This one is around £190 - although currently discounted to £170 - which is fairly reasonable.

How much will it save you? Well, it can tell you where your insulation isn't working - or which plugs are about to burst into flames; so a decent investment.

Final Thoughts

I've reviewed a lot of thermal cameras and I think this might be one of my favourites. The fact that it (optionally) captures both the thermal and the optical image makes it great for diagnosing problems because you can easily see what it is you're looking at.

There are enough settings to fiddle around with to keep most tinkerers happy and the image quality is more than good enough for spotting problems in the home. It's well worth buying for your home if you want to check for leaks, insulation gaps, hotspots, and other domestic problems. I'd recommend sharing the cost with your neighbours, or loaning it to a local tool library.

This is lightweight, quick to boot up, has good accuracy, and is (relatively) cheap. Well worth it, in my opinion.

📝 2026-08-01 08:47: Today is the first of August. Where the hell did the first two thirds of... - Kev Quirk

2026-08-01T07:47:00.000Z

Today is the first of August. Where the hell did the first two thirds of 2026 go??? 😵‍💫

Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️

You can reply to this post by email, or leave a comment.

Countryside; Blaugust - James' Coffee Blog

2026-08-01T00:00:00.000Z

With the window open and the breeze flowing through, I hear the calls and songs of birds. A calling pigeon in particular stands out. I love the calls of pigeons in the evening. The sound reminds me of childhood, looking out the window, onto Nature. A flock of birds fly by as the occasional person strolls down the street. While the sun set a little while ago, day is still here.

A gust of wind moves the leaves across a big tree, and then the breeze settles down, and picks up again. I think about the cycles of Nature: a breeze comes, and another. I watch the leaves that seem to dance with the wind; therein, a beautiful rhythm. The songs of other birds come to the fore, ones I don’t recognise but whose music is nevertheless soothing.

My eyes are heavy. The day was busier than normal, occupied with studies and essay writing and time with friends and watching the joy of community pop up around the Blaugust challenge. It got me thinking again about what it means to write on the web. When we write on the web, we can do so in a broader context: as part of the communities we are in. Seeing all the people come around for Blaugust motivated me to write this piece, and to try and participate. With this challenge, we’re all writing together. Whether I will participate often or not, I am unsure, but I do know that, at minimum, I am abundantly excited to read what my friends write.

In the spirit of sharing, while I can’t bring the fresh air of a Scottish countryside to you, I can bring part of what I hear and see; a snippet of time, for you, dear reader. That is this blog post – a little part of the Scottish countryside, as seen through my eyes, on this evening, August 1st.

Mark Temple (Belghast), who started Blaugust, passed away on July 2nd, 2026. I didn't know Mark, but I am sincerely grateful to him for starting a challenge that brings the web together. Projects like Blaugust bring light to the beautiful potential of the web. May he rest in peace.

Mark Temple (Belghast) Blaugust

Linkception - Kev Quirk

2026-07-31T22:05:00.000Z

So many links in one post. I ended up going down all kinds of rabbit holes off the back of this single post (also the second time I've linked to Sal's blog today 🙃).

I discovered Coyote's blog, and Sylvia's. So went ahead and read some of their posts. I was already aware of Brennan's fantastic blog, but it's a great read, so check it out.

Anyway, I completely agree with what Sal, Coyote, Sylvia, and Brennan say in their posts - the backbone of the internet is the hyperlink, so go forth and link out to your fellow bloggers with reckless abandon.

It's what makes the web, the web. 🕸️

Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️

You can reply to this post by email, or leave a comment.

Open-ear earbuds: A comparison - Cool As Heck

2026-07-31T18:51:30.000Z

I've recently been curious about open-ear earbuds since I've been having so many problems with my ears hurting and/or getting infected from wearing earbuds that block the ear canal. I also recently got a pair of Bose Quiet Comfort Ultra 2 over-the-ear headphones, and whatever material their ear cups are made of made my skin break out. 😩 So I had to get some cooling gel, memory foam ear pads for those and they're fine now. But I don't always want to wear those giant cans over my ears.

I ordered both the Nothing Ear (open) 2 and the Soundcore Aeroclip earbuds.

Both are very lightweight and comfortable. As you can see from the images, the Nothing earbuds wrap around the ear while the Soundcore buds sort slide or clip onto the ear. Both have drivers that sit just outside the ear canal and deliver sound directly into your ear without blocking the ear canal.

Both are roughly the same price, around $100 depending on where and when you buy them. The estimated battery life is the same for both, but in practice I got a bit more play time out of the Nothing buds; maybe 30-60 minutes more. I also have no complaints about the charging case for either one; both provide up to nearly 30 hours of charge for the buds and charge with USB-C.

I think the Soundcore app is a bit better than the Nothing app, with better EQ options.

What this comparison ultimately comes down to is sound quality, which is why I would certainly recommend the Soundcore Aeroclip earbuds over the Nothing Ear open 2 earbuds. They have better bass, better clarity in the highs, and can get louder without getting distorted.

If you have any more questions about these, please shoot me an email or a message on Mastodon!

Notable links: July 31, 2026 - Werd I/O

2026-07-31T13:01:57.000Z

Most Fridays, I share a handful of pieces that caught my eye at the intersection of technology, media, and society.

Did someone forward this to you? Subscribe for free.

Leaders are Leverage

I’ve often shared Corey Ford’s pieces. I find his frameworks and thinking genuinely useful, and he’s been a friend and mentor to me for well over a decade.

This piece outlines his underlying thinking, and why he’s focused where he has:

“When I work with one leader, I'm not working with one person. I'm working with every person on their team, every meeting they'll ever run, every piece of feedback they'll ever give, every subculture they'll ever build. A leader is not a single node in an organization. A leader is a multiplier. Change how one leader leads, and you change what work feels like for everyone around them, and everyone around the people they develop, for years.”

It’s all about seeding culture. I see a lot of similarities in the underlying ideas in Corey’s work and the intention behind culture change manifestos like Emergent Strategy. Change is fractal, bubbling up from one person to affect a whole system.

I was involved in Matter, the accelerator Corey founded, in two ways: first as an entrepreneur, receiving an earlier version of the ideas he continues to teach, and then as a member of the team, helping to deliver them to cohorts of entrepreneurs. It changed my life, and I watched it change the way other participants think about building teams, products, and cultures.

Those ideas are now part of the Sulzberger Executive Leadership Program at Columbia University. If you’re a newsroom leader, I believe you should strongly consider it. And even if you’re not, I recommend that you follow Corey and his work. I guarantee he’ll change your thinking.

Fed up with Big Tech, communities turn to data collectives for control

It’s interesting to contrast the current moment to the “information wants to be free” era of Web 2.0, twenty or so years ago. Back then, everyone was talking about open APIs and open data. Now, it’s become clearer that communities need to control the terms of their data if they’re going to avoid being strip-mined for somebody else’s profit.

“Workers, producers, consumers, and others have been establishing cooperatives and other community-led associations to pool resources, share benefits, and address socioeconomic challenges for centuries. The United Nations marked 2025 as the year of cooperatives, positioning them as “essential solutions to today’s global problems,” kindling renewed interest in data collectives and cooperatives.”

While there’s certainly an argument to be made that communities tend to over-estimate the value of their own data (looking at you, news), some of these datasets may be truly unique in ways that would add value to an AI service or model. As this article points out, collectively-owned data includes creative works in more than 20 African languages that aren’t recognized in mainstream linguistic frameworks.

The danger, of course, is that putting these kinds of gates in front of underrepresented cultures just works to further marginalize them: in that potential future, if everyone’s using a model where those languages are missing, they become irrelevant. But there’s another one where data collectives can pull the levers they have to bring about the world they want to see. That’s exactly what the Nwulite Obodo Open Data License aims to do: data rights holders can negotiate to share their work and cultural heritage without losing their right to benefit from it. (Nwulite Obodo is Igbo for raising, reviving, and building the community.)

In one model, vendors building non-extractive and responsibly trained models for public interest purposes get to use their data for free, but the closed-model big tech vendors have to pay. That’s what Meesum Alam did with voice data for 39 at-risk languages in Pakistan: the communities he worked with determined that the data was free for research and non-commercial purposes, but for-profit tech companies would need to negotiate terms (which Meta did).

That potentially becomes more interesting: either OpenAI et al negotiate to license the data, or they lose functionality to their public interest competitors. There’s also a world where some communities proactively document their cultures and make them available specifically so that models, whoever they’re built by, won’t omit them. Either the world has more equitable AI or the communities financially benefit from their cultural heritage.

Whatever happens, these communities certainly have the right to control their data however they see fit. What vendors do about it is the open question. But initiatives like Mozilla Data Collective make it more possible to have more substantive conversations about how data is provided and used, and that can only be a good thing.

US government targets Cop City protester over phone operating system

This is worth knowing about and is concerning — but not necessarily for the main reason that’s being reported.

The Department of Justice is trying to prosecute Sam Tunick, an Atlanta-based activist, for allegedly using a duress password on his GrapheneOS phone when he crossed the border in January 2025.

“Agent Findley and several others repeatedly asked Tunick to open his phone during the interrogation, telling him they would seize it if he did not. When he finally provided a passcode, “the screen went blank, flashed several times and the phone appeared to restart”, according to the motion.”

The phone was wiped. According to the Department of Justice, rather than the usual unlock password, the one Tunick had provided was a signal that GrapheneOS should reset the device to factory settings. That’s the core issue: it’s not that he was using GrapheneOS or had set up a duress password, but he was accused of using it to reset his device rather than give his data to law enforcement when asked.

At the point where law enforcement or border protection are asking you for data, it’s your right to refuse a search, but you typically can’t actively destroy it. I’ve always understood that the police can’t compel you to unlock your phone without a warrant, although, unfortunately, Customs and Border Protection has an exemption around the border. If there is a warrant, or if CBP asks you in a border zone, you may still refuse to unlock it, but the device may be seized and held. The trick here, which Tunick’s lawyers are arguing, is that the request was unlawful to begin with.

Because Tunick was a part of Atlanta’s Stop Cop City protests, he had been put on a terrorist watchlist; that fact was circulated just three hours prior. That flagged him for the secondary inspection that led to him being asked to unlock his phone. Protest is protected by the first amendment and a core component of democratic speech; putting protesters on a watchlist designed to protect the public against violent extremism is undemocratic. That’s even more affronting when you consider that the protest was against a police training center: the message it sends is nakedly authoritarian. Finally, and most egregiously, the questioning was about child exploitation imagery, which they had no reason to suspect him of holding. As a result, the search may not have been legal.

While a duress password is a deliberate act of destruction, the better path when crossing the border is to not have data to seize to begin with. Anyone who deals with sensitive information should consider that their phone might be taken at the border. Customs and Border Protection policy even allows agents to clone it, giving them permanent access to your data even after they hand your device back to you. They’re only supposed to do this when there’s a national security concern or reasonable suspicion of a crime — but if activists are being targeted as terrorists, that policy threshold doesn’t feel like a solid protection.

So: log out of your email, calendar, and file sharing before you embark upon your travels. Delete Signal entirely (but back it up). Consider which photos you want to travel with. Don’t travel with a stock phone — that can lead to more questions — but intentionally cut down your information footprint. That way, even if you are stopped, you won’t compromise sources (if you’re a journalist) or your compatriots (if you’re an activist). And you’re not forced to delete data in the moment in a way that could leave you vulnerable.

Left-Handed People Can’t Use a Fountain Pen - Kev Quirk

2026-07-31T09:52:00.000Z

Apparently left-handed people can't use a fountain pen as the left hand smudges the ink as they write. I call bullshit on that. I'm left-handed, and I use a fountain pen just fine - even with an "overhand" grip.

I read this post from Neal Stephenson a few days ago (thanks to Sal for sharing it), where Neal - a professional, left-handed writer who writes his books with a pen and paper - shares some of his experience and advice on writing with a fountain pen.

I've been back using fountain pens for a few months now and it's going great, but as Neal says - it's all about the paper. I use a decent quality notepad for writing my notes, with either a £30 Lamy Safari fountain pen, or a ~£100 Kaweco AL Sport. Both work great and I'm yet to find myself with pen on my hand. Here's an example of me writing in my notebook, using both my Lamy and Kaweco.

As you can see, I have an overhand grip where my hand swipes across the ink as I write, but the ink is dry by the time my hand gets there. Both these pens have a medium nib too.

So if you're left-handed and think you can't use a fountain pen, you can! You just need some decent paper.

Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️

You can reply to this post by email, or leave a comment.

Of Day - James' Coffee Blog

2026-07-31T00:00:00.000Z

I hear the birds singing as I sit by the window and look out on the horizon. I like looking at all the colours of the sky in the moments after sunset, when ambers recede and the sky becomes ever more blue before night time. I hear the sound of my fingers typing on my keyboard, too: nature and words are my evening.

Nature and words are my evening, and so too is music. Moments ago I was playing on the piano, two songs I love but haven’t played in as long as I can remember. And one more song that I play often: one that always makes me feel free to improvise; one where the piano shines through the recording to which I listen while I play; one where I can be an accompaniment to the melody.

A cool breeze comes through the periphery of a window; I had a window open earlier while I played music, hoping that perhaps someone would hear a note or two and feel in wonder. I remember a story a friend told me about how welcomed their music was by a neighbour. I don’t know what it is about music that makes me feel confident: I don’t need to be perfect, as long as I can play a few notes that sound good. (If only, however, my singing voice were better – someone, guide me.)

My week has been full: of tasks and ideas, assignments and readings, writing and chatting. But now, sitting here, I am starting to wind down. I look out the window to see what I can see: the tiny birds dancing around the air (which reminds me that I saw two butterflies dancing together recently; I had to write that down); the sky taking on a new blue as the sun goes even further beyond the horizon; a canvas of green; of trees whose age I will never know and whose beauty grows by the day.

Lattes - James' Coffee Blog

2026-07-31T00:00:00.000Z

I watched the movie "Valentines Day" (2010) for the first time today, which stars, among others, Taylor Swift. The energy in this scene (especially the enthusiastic and excited way in which the words are said, while Taylor carries a huge bear) ¹ fills me with joy:

[call out: "Save the Lattes!"]
Taylor: They're putting lattes in the vending machines? Finally!
Taylor: Robbie, I am so glad you are taking care of this.
Robbie: You got it.
Taylor: And, I like caramel lattes, just FYI.

I am not a fan of caramel lattes, but I do love this scene!

1m06s to 1m18s in the linked video.

[↩]

1 [↩] The energy in this scene

Toot.community is shutting down - Kev Quirk

2026-07-30T15:59:00.000Z

Toot.community is shutting down

by Jorijn Schrijvershof

Sadly, toot.community is shutting down in October. This post talks about why Jorijn has made that decision.

Read post ➡

So much of this post resonated with me and aligned closely with my reasons to step away from Fosstodon. Being a fediverse server admin is a thankless job and as Jorijn says:

I find myself feeling more angry or discouraged after spending time as an admin, and that’s not what I want from social media or a volunteer project.

Over a year on since I stepped away from the Fosstodon team, I'm much happier now, but the experience has tainted my experience of social media. These days I probably visit Fosstodon maybe once per week. Every post I write is written here, on my site, and syndicated over there. I feel this is much better for me personally, as it keeps me away from the latest drama.

When I do go visit the timeline, it's usually fun because it's fleeting. I don't have time to get involved in the latest drama. I go, check notifications, quickly peruse the timeline, and leave. It's a much healthier way of engaging, I think.

More broadly, I think the issue with admin and mod burnout on the fediverse is what will limit it in the long run. It's almost entirely propped up by volunteers, who don't want to be involved with the drama, or be attacked for making a decision you don't agree with. And as a result, servers like toot.community fall by the wayside.

I don't know what the solution is here - I actually don't think there is one. It's a fundamental limitation of the way in which the fediverse is architected and as a result, another great server is gone. 😔

Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️

You can reply to this post by email, or leave a comment.

Change is fractal. It starts with leaders - Werd I/O

2026-07-30T12:15:48.000Z

Link: Leaders Are Leverage, by Corey Ford at Point C

I’ve often shared Corey Ford’s pieces. I find his frameworks and thinking genuinely useful, and he’s been a friend and mentor to me for well over a decade.

This piece outlines his underlying thinking, and why he’s focused where he has:

“When I work with one leader, I'm not working with one person. I'm working with every person on their team, every meeting they'll ever run, every piece of feedback they'll ever give, every subculture they'll ever build. A leader is not a single node in an organization. A leader is a multiplier. Change how one leader leads, and you change what work feels like for everyone around them, and everyone around the people they develop, for years.”

Are political journalists always wrong? - Terence Eden’s Blog

2026-07-30T11:34:31.000Z

I've mostly tuned out of reading the news. But, once in a while, a headline will be shared on social media and I'll momentarily stare into the abyss.

There has recently been a change in UK Prime Minister. I neither know nor care whether that's a good thing. What I do know is that Senior Political Correspondents collectively shat their pants with excitement at being able to breathlessly report any half-baked gossip which would drive clicks.

I saw "Rumours suggest so-and-so will be appointed…", and "Supporters say that A. N. Other will be fired from…", and "Insiders reveal urgent change of policy around…", and so on.

They were all bollocks.

I spent a dull afternoon going through a couple of dozen "sources say" headlines. About 85% were completely wrong. That person didn't become Minister for Administrative Affairs, that other one wasn't fired, the much ballyhooed policy announcement never came.

A few weeks ago, The Economist ran a searing exposé on the accuracy of… The Economist. In an article called "Is The Economist always wrong?" they used a Large Langue Model to test the accuracy of their forecasts. It made for fascinating reading:

We declared smartphones the future of computing in 2002, said that something like streaming would devour DVDs in 2008, and cautioned in 2011 that a flood of Chinese-made cars would wash over the West. Still, our techno-optimism occasionally got ahead of itself. Distributed electric grids (boosted by The Economist in 2000), cheap bioethanol (2003), open standards for social media (2008) and augmented reality (2016) have yet to bring about the breakthroughs we prophesied.

I'd like someone to run the same process on the political rumours reported by the mainstream press. Just how accurate are the tips journalists receive?

Now, obviously, perhaps the rumour was true at the time - but circumstances changed. Perhaps journalists are hanging around in bars and listening to SpAds boast about what the boss has just said. Perhaps they're just making shit up.

It would be fascinating to see if any political journalist has a better than 50% ratio of hits to misses. I strongly suspect that they have an incentive to post the most outrageous rumour rather than the most accurate one.

So, if you have access to a couple of years of newspaper archives, a local AI model which won't burn the planet, and want to cause chaos - please create a leaderboard of the most- and least-accurate political rumour-mongers in the UK.

Building secure Uniswap v4 hooks - Trail of Bits Blog

2026-07-30T11:00:00.000Z

Uniswap v4 hooks let developers add custom behavior to pools, including dynamic fees, custom accounting, and external integrations. This flexibility moves some security responsibilities into application and hook code. The Cork and Bunni exploits are two app-level incidents that show what can go wrong in that code. Together, they account for more than $20M in losses. Neither incident stemmed from a flaw in the Uniswap v4 core protocol or the PoolManager; both arose from application-specific authorization and accounting logic built around hooks. After analyzing dozens of findings from Trail of Bits audits (including our <a href="https://github.com/trailofbits/publications/blob/master/reviews/2024-07-uniswap-v4-core-securityreview.pdf">Uniswap v4-core security review</a>), public reports from other firms, and the Solodit database, I’ve identified seven recurring failure patterns in application and hook code, including missing caller checks and accounting bugs that still satisfy the PoolManager’s settlement invariant. Builders can use these patterns as a secure-development checklist; auditors can use them to focus their review. <h2 id="what-the-poolmanager-guarantees">What the PoolManager guarantees</h2> If you’re familiar with Uniswap v3, where each pool was a separate contract, v4 inverts the model. All pool state now lives in a singleton PoolManager contract, with each pool represented in its storage. Uniswap v4 adds hooks: independent contracts that execute custom logic at specific points in the swap and liquidity lifecycle. <figure> <img src="https://blog.trailofbits.com/2026/07/30/building-secure-uniswap-v4-hooks/uniswapv4-figure-1_hu_b3e8804f4c7e53ff.webp" alt="“Figure 1: Pools live inside the singleton PoolManager, and multiple pools can use the same hook contract.”" width="1200" height="900" loading="lazy" decoding="async" /> <figcaption>Figure 1: Pools live inside the singleton PoolManager, and multiple pools can use the same hook contract.</figcaption> </figure> Here’s what a pool looks like in v4: <figure class="highlight"> <pre tabindex="0"><code class="language-" data-lang="" >struct PoolKey { Currency currency0; Currency currency1; uint24 fee; int24 tickSpacing; IHooks hooks; }</code></pre> <figcaption>Figure 2: A pool's PoolKey includes both currencies, the fee, tick spacing, and the hook address (<a href='https://github.com/Uniswap/v4-core/blob/main/src/types/PoolKey.sol'>v4-core/src/types/PoolKey.sol</a>).</figcaption> </figure> Notice that the hook address (<code>IHooks hooks;</code>) is part of the pool’s identity. If you change any of these fields, you’re talking to a different pool. This matters because trusting the wrong <code>PoolKey</code> means trusting the wrong pool. v4 also introduces a session-based model that works like a flash loan. Your contract calls <code>unlock()</code> on the PoolManager, which triggers a callback into your code. At the end, the PoolManager checks that no unsettled currency deltas remain: <figure class="highlight"> <pre tabindex="0"><code class="language-" data-lang="" >function unlock(bytes calldata data) external returns (bytes memory result) { Lock.unlock(); // ... callback execution happens here ... if (NonzeroDeltaCount.read() != 0) revert CurrencyNotSettled(); Lock.lock(); }</code></pre> <figcaption>Figure 3: Simplified PoolManager.unlock() flow: unlock the session, execute the callback, and revert unless all currency deltas settle to zero (<a href='https://github.com/Uniswap/v4-core/blob/main/src/PoolManager.sol'>v4-core/src/PoolManager.sol</a>).</figcaption> </figure> <figure> <img src="https://blog.trailofbits.com/2026/07/30/building-secure-uniswap-v4-hooks/uniswapv4-figure-4_hu_452027c95338c4e1.webp" alt="“Figure 4: A periphery or hook calls PoolManager.unlock(), handles unlockCallback(), and calls swap() inside the unlocked session.”" width="1200" height="312" loading="lazy" decoding="async" /> <figcaption>Figure 4: A periphery or hook calls PoolManager.unlock(), handles unlockCallback(), and calls swap() inside the unlocked session.</figcaption> </figure> The PoolManager enforces v4’s protocol mechanics, including pool initialization rules, swap and liquidity math, hook-callback sequencing, and end-of-session settlement. Hook developers are responsible for validating the application-specific assumptions their hooks add. Each hook must decide: <ul> <li>Who can call its privileged paths</li> <li>Which pools are legitimate</li> <li>How custom balances and deltas should be accounted for</li> <li>Whether external integrations can fail or reenter safely</li> </ul> <h2 id="1-anyone-can-call-your-hook">1. Anyone can call your hook</h2> Hook callbacks are external functions on your contract. If you don’t check the caller, an attacker can call those callbacks directly with malicious parameters. A loose <code>unlockCallback</code> path can also reach internal actions that should never be callable. The fix: use <code>BaseHook</code> for hook entrypoints and <code>SafeCallback</code> for <code>unlockCallback</code>. Together, they enforce caller checks on the callback paths they cover: <figure class="highlight"> <pre tabindex="0"><code class="language-" data-lang="" >modifier onlyPoolManager() { if (msg.sender != address(poolManager)) revert NotPoolManager(); _; }</code></pre> <figcaption>Figure 5: onlyPoolManager restricts hook callbacks to the configured PoolManager.</figcaption> </figure> Add an equivalent caller check only on paths those contracts don’t cover. Real-world example: The <a href="https://www.cork.tech/blog/post-mortem">Cork exploit</a> (~$12M, May 2025) shows why this check matters. Cork let data from an untrusted path reach hook logic that affected redemptions. That access-control gap, combined with a pricing issue elsewhere in the protocol, gave the attacker a way to drain funds. <h2 id="2-treating-any-pool-as-legitimate">2. Treating any pool as legitimate</h2> Pool creation through the PoolManager is permissionless by default. Unless your hook restricts initialization in beforeInitialize, anyone can create a pool with your hook address attached. If your hook trusts a user-supplied <code>PoolKey</code> without validation, an attacker can route your logic through a malicious pool with currencies and parameters they choose. An attacker-created pool presents two immediate risks. First, if your hook stores per-pool data keyed by <code>PoolId</code>, the new pool gets its own mapping slot. The attacker can influence values written through activity in that pool, and later accounting paths may treat those values as trusted. Second, <code>currency0</code> and <code>currency1</code> are attacker-chosen currencies. If either is an ERC-20, token interactions can trigger malicious behavior or reenter other hook functions mid-flow. The fix: bind your hook to canonical pools during deployment or trusted configuration, or maintain a strict allowlist. Re-check the derived <code>PoolId</code> on every user-controlled path: <figure class="highlight"> <pre tabindex="0"><code class="language-" data-lang="" >// Pseudocode for pool binding PoolId poolId = key.toId(); if (!allowedPools[poolId]) revert InvalidPool();</code></pre> <figcaption>Figure 6: Derive the PoolId from the supplied PoolKey and reject pools that are not allowlisted.</figcaption> </figure> Real-world example: In Semantic Layer’s <a href="https://solodit.cyfrin.io/issues/chat-points-manipulation-by-adding-liquidity-to-custom-pools-via-svfhook-contract-spearbit-none-semantic-layer-pdf">SVFHook finding</a>, the <code>addLiquidity</code> function lets callers specify the <code>PoolKey</code>. An attacker could route deposits through a custom WETH/SVF pool with a malicious hook and earn points at a lower cost than intended. <h2 id="3-custom-accounting-leaks-value">3. Custom accounting leaks value</h2> In v4, a delta is a signed currency-balance change owed to or from the PoolManager. Once your hook touches deltas, a wrong sign, a rounding error, or mixing balance buckets can silently leak value. These bugs are subtle because settlement only checks that the session’s currency deltas resolve; it does not validate the hook’s internal accounting. A hook’s accounting can still be wrong even when settlement succeeds. Return-delta hooks can move beyond fee bookkeeping. If a <code>BeforeSwapDelta</code> consumes the user’s entire specified amount, the PoolManager has no amount left for its concentrated-liquidity swap; the hook supplies the trade instead. This is often called a NoOp swap. Treat that hook as a custom AMM: test conservation, price bounds, rounding, and returned deltas against real balances. Dynamic fees are also price-sensitive. A dynamic-fee pool can accept a per-swap fee override from <code>beforeSwap</code>, and its hook can update the stored LP fee. Bound every fee, limit how quickly privileged changes can move it, and do not derive it directly from inputs an attacker can cheaply manipulate. For hooks that move value, test at least these three accounting invariants: <ul> <li>No user receives output that the accounting did not charge for.</li> <li>A same-transaction round trip cannot create value from accounting alone.</li> <li>Internal accounting matches actual asset balances.</li> </ul> Those invariants must also hold for the tokens the hook handles. Fee-on-transfer tokens can make the amount received smaller than the amount sent; rebasing tokens can change balances without a transfer; callback-enabled tokens can reenter; and pausable or blacklistable tokens can block settlement. State which behaviors you support and test accounting against observed balance changes. The fix: keep LP funds, fees, and incentives in separate buckets. Label every balance and delta, including who owns it, and who can move it. Real-world example: The <a href="https://blog.bunni.xyz/posts/exploit-post-mortem/">Bunni exploit</a> ($8.4M, September 2025) was a rounding bug in BunniHook’s idle-balance accounting. The attacker pushed a pool’s price tick with a flash loan, then made 44 tiny withdrawals that each shrank the active balance disproportionately to the shares burned, eventually extracting profit from the affected pools. Each transaction satisfied the PoolManager’s settlement invariant because the bug was in BunniHook’s internal accounting. <h2 id="4-right-logic-wrong-hook">4. Right logic, wrong hook</h2> <figure> <img src="https://blog.trailofbits.com/2026/07/30/building-secure-uniswap-v4-hooks/uniswapv4-figure-7_hu_bc0da7962af6947f.webp" alt="“Figure 7: PoolManager runs beforeSwap before executing the swap and afterSwap afterward when the corresponding address flags are set.”" width="1200" height="1275" loading="lazy" decoding="async" /> <figcaption>Figure 7: PoolManager runs beforeSwap before executing the swap and afterSwap afterward when the corresponding address flags are set.</figcaption> </figure> The <code>beforeSwap</code> hook executes with pre-swap state, but the <code>afterSwap</code> hook sees post-swap state. Code that’s correct in one hook can be unsafe in another. The same timing problem affects liquidity callbacks. In this <a href="https://solodit.cyfrin.io/issues/jit-liquidity-penalty-can-be-bypassed-openzeppelin-none-openzeppelin-uniswap-hooks-v110-rc-1-audit-markdown"><code>LiquidityPenaltyHook</code> finding</a>, a JIT-liquidity penalty was computed during <code>afterRemoveLiquidity</code>, but a user could first make a tiny liquidity increase that collected the fees separately. By the time removal ran, the hook saw no fees left to penalize. In our hook audits, we’ve repeatedly observed developers put logic that needs the final swap result in <code>beforeSwap</code> instead of <code>afterSwap</code>. The code looks correct in isolation, but it’s operating on stale data. The fix: verify your logic is in the correct hook for the state it needs. <h2 id="5-address-bits-are-part-of-the-api">5. Address bits are part of the API</h2> In v4, the hook address itself encodes which hook functions the PoolManager will call. This design makes the deployed address part of a hook’s API, so developers must keep its permission bits in sync with the functions they implement. <figure class="highlight"> <pre tabindex="0"><code class="language-" data-lang="" >function hasPermission(IHooks self, uint160 flag) internal pure returns (bool) { return uint160(address(self)) & flag != 0; }</code></pre> <figcaption>Figure 8: hasPermission reads callback permissions from the hook address bits (<a href='https://github.com/Uniswap/v4-core/blob/main/src/libraries/Hooks.sol'>v4-core/src/libraries/Hooks.sol</a>).</figcaption> </figure> Three permission mismatches can cause problems: <ul> <li>Callback bit set + callback missing → transaction reverts.</li> <li>Callback implemented + callback bit missing → PoolManager does not call it.</li> <li>Return-delta bit missing → PoolManager may call the callback but treat its returned delta as zero.</li> </ul> For example, if the <code>afterSwapReturnDelta</code> bit is missing, your hook might record a fee even though the PoolManager ignored the returned delta. Address bits do not make the hook’s behavior immutable. If a pool’s hook address points to a proxy, the permission bits stay fixed while an upgrade can change the code reached through that address. Review the upgrade admin, delay, storage layout, and implementation checks as part of the hook’s security boundary. Prefer immutable, versioned deployments when possible. The fix: inherit from <code>BaseHook</code> and keep <code>getHookPermissions()</code> in sync with the callbacks and return deltas your hook actually uses. <code>BaseHook</code> validates that the deployed address bits match those declared permissions. Real-world example: In the <a href="https://solodit.cyfrin.io/issues/all-swaps-will-revert-if-the-dynamic-protocol-fee-is-enabled-since-hook-configsol-does-not-encode-the-afterswapreturndelta-permission-cyfrin-none-sorella-l2-angstrom-markdown">Sorella Angstrom finding</a>, the hook returned a non-zero delta for the dynamic protocol fee, but <code>hook-config.sol</code> did not encode the <code>afterSwapReturnDelta</code> permission. The PoolManager wasn’t authorized to settle the delta, so every swap reverted with <code>CurrencyNotSettled()</code> once the fee was enabled. <h2 id="6-hook-failures-can-block-pool-actions">6. Hook failures can block pool actions</h2> Hook callbacks execute in the same transaction as the pool action. If reward distribution, dust cleanup, or other non-essential code reverts inside an <code>afterRemoveLiquidity</code> callback, users cannot exit their positions. The same applies to swaps when non-essential code reverts inside <code>afterSwap</code>. The PoolManager preserves atomic execution by reverting the parent action, so hook developers must keep optional logic from blocking core user flows. Required external reads can cause the same denial of service. If a price feed rejects stale data, a lending protocol pauses, or another dependency reverts, the callback can revert the user’s swap or withdrawal. For each dependency, decide which paths must fail closed and which can degrade without blocking safe exits. Never silently use stale pricing data. External calls are not the only source of failure. In our hook audits, we’ve seen happy-path accounting block withdrawals because of a zero balance, decimal mismatch, or missing reward token. The fix: keep non-essential code out of the main user flow. Wrap optional external calls in <code>try</code>/<code>catch</code>, or move optional logic to a separate function users can call after exiting. For safety-critical dependencies, validate freshness and bounds, and provide an explicit exit-safe fallback when the design permits one. <h2 id="7-state-can-change-during-a-callback-sequence">7. State can change during a callback sequence</h2> When enabled, <code>beforeSwap</code> and <code>afterSwap</code> run during the same swap, but values cached between them are not automatically safe. A hook can call external contracts, and one hook contract can serve many pools. Nested actions can therefore change shared hook storage, pool state, balances, or oracle data before the outer callback sequence finishes. The fix: avoid shared scratch state. If data must cross callbacks, key it by <code>PoolId</code> and caller, reject overlapping operations while that state is live, and clear it after use. Apply checks-effects-interactions before external calls, and test nested swaps and liquidity changes across multiple pools that share the hook. <h2 id="building-secure-hooks">Building secure hooks</h2> If you’re developing a v4 hook, verify these eight items: <ol> <li>Gate every callback and unlock path: Use <code>BaseHook</code> for hook entrypoints and <code>SafeCallback</code> for <code>unlockCallback</code>. Add equivalent caller checks only on uncovered paths.</li> <li>Allowlist pools, not just tokens: Bind to specific <code>PoolKey</code> values or maintain strict allowlists.</li> <li>Label every balance and delta: Document who owns it, who can move it, and which token behaviors the accounting supports.</li> <li>Keep LP funds, fees, and incentives separate: Don’t mix balance buckets.</li> <li>Keep non-essential code away from the main user flow: Reward, oracle, and cleanup failures shouldn’t block safe exits.</li> <li>Verify address permissions: Inherit from <code>BaseHook</code> and confirm that the address bits match your declared permissions. If the hook is upgradeable, review its proxy and upgrade controls separately.</li> <li>Fuzz nested callbacks, fee extremes, malicious pools, and malicious or non-standard tokens: Use Echidna and Medusa to test adversarial scenarios, not just happy paths.</li> <li>Isolate callback state: Key temporary data by <code>PoolId</code> and caller, reject overlapping operations, and clear it after use.</li> </ol> <h2 id="auditing-v4-hooks">Auditing v4 hooks</h2> If you’re reviewing a v4 hook, ask these seven questions: <ol> <li>Can an attacker call a callback directly? Check every external function for access control.</li> <li>Can an attacker route logic through a malicious pool? Trace how <code>PoolKey</code> values are validated.</li> <li>Who owns each balance and delta, and can a return delta or dynamic fee leak value? Test conservation, price bounds, and fee limits.</li> <li>What happens if reward, cleanup, or oracle code reverts during removeLiquidity? Test failure paths and dependency outages.</li> <li>Do the permission bits, implemented functions, returned values, and any proxy upgrade path all match? Verify the address flags and upgrade controls.</li> <li>What breaks if the hook, token, or fee input is malicious? Assume adversarial counterparties.</li> <li>Can state change between callbacks? Test nested actions across multiple pools that share the hook.</li> </ol> <h2 id="security-responsibilities-for-hook-developers">Security responsibilities for hook developers</h2> The PoolManager enforces v4’s protocol-level guarantees, including pool mechanics and settlement. Hook developers secure the application-specific logic they add, including authorization, pool selection, value accounting, and external integrations. Ask which assumptions the hook adds beyond the PoolManager’s guarantees. For operational guidance beyond code review, see Uniswap’s <a href="https://developers.uniswap.org/docs/protocols/v4/security">v4 Security Framework</a>. If you’re building on Uniswap v4 and want help reviewing your hooks, <a href="https://www.trailofbits.com/contact">reach out to Trail of Bits</a>. And if you’re interested in smart contract security, check out our <a href="https://github.com/trailofbits">public tools and research</a>. This post is based on a <a href="https://www.youtube.com/watch?v=F4QjFySPS_0">presentation I gave at EthCC\[9\]</a>. You can find me on X at <a href="https://x.com/nisedo_">@nisedo_</a>.

the writer’s mind - James' Coffee Blog

2026-07-30T00:00:00.000Z

making notes and reviewing quotes,
collected from day and night:
here, there are stories.

i revel in observing, and
in place-
making.
where am i? how do i feel?
what does this mean to me?

i think of the melody of words
their cadence and shape and tense
and from all, i feel:.
from words, wonder;
with words, wonder.