Anyway, I hope webrecorder desktop clears up most of the hassle. There was literally no other way I could think of to get posts and comments from my account.
Facebook's own download function was useful mainly to get me the URLs for my posts, which I fed into webrecorder to take the uncertainty out of the news feed algorithm and make sure I really got every post.
When I was done, I changed my Facebook password to be safe. Towards the end of the process, which was a full weekend of clicking, Facebook started treating my behavior as suspicious and I was having to sign in and complete captchas every few minutes.
Access to those WARCs isn't great: I don't really have a search and I have to spin up a VM to serve them, but the rendering with pywb is remarkably faithful to vintage 2016 Facebook.
Years ago, when I was about to delete my Facebook account and webrecorder was architecturally a bit different and I was routinely in and out of virtual machines, I set up my own webrecorder VM to capture just my own Facebook to WARCs.
The fact that it was possible to do this without knowing the internals of how webrecorder worked has always impressed me. It was a little weird to have all the account management functionality on my own locally hosted version, but I just ignored it.
I don't have anything to capture with webrecorder at the moment but it's interesting to see the mention here that the server version could potentially capture passwords.
I'd always wondered about that and avoided the hosted version for anything requiring a login.
This San Jose State MS admissions FAQ is unintentionally revealing of not just the types of questions they must get, but also the phrasing:
Q: I need to know NOW whether you will accept me later, so that I can decide whether I should try applying at a different department or university.
Q: I was accepted with a condition, but I don't like the condition. Can I negotiate to have it waived or changed?
I know that this program to get a CS BS for people who already have a Bachelors degree exists
and even predates the MOOC craze. But it's basically at least a two-year degree if you also have a job.
I forgot AMIA-L is a moderated list. I guess that's probably not a bad thing. I was just confused by Gmail's filters putting my send message in my AMIA folder.
Not entirely related, it took a while for me to remember that moderation online generally used to mean identifiable people visibly doing moderation things, unlike today's hellscape of deliberately obfuscated labor. I need to read https://yalebooks.yale.edu/book/9780300235883/behind-screen
TFW what you thought was a throwaway digipres joke surfaces as a serious proposal
Here's a weird and slightly spooky 1-minute trailer(!) I made for the upcoming jpylyzer 2.0.0 release (don't miss out on the audio on this one) https://youtu.be/gIutpFxGy28
Signs you are working with custom-built in-house software:
it's easy to do one thing at a time but not a batch
you can do batches but the batch interface is totally different from one at a time
you can add data in a batch, but you can't make changes in a batch
you can add data in a batch, but you can't delete in a batch
you can add data but you can't delete
if there's an administrative interface, it was clearly built after the public-facing interface, and probably by different people
It makes me think what we were doing at the museum was a lot more on the edge of things than I'd thought.
"bio" : "basic input output"
Digital Archivist, posting mostly digipres-related content at this account, with some general spillover from work/life. (He/him)
digipres.club is a space for folks interested in productive conversations about, well, digital preservation! If you enjoy talking about how to do memory work with computers, or even with cardboard boxes of old photos, you belong with us on digipres.club. Many of us are/were Twitter users looking for an inclusive and community supported approach to social media. If any of these things sound good to you, consider joining us now.