drio

We have some possible new markers, please head over the github repo -- I'd love to hear your thoughts.

https://github.com/drio/unixmagic/issues

Me neither. It is fascinating to see the progress from those to the final version. I wish I could speak to the author to learn a bit more about his creative process.

Not at the moment. Do you see a lot of references in the other ones?

Thank you, MT.

> A lot this mental health stuff is re-training yourself to break and avoid bad habits.

:this:

> Do you have ADHD?

I haven't done any professional evaluation.

> setting a timer for 20-30 minutes

This is what I've been using, and it works most of the time, but I still get hyperfocus stints, as you say. I guess I have to keep at it.

Also, a longer break that includes a walk after a few 25-minute chunks is extremely impactful. When I come back from that, I am so much more effective.

> But I realized I have to learn when to take a break and go outside or something.

This is a big problem for me. I can force myself to step away sometimes, but more often than not I end up chasing a bug or trying to finish "just one more thing". Then I fall into a vicious cycle where I'm tired but keep going anyway -- which only makes things worse. Does anyone else have that problem? Were you able to fix it?

Curious to hear what integration you are working on.

I am thinking about making this (1) into an integration also. It is an alternative way to visualize forecasts. It uses the dew point instead of temperature. I currently use a dashboard that shows the site on an iframe within Home Assistant.

1. https://observablehq.com/@drio/shader-galaxy

Scary stuff.

I’d love to hear your thoughts on LLMs, Jason. How do you use them in your projects? Do they play a role in your workflow at all?

> Just don't rely on centralized for-profit entities, rely on stuff produced by non-profits and foundations, that you know isn't gonna screw you over as soon as they need money

What do you use that fits that philosophy and offers the basic functionality (NAT traversal, Magic DNS, failover relaying) TS provides?

Yggdrasil is great, but AFAIK it doesn't have built-in NAT traversal, so you need at least some publicly reachable nodes.

I'm writing a minimal, educational WireGuard implementation to practice networking and cryptography: https://github.com/drio/miniwg. It's still in heavy development, but it's been a great learning experience. I've already been able to create tunnels between two miniwg instances and between miniwg and Jason's WireGuard from the Linux kernel.

Before that I wrote: https://github.com/drio/unboxing, a c/webassembly implementation of Danielle Navarro's beautiful IFS fractals.

For those using WireGuard directly: What techniques do you use to establish connections when behind network infrastructure that blocks all UDP traffic?

Amen.

Would you mind sharing a picture?

For the past few weeks, I've been annotating all the references I could find in the legendary Unix magic poster: https://unixmagic.net.

I'm happy to reach this first milestone, but I'm already envisioning future iterations. My goal is to transform this into a proper celebration of Unix – a system whose elegant simplicity and powerful design principles continue to inspire me. There's something deeply satisfying about connecting with this foundational piece of computing history.

Contributions are always welcome.

Special shout-out to @abetusk for all the support and enthusiasm with the project.

I just wanted to express my support for KOReader—it’s a fantastic piece of software. I use it on my Kobo, and the UI is noticeably faster than the device’s default system. It also offers a wealth of customization options. This may not be an issue on newer e-readers, but the ability to highlight seamlessly across adjacent pages is truly liberating.

I finished my puzzle this morning. Fun!

https://github.com/drio/unixmagic/raw/main/static/puzzle.web...

Thank you! I’ve updated the content from "wheel" to "valve handle".

Please feel free to contribute—there’s still so much to uncover! I can easily think of 50 more references, and I’ll be adding them gradually over time.

This project is an invitation to dig deep into the meaning behind each reference—to explore their significance and understand how they fit into the historical context of Unix’s early days. I tried to capture that in the README (https://github.com/drio/unixmagic):

"When contributing, remember that this is an opportunity to dig deep into the history behind what you’re describing. Feel free to share what this particular component means to you personally, but also aim to frame the explanation within the context of Unix’s early days. How did this functionality compare to other operating systems at the time? What made it special or innovative? This project is not just about explaining what things are, but understanding why they mattered—both technically and culturally—in the evolution of Unix."

I’d love to see a PR from you—I bet your take on one of these references would be fascinating.

man(1)

A quick reminder for anyone interested in the project: if you come across an annotation that you disagree with or feel is missing important details, please open an issue in the GH repo. That way, we can discuss it and work toward incorporating the knowledge into the project.

That is a good one. Would be great to talk to the author and learn what they originally had in mind.

Nice! Did you print it yourself, or did you use a company?

I'm probably going to frame my puzzle once I finish it. I know I can get a frame that allows me to "unframe" it and redo it again.

Glad you like it.

I actually made a puzzle out of this image. :)

Thank you for the feedback.

> Reposition markers to make the item they're referencing clear. In particular, marker 6 (C) completely obscures the text on the jar.

I agree, and I'll take care of that. It’s a bit tricky because the marker’s exact position can shift slightly depending on the display being used, but I’ll adjust it for better clarity.

> Allow a toggle for markers to be unhighlighted.

Yes, this will be especially useful as we add more markers. I already have at least 50 more in mind that I plan to include.

> Having 'hover highlighting' for the annotations/markers.

I intentionally designed the layout this way to ensure the image and annotations remain functional across different screen types without introducing overly complex logic. That said, I’m sure someone with more expertise in web development could refine this further.

> Licensing information.

100%. I’ll add that shortly.

Hi Jason,

Thank you for wireguard - it's been a hugely impactful piece of software.

Do you think it would be helpful to outline what hardware resources you would need to successfully migrate the project and all the CI/CD computations to a new home? This would help people determine if they can help with hosting.

That’s interesting. Tailscale userspace mode does not require tun write access as (I believe) is implemented within the process that runs the gvisor stack (tailscaled). I am wondering if httptap could use the same approach?

Outstanding! Congratulations on writing such a wonderful project!

I have a suggestion regarding the "How It Works" section. When reading it, I initially thought you had implemented your TCP/IP stack from scratch. Later, I discovered through the comments that you're using gVisor. Perhaps you might consider mentioning this explicitly in the documentation?

As an interesting side note, gVisor's netstack is also used in the Tailscale client, enabling features like connecting a machine to multiple tailnets without requiring special privileges.

I can totally relate to this. My approach depends on how often I'll be working on the server. For quick, one-off tasks, I stick with the system's plain vim distribution. However, if it's a machine I'll be accessing frequently, I go ahead and set up neovim with my config files.

The setup process can be tricky, as you mentioned. My config relies on several external dependencies, particularly for LSP servers. I usually ignore the dependency errors initially unless I know I'll need those specific features – then I'll invest the time to fix them properly.

Installing neovim itself can also be challenging, especially on fixed/point release operating systems. I've found using AppImage to be the most reliable solution in these cases.

I'm curious to hear how others handle this balance between convenience and functionality on remote servers.