frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

US Court of Appeals: TOS may be updated by email, use can imply consent [pdf]

https://cdn.ca9.uscourts.gov/datastore/memoranda/2026/03/03/25-403.pdf
160•dryadin•3h ago•73 comments

Show HN: Mcp2cli – One CLI for every API, 96-99% fewer tokens than native MCP

https://github.com/knowsuchagency/mcp2cli
72•knowsuchagency•4h ago•39 comments

Agent Safehouse – macOS-native sandboxing for local agents

https://agent-safehouse.dev/
576•atombender•13h ago•141 comments

Microscopes can see video on a laserdisc

https://www.youtube.com/watch?v=qZuR-772cks
436•zdw•1d ago•55 comments

PCB devboard the size of a USB-C plug

https://github.com/Dieu-de-l-elec/AngstromIO-devboard
176•zachlatta•1d ago•33 comments

Ask HN: What Are You Working On? (March 2026)

152•david927•10h ago•509 comments

We should revisit literate programming in the agent era

https://silly.business/blog/we-should-revisit-literate-programming-in-the-agent-era/
238•horseradish•14h ago•139 comments

Every single board computer I tested in 2025

https://bret.dk/every-single-board-computer-i-tested-in-2025/
167•speckx•3d ago•51 comments

FrameBook

https://fb.edoo.gg
431•todsacerdoti•18h ago•72 comments

The death of social media is the renaissance of RSS (2025)

https://www.smartlab.at/rss-revival-life-after-social-media/
138•jruohonen•5h ago•81 comments

I love email (2023)

https://blog.xoria.org/email/
13•surprisetalk•3d ago•3 comments

My Homelab Setup

https://bryananthonio.com/blog/my-homelab-setup/
232•photon_collider•17h ago•152 comments

Linux Internals: How /proc/self/mem writes to unwritable memory (2021)

https://offlinemark.com/an-obscure-quirk-of-proc/
80•medbar•11h ago•18 comments

How the Sriracha guys screwed over their supplier

https://old.reddit.com/r/KitchenConfidential/comments/1ro61g2/how_the_sriracha_guys_screwed_over_...
176•thunderbong•5h ago•45 comments

Artificial-life: A simple (300 lines of code) reproduction of Computational Life

https://github.com/Rabrg/artificial-life
110•tosh•13h ago•12 comments

I made a programming language with M&Ms

https://mufeedvh.com/posts/i-made-a-programming-language-with-mnms/
80•tosh•15h ago•34 comments

Why can't you tune your guitar? (2019)

https://www.ethanhein.com/wp/2019/why-cant-you-tune-your-guitar/
210•digitallogic•4d ago•148 comments

My “grand vision” for Rust

https://blog.yoshuawuyts.com/a-grand-vision-for-rust/
189•todsacerdoti•4d ago•183 comments

Living human brain cells play DOOM on a CL1 [video]

https://www.youtube.com/watch?v=yRV8fSw6HaE
190•kevinak•19h ago•188 comments

Triumph of the toons: how animation came to rule the box office

https://economist.com/culture/2026/03/05/triumph-of-the-toons-how-animation-came-to-rule-the-box-...
19•andsoitis•3d ago•20 comments

Pushing and Pulling: Three reactivity algorithms

https://jonathan-frere.com/posts/reactivity-algorithms/
101•frogulis•1d ago•16 comments

Humanoid robot: The evolution of Kawasaki’s challenge

https://kawasakirobotics.com/in/blog/202511_kaleido/
14•hhs•3d ago•2 comments

Z80 Sans – a disassembler in a font (2024)

https://github.com/nevesnunes/z80-sans
113•pabs3•4d ago•12 comments

WSL Manager

https://github.com/bostrot/wsl2-distro-manager
104•gballan•15h ago•55 comments

The legendary Mojave Phone Booth is back (2013)

https://dailydot.com/mojave-phone-booth-back-number
32•1970-01-01•2d ago•6 comments

Ask HN: How to be alone?

466•sillysaurusx•22h ago•337 comments

Show HN: Skir – like Protocol Buffer but better

https://skir.build/
88•gepheum•16h ago•45 comments

Show HN: I built a real-time OSINT dashboard pulling 15 live global feeds

https://github.com/BigBodyCobain/Shadowbroker
238•vancecookcobxin•15h ago•100 comments

Case Study: lynnandtonic.com 2025 refresh

https://lynnandtonic.com/thoughts/entries/case-study-2025-refresh/
16•surprisetalk•3d ago•2 comments

Claude built a system in 3 rounds, latent bugs from round 1 exploded in round 3

https://github.com/mycelium-clj/mycelium/blob/main/benchmarks/SCALING.md
28•yogthos•1d ago•28 comments
Open in hackernews

