@benpate Ben this is so impressive!

I can’t come up with coherent comments or questions just now but I’m definitely tuned in and pondering how this connects to all my Future Cities/civic tech tangles.

Cc @samnabi this is one of the “somebody had an idea sometime around FediForum two weeks ago and now there’s a whole new dimension…” things I was trying to explain. I will include Ben’s FediCON talk in what I send you, as well.

@benpate this is pretty exciting! do you have any idea what safety features will look like? would you build something into it that, say, actively prevents others from doxing someone?

@benpate love what you’ve done so far. Can see so many uses. There’s a definite need to have ‘private’ tags / entries as well as public ones.

@benpate Super cool! I wish the README had instructions on how to run this

@benpate ooh!

Better Atlas than the other one. A couple of questions:
- are you envisioning this to be a federated Foursquare or Yelp?
- inserting location tags to people's posts increases their personal data exposure quite a lot. What privacy implications do you see here?
- I didn't catch in the video what is the identity model you're basing this on. New identity on Atlas, or a tie-in to an existing fedi identity?
@benpate

@benpate This is really great! One project that could very well be a nail for this hammer is https://wanderer.to !

osma@mas.to benpate@mastodon.social I'd assume that if you're using Atlas that you're explicitly aware that the location data is being broadcast out, yeah?

I'd imagine it to be akin to an opt-in mechanism.

I think we have enough evidence by now to know that even people who should have training to know better, accidentally reveal too much on apps, and that location is a particularly sensitive item.

https://dl.acm.org/doi/10.1145/1978942.1979295

https://www.runnersworld.com/uk/news/a40358143/strava-israeli-military/

https://www.securityweek.com/fitness-app-strava-gives-away-location-of-biden-trump-and-other-leaders-french-newspaper-says/

@julian @benpate

@julian @osma @benpate  I don’t think that an app should tie my physical location to posting about a location, and it is not necessarily true that you need to be there to talk about that location.

And that could be anything from trip advisor like blog posts and reviews to boosting and chatting about social activism or events happening at a location.

For example, I may want to location tag Yosemite when writing about the current lack of funding to protect the land from human aggression. Or I would want to do so when writing about my experience at the top of Half  Dome decades ago as part of a shared human experience.

@benpate this could be fun for geocaching

@ddlyh Cool. And thank you. I'll check it out. I can't really compare features until I've done the class reading --but Atlas is pretty bare-bones right now, so I'll have a lot of catching up to do for anything that's already out there.

The good thing is that Atlas is an empty slate, and we can make it do whatever we need.

So, for favorites: is this to mark locations in your inbox as "favorite" locations to review later?

What are the important things we should put into this app?

@rimu Hey Rimu

I'm running this in an iOS simulator just to show the mobile theme, but this is 100% a web app.

There are many uses for this kind of geotagging. I won't be hosting a public Atlas server, but others communities/organizations can launch their own for whatever purposes they need.

@ben Yeah, I really wanted to post comments on some billboards I saw on the freeway. Augmented Reality is beyond my current skillset -- and to make it work, we'd probably need to build out an AR ecosystem on the Fediverse, too.

Hopefully tagging addresses/locations is enough of a step forward that we can find some good uses for this.

@benpate I think the federation is the hard part. I think writing the actual AR application is probably pretty straightforward, at least for developers who are already familiar with their AR platform. (I don't know visionOS or whatever Meta uses, but I know iOS and I doubt it's that much different.)

@sl007 Yes, I'd love to work together on geocoding, too.

Right now, there's not much to it..

I'm using commercial geocoders to translate addresses into Lat/Long, then including that in 1) the ActivityStream document, and 2) the search results.

I'd love to work with https://places.pub in some way, but I'm not sure (yet) what that integration would look like, or what we'd get out of it.

So yes: let's keep talking about how we make this seamless. There should be one standard, not six

@julian @evan

Hey Julian..

I would love to integrate with places.pub, and I have this on my list of bookmarks for research.

I'm not sure what that would look like, just yet. Right now, the `Place` isn't its own actor, but just an extra set of data on a `Note`.

Maybe I could use places.pub as a datasource to look up previous addresses? I'm still researching, and would love to get your suggestions

@computersandblues

I'll build whatever people say is most important. These policies will likely be up to individual server owners.

After spammers found Bandwagon, I've been kicking around ways to do moderation before profiles and posts become public.

But whether we're using maps or toots, the issues would still be the same. Bad actors will need to be identified quickly, and dealt with decisively.

I'm adding this into the project board. Feel free to pile on: https://github.com/orgs/EmissarySocial/projects/3/views/1?pane=issue&itemId=135226795&issue=EmissarySocial%7Cemissary%7C566

@RossA Yes. And this is a really good point.

I'm planning to use Emissary's "Circles" for this (https://emissary.dev/circles) which let you limit posts to certain people. I'll show this in the next video.

And right now, Atlas also has disappearing messages that auto-delete after a set period time.

Nothing on the Fediverse is 100% private; it's always possible a remote server might share your "private" posts with unintended people. But this should help limit comments in most cases.

@decibyte Sorry about the README. Right now, Atlas barely runs on my own development laptop.

I've added a lot of new stuff into Emissary to support geolocation, and that still needs to be merged and posted to Github.

But, I'd love to work with you to see this run on your machines - even if it's still an early draft.

I'll have a super-rough-preview release ready in the next few weeks. Let's try to talk then and I'll help you get it running.