zlacker

>>g0xA52+(OP)
Bluesky is very useful to store information on users' existing accounts.

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.

>>maelit+WC
Wait, what? Please don't do that, use mangrove.reviews instead please. They use clear CC-BY-SA licenses; MapComplete.org uses it

Bluesky _will_ enshittify sooner or later

>>pieter+tl1
Mangrove has almost nothing in its DB, no news for years, and a broken website.

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...

>>maelit+Xm1
Except that it got around 2.9K reviews by now, which is more then you have right now. Furthermore, we shouldn't further fragment the few open source review efforts we have.

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

>>pieter+Bp2
> Many OSM apps will also be reluctant to adopt a closed source solution that might be closed of any moment.

Bluesky is not closed-source, it's mostly open. It's a hard mastodon-circle myth. Aside from being open-source, it's a protocol.

What I'm doing with Bluesky should be easy to reproduce with Mastodon, opening to 10 M accounts more.

People won't create an account to review. Not even a OSM account. We need to build on what's available, and ATProto is spot-on for this usage.