#digipres — Public Fediverse posts

#fileformat Friday! Ready, Set, Go! Early #macintosh desktop publishing. #digipres https://preservation.tylerthorsted.com/2026/07/31/ready-set-go/

#fileformat Friday! Ready, Set, Go! Early #macintosh desktop publishing. #digipres https://preservation.tylerthorsted.com/2026/07/31/ready-set-go/

#fileformat Friday! Ready, Set, Go! Early #macintosh desktop publishing. #digipres https://preservation.tylerthorsted.com/2026/07/31/ready-set-go/

#fileformat Friday! Ready, Set, Go! Early #macintosh desktop publishing. #digipres https://preservation.tylerthorsted.com/2026/07/31/ready-set-go/

#fileformat Friday! Ready, Set, Go! Early #macintosh desktop publishing. #digipres https://preservation.tylerthorsted.com/2026/07/31/ready-set-go/

Pour illustrer mon précédent billet de blog, j'ai tenté de sauver un jeu vidéo ancien sur une vieille disquette toute pourrite. C'était très rigolo - et j'ai appris pas mal de choses (dont la différence entre des poissons migrateurs amphibiotiques et holobiotiques).

https://digipres.fr/archives/404

Et y a même une vidéo de moi qui sais pas streamer, avec une voix trop basse pour éviter de gêner le reste du monde. C'est-y pas beau ça ?

#DigiPres_FR #digipres #retrogaming #retrocomputing

Pour illustrer mon précédent billet de blog, j'ai tenté de sauver un jeu vidéo ancien sur une vieille disquette toute pourrite. C'était très rigolo - et j'ai appris pas mal de choses (dont la différence entre des poissons migrateurs amphibiotiques et holobiotiques).

https://digipres.fr/archives/404

Et y a même une vidéo de moi qui sais pas streamer, avec une voix trop basse pour éviter de gêner le reste du monde. C'est-y pas beau ça ?

#DigiPres_FR #digipres #retrogaming #retrocomputing

Pour illustrer mon précédent billet de blog, j'ai tenté de sauver un jeu vidéo ancien sur une vieille disquette toute pourrite. C'était très rigolo - et j'ai appris pas mal de choses (dont la différence entre des poissons migrateurs amphibiotiques et holobiotiques).

https://digipres.fr/archives/404

Et y a même une vidéo de moi qui sais pas streamer, avec une voix trop basse pour éviter de gêner le reste du monde. C'est-y pas beau ça ?

#DigiPres_FR #digipres #retrogaming #retrocomputing

Pour illustrer mon précédent billet de blog, j'ai tenté de sauver un jeu vidéo ancien sur une vieille disquette toute pourrite. C'était très rigolo - et j'ai appris pas mal de choses (dont la différence entre des poissons migrateurs amphibiotiques et holobiotiques).

https://digipres.fr/archives/404

Et y a même une vidéo de moi qui sais pas streamer, avec une voix trop basse pour éviter de gêner le reste du monde. C'est-y pas beau ça ?

#DigiPres_FR #digipres #retrogaming #retrocomputing

Pour illustrer mon précédent billet de blog, j'ai tenté de sauver un jeu vidéo ancien sur une vieille disquette toute pourrite. C'était très rigolo - et j'ai appris pas mal de choses (dont la différence entre des poissons migrateurs amphibiotiques et holobiotiques).

https://digipres.fr/archives/404

Et y a même une vidéo de moi qui sais pas streamer, avec une voix trop basse pour éviter de gêner le reste du monde. C'est-y pas beau ça ?

#DigiPres_FR #digipres #retrogaming #retrocomputing

The stuff I've been working on recently is finally public! I've spent the past bit revamping the social media site support in Browsertrix. We can capture much more content from Facebook and Instagram now, and I've also fixed Youtube video capture.

In addition, we've added a new "smart scoping" feature that ensures we crawl more pages from social media profiles even if they wouldn't otherwise be in scope.

https://webrecorder.net/blog/2026-07-27-social-media-improvements/

#digipres

