Blogbastelei
General Discussion
1
Posts
1
Posters
0
Views
-
Blogbastelei
Nur ganz kurz, das ActivityPub Plugin ist wieder aktiv. Eigentlich hatte ich es nur nochmal installiert weil ich was nachschauen wollte. Dann habe ich mir gedacht, ich lasse jetzt mal drin.
Vielleicht kann ich es tatsächlich demnächst mal brauchen, mal sehen.
Man kann dem Blog also wieder im Fediverse folgen unter: @blog
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Then it once sends an Update to all attached taxiteam machines meaning „Hey there, we are new and geocode ["u1"]“ (or ["u1r","u1w","u1x"]) then the network knows.
Now any taxidriver can add infos, warnings etc. directly.Next time when a user clicks on a map, we once decode Lat/Long to geohash, if your own instance doen't have it, it can ask the best suited option (e.g. serer proximity, load or trust).
As smaller the instance area is, as more detailed infos about em places ith might have :)
User now knows "You clicked on Fischmarkt Hamburg but unfortunately the area is currently flooded. Flashflood warning, go away" -
well, or maybe " … and your cab arrives in 1 minute" or "… cool exhibition nearby" or whatever.Sorry if I got either too complicated or short :)
We have frequent team mmetings, next is Saturday but I am also looking forward to the dev meeting with @reiver re. https://digitalcourage.social/@reiver@mastodon.social/115317680720978044🧵 3/3
-
The hoods have then all the street addresses, relations, boundaries like places.pub (with icons cached static etc. pp).
So, you know all the administrative parents from any address -
but what makes it really special is that any taxiteam instance could add info to any address (just as with your annotated places …).
As said, described it just very briefly in https://github.com/w3c/activitystreams/issues/582
It includes federated _reverse_ geocoding too but Lat/Long would not be cool for this, so we use geohash for the Service Actor.
https://en.wikipedia.org/wiki/Geohash https://geohash.softeng.co/Let's see a practical example:
A new fair
taxiteam forms in any city to "FCK UBER". They install an instance and choose a geohash they would like to geocode.
E.g. the square for Hamburg and some other cites.
These might overlap, it doesn't matter cause geohash is strictly hierarchical too.
We do also have a server for all Germany by default, anyway:
The instance once fetches the cache of needed infos up to street addresses.
🧵 2/3
-
cool. I am doing funded work for taxiteam and menschys and for redaktor (CMS) and Public Spaces Incubator (EBU and Public Broadcasters), fulltime, anyway :)
About places.pub - did post the code to federate OSM a long while ago https://gist.github.com/sebilasse/ca76c60955e5414cff2c253f1cd89af4
this snippet comes with a bunch of other modules.
An OSM to JSON-LD proxy like places.pub is super nice but what we need in taxiteam is a bit more.
Our database is a consolidated cache of OSM and wikidata knowledge but organized as hierarchical Collections, both political-administrative as well as by geohash.
So, if you are down to Country "DE"
https://gist.github.com/sebilasse/9b4c50bfabad43879c9c43c3adbe9ca1 it is a Collection of Federal States with its own id (2nd file).
With ActivityPub, we have the ability to define these hierarchies starting by Collection Q2 having the M49 regions as items with ['Collection', 'CollectionPage'] and that goes down to e.g. country/state/adm3/city/district/suburb/"hood" …🧵 1/3
-
Interesting point. Age verification laws around the world are going to make everything a lot more tricky.
Though Mastodon's argument doesn't make sense to me: IP addresses inherently map to location data, so we all receive *some* location, whether we're listening or now.
I don't have a good solution for this, right now.
It'll probably need to be baked into new user registrations, which admins would need to choose in some way.
Do you have a solution you'd recommend?
-
Yes. Great point. And UX and privacy are both top concernse of mine.
So, #Emissary's default registration options ask for very little information: name you want to use, public-facing username, and an email address where you can receive notifications.
This should be enough to provide anonymity for those who require it, while still allowing them to build trust and reputation with their community via this new identity.
-
@ben Ha! I'd have figured the exact opposite 😅
Even as someone who'll never stop whining about how hard it is to get ActivityPub going, 3D graphic and Augmented Reality seems (to me) like another level of work altogether.
So, if you happen to know someone who could take a list of addresses and map it into a 3D space...
Let me know if you're interested in this? I could easily give you a JSON file of annotations tied to your current location.
-
Somewhat relevant, I believe mastodon's argument for not supporting age verification is that they don't collect location data and so there's no way for them to determine if their users are somewhere where age verification applies. I don't know how well that works on legal grounds, but probably worth thinking about if you're building social apps that require geolocation
