#geosocial #fediverse #fedigeo
@julian
@mat
et al.
This is about https://www.iso.org/obp/ui/#iso:code:3166:IO which will stop to exist „by the end of the year“ https://digitalcourage.social/@mat@friendica.exon.name

We will mark it as "deprecated" and send an `Update` then.
What else to do?

[we did assign the following already]
XK Kosovo
XF In Flight
XS At Sea (intl)

for "do nothing" or other, please comment

The monthly SWICG GeoSocial Task Force meeting is about to start if you have thoughts on location data use cases and the social web.

https://www.w3.org/events/meetings/ed630a3d-7581-4053-9978-75949ad42f2a/20260108T130000/

#geoSocial #GeoSocialTF #SWICG

#SayWhere Geocoding System: Human-Memorable Geographic Coordinates
[ based on #geohash ]

 https://datatracker.ietf.org/doc/draft-saywhere-geocoding/

#geosocial #geodata

Notes from the 2025-11-13 @socialcg Geosocial Task Force meeting

https://hedgedoc.socialweb.coop/s/H4O8EhObI

#geoSocial #SWICG #fediDevs

I just stumbled upon @socialcg's Geosocial efforts and added a bit of my perspective on public transit checkins https://github.com/swicg/geosocial/issues/20. Would be really cool to have these on the social web :)

#geosocial #travelynx #träwelling

We're experimenting with federated geosocial features in Bonfire, free from surveillance capitalism.
Check into your local community garden. Add location to mutual aid requests. Find tools nearby.
Imagine your local fablab or community center sharing check-ins, calendars, events, opening hours - all federated. A living hub for what's happening there.
🔧 https://github.com/bonfire-networks/bonfire-app/issues/1444

This unlocks new possibilities for local organizing, let's explore together 🔥

#Geosocial #CommonsEconomy #Fediverse

Seeking interop testing for geosocial ActivityPub client

Hey, all! I’m seeking some help testing an application I whipped up for the Geosocial task force of the W3C Social Web Community Group. It’s called https://checkin.swf.pub/ , and it’s a barebones checkin service, similar to Swarm, but implemented as a pure Web client. You can watch the application in action.

https://videopress.com/v/zCMu0OeZ?resizeToParent=true&cover=true&preloadContent=metadata&useAverageColor=true

It logs into your account on an ActivityPub server using OAuth 2.0. It […]

https://socialwebfoundation.org/2025/07/14/seeking-interop-testing-for-geosocial-activitypub-client/

The monthly meeting of the @socialcg Geosocial Task Force is starting now!

https://www.w3.org/events/meetings/ed630a3d-7581-4053-9978-75949ad42f2a/20250710T130000/

#geosocial #SWICG #fedidevs

@Jeremiah #geosocial
working now on a compact representation of all the geo things described in https://github.com/w3c/activitystreams/issues/582#issuecomment-2498916869

It is for a kv store which would play nicely with fedify @hongminhee

I have a question about the conversion of as:Place properties to the geo: uri scheme cause I am pretty bad at math.

Can we convert geo: `Uncertinty` to as:accuracy ?
https://en.wikipedia.org/wiki/Geo_URI_scheme#Uncertainty

And:
The most compact representation would be geohash again but then we might loose some precision if it is "certain".

E.g. the link
geo:37.786971,-122.399677;u=35?info=a

is normalized to a kv key array (like any link by user/pw, host, pattern or path, parameters, hash, search etc.)

resulting in e.g.
2|9q8yywzm0ccy|;35|?info=a
but reversed then to

geo:37.78697108,-122.39967691;u=35?info=a

[semantically ok cause uncertainty but not strictly equal]
But can we calc what uncertainty means e.g. 1 floating point of the coordinates?

btw: enums, using fedidb for constant host shorts, most popular have then 1 byte, then 2 :)