Better go with my own DB.
Or use a network with a well-designed protocol, a hosted service, 30 million users, a social graph, moderation...
Many OSM apps will also be reluctant to adopt a closed source solution that might be closed of any moment. And under what licenses will those reviews be? As MapComplete developer, I can not and will not be adopting a system based on Bluesky
I'm currently building a review system for my open source Web map https://cartes.app, based on Bluesky. Not trivial though, you have to create a lexicon and maintain a DB based on the Bluesky stream.
Bluesky _will_ enshittify sooner or later
Add to that an infinite stream of bug reports and feature requests, and it gets tiring. I don't even have the time to answer all bug reports...
Thanks for hosting this all those years. I'll try to find a new home for my bot.
I'm trying to build a somewhat generic map view, which features many thematic maps (e.g. shops, restaurants, bicycle pumps, toilets, ...)
Most data comes from OpenStreetMap, but it also allows to make changes, upload pictures, show wikipedia or make reviews with mangrove.Reviews
Probably the best generic "frontend" for OSM is Organic Maps, which however is confined to Android and iOS. I think if there would be a web version of Organic Maps, this could greatly accelerate OSM adoption.
In either case, I've heard quite some people being in love with Qwant Maps.
And I try to get to build specialized maps with https://mapcomplete.org
[1] https://forgejo.org
[2] https://codeberg.org
[3] https://sourcehut.org
Pushes and pulls would still kinda work, actions not so much (but that's cause it needed to transfer more then 100MB)