What's up: https://codeberg.org/comaps/comaps/projects/16883

and an example of major UI discussion that you are interested in: https://codeberg.org/comaps/comaps/issues/348

I use it since the fork and love their energy and tempo. It's amazing when you take into account it's history, that it was closed source at some point (maps.me), opensourced, forked...

> It is pretty interesting because it is true that design is better solo'd than committee'd.

This applies to all manner of "design", especially when it's at the edge/interface, which includes humans interfacing with a tool, but also with interfaces such as APIs. It's hard to maintain consistency and coherency and vision in the design of anything when it's committee'd and/or a free-for-all.

Its just too difficult to manage _alone_ as an open source or not-for profit project or even a subscription based thing. Though there are nice niche alternatives like alltrails, nothing complete exists IIUC.

A company will have to have a solid adjacent source of income to support such massive projects, analogously to like how rust is paid for by mozilla by money from their other sources(like browser rev sharing). But as a new company, criticially, that rev stream cannot be _easily_ made from people's location data _alone_, not only because of privacy concerns, but because location product market is quite fragmented with 1000's of different products and it would become hard to scale those products to match the revenue stream needed to keep this kind of massive product alive.

I feel that at this point this service is so critical it could be provided as a utility.

[0]: https://www.openstreetmap.org