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?

You are viewing a single thread.
View all comments
10 points

I don’t self-host it, I just use archive.org. That makes it available to others too.

permalink
report
reply
0 points

Yes. This isn’t something you want your own machines to be doing if something else is already doing it.

permalink
report
parent
reply
21 points

But then who backs up the backups?

permalink
report
parent
reply

I guess they back either other up. Like archive.is is able to take archives from archive.org but the saved page reflects the original URL and the original archiving time from the wayback machine (though it also notes the URL used from wayback itself plus the time they got archived it from wayback).

permalink
report
parent
reply
-1 points

Realize how how much they are supporting and storing.

Come back to the comments after.

permalink
report
parent
reply
9 points

Your argument is that a single backup is sufficient? I disagree, and I think that so would most in the selfhosted and datahoarder communities.

permalink
report
parent
reply
33 points

There was the attack on the Internet archive recently, are there any good options out there to help mirror some of the data or otherwise provide redundancy?

permalink
report
parent
reply
35 points

It’s a single point of failure though.

permalink
report
parent
reply
3 points

In that they’re a single organization, yes, but I’m a single person with significantly fewer resources. Non-availability is a significantly higher risk for things I host personally.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create 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!

Community stats

  • 3.7K

    Monthly active users

  • 2K

    Posts

  • 23K

    Comments