Yes exactly! I did this kind of thing too for a little while. I ended up using the Gist to access the bookmarks but figured it would be nice to have an optional viewer to search/sort. Also having it across all devices is a big plus. One of the features I miss now that Pocket used to offer with their bookmarklet.
One of the benefits of graph databases is that you can measure strengths of connections and also infer connections that don’t actually exist (edge prediction) among many other path traversal techniques. It’s not always just about the connection itself. Many have these algorithms built in so you don’t have to reinvent it.
Following up here, I just added a game interface abstraction to make it easier to support more devices. Planning on getting a few MakeCode-compatible devices to adapt for them.
This is cool thanks for sharing! I'm definitely be digging into these. It would be neat to support some of these devices too. I didn't know about MaplePad (+1 to Dreamcast VMU projects!)
This is for 72×40 display right now but I was also working on an interface layer to abstract Thumby specific functionality in order to play on potentially other platforms running MicroPython/Python. Going to try and add that in the next iteration.
Yeah great catch. So I mentioned this in the README but much of the mechanics were heavily inspired by jhhoward's MicroCity. This is the same way he calculated taxes and I figured to test it out to see how it worked in game. I really liked the flow of how his game played and seems like there are some pros/cons to that inbalance.
Pros:
- Makes residential population more valuable for taxes, which helps early‑game cash flow.
- Encourages zoning residential since it has outsized budget impact.
- Offsets the fact that residential growth can be more constrained by pollution/unemployment.
Cons:
- Skews the economy away from industrial/commercial impact.
- Makes budget feel inconsistent with “total population.”
- Can mask balance issues by injecting extra money, making difficulty tuning harder.