Generating Mazes with Inductive Graphs (2017)

https://jelv.is/blog/Generating-Mazes-with-Inductive-Graphs/
20•todsacerdoti•10mo ago

Comments

tomfly•10mo ago
where is the entrance and exit?
Jaxan•10mo ago
Doesn’t matter, because all positions are reachable. So just pick any two positions at the border and remove a wall.
kazinator•10mo ago
Here is a maze that was generated recursively starting at the upper left cell.

  +    +----+----+----+----+----+----+----+----+----+
  |    |                        |                   |
  |    |                        |                   |
  +    +----+----+    +----+    +----+    +----+    +
  |              |         |                   |    |
  |              |         |                   |    |
  +----+----+    +    +----+----+----+----+----+    +
  |              |    |                        |    |
  |              |    |                        |    |
  +    +----+----+    +    +----+----+----+    +    +
  |         |              |              |    |    |
  |         |              |              |    |    |
  +    +----+    +    +----+----+----+    +    +----+
  |              |    |                   |    |    |
  |              |    |                   |    |    |
  +----+----+----+    +    +----+----+----+    +    +
  |                        |                   |    |
  |                        |                   |    |
  +    +----+----+----+    +    +----+----+----+    +
  |    |    |              |    |              |    |
  |    |    |              |    |              |    |
  +    +    +    +    +----+    +    +----+    +    +
  |    |    |    |    |         |    |         |    |
  |    |    |    |    |         |    |         |    |
  +    +    +    +    +----+----+----+    +    +    +
  |    |    |    |    |                   |         |
  |    |    |    |    |                   |         |
  +    +    +----+    +    +----+----+    +----+----+
  |              |         |                        |
  |              |         |                        |
  +----+----+----+----+----+----+----+----+----+    +

It matters to start there because it will be easier if you go backwards.

The maze has 100 cells. For each cell, we can calculate which exit goes back toward the entrance, assigning the letters U, D, L, R:

  U R R D L L R D L L
  U L L D L U L L L U
  R R U D D L L L L U
  U L D L L R R D U U
  U L L U D L L L U D
  R R R U L R R R U D
  U D R R U U R R D D
  U D U U R U U D L D
  U D U U D L L L U L
  U L L U L R R U L L
Stats:

  L - 33
  U - 29
  R - 20
  D - 18
Left and Up are more frequent back-to-entrance escapes than Right or Down. This is because of the way the maze was generated.

To check the hypothesis, we should analyze it in the other direction. For each cell, determine the exit which heads in the direction of the exit:

  D R R D L L R D L L
  D R D D L U L L L U
  D L L D D L L L L U
  D L R D L R R D D U
  R R U D D L L L U D
  R R R R D R R R U D
  U D R D L U R R D D
  U D U D R U U D L D
  U D U D R R R D U L
  U L L R U R R R R D
Stats:

  D - 30
  R - 28
  L - 24
  U - 18
There is a weaker bias for the D-R axis toward the exit, compared to the L-U axis toward the entrance. I suspect if we study larger numbers of larger mazes, we will find similar findings.

So that is to say, it is easier to navigate the maze in the reverse direction: the heuristic to try left/up exits will work more often than the right/down in the proper direction.

smartmic•10mo ago
From the book "Mazes for Programmers" by Jamis Buck, 2015, The Pragmatic Programmers (a must-read for any maze/programming enthusiast!):

> Aren't mazes supposed to have starting points and end points? […] honestly, […] it's entirely up to you. […] The maze […] is a perfect maze, and one of the attributes of a perfect maze is that there exists exactly one path between any two cells in it. […] You pick them, and there's guaranteed to be a path between them.

You do not need to choose an entrance or exit only on the sides, but you can also choose "Pacman-style" where the goal is to reach points inside the maze.

"Perfect" refers to the mathematical/logical properties of a maze (i.e. no loops), not the aesthetical aspect. I have not checked though if the mazes in the source here are all perfect.

kazinator•10mo ago
While you can put the entrance and exit wherever you want, if you know that the maze was generated by a recursive branching process which had a starting point somewhere, it probably behooves you to put the start at that point corresponding to the root of the tree, so that the maze wanderer faces the most branching choices.

Laying out the abstract maze tree into the rectilinear grid of cells obfuscates the tree somewhat, but not entirely. A process that generates from upper left to lower right, for instance, will tend to generate cells whose parent-headed exits going left and up more often than not, making the reverse direction a bit easier.

(Again, it depends on the maze generation process.)

kazinator•10mo ago
Making random mazes in a rectilinear grid is a good exercise for one big reason: mazes are not all the same. Mazes have style can be very knotty and twisty, or have long passages. You can add hacks into a given algorithm to vary the style, but there are certain things it won't necessarily do.