The stuff I've been working on recently is finally public! I've spent the past bit revamping the social media site support in Browsertrix. We can capture much more content from Facebook and Instagram now, and I've also fixed Youtube video capture.

In addition, we've added a new "smart scoping" feature that ensures we crawl more pages from social media profiles even if they wouldn't otherwise be in scope.

https://webrecorder.net/blog/2026-07-27-social-media-improvements/

#digipres

The stuff I've been working on recently is finally public! I've spent the past bit revamping the social media site support in Browsertrix. We can capture much more content from Facebook and Instagram now, and I've also fixed Youtube video capture.

In addition, we've added a new "smart scoping" feature that ensures we crawl more pages from social media profiles even if they wouldn't otherwise be in scope.

https://webrecorder.net/blog/2026-07-27-social-media-improvements/

#digipres

The stuff I've been working on recently is finally public! I've spent the past bit revamping the social media site support in Browsertrix. We can capture much more content from Facebook and Instagram now, and I've also fixed Youtube video capture.

In addition, we've added a new "smart scoping" feature that ensures we crawl more pages from social media profiles even if they wouldn't otherwise be in scope.

https://webrecorder.net/blog/2026-07-27-social-media-improvements/

#digipres

The stuff I've been working on recently is finally public! I've spent the past bit revamping the social media site support in Browsertrix. We can capture much more content from Facebook and Instagram now, and I've also fixed Youtube video capture.

In addition, we've added a new "smart scoping" feature that ensures we crawl more pages from social media profiles even if they wouldn't otherwise be in scope.

https://webrecorder.net/blog/2026-07-27-social-media-improvements/

#digipres

Rolled out a new update for the Data Dungeon site. This also includes some major layout changes; let me know if you spot any issues and I'll try to sort them as soon as I can.

https://archive.thedatadungeon.com/changes.html#2026-07-26

#datapreservation #digipres #preservation

Rolled out a new update for the Data Dungeon site. This also includes some major layout changes; let me know if you spot any issues and I'll try to sort them as soon as I can.

https://archive.thedatadungeon.com/changes.html#2026-07-26

#datapreservation #digipres #preservation

Rolled out a new update for the Data Dungeon site. This also includes some major layout changes; let me know if you spot any issues and I'll try to sort them as soon as I can.

https://archive.thedatadungeon.com/changes.html#2026-07-26

#datapreservation #digipres #preservation

Rolled out a new update for the Data Dungeon site. This also includes some major layout changes; let me know if you spot any issues and I'll try to sort them as soon as I can.

https://archive.thedatadungeon.com/changes.html#2026-07-26

#datapreservation #digipres #preservation

Is there a chance that somebody at #Wikimania knows something about the recent loss of years of ahort links to #Wikidata queries on https://query-chest.toolforge.org/? The seeming flushing of all caches at some point earlier this month makes the service utterly useless and caused thousands of links in publications, on websites etc. to rot.

#LinkRot #DigiPres

Is there a chance that somebody at #Wikimania knows something about the recent loss of years of ahort links to #Wikidata queries on https://query-chest.toolforge.org/? The seeming flushing of all caches at some point earlier this month makes the service utterly useless and caused thousands of links in publications, on websites etc. to rot.

#LinkRot #DigiPres

Is there a chance that somebody at #Wikimania knows something about the recent loss of years of ahort links to #Wikidata queries on https://query-chest.toolforge.org/? The seeming flushing of all caches at some point earlier this month makes the service utterly useless and caused thousands of links in publications, on websites etc. to rot.

#LinkRot #DigiPres

Is there a chance that somebody at #Wikimania knows something about the recent loss of years of ahort links to #Wikidata queries on https://query-chest.toolforge.org/? The seeming flushing of all caches at some point earlier this month makes the service utterly useless and caused thousands of links in publications, on websites etc. to rot.

#LinkRot #DigiPres

Is there a chance that somebody at #Wikimania knows something about the recent loss of years of ahort links to #Wikidata queries on https://query-chest.toolforge.org/? The seeming flushing of all caches at some point earlier this month makes the service utterly useless and caused thousands of links in publications, on websites etc. to rot.

