#code4lib — Public Fediverse posts

I'm running updates on the servers, #code4lib, so you may experience a few hickups.

#code4lib Who runs the server Planet Code4Lib is on? Any C4L people here know?

Time for a few updates, #code4lib !

#code4lib journal has a call out for articles about the use of #staticsite publishing:

> Contributions from any practitioner working on digital publication are welcome, regardless of the stage or sophistication of the publication’s development. This includes boutique, shoestring publications ... as well as large-scale projects that rely on institutional backing, development teams, practices, & infrastructure.

https://lists.clir.org/cgi-bin/wa?A2=ind2603&L=CODE4LIB&P=27708

Note for #code4lib: I'm starting server updates, so you may experience a few hickups.

I've made a blog post out of my recent lightning talk at #c4l26, sharing some ideas I've been contemplating lately while in libraries and on trails.

The post includes my full text, links to sites and images shown in the talk, and some bonus links for context (including a book link that @platypus gave on the conference Slack channel).

My thanks again to the #Code4Lib community for hosting the event, and to everyone there for their contributions and participation!

https://everybodyslibraries.com/2026/03/06/trails-and-tours-in-library-online-environments/

Enjoyed hearing talks and meeting people at #c4l26 this year! Especially impressed to be meeting with a group which, as one participant put it, moved the whole conference across the state rather than compromise its values. (And for pulling that off on short notice, I'm willing to forgive any glitches I've encountered, not that I had to deal with any major ones.) Thank you as well to the many volunteers and site staff that made it a pleasure to join #Code4Lib in Philly!

I'm seeing #c4l26 projected on the screen at the #Code4LIb conference in Philly, so I'm going to assume that #c4l26 is this conference's official hashtag for people posting on social media. Don't know how many attendees are posting in the fediverse, but hi to those who are here!

(The conference also has a Slack channel for discussion among attendees.)

I'm boarding a train to #philly this morning for the Penn Linguistics Conference and then #code4lib -- & hopefully a trip to @iffybooks for the #permacomputing meetup. Fun times can happen.

Today, I released version 0.2.0 of a new tool that processes MARC-21 records. It focuses on efficient processing of records and tabulating data for integration into data science or data engineering applications. Feedback and new ideas are very welcome.

https://github.com/deutsche-nationalbibliothek/marc21-rs

#code4lib #marc21 #metadata

finally was able to get analytics on our catalog and it was sad that: we only had 1.2k searches over 3 days so far (I don't track what's searched, created an event just whether a search is made & what value is from the drop-down menu is selected also surprised that 99% of searches use the default value in the dropdown (i expected default to be high but not that high; fortunately, i may be able to change this vendor provided layout) #code4lib

I sent a donation to #Code4Lib's diversity scholarship fund, after I'd heard that CMU had pulled support because of it, and that the Code4Lib community had committed to keeping it. If you'd like to support it as well, donation links are on this page: https://2026.code4lib.org/general-info/scholarships

If you haven't registered yet (it's not yet sold out), you can also add a donation with your registration, though if you're getting reimbursed you may need to ensure you distinguish the registration fee from your donation.

A federal judge formally dismissed the NEA/ACLU lawsuit against the US Department of Education, after an agreement that the DoE would not attempt to enforce the anti-DEI "Dear Colleague" letter they sent schools last year: https://newhampshirebulletin.com/briefs/new-hampshire-judge-announces-formal-end-to-trump-policy-against-dei-in-schools/ Here's the motion to dismiss: https://storage.courtlistener.com/recap/gov.uscourts.nhd.65138/gov.uscourts.nhd.65138.99.0_1.pdf. and the original letter: https://www.ed.gov/media/document/dear-colleague-letter-sffa-v-harvard-109506.pdf

Some schools are still cautious, though, which is why #Code4Lib is now in Philly and not at CMU: https://americanlibrariesmagazine.org/2026/01/23/one-year-of-the-trump-administration/

#USPol #HigherEd

As of this morning, there are still some seats available for #Code4Lib 2026, which is being held in Philadelphia the first week of March. I hope to see you there! Their site now has a full schedule, and links for registration: https://2026.code4lib.org/

wow JUST now hearing about what happened with the #code4Lib conference...good on the code4Libbers for keeping the diversity scholarship AS IS :meowflower:

