Working on a FediHood-inspired "Nearby" feature for Catodon. Since FediHood's development has halted, I'm using it as a base, but without being restricted by it. I'm trying to build this not only thinking of Catodon's implementation, but with fedi on my mind, since we don't have a standard for location, and it could be useful for a lot of cases (events, marketplaces - even a federated dating app could use something like this, why not). So once I'm done, I'll propose two FEPs, so that other projects can also build on this.
#catodon #fedihood #fediverse #activitypub #fep
1 Boost
0 Likes
@sl007@digitalcourage.social no, I didn't know Ben's Atlas, will take a look and see if there's any common ground with our implementation, thank you!
While you’re there, look at this.. It’s the same idea as Atlas, but with a per-user map: https://qwerty.social/@6af0adf8945d63cfa435f2fd?tab=6af0f09e8dbc6ee2aa3fb002
On standards, I think the most important issue will be to lock down how we represent addresses. A good start would be a mandatory lat/long, with optional fields for location name/address/city/region/country.
Next might be making location optional on user profiles, too.
From there, everyone could query “what’s nearby” on their own.
@panos
It would be nice to have a decent meeting about Places in ActivityPub.
Have you seen Atlas by @benpate ?
It would be nice to have a common ground.
We are currently in a mess because of the "deno situation" but I did write down how we use Place in our code (small team, financed by private people):
https://codeberg.org/Menschys/fedi-codebase/src/branch/main/README.md
Especially for a feature like "Nearby" the use of geohash for automatically geographical indexed AP Collections might be interesting.
imho lat/lon-only is not the best for the fediverse.