This is promising. Thanks! I'll check it out. I hope it gets the major features and works well.
2,398 karma · joined February 14, 2012
Because yes, the remote stuff -- and PlexAmp just working the same wherever I am -- is the huge part of it. Music sits on my NAS and things... just work.
I also really like how easy the caching and offline mode is, because I frequently find myself driving in areas without mobile data service. I keep a couple favorite albums downloaded to my phone, then knowing the app will cache the next ~2 albums of queued tracks generally makes it Just Work.
I use Plexamp on desktop/laptop computers and then the Android and iOS apps for on-the-go music. I tried Symfonium [1] because it seemed promising and would give me a Jellyfin path, but it was weird and kinda buggy and ate my phone's battery.
I'm hopeful there'll be a good replacement available eventually, but for now, I just have to stick with Plex.
Works out really well.
I build and maintain trails for hiking and mountain biking. We build a new trail or change a route and I can just put it in OSM and off it goes into all the other systems. And then I can pull the data back and use it to make maps for planning, signage... whatever.
Google you just give them data, in their format, without all the nice OSS tools that have developed around OSM and... Let them use it. I'm wholly uninterested in contributing to Google, most especially because the barrier to entry is so high.
Powerful, but very not straightforward.
Summary quote from IMDB: "The U.S. President, low in the opinion polls, gets talked into raising his popularity by trying to start a cold war against Canada."
Also, it kinda sounds like the UNAS might not be supporting ADS' for some reason? That alone could be a problem later on...
I can just turn it off. I can unplug it from the network if I'm worried. I can easily isolate it network-wise using just a VLAN and normal firewalls. Hardware connectivity (ESP32 stuff I'm doing this weekend) -- as you describe -- is just easier.
Very much so. When she (my wife) was first looking at getting one I went down the whole "maybe you should get an X, Y, or Z instead..." and then began thinking about her having to learn a more complicated design package, seeing how cheap some of the different Cricut tools can be when bought on sale, and I realized that it probably was just fine.
Sure, it's not a pro level device, but it did allow her to easily get shapes cut out of vinyl or cardboard or whatever with very little ease. The software worked for someone without a background in traditional design software. And it really didn't cost that much.
Few years on she still uses it, it works well enough... And that's it.
I sometimes/often think/realize the HN crowd falls hard into the technical perfect-is-the-enemy-of-good, and a number of the replies here clearly illustrate that.
The Electron app felt a bit weird, but I was able to accomplish the goal of cutting out my design at a desired size, so I didn't think any more about it. <shrug>
It seemed more to me that their app leans hard into getting people to buy vector designs through them, and making it easy for those who might not even understand what a "vector" graphic is, but it didn't seem to preclude me from cutting out my own stuff.
If you want a Free work-alike, why don't /you/ put in the work and make it happen?
(And so, so many little bugs in my map thing from upthread were these odd timing quirks when a user didn't have good service and one check would run and leave something else hanging resulting in a blank map. <sigh>)
The main idea was to solve the gap of how many trail systems have colored loops, or signed/colored loops made up of multiple "trails", and Trailforks (et al) has no concept of that. So the situation a user finds themselves in is being at a trail, with Trailforks up, wanting to follow the "Orange" loop (for example), and Trailforks doesn't show that.
Hopefully the "Orange" loop is documented as a route, but this stuff often gets missed, and is still awkward since the image of the map still doesn't match the signs.
So my goal was to show the map close to what's physically there, use OSM data as much as possible, and filling in gaps for what OSM doesn't capture, rendering it all into a static map that also happens to work offline. For some specific examples, compare these two systems and their print, Trailforks, and trailmaps.app maps:
RAMBA: [1], [2], [3] Shelden Trails: [4], [5], [6]
There is the same kind of gap when compared to RideWithGPS, Strava, Gaia, etc.
And also, I'm a volunteer with our local trails non-profit. I want anyone and everyone to be able to find maps so they can enjoy the trails. A /lot/ of trail clubs are starting to replace maps with a link to Trailforks, which I believe does riders a disservice because it both requires an app and account and (if a user is trying to view a map out of their home area on a phone) payment. It's literally locking the basic info about a trail -- the map -- behind a semi-paywall. By making a system like this for our local trails I've helped completely avoid that mess. And so I made the map generator open as well so other techy folks can do the same or build on this.
This generated-static-map system does have the downside of being single-person-ish manually managed, and the maps do NOT update automatically. But I also see this as a feature, just like the print maps and in-person signage they are designed to complement.
I've prattled on a little more about the what-why-etc over here on my personal blog if you're interested: https://nuxx.net/blog/2026/06/25/trailmaps-app-map-generator...
--
[1]https://static.wixstatic.com/media/9d19d2_b85c5684f54a4fdc85...
[2] https://www.trailforks.com/region/ramba-trails/
[3] https://trailmaps.app/ramba/
[4] https://www.metroparks.com/wp-content/uploads/2022/04/2022-S...
[5] https://www.trailforks.com/region/stony-creek-metropark/
Each map is 16MB - 20MB in total, so this is all nice and simple to do. Even on a slow 3G connection it's only a minute or so for a full map update to stream in.
The whole point of this system was to take a snapshot of data (mostly OSM), add on some local things that can't really be represented in OSM (like WHICH parking lots are most appropriate, stylistic overrides, system descriptions, etc) and display them. Because of issues I've had in the past with well-meaning-but-misguided OSM mappers wrongly editing trail systems I did not want anything that pulls live.
And then by having purely static content the hosting is very cheap and easy, there's no security concerns around... well... anything dynamic on the site. And each map is portable were I to want someone else to host them. And literally in a couple of years if I haven't updated the map it won't change yet still will work, and that's fine and accepted for this use. Sort-of like a mobile version of a traditional print map. Kinda like the print workflow of editing/design/etc and then rendering the PDF, but web.
This all aligned nicely for me to have a tool that works this way, with each map generated by a tool.
(Sort-of disclaimer: It was also a big personal project in learning to work with AI stuff for development. I knew and understood the inputs and outputs, was able to design the UI, handled/managed all the testing... But I didn't have to worry about the actual-code part. I was able to make pretty quick progress and iterate nicely on my ideas.)
Happy to talk, etc, more about it too. Either here, or contact info is on the site.
Also, apparently Apple really doesn't like approving apps that are basically wrapped PWAs (Google will, I guess?) so that is yet another check against bothering with an app.
The idea of an app really appealed to me (at first), but the more I thought about it the more I didn't want to deal with iOS and then Android and then maintaining parallel functionality on the web and all that mess just for a fairly-local hobby project that I make no money off of.
So, I just kept it as a website (which is also a PWA) with extensive testing on every platform I can think of. It's just worked out so well and is so, so, so much less complicated. And if I abandon it, should just keep working for years so long as the website stays up (or until browsers start doing something very different JS-wise.)
(You can see it at https://trailmaps.app if you're interested.)
Not as nice as an office with a door, but really not bad. Especially the taller ones.
The idea came from using the Strava heatmap in JOSM to trace the proper location of mountain bike trails. I'm trying to use Strava less, and usually have ridden the trails enough myself before mapping them that I could use my own routes... So I figured why not have my own heatmap tile server?
It's also cool to just look at.
I could take it a lot further with time boxing what's displayed and whatnot, but generating the tiles is computationally expensive, so I just stuck with what I have for now. It meets the need.
This one generates maps from OpenStreetMap data + some custom curated info in YAML: https://github.com/c0nsumer/trailmaps.app-map-generator
This one converts a basic chunk of OpenStreetMap data to an SVG so I can mark it up (by hand) in Adobe Illustrator to make specifically-styled print/PDF maps, such as what get installed at trailheads: https://github.com/c0nsumer/osm_to_ai
This one takes GPS recorded rides and builds custom/personal heatmaps serving up the map tiles so I can use them in map editing software: https://github.com/c0nsumer/local-heatmap-tile-server
And all of this has been put together to make the custom, local, specific-use-case maps that are at https://trailmaps.app (which, via local curation, are overall better mobile/online maps than many of the bigger auto-generated systems such as Trailforks, Gaia, RideWithGPS, etc, for visualizing local systems).
It's neat stuff where I understand all the inputs, outputs, and how most of it works, but AI tooling (Claude, mostly) has allowed me to bolt it together much faster than I would have writing it myself.
Just something as simple as "that ceiling fan doesn't work so well, and squeaks once in a while when on high" can easily be remedied yourself when owning the house by just going buying and installing a new ceiling fan.
Regardless of how handy one is, with a landlord that's generally not allowed without permission, the landlord often won't install as nice of one as you might like, etc.
This goes for every fixture that's not part of the rental. Major appliances, flooring, even door knobs... Like if you suddenly want an electronic keypad on your deadbolt.
Of course, this flexibility has to be something you care about. Not everyone does, but for those of us that do...
There's no reason why it couldn't be used anywhere else. This just makes maps that fit within the bounding box of a relation. The only thing US specific about it is the elevation data, and I'm sure something else could be used to get that elsewhere. Or else it could just be turned off for a given map with show_terrain: false.
So while the content is in RAM on the Pi, a lot of the heavier lifting (TLS termination) is done elsewhere, which saves a ton of CPU load on the Pi.