I saw this post and I was curious what was out there.

https://neuromatch.social/@jonny/113444325077647843

Id like to put my lab servers to work archiving US federal data thats likely to get pulled - climate and biomed data seems mostly likely. The most obvious strategy to me seems like setting up mirror torrents on academictorrents. Anyone compiling a list of at-risk data yet?

Otter
creator
link
fedilink
English
737d

One option that I’ve heard of in the past

https://archivebox.io/

ArchiveBox is a powerful, self-hosted internet archiving solution to collect, save, and view websites offline.

@tomtomtom@lemmy.world
link
fedilink
English
96d

I am using archivebox, it is pretty straight-forward to self-host and use.

However, it is very difficult to archive most news sites with it and many other sites as well. Most cookie etc pop ups on a site will render the archived page unusable and often archiving won’t work at all because some bot protection (Cloudflare etc.) will kick-in when archivebox tries to access a site.

If anyone else has more success using it, please let me know if I am doing something wrong…

Daniel Quinn
link
fedilink
English
16d

Monolith has the same problem here. I think the best resolution might be some sort of browser-plugin based solution where you could say “archive this” and have it push the result somewhere.

I wonder if I could combine a dumb plugin with Monolith to do that… A weekend project perhaps.

Admiral Patrick
link
fedilink
English
14
edit-2
7d

Going to check that out because…yeah. Just gotta figure out what and where to archive.

@M600@lemmy.world
link
fedilink
English
77d

This seems pretty cool. I might actually host this.

That looks useful, I might host that. Does anyone have an RSS feed of at risk data?

@Boomkop3@reddthat.com
link
fedilink
English
26d

Eyy, I want that!

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 77 users / day
  • 481 users / week
  • 1.17K users / month
  • 3.79K users / 6 months
  • 1 subscriber
  • 3.73K Posts
  • 75.4K Comments
  • Modlog