>>2565 >state of funding
We have two options.
1. Buy a new motherboard with DDR3 RAM and 2 CPU slots and use all the same components. Around $200-500.
2. Or buy a whole new 2U server as a package, for $500-1000.
We can bear the cost ourselves but donations do help if you feel like it.
We will produce a report of what exact hardware options we are thinking of before we take any donations. Though Archived.moe is already taking donations for their part of the server loss now.>Distributed image hosting would be a clusterfuck/borderline impossible, but does it have merit anyway?
IPFS (and it's blockchain subset, Filecoin) would probably be the solution to all this mess since anyone with their meager home connection could operate as a "seed" of the images. We would still need to operate our own big storage seed to prevent rarely accessed images from being lost, but we would be able to do it from our Comcastic home connection. https://ipfs.io/
The problem with IPFS right now is that if most users aren't using IPFS, there is no bandwidth savings and few seeds. So unless you are running the IPFS software on your own computer, we have to host an IPFS Content Delivery Network (CDN)-style gateway to serve users the files. Thus, since we have to operate our own IPFS gateways and storage "seeds", it would operate as a less effective CDN (Content Delivery Network), so it is theoretically no better than Cloudflare upon our existing storage servers.
The solution is IPFS.js, which allows a user's own browser to allow users to connect directly to p2p seeds. But it doesn't yet have DHT support so it has trouble finding IPFS peers without having a torrent-style tracker.
But maybe one day IPFS.js will have DHT support. The best bet is to help them make it possible so the majority of users can rely on it.
I mean, Ethereum (a very successful decentralized blockchain computing network) has the Metamask browser addon, it should be possible.
Track the progress of IPFS.js here: https://github.com/libp2p/js-libp2p-kad-dht/pull/1>>2567 >>2568>>2570>>2571
As stated in the announcement link here, Server 2 which hosts our full images will not turn on. Read it for a full technical analysis. We thus took the hard drives home and are updating our offsite backups of the 20TB RAID, of which the majority are already backed up.
Server 2 will have to be replaced before we can serve full images again, which will take weeks to one month, since we will have to decide what to buy, wait for it to arrive, put it together, and deploy it. https://wiki.bibanon.org/News/2017-11-22_Server_Failure#Server_2_.28Inoperable.29_2
But in the meantime, we continue to scrape 4chan with Asagi at home as of now.>>2566
You can run your own FoolFuuka/Asagi archiver by following our guide here, and using the SQL dumps of previous 4chan archivers located at the Internet Archive. We will upload more dumps of our archivers when possible, though offsite backup is first priority.https://wiki.bibanon.org/FoolFuuka/Install/Ubuntu16
I will update the guide with what we actually use in our current prod environment.