Notices by thisisaaronland (thisisaaronland@orthis.social)

recently I reverse-geocoded all 170M venues in both the overture and foursquare open data releases / assigning each record a who's on first parent ID and hierarchy / there are still some open questions about how to encode and distribute the results / but as part of figuring that out I have published all the data for the US using the current working model / here: https://github.com/whosonfirst-data/whosonfirst-external-foursquare-venue-us and here: https://github.com/whosonfirst-data/whosonfirst-external-overture-venue-us

@evan @timbray @stefan @Gargron @ricmac it also feels like some of the concerns are really proxies for anxieties around the cold hard reality of the ongoing usuability and onboarding challenges that a big centralized (and well-financed) service like threads doesn’t have to deal with and, by extension, why they are able to attract a volume of participants who genuinely don’t care or have the time to care about how “the sausage is made” - 2/4

@evan @timbray @stefan @Gargron @ricmac I think there is a measure of wishful thinking (generally) about what it would mean for AP services to be on the receiving end of the threads-scale traffic necessary to make bi-directional sharing work and in fairness to the threads crew they may be hard at work trying to address that but if I understand @ricmac ‘s argument then I am sympathetic to the critique that at this point threads is violating the spirit if not the letter of the AP spec 1/4

@evan @timbray @stefan @Gargron @ricmac I am not sure I follow the thread behind the comment about sfo museum accounts switching services but in as much as we may eventually move all the AP work to another subdomain I guess maybe we might in that we will have to notify all the existing subscribers of the change? data portability across instances risks getting me started about “artisanal integers” so I will hold off on that until someone actually asks me about it 4/4

@evan @timbray @stefan @Gargron @ricmac the sfo museum AP accounts are publish-only at the moment largely out of expediency because that work is only one part of everything which needs to happen in a day and because it shines a light on some larger issues and challenges in the museum sector unrelated to AP itself; the long and longer discussions of those issues are here: https://www.aaronland.info/weblog/2024/10/26/exuding/#mcn24 and https://www.aaronland.info/weblog/2024/04/26/matrix/#usf 3/4

as promised / the @instagram account will automatically send you a new post as soon as you follow it / this is made possible by the addition of a general purpose “process follower” queue facility to handle follow events in the go-activitypub package – https://github.com/sfomuseum/go-activitypub/tree/main/queue#follower-processing-queues
https://orthis.social/@thisisaaronland/113488431335625693

“Gate accounts don’t publish anything at regular intervals (yet) but if you send them a private message with the text “nearby” they will reply with the list of galleries, exhibitions and public art that are within walking distance of that gate’s waiting area. The nearby functionality is derived from the SFO Museum Wayfinding system so each item listed also contains a link showing how to get there from the gate you’re “talking” to. “ – https://millsfield.sfomuseum.org/blog/2024/11/12/activitypub/

@evan @OldManToast there is a whole body of work from the before times about and around the idea of “social objects” / sadly those efforts mostly sputtered out for reasons best saved for tears-in-beers hour / but in the meantime it remains a conversation worth revisiting

@evan that object has not been published to the collection website yet / despite some perfectly reasonable “wait, but if…” questions / it does suggest that it should be possible to make a web finger-style query to an accession number though

@evan we also haven’t automated AP account creation when an object is published yet / all the AP stuff has been left to “bake” for a while to see how it holds up and to make room for other things / but I hope to spend some more time with it soon

@evan I am working on it / it’s not a technology problem – https://aaronland.info/weblog/2022/06/17/expectations/#usf-049

@evan @Edent the spec, such as it is, says the value / being everything after “=“ / can be anything including I suppose a whole other machine tag

@Edent @evan the “path_hierarchy” tokenizer makes it much easier to implement general purpose compound query and wildcard machine tag indexing and searching in open/elastic search these days / postgres etc still has the “left most index” problem to support all the possibilities unless something has changed recently – https://github.com/whosonfirst/whosonfirst-opensearch/blob/ee737f8b52501a9fbb69bb48de39f0586c1b36af/schema/2.x/mappings.spelunker.json#L62

@Edent @evan neither approach solves the interpreting values question which still needs to happen in code and convention / the long-really-long version is here – https://www.aaronland.info/weblog/2010/04/14/structure/#mw2010

@evan tell:me=more

@evan paging @simon to the courtesy https://en.m.wikipedia.org/wiki/Lanyrd conference phone

have you ever wanted / a "simpler and dumber geojson.io" but for geoparquet files / I did, so now it has started to exist – https://github.com/sfomuseum/go-geoparquet-show

@ricmac @laurenshof @evan I am working on it / the challenge is not technical (we could do it yesterday) so much as organizational (and not limited to sfo museum) / and then further complicated by concerns over who has the authority to speak on behalf of those works particularly in the case of living artists / and if you think that museums should proactively work to facilitate those voices on behalf of artists and their estates / then we agree – https://www.aaronland.info/weblog/2022/06/17/expectations/#usf-049

@jessamyn @anildash there is a whole other side-car (clown-car?) discussion about whether or not a limit on the number of photos in a gallery is meaningful / but the motivation behind the “galleries” project at flickr was to explicitly try and push back against the fetishization and dysfunction of the “explore” and “interestingness” algorithms / and demonstrate to people that their understanding of the site was better than robot-eyes or math / https://blog.flickr.net/en/2009/09/14/galleries-unleash-your-inner-curator/ and https://www.aaronland.info/weblog/2010/04/05/milkshake/#buckets

I have finally written up the notes from the talk I gave to a #museum studies class at usf recently / this one is long even by standards and covers a lot of ground / it is titled "talking about the pen without talking about the pen" – https://www.aaronland.info/weblog/2024/04/26/matrix/#usf