@andrewjbtw exactly the kind of question I love forcing Brandon to answer as a lawyer

馃捑 Have questions about building a video game collection? Wondering how the DMCA affects access to your collection?

Join the Software Preservation Network and our expert panelists (including folks from the Video Game History Foundation, the Harvard CyberLaw Clinic, and the Strong Museum of Play) for the Fall 2022 SPN Forum discussion 鈥淏uilding a Video Game Collection: Community Q&A":

softwarepreservationnetwork.or

@anj also yes to just constantly/regularly reminding people that it (and qanda.digipres.org) exist. I feel like I'm repeating myself all the time when beating the drum on EaaSI resources, but (as the survey I just put out proved), I'll often think that something didn't register or isn't of use to folks and it's really just that it hasn't broken through the considerable noise

@anj I like the Awesome List idea! Like you say, it's a worthy idea to have as a portal (I was just trawling the sample corpuses on there the other day!), so it seems like the main issue is clearing up formatting (again I'd agree with your thoughts in the GitHub ticket, probably remove the buttons, etc.) and trying to ease contribution/maintenance as much as possible for yourself and others so it can keep up

to that end also: maybe some clear instructions for adding/contributing new links?

@joe @anj I've also struggled a bit with how thoroughly to push this instance given, as you say, it's wound up being a slightly different kind of community/support rather than a drop-in digipres twitter replacement (e.g. like you say, less live-tooting/discussion of conferences), so it's a little hard to summarize

I feel like the folks who "get"/intuit/want that difference stick around though, and never any harm nor foul in encouraging more folks to give us a whirl!

the queasy relationship between forensic tooling and digital heritage/cultural archives is well-covered at this point, but sifting through examples like "a fun-to-solve university harassment scenario" just to get some sample files is making we want to barf

Show thread

Is anyone aware of a set of sample EWF/E01 disk images *other* than the ones on Digital Corpora? (or would be willing/able to send some examples for testing purposes?)

trying out a few things for a possible BUF proposal on forensic imaging -> emulation workflows and I worked through the DC ones (which would do the trick for a demo but I'm curious to attempt others)

Made a couple critical tweaks to Qiwi that make me feel more confident moving it from "alpha" to "beta" status and seeking more feedback!

Do you use QEMU on the regular, particularly for retro-computing/emulation? Please give a try and leave comments/tickets so I can improve!

(M series Apple testers esp wanted since I don't have that hardware!)

gitlab.com/EG-tech/qiwi/-/rele

@ashley @anj no worries!! I appreciate the sanity check that that's like, the way people would do it; I am sure I will start learning more of the actual differences between GitHub and GitLab now that I'm doing something more complicated than just docs

ok first release and pre-built versions are up! macOS .app bundles are even wonkier than I realized so I'd probably still just recommend using the qiwi.py if you're at all CLI savvy, but will keep working on that

gitlab.com/EG-tech/qiwi/-/rele

@ashley @anj unless I'm missing something on GitLab, you have to provide a link to external storage for any non-CI-generated assets; they don't let you just upload arbitrary files to attach to a release (which I guess makes sense for their costs and not accidentally becoming a storage service for non-code)

I can just use my Nextcloud for that for now, will have to look into other options later

@axfelix right - I'm fine/resigned to that and I think have the ability to build for each platform (M1 macOS is TBD)

so maybe this question is even dumber than it seems and is just: where do I...put the files once I have them? GitLab seems to assume you do everything through CI, even when, as you say, that's not an option here

Q for dev folks:

I am very new to deploying anything on CI/CD beyond static sites. I've made a lil Python app and want to package it up with pyinstaller and share the various executables as assets on a release in GitLab. Is there no way to just upload executables I've bundled locally? Do I have to figure out GitLab CI jobs for pyinstaller? I don't get how that would work for making macOS/Windows versions (also don't like automating until I've had a chance to do something myself at least once)

@axfelix cool, yeah, I tried out pyinstaller and once I sorted out the trick for including supplementary data like images, it worked quickly to make a binary compatible with BitCurator/Ubuntu 18.04; but then I got tripped up making a first run on macOS (Big Sur VM). but I think I worked out what I was doing wrong and am going to give it another go today on my older MacBook running Mojave

Who wants to help me test a new thing?

gitlab.com/EG-tech/qiwi

(and/or has advice for packaging wxPython/Gooey-based python apps for macOS and Windows?)

@platypus yessss I figured MA's would be the dinosaur footprints! one of my absolute favorite parks to go to. it's the best b/c there's so many that they don't try to rope them off or anything, you just walk around literally in the footsteps of some triassic-era lizard

(tl;dr - we gather a lot, send a lot to Wikidata, but most of it's not actually standardized or integrated directly into the EaaSI platform! read on for more detail on our thought process, influences, and needs though)

Show thread
Show older

Hometown is adapted from Mastodon, a decentralized social network with no ads, no corporate surveillance, and ethical design.