home.social

#longtermarchival — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #longtermarchival, aggregated by home.social.

fetched live
  1. Ingram Braun

    The bsky-docker script


    bsky.pl as standalone script on a Windows 11 Powershell
    Intro
    bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky …


    #Bluesky #Docker #Perl #SocialMedia #WebDevelopment #longtermarchival

  2. Ingram Braun

    The bsky-docker script


    bsky.pl as standalone script on a Windows 11 Powershell
    Intro
    bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky …


    #Bluesky #Docker #Perl #SocialMedia #WebDevelopment #longtermarchival

  3. Ingram Braun

    The bsky-docker script


    bsky.pl as standalone script on a Windows 11 Powershell
    Intro
    bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky …


    #Bluesky #Docker #Perl #SocialMedia #WebDevelopment #longtermarchival

  4. Ingram Braun

    The bsky-docker script


    bsky.pl as standalone script on a Windows 11 Powershell
    Intro
    bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky …


    #Bluesky #Docker #Perl #SocialMedia #WebDevelopment #longtermarchival

  5. The bsky-docker script

    bsky.pl as standalone script on a Windows 11 Powershell Intro bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky timeline and author feeds. I did it mainly for use in conjunction with archive.pl. Requirements Perl's Bluesky module requires Perl 5.40.0 at least. Preferably, use the script through the Docker container: $ docker pull archaeopath/bsky-docker:latest Usage As standalone: $ perl bsky.pl USER APPPASSWORD […]

    ingram-braun.net/erga/the-bsky

  6. The bsky-docker script

    bsky.pl as standalone script on a Windows 11 Powershell Intro bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky timeline and author feeds. I did it mainly for use in conjunction with archive.pl. Requirements Perl's Bluesky module requires Perl 5.40.0 at least. Preferably, use the script through the Docker container: $ docker pull archaeopath/bsky-docker:latest Usage As standalone: $ perl bsky.pl USER APPPASSWORD […]

    ingram-braun.net/erga/the-bsky

  7. The bsky-docker script

    bsky.pl as standalone script on a Windows 11 Powershell Intro bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky timeline and author feeds. I did it mainly for use in conjunction with archive.pl. Requirements Perl's Bluesky module requires Perl 5.40.0 at least. Preferably, use the script through the Docker container: $ docker pull archaeopath/bsky-docker:latest Usage As standalone: $ perl bsky.pl USER APPPASSWORD […]

    ingram-braun.net/erga/the-bsky

  8. The bsky-docker script

    bsky.pl as standalone script on a Windows 11 Powershell Intro bsky-docker is a Docker image of a simple Perl script that extracts an alphabetically sorted list of URLs from a Bluesky timeline and author feeds. I did it mainly for use in conjunction with archive.pl. Requirements Perl's Bluesky module requires Perl 5.40.0 at least. Preferably, use the script through the Docker container: $ docker pull archaeopath/bsky-docker:latest Usage As standalone: $ perl bsky.pl USER APPPASSWORD […]

    ingram-braun.net/erga/the-bsky

  9. So if you mount a folder sitting on a spinning drive formatted with xFAT into a qemu instance, chowning a large number of folders and files recursively does take a surprising amount of time.

    All of that just to satisfy nginx and because I couldn't find a way to map the files to a certain UID/GID during mounting.

    #LongTermArchival #thestorycontinues

  10. So if you mount a folder sitting on a spinning drive formatted with xFAT into a qemu instance, chowning a large number of folders and files recursively does take a surprising amount of time.

    All of that just to satisfy nginx and because I couldn't find a way to map the files to a certain UID/GID during mounting.

    #LongTermArchival #thestorycontinues

  11. So if you mount a folder sitting on a spinning drive formatted with xFAT into a qemu instance, chowning a large number of folders and files recursively does take a surprising amount of time.

    All of that just to satisfy nginx and because I couldn't find a way to map the files to a certain UID/GID during mounting.

    #LongTermArchival #thestorycontinues

  12. So if you mount a folder sitting on a spinning drive formatted with xFAT into a qemu instance, chowning a large number of folders and files recursively does take a surprising amount of time.

    All of that just to satisfy nginx and because I couldn't find a way to map the files to a certain UID/GID during mounting.

    #LongTermArchival #thestorycontinues

  13. So if you mount a folder sitting on a spinning drive formatted with xFAT into a qemu instance, chowning a large number of folders and files recursively does take a surprising amount of time.

    All of that just to satisfy nginx and because I couldn't find a way to map the files to a certain UID/GID during mounting.

    #LongTermArchival #thestorycontinues

  14. Also I decided that I want to try to get a static image browser of sorts in. Still not super sure if I will build that using some sort of static site generator or a SPA approach. In any case, I am currently exporting JSON data from the database to be able to back both approaches.

    #LongTermArchival

  15. Also I decided that I want to try to get a static image browser of sorts in. Still not super sure if I will build that using some sort of static site generator or a SPA approach. In any case, I am currently exporting JSON data from the database to be able to back both approaches.

    #LongTermArchival

  16. Also I decided that I want to try to get a static image browser of sorts in. Still not super sure if I will build that using some sort of static site generator or a SPA approach. In any case, I am currently exporting JSON data from the database to be able to back both approaches.

    #LongTermArchival

  17. Also I decided that I want to try to get a static image browser of sorts in. Still not super sure if I will build that using some sort of static site generator or a SPA approach. In any case, I am currently exporting JSON data from the database to be able to back both approaches.

    #LongTermArchival

  18. Also I decided that I want to try to get a static image browser of sorts in. Still not super sure if I will build that using some sort of static site generator or a SPA approach. In any case, I am currently exporting JSON data from the database to be able to back both approaches.

    #LongTermArchival

  19. Hm, so today was a bit of a mixed bag. While I was able to run the VM image in qemu (in emulation, not in kvm), it is really, really slow on both my PC and my M1 MacMini.

    As in unusably slow. Sure, in terms of long term storage, it's probably okay as things will get faster and faster, but I want this to be usable out of the box.

    Back to the drawing board.

    #LongTermArchival

  20. Hm, so today was a bit of a mixed bag. While I was able to run the VM image in qemu (in emulation, not in kvm), it is really, really slow on both my PC and my M1 MacMini.

    As in unusably slow. Sure, in terms of long term storage, it's probably okay as things will get faster and faster, but I want this to be usable out of the box.

    Back to the drawing board.

    #LongTermArchival

  21. Hm, so today was a bit of a mixed bag. While I was able to run the VM image in qemu (in emulation, not in kvm), it is really, really slow on both my PC and my M1 MacMini.

    As in unusably slow. Sure, in terms of long term storage, it's probably okay as things will get faster and faster, but I want this to be usable out of the box.

    Back to the drawing board.

    #LongTermArchival

  22. Hm, so today was a bit of a mixed bag. While I was able to run the VM image in qemu (in emulation, not in kvm), it is really, really slow on both my PC and my M1 MacMini.

    As in unusably slow. Sure, in terms of long term storage, it's probably okay as things will get faster and faster, but I want this to be usable out of the box.

    Back to the drawing board.

    #LongTermArchival

  23. Hm, so today was a bit of a mixed bag. While I was able to run the VM image in qemu (in emulation, not in kvm), it is really, really slow on both my PC and my M1 MacMini.

    As in unusably slow. Sure, in terms of long term storage, it's probably okay as things will get faster and faster, but I want this to be usable out of the box.

    Back to the drawing board.

    #LongTermArchival

  24. Wrote a little bit yesterday about my ideas and my progress regarding the #LongTermArchival project I talked about.

    jan.krutisch.de/en/2024/03/11/

  25. Wrote a little bit yesterday about my ideas and my progress regarding the #LongTermArchival project I talked about.

    jan.krutisch.de/en/2024/03/11/

  26. Wrote a little bit yesterday about my ideas and my progress regarding the #LongTermArchival project I talked about.

    jan.krutisch.de/en/2024/03/11/

  27. Wrote a little bit yesterday about my ideas and my progress regarding the #LongTermArchival project I talked about.

    jan.krutisch.de/en/2024/03/11/

  28. Wrote a little bit yesterday about my ideas and my progress regarding the #LongTermArchival project I talked about.

    jan.krutisch.de/en/2024/03/11/

  29. This week is dedicated to a very different project: I'm trying to create an archive of a web application (including data) that should be as long lasting as possible.

    It's an interesting challenge, for sure and I hope I can blog a bit more and maybe do 1-2 videos about what I'm doing there. I'm still debating with myself if I will create two versions, one with an unaltered database we'll keep private and one with scrubbed data that could theoretically be public.

    #LongTermArchival #archival

  30. This week is dedicated to a very different project: I'm trying to create an archive of a web application (including data) that should be as long lasting as possible.

    It's an interesting challenge, for sure and I hope I can blog a bit more and maybe do 1-2 videos about what I'm doing there. I'm still debating with myself if I will create two versions, one with an unaltered database we'll keep private and one with scrubbed data that could theoretically be public.

    #LongTermArchival #archival

  31. This week is dedicated to a very different project: I'm trying to create an archive of a web application (including data) that should be as long lasting as possible.

    It's an interesting challenge, for sure and I hope I can blog a bit more and maybe do 1-2 videos about what I'm doing there. I'm still debating with myself if I will create two versions, one with an unaltered database we'll keep private and one with scrubbed data that could theoretically be public.

    #LongTermArchival #archival

  32. This week is dedicated to a very different project: I'm trying to create an archive of a web application (including data) that should be as long lasting as possible.

    It's an interesting challenge, for sure and I hope I can blog a bit more and maybe do 1-2 videos about what I'm doing there. I'm still debating with myself if I will create two versions, one with an unaltered database we'll keep private and one with scrubbed data that could theoretically be public.

    #LongTermArchival #archival

  33. This week is dedicated to a very different project: I'm trying to create an archive of a web application (including data) that should be as long lasting as possible.

    It's an interesting challenge, for sure and I hope I can blog a bit more and maybe do 1-2 videos about what I'm doing there. I'm still debating with myself if I will create two versions, one with an unaltered database we'll keep private and one with scrubbed data that could theoretically be public.

    #LongTermArchival #archival

  34. So, after sunsetting that rails app, what I would love to do is preserve the app together with the data and all dependencies in some form.

    To make this somewhat future proof, I thought about building a docker container and save that as a single file.

    But maybe a disk image that could boot a VM is better if we think about long term archival?

    Any ideas on that anyone?

    #archival #longTermArchival

  35. So, after sunsetting that rails app, what I would love to do is preserve the app together with the data and all dependencies in some form.

    To make this somewhat future proof, I thought about building a docker container and save that as a single file.

    But maybe a disk image that could boot a VM is better if we think about long term archival?

    Any ideas on that anyone?

    #archival #longTermArchival

  36. So, after sunsetting that rails app, what I would love to do is preserve the app together with the data and all dependencies in some form.

    To make this somewhat future proof, I thought about building a docker container and save that as a single file.

    But maybe a disk image that could boot a VM is better if we think about long term archival?

    Any ideas on that anyone?

    #archival #longTermArchival

  37. So, after sunsetting that rails app, what I would love to do is preserve the app together with the data and all dependencies in some form.

    To make this somewhat future proof, I thought about building a docker container and save that as a single file.

    But maybe a disk image that could boot a VM is better if we think about long term archival?

    Any ideas on that anyone?

    #archival #longTermArchival

  38. So, after sunsetting that rails app, what I would love to do is preserve the app together with the data and all dependencies in some form.

    To make this somewhat future proof, I thought about building a docker container and save that as a single file.

    But maybe a disk image that could boot a VM is better if we think about long term archival?

    Any ideas on that anyone?

    #archival #longTermArchival

  39. I have released v2.2 of my #Perl script archive.pl for saving URL sets in the #InternetArchive. Most important improvement is the Docker image now that contains TOR as service for fast IP rotation and a headless #Firefox#longtermArchival
    ingram-braun.net/erga/2022/12/a…
  40. I have released v2.2 of my #Perl script archive.pl for saving URL sets in the #InternetArchive. Most important improvement is the Docker image now that contains TOR as service for fast IP rotation and a headless #Firefox#longtermArchival
    ingram-braun.net/erga/2022/12/a…