I know the Internet Archive has been under a ton of infrastructural pressure lately, but anyone have any idea about how long they might take to review an application and get back to you?
-
@aud oh good
-
Asta [AMP]replied to Asta [AMP] last edited by [email protected]
@[email protected] To that end, I think what I've spent most of my time thinking about re: this is:
1. How do we ensure data integrity?
2. How do we make it easy for people to contribute, audit, curate?
3. How do we help build trust?
4. How can we distribute the computational and mental workload necessary to ensure knowledge is preserved and discoverable without corruption?
And then, finally, 5. search algorithms on said data.
(these aren't really listed in order of technical importance; for instance, point 5 absolutely will end up informing points 1 through 4. But, you know, just talking about what I think the goals should be). -
@aud we for sure have thoughts on all those, we'll try to get them together after this meeting
-
@[email protected] I've got some CV updating to do (well, making a separate CV for lab positions and then applying to them) today but I'm willing to bet your thoughts are slightly more formalized on this. Especially as I've largely been thinking about how the technical aspects of scaling out would work (I mean... makes sense, a lot of my experience is HPC).
-
Fuck it, gonna fix an issue on the GitHub, get myself noticed
-
@aud yeah do it
-
@[email protected] I don't think what they're asking for is particularly complex and we actually did stuff like this when I worked at Microsoft so?
But when I submit the PR we'll see -
@aud fix around and find out
-
maybe I'll try and fix the
docker composew/ podman issue that exists after this. -
https://github.com/internetarchive/openlibrary/pull/10015 welp, it's been a sec since I've tried to fix and test something in a large python code base. Hopefully I don't get laughed out of the room.
-
squeaky worm gets the sweet sweet grease motherfuckers
(I mean, potentially) -
@aud would be very difficult to get laughed out of the room by contributing code
-
@[email protected] fair enough! I also went into their gitter channel and was like " I put in an application for a job at the IA so I decided to also try and fix an issue while I was at it to draw some attention to myself (but also just to help out in general)
"
subtle! -
@aud that is useful info for them to know!
-
@[email protected] right!? why not. Worst case scenario, I spent 30 minutes remembering how to do stuff in Python and some REST api stuff and contributed some code that either works as is or could be worked into something that fixes the problem in a way they need.
-
@aud so, belatedly... pieces like this make us wonder if the idea of searching the entire web is just over https://www.giantfreakinrobot.com/ent/independent-ends.html
-
@aud we wonder if there's a way to, like... make the act of curation into something more social
like, the early post-based social media platforms may have thought of themselves as doing that, but the artifacts they produce are fundamentally bound to a moment in time in the sense that you can't make sense of them without knowing the person and having the same social context they did when they wrote it
-
@aud our thinking here is that when it's a communal activity, people are more likely to see it as important, which is necessary if it's going to be a long-term pattern
-
@aud we also want to call your attention to this art project which is, essentially, a curated "catalog" of physical stuff you can get free directions for making (and source code, where applicable)
-
@aud in the past, when we've seen people do lists of favorite projects as github notes repos or whatever, it's felt like the lists are both too hard to get actionable information from, and too un-memorable to go back to when we have a need for them. this addresses both problems. it's particularly fascinating because paper catalogs are nowhere near as common as they used to be...