#LinkRot #DigiPres

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ' (hex: 0x27) and double quotes " (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

If you want an AppleSauce+ floppy disk flux imager, the pre-orders just went live. #digipres https://shop.applesaucefdc.com/products/applesauce-copy?variant=59643823325470

If you want an AppleSauce+ floppy disk flux imager, the pre-orders just went live. #digipres https://shop.applesaucefdc.com/products/applesauce-copy?variant=59643823325470

If you want an AppleSauce+ floppy disk flux imager, the pre-orders just went live. #digipres https://shop.applesaucefdc.com/products/applesauce-copy?variant=59643823325470

If you want an AppleSauce+ floppy disk flux imager, the pre-orders just went live. #digipres https://shop.applesaucefdc.com/products/applesauce-copy?variant=59643823325470

If you want an AppleSauce+ floppy disk flux imager, the pre-orders just went live. #digipres https://shop.applesaucefdc.com/products/applesauce-copy?variant=59643823325470

And another post regarding the #Zenodo #digipres community...had a great chat with Chelle Sanders, the current program manager of the Software Preservation Network (SPN) yesterday. As SPN is currently in its controlled sunsetting phase (to conclude dec 31st 2026), we are exploring the possibility of collecting as many of their publications as possible & adding them to the Zenodo digipres community to make sure there's a central home for SPN's important legacy! Fingers crossed it'll all work out.

And another post regarding the #Zenodo #digipres community...had a great chat with Chelle Sanders, the current program manager of the Software Preservation Network (SPN) yesterday. As SPN is currently in its controlled sunsetting phase (to conclude dec 31st 2026), we are exploring the possibility of collecting as many of their publications as possible & adding them to the Zenodo digipres community to make sure there's a central home for SPN's important legacy! Fingers crossed it'll all work out.

And another post regarding the #Zenodo #digipres community...had a great chat with Chelle Sanders, the current program manager of the Software Preservation Network (SPN) yesterday. As SPN is currently in its controlled sunsetting phase (to conclude dec 31st 2026), we are exploring the possibility of collecting as many of their publications as possible & adding them to the Zenodo digipres community to make sure there's a central home for SPN's important legacy! Fingers crossed it'll all work out.

And another post regarding the #Zenodo #digipres community...had a great chat with Chelle Sanders, the current program manager of the Software Preservation Network (SPN) yesterday. As SPN is currently in its controlled sunsetting phase (to conclude dec 31st 2026), we are exploring the possibility of collecting as many of their publications as possible & adding them to the Zenodo digipres community to make sure there's a central home for SPN's important legacy! Fingers crossed it'll all work out.

And another post regarding the #Zenodo #digipres community...had a great chat with Chelle Sanders, the current program manager of the Software Preservation Network (SPN) yesterday. As SPN is currently in its controlled sunsetting phase (to conclude dec 31st 2026), we are exploring the possibility of collecting as many of their publications as possible & adding them to the Zenodo digipres community to make sure there's a central home for SPN's important legacy! Fingers crossed it'll all work out.

*newest addition to the #zenodo #digipres community*

"Borealis CTS Certification Documentation Suite, 2024-2025" - documentation, policy and application templates developed by the Digital Research Alliance of Canada's Preservation Expert Group & the Borealis Community for CTS certification. The suite was recently officially endorsed by the CTS board.

Check it out here:
https://zenodo.org/records/21460628

*newest addition to the #zenodo #digipres community*

"Borealis CTS Certification Documentation Suite, 2024-2025" - documentation, policy and application templates developed by the Digital Research Alliance of Canada's Preservation Expert Group & the Borealis Community for CTS certification. The suite was recently officially endorsed by the CTS board.

Check it out here:
https://zenodo.org/records/21460628

*newest addition to the #zenodo #digipres community*

"Borealis CTS Certification Documentation Suite, 2024-2025" - documentation, policy and application templates developed by the Digital Research Alliance of Canada's Preservation Expert Group & the Borealis Community for CTS certification. The suite was recently officially endorsed by the CTS board.

Check it out here:
https://zenodo.org/records/21460628

*newest addition to the #zenodo #digipres community*

"Borealis CTS Certification Documentation Suite, 2024-2025" - documentation, policy and application templates developed by the Digital Research Alliance of Canada's Preservation Expert Group & the Borealis Community for CTS certification. The suite was recently officially endorsed by the CTS board.

Check it out here:
https://zenodo.org/records/21460628

*newest addition to the #zenodo #digipres community*

"Borealis CTS Certification Documentation Suite, 2024-2025" - documentation, policy and application templates developed by the Digital Research Alliance of Canada's Preservation Expert Group & the Borealis Community for CTS certification. The suite was recently officially endorsed by the CTS board.

Check it out here:
https://zenodo.org/records/21460628

Small trick for #digipres folks using Unix file: did you know that when identifying the format of a file, you changed its Access time (utime)?

Small trick for #digipres folks using Unix file: did you know that when identifying the format of a file, you changed its Access time (utime)?

Small trick for #digipres folks using Unix file: did you know that when identifying the format of a file, you changed its Access time (utime)?

Small trick for #digipres folks using Unix file: did you know that when identifying the format of a file, you changed its Access time (utime)?

Small trick for #digipres folks using Unix file: did you know that when identifying the format of a file, you changed its Access time (utime)?

When the World Cup and Floppies collide. #digipres https://www.instagram.com/reel/Daib8iHuVUk/?igsh=YWp3cDM0Y3NvdGZ0

When the World Cup and Floppies collide. #digipres https://www.instagram.com/reel/Daib8iHuVUk/?igsh=YWp3cDM0Y3NvdGZ0

When the World Cup and Floppies collide. #digipres https://www.instagram.com/reel/Daib8iHuVUk/?igsh=YWp3cDM0Y3NvdGZ0

When the World Cup and Floppies collide. #digipres https://www.instagram.com/reel/Daib8iHuVUk/?igsh=YWp3cDM0Y3NvdGZ0

When the World Cup and Floppies collide. #digipres https://www.instagram.com/reel/Daib8iHuVUk/?igsh=YWp3cDM0Y3NvdGZ0

Has anyone in the cultural heritage domain tried using the Bellingcat Auto Archiver to gather social media? https://bellingcat.gitbook.io/toolkit/more/all-tools/auto-archiver #DigiPres #OpenSourceInvestigation

Has anyone in the cultural heritage domain tried using the Bellingcat Auto Archiver to gather social media? https://bellingcat.gitbook.io/toolkit/more/all-tools/auto-archiver #DigiPres #OpenSourceInvestigation

Has anyone in the cultural heritage domain tried using the Bellingcat Auto Archiver to gather social media? https://bellingcat.gitbook.io/toolkit/more/all-tools/auto-archiver #DigiPres #OpenSourceInvestigation

Has anyone in the cultural heritage domain tried using the Bellingcat Auto Archiver to gather social media? https://bellingcat.gitbook.io/toolkit/more/all-tools/auto-archiver #DigiPres #OpenSourceInvestigation

Has anyone in the cultural heritage domain tried using the Bellingcat Auto Archiver to gather social media? https://bellingcat.gitbook.io/toolkit/more/all-tools/auto-archiver #DigiPres #OpenSourceInvestigation

📢 New #DPClinic!

🌍 How can humanitarian organisations create sustainable digital archives?

Join Flora Chatt (University of Manchester) and the #DPC on 23 July, 14:00–15:00 UTC for an introduction to the new Digital Humanitarian Archives Toolkit.

💬 Explore the toolkit, hear why it was developed, and help shape it with your feedback.

🎟️ Free registration:
https://www.dpconline.org/events/eventdetail/815/-/dpclinic-july-digital-humanitarian-archives-toolkit

#DigitalPreservation #Coalition #DPC #Archives #Humanitarian #DPClinic #digipres #community #JoinUs