Hey #code4lib, we're at the latest Mastodon again – in case you wondered about the hickups.

I wonder if it might be fun to arrange a fediverse get together (lunch, coffee, something) in person at #code4lib?

The registration for #code4lib 2026 in #philly (the conference that wouldn't be cancelled) just opened:

https://concentracms.regfox.com/code4lib-2026

more at: https://2026.code4lib.org/

(it is 2026 isn't it?)

Code4Lib Journal is seeking new editors to join our editorial team! If you have a passion for editing and library technology, please consider joining us! https://journal.code4lib.org/call-for-editors #code4lib

@rwg if you feel like that might be your crowd and platform, there is a nice and busy #bots room on the #Code4lib slack.

@ink #code4lib

Hey #code4lib, I did something: when you open a post from another server that is older than 5 minutes, you should see all replies after a short delay. Code4lib.social fetches replies from other servers, up to a limit.

I'll try to keep an eye on the database so that this doesn't make the server explode 😇
Do feel free to help sustain the server: https://code4lib.social/@bencomp/115416566159449225

Hey #code4lib-dot-social, if you could have another look at https://liberapay.com/kayiwa/ to help with paying for server costs, that would be great.

#Presentation: How to stay web accessible: Applying #WCAG 2.1 & 2.2
#websites #a11y #weba11y #libtech #code4lib #c4lbc

https://cynthiang.ca/2025/10/16/presentation-how-to-stay-web-accessible-applying-wcag-2-1-2-2/

Revisiting bsdiff as a tool for digital preservation

by @beet_keeper

I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

#ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

Revisiting bsdiff as a tool for digital preservation

by @beet_keeper

I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

#ac3 #archives #audio #audiovisual #audit #authenticity #av #bash #bsdiff #checksums #code4lib #corruption #corruptionIndex #digipres #digitalArchiving #digitalForensics #digitalLiteracy #digitalPreservation #digitalStorage #diplomatics #fileFormats #glitch #glitchAudio #glitchart #integrity #preservationAnalysis #preservationMetadata #provenance #sensitivityIndex #storage

Revisiting bsdiff as a tool for digital preservation

by @beet_keeper

I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

#ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

Revisiting bsdiff as a tool for digital preservation

by @beet_keeper

I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

#ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

Revisiting bsdiff as a tool for digital preservation

by @beet_keeper

I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

#ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

We're hosting #Code4lib #BC at Emily Carr on October 16 & 17. If you're interested in the intersection of #libraries #archives and #technology, join us!

Registration, proposals, bursary and more info: https://wiki.code4lib.org/BC

#Vancouver #Code4LibBC #LibTech

We're hosting #Code4lib #BC at Emily Carr on October 16 & 17. If you're interested in the intersection of #libraries #archives and #technology, join us!

Registration, proposals, bursary and more info: https://wiki.code4lib.org/BC

#Vancouver #Code4LibBC #LibTech

We're hosting #Code4lib #BC at Emily Carr on October 16 & 17. If you're interested in the intersection of #libraries #archives and #technology, join us!

Registration, proposals, bursary and more info: https://wiki.code4lib.org/BC

#Vancouver #Code4LibBC #LibTech

We're hosting #Code4lib #BC at Emily Carr on October 16 & 17. If you're interested in the intersection of #libraries #archives and #technology, join us!

Registration, proposals, bursary and more info: https://wiki.code4lib.org/BC

#Vancouver #Code4LibBC #LibTech

We're hosting #Code4lib #BC at Emily Carr on October 16 & 17. If you're interested in the intersection of #libraries #archives and #technology, join us!

Registration, proposals, bursary and more info: https://wiki.code4lib.org/BC

#Vancouver #Code4LibBC #LibTech

Version 1.4 of the Annif automated subject indexing tool has been released! 🚀

• 3 new corpus formats (JSON, JSONL, CSV) supporting metadata + document IDs
• Include/exclude vocab concepts for better control
• annif index now supports short-text formats
• Faster hyperopt with parallel processing
• tfidf backend refactored (no gensim!)
• REST API improvements & Python 3.13 support

https://github.com/NatLibFi/Annif/releases/tag/v1.4.0

#Annif #NLP #opensource #subjectindexing #machinelearning #code4lib #libraries

Version 1.4 of the Annif automated subject indexing tool has been released! 🚀

• 3 new corpus formats (JSON, JSONL, CSV) supporting metadata + document IDs
• Include/exclude vocab concepts for better control
• annif index now supports short-text formats
• Faster hyperopt with parallel processing
• tfidf backend refactored (no gensim!)
• REST API improvements & Python 3.13 support

https://github.com/NatLibFi/Annif/releases/tag/v1.4.0

#Annif #NLP #opensource #subjectindexing #machinelearning #code4lib #libraries

Version 1.4 of the Annif automated subject indexing tool has been released! 🚀

• 3 new corpus formats (JSON, JSONL, CSV) supporting metadata + document IDs
• Include/exclude vocab concepts for better control
• annif index now supports short-text formats
• Faster hyperopt with parallel processing
• tfidf backend refactored (no gensim!)
• REST API improvements & Python 3.13 support

https://github.com/NatLibFi/Annif/releases/tag/v1.4.0

#Annif #NLP #opensource #subjectindexing #machinelearning #code4lib #libraries

Version 1.4 of the Annif automated subject indexing tool has been released! 🚀

• 3 new corpus formats (JSON, JSONL, CSV) supporting metadata + document IDs
• Include/exclude vocab concepts for better control
• annif index now supports short-text formats
• Faster hyperopt with parallel processing
• tfidf backend refactored (no gensim!)
• REST API improvements & Python 3.13 support

https://github.com/NatLibFi/Annif/releases/tag/v1.4.0

#Annif #NLP #opensource #subjectindexing #machinelearning #code4lib #libraries

Version 1.4 of the Annif automated subject indexing tool has been released! 🚀

• 3 new corpus formats (JSON, JSONL, CSV) supporting metadata + document IDs
• Include/exclude vocab concepts for better control
• annif index now supports short-text formats
• Faster hyperopt with parallel processing
• tfidf backend refactored (no gensim!)
• REST API improvements & Python 3.13 support

https://github.com/NatLibFi/Annif/releases/tag/v1.4.0

#Annif #NLP #opensource #subjectindexing #machinelearning #code4lib #libraries

Für das Deutsche Literaturarchiv in Marbach habe ich vor einiger Zeit einen performanten OAI-PMH-Dienst entwickelt, um die ca. 3,5 Millionen bibliographischen Datensätze standardisiert in verschiedenen Formaten anbieten zu können.

Die Software ist selbstverständlich quelloffen und jetzt ist endlich auch die Dokumentation fertig.

#opensource #oaipmh #code4lib

https://github.com/opencultureconsulting/oai-pmh2

The first alpha version of Skosmos 3 has been published! This release provides a peek into the upcoming next major version of the Skosmos publishing tool for SKOS controlled vocabularies.

The release features a reimplemented front-end with a fresh layout and improved accessibility, as well as many architectural improvements and modernization of the codebase.

https://github.com/NatLibFi/Skosmos/releases/tag/v3.0-alpha.1

#Skosmos #SKOS #thesaurus #classification #ontology #code4lib #OpenSource

The first alpha version of Skosmos 3 has been published! This release provides a peek into the upcoming next major version of the Skosmos publishing tool for SKOS controlled vocabularies.

The release features a reimplemented front-end with a fresh layout and improved accessibility, as well as many architectural improvements and modernization of the codebase.

https://github.com/NatLibFi/Skosmos/releases/tag/v3.0-alpha.1

#Skosmos #SKOS #thesaurus #classification #ontology #code4lib #OpenSource

The first alpha version of Skosmos 3 has been published! This release provides a peek into the upcoming next major version of the Skosmos publishing tool for SKOS controlled vocabularies.

The release features a reimplemented front-end with a fresh layout and improved accessibility, as well as many architectural improvements and modernization of the codebase.

https://github.com/NatLibFi/Skosmos/releases/tag/v3.0-alpha.1

#Skosmos #SKOS #thesaurus #classification #ontology #code4lib #OpenSource

The first alpha version of Skosmos 3 has been published! This release provides a peek into the upcoming next major version of the Skosmos publishing tool for SKOS controlled vocabularies.

The release features a reimplemented front-end with a fresh layout and improved accessibility, as well as many architectural improvements and modernization of the codebase.

https://github.com/NatLibFi/Skosmos/releases/tag/v3.0-alpha.1

#Skosmos #SKOS #thesaurus #classification #ontology #code4lib #OpenSource

The first alpha version of Skosmos 3 has been published! This release provides a peek into the upcoming next major version of the Skosmos publishing tool for SKOS controlled vocabularies.

The release features a reimplemented front-end with a fresh layout and improved accessibility, as well as many architectural improvements and modernization of the codebase.

https://github.com/NatLibFi/Skosmos/releases/tag/v3.0-alpha.1

#Skosmos #SKOS #thesaurus #classification #ontology #code4lib #OpenSource

The sensitivity index: Corrupting Y2K

by @beet_keeper

In December I asked “What will you bitflip today?” Not long after, Johan’s (@bitsgalore) Digtial Dark Age Crew released its long lost hidden single Y2K — well, I couldn’t resist corrupting it.

Fixity is an interesting property enabled by digital technologies. Checksums allow us to demonstrate mathematically that a file has not been changed. An often cited definition of fixity is:

Fixity, in the preservation sense, means the assurance that a digital file has remained unchanged, i.e. fixed — Bailey (2014)

It’s very much linked to the concept of integrity. A UNESCO definition of which:

The state of being whole, uncorrupted and free of unauthorized and undocumented changes.

Integrity is massively important these days. It gives us the guarantees we need that digital objects we work with aren’t harboring their own sinister secrets in the form of malware and other potentially damaging payloads.

These values are contingent on bit-level preservation, the field of digital preservation largely assumes this; that we will be able to look after our content without losing information. As feasible as this may be these days, what happens if we lose some information? Where does authenticity come into play?

Through corrupting Y2K, I took time to reflect on integrity versus authenticity, as well as create some interesting glitched outputs. I also uncovered what may be the first audio that reveals what the Millennium Bug itself may have sounded like! Keen to hear it? Read on to find out more.

#ac3 #Archives #audio #audiovisual #authenticity #av #Bash #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #digitalLiteracy #DigitalPreservation #diplomatics #FileFormats #flac #glitch #GlitchArt #glitchaudio #integrity #mp3 #sensitivityIndex #wav

The sensitivity index: Corrupting Y2K

by @beet_keeper

In December I asked “What will you bitflip today?” Not long after, Johan’s (@bitsgalore) Digtial Dark Age Crew released its long lost hidden single Y2K — well, I couldn’t resist corrupting it.

Fixity is an interesting property enabled by digital technologies. Checksums allow us to demonstrate mathematically that a file has not been changed. An often cited definition of fixity is:

Fixity, in the preservation sense, means the assurance that a digital file has remained unchanged, i.e. fixed — Bailey (2014)

It’s very much linked to the concept of integrity. A UNESCO definition of which:

The state of being whole, uncorrupted and free of unauthorized and undocumented changes.

Integrity is massively important at this time in history. It gives us the guarantees we need that digital objects we work with aren’t harboring their own sinister secrets in the form of malware and other potentially damaging payloads.

These values are contingent on bit-level preservation, the field of digital preservation largely assumes this; that we will be able to look after our content without losing information. As feasible as this may be these days, what happens if we lose some information? Where does authenticity come into play?

Through corrupting Y2K, I took time to reflect on integrity versus authenticity, as well as create some interesting glitched outputs. I also uncovered what may be the first audio that reveals what the Millennium Bug itself may have sounded like! Keen to hear it? Read on to find out more.

#ac3 #archives #audio #audiovisual #authenticity #av #bash #checksums #code4lib #corruption #corruptionIndex #digipres #digitalArchiving #digitalLiteracy #digitalPreservation #diplomatics #fileFormats #flac #glitch #glitchart #glitchaudio #integrity #mp3 #sensitivityIndex #wav

The sensitivity index: Corrupting Y2K

by @beet_keeper

In December I asked “What will you bitflip today?” Not long after, Johan’s (@bitsgalore) Digtial Dark Age Crew released its long lost hidden single Y2K — well, I couldn’t resist corrupting it.

Fixity is an interesting property enabled by digital technologies. Checksums allow us to demonstrate mathematically that a file has not been changed. An often cited definition of fixity is:

Fixity, in the preservation sense, means the assurance that a digital file has remained unchanged, i.e. fixed — Bailey (2014)

It’s very much linked to the concept of integrity. A UNESCO definition of which:

The state of being whole, uncorrupted and free of unauthorized and undocumented changes.

Integrity is massively important these days. It gives us the guarantees we need that digital objects we work with aren’t harboring their own sinister secrets in the form of malware and other potentially damaging payloads.

These values are contingent on bit-level preservation, the field of digital preservation largely assumes this; that we will be able to look after our content without losing information. As feasible as this may be these days, what happens if we lose some information? Where does authenticity come into play?

Through corrupting Y2K, I took time to reflect on integrity versus authenticity, as well as create some interesting glitched outputs. I also uncovered what may be the first audio that reveals what the Millennium Bug itself may have sounded like! Keen to hear it? Read on to find out more.

#ac3 #Archives #audio #audiovisual #authenticity #av #Bash #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #digitalLiteracy #DigitalPreservation #diplomatics #FileFormats #flac #glitch #GlitchArt #glitchaudio #integrity #mp3 #sensitivityIndex #wav

The sensitivity index: Corrupting Y2K

by @beet_keeper

In December I asked “What will you bitflip today?” Not long after, Johan’s (@bitsgalore) Digtial Dark Age Crew released its long lost hidden single Y2K — well, I couldn’t resist corrupting it.

Fixity is an interesting property enabled by digital technologies. Checksums allow us to demonstrate mathematically that a file has not been changed. An often cited definition of fixity is:

Fixity, in the preservation sense, means the assurance that a digital file has remained unchanged, i.e. fixed — Bailey (2014)

It’s very much linked to the concept of integrity. A UNESCO definition of which:

The state of being whole, uncorrupted and free of unauthorized and undocumented changes.

Integrity is massively important these days. It gives us the guarantees we need that digital objects we work with aren’t harboring their own sinister secrets in the form of malware and other potentially damaging payloads.

These values are contingent on bit-level preservation, the field of digital preservation largely assumes this; that we will be able to look after our content without losing information. As feasible as this may be these days, what happens if we lose some information? Where does authenticity come into play?

Through corrupting Y2K, I took time to reflect on integrity versus authenticity, as well as create some interesting glitched outputs. I also uncovered what may be the first audio that reveals what the Millennium Bug itself may have sounded like! Keen to hear it? Read on to find out more.

#ac3 #Archives #audio #audiovisual #authenticity #av #Bash #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #digitalLiteracy #DigitalPreservation #diplomatics #FileFormats #flac #glitch #GlitchArt #glitchaudio #integrity #mp3 #sensitivityIndex #wav

The sensitivity index: Corrupting Y2K

by @beet_keeper

In December I asked “What will you bitflip today?” Not long after, Johan’s (@bitsgalore) Digtial Dark Age Crew released its long lost hidden single Y2K — well, I couldn’t resist corrupting it.

Fixity is an interesting property enabled by digital technologies. Checksums allow us to demonstrate mathematically that a file has not been changed. An often cited definition of fixity is:

Fixity, in the preservation sense, means the assurance that a digital file has remained unchanged, i.e. fixed — Bailey (2014)

It’s very much linked to the concept of integrity. A UNESCO definition of which:

The state of being whole, uncorrupted and free of unauthorized and undocumented changes.

Integrity is massively important these days. It gives us the guarantees we need that digital objects we work with aren’t harboring their own sinister secrets in the form of malware and other potentially damaging payloads.

These values are contingent on bit-level preservation, the field of digital preservation largely assumes this; that we will be able to look after our content without losing information. As feasible as this may be these days, what happens if we lose some information? Where does authenticity come into play?

Through corrupting Y2K, I took time to reflect on integrity versus authenticity, as well as create some interesting glitched outputs. I also uncovered what may be the first audio that reveals what the Millennium Bug itself may have sounded like! Keen to hear it? Read on to find out more.

#ac3 #Archives #audio #audiovisual #authenticity #av #Bash #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #digitalLiteracy #DigitalPreservation #diplomatics #FileFormats #flac #glitch #GlitchArt #glitchaudio #integrity #mp3 #sensitivityIndex #wav