No.868721
>Madokami's been left to die
>queue hasn't even checked IRC in weeks, too busy with VR
>closed off all applications, not even the janitors left want to clean up the unorganized mess
Mangatraders 2.0 crash here we come.
No.868727
>that stupid overdramatic shit inonly like 20 lines of conversation
Why is every site management plagued with drama queens? Drama and ego have killed more good websites than anything else.
No.868739
>>868727
It gets boring to maintain a site for years without getting paid. Then real life complications come in. Does he have cancer?
No.868744
Are you fucking kidding me? Madokami WAS the backup plan when Mangatraders died. What the fuck do we do now? There's shit-all for torrents when it comes to manga.
No.868749
>>868744
Hopefully you and others have been archiving as much manga as possible.
No.868754
>>868749
Manga is different. Many manga are terminally "in progress" and have been for decades. You don't just archive once and you're done, it has to be constantly refreshed and updated to track and absorb new volumes and chapters.
No.868755
>>868744
I guess Animebytes. But that place is very exclusive.
No.868757
>>868721
God fucking damn it. No nice things allowed.
Ever.
No.868764
Please no. At least, I have ~225GB of it on me drive.
No.868768
>>868764
I just checked if the torrent is still alive. It's not.
No.868778
Well at least this means another site will pop up. Probably. Here's hoping mado doesn't die.
No.868783
No.868791
>>868739
>Does he have cancer?
I recall Sunako had a heart condition or something and kept going in for surgeries.
No.868792
>>868744
I could do something if anons were willing to help seed. The problem is there's 6TB of it and nobody seems willing to help seed even a little of it.
No.868800
I was always waiting for the applications to reopen. RIP.
No.868802
>>868792
How much is a little? I've got almost 800 GB free on my current 4 TB drive, and at some point I plan to set up a proper NAS/seedbox with significantly more capacity.
No.868805
>just spent 3 hours simply going through my manga and downloading all the latest chapters
>not even finished with the K's yet, much less gotten to the point that I can start grabbing entire series that I haven't even touched yet
No.868826
Get most of my manga ripped from lib gen and my comic post. Torrents die in 2 years or less to get seeds from unless it's really popular. Stuff disappears if their isn't a backup for the backups and being too exclusionary. There really needs to be a better place to host manga and anime.
No.868839
I got in contact with Archive Team and they managed to prod the admin out of his slumber. They were able to coax rsync access out of him (so the actual repo probably isn't in danger), and the admin then made a couple of posts on half/a/, as pictured.
Either way, I think things will be fine. In fact I'll put our names to it: if it comes down to it then we will host the site ourselves. We may need help with funding though, I don't really have a spare $1200+/year on hand to throw at it myself.
No.868840
>>868839
I bless this news with my idol, Momo-i Halko.
No.868844
>>868839
I have certain skills, so I'd be willing to help if that's what it takes to keep my sources running.
That said, I can't host it myself since my government has decided that certain patterns of colour are actually children, and I don't want to ride the partyvan.
How much data is there in total? Multiple terabytes of storage and an unmetered connection isn't gonna come cheap, even shitholes like OVH or leaseweb probably would be > $100
No.868855
>>868844
Currently the repo sits at 6TB.
No.868867
>>868744
HakuNeko S and download from sites?
No.868876
>>868839
I dont even have a mado account but want to help if I ever feel insane enough to read ongoing manga again.
>Funding
Are you willing to accept cryptoshekels?
>>868844
Is this not a good opportunity for something like IPFS? If the data is distributed with redundancy between a great many of us bandwidth becomes less of an issue.
No.868896
>>868876
>Is this not a good opportunity for something like IPFS?
I think so, but IPFS has not been tried with anything anywhere near 6TB, I'm not convinced it could cope with it.
>Are you willing to accept cryptoshekels?
Yes, if it came to it I was thinking of something like what cock.li does.
No.868900
>>868896
>IPFS
Wouldnt be fun if it burst into flames on day one. I cant think of a network distributed system other than torrents where even people with small upload speeds can make meaningful contributions. 6TB of storage is easy., sharing it is hard.
>cock.li
Excellent.
No.868901
>>868800
If they haven't changed the process when they reopen I would recommend anons go for it. You just had to register on IRC with a bot and that was all there was to it.
No.868906
>>868839
Thank you, based head maid.
No.868911
>>868839
>going to halfchan
Why hasn't this newfag been banned yet?
No.868915
>>868839
>Head meido can pull strings in high places
No.868933
>>868900
And you still have the problem I mentioned here >>868754
Nobody wants a stale crusty old torrent that's missing months or even years worth of chapter releases because torrents are static. Nobody has really gotten a good way to update a torrent's contents without also having to update the whole torrent itself.
No.868940
>>868896
>IPFS
How much effort would it take to attempt such a large IPFS setup? Sooner or later someone has to try it so why not all of us? Its not "us" when most of the work will likely be shouldered by you and a handful of others with sufficient programming talent
No.868941
>>868940
Hell I'd jump on the IPFS boat now. What better way to start to get more people into the system than offering something people want, e.g. bullshit free manga.
No.868942
The best model of a practical semi-distributed system might be sadpanda's Hentai at Home software. It'd be worth looking into the details of how that works.
>>868933
Dedicated client/peer software can solve the problem of torrents getting out of date. Have an RSS-like feed to automatically fetch updated torrent files and merge them with previously downloaded data so only new pages need to be downloaded.
A web interface could be provided by torrenting and unpacking the pages entirely in javascript. Maybe add in some rate limits and rewards to encourage people to seed generously and you're done.
Server costs could be kept very low because only torrent files would need to be centrally hosted.
No.868944
>>868942
>lets write a torrent client in javascript
This is an awful idea. There's got to be a way to do this without going full nu-web 3.0 on it. The best part about madokami was how fucking simple the actual site was. The only script is a jquery-ui bundle that I'm willing to bet is entirely for the search typeahead.
No.868945
>>868933
No, the reason he brought up IPFS is it explicitly solves that problem. In IPFS, each file is individually hashed and addressed in the DHT, so you can mangle the directory structure however you want and it won't split the swarm.
No.868947
>>868942
Bad idea, not ideal for archiving.
No.868948
>>868940
It depends on how deep into it you want to go. You could just host the files through IPFS keeping the current system for uploading, or you could go all the way in to https://github.com/DistributedMemetics/DM/issues/2
No.868949
>>868945
Exactly, I wasn't disagreeing with IPFS, I was disagreeing with torrents. Besides the idea that we would need to focus so hard on "meaningful contributions" from users is the wrong way to go about it too. That's just setting up another exclusive walled garden, and at that point you might as well just hoard it all on disconnected disks and mail copies to your friends.
No.868961
>>868949
>meaningful contributions
>walled garden
That wasn't how I meant that phrase. The intention was a system everyone can contribute to regardless of internet service limitations so it doesn't become reliant on a handful of users with no rate limits and no "data caps". To be blunt, it shouldn't die or slow down a great deal if the one person with 100 Mbps upload speed goes offline. Ideally users are given a workload suited to their connection (small files for low speeds and large files for high speeds) but thats not how IPFS works I believe.
No.868968
>>868961
How many people are actually going to be running the full IPFS software rather than just connecting through a public gateway?
I can't imagine it ever not being reliant on a handful of users.
No.868987
>>868968
If there are only a handful of full IPFS users doesn't that somewhat defeat the purpose? With so few full nodes won't things degenerate into muh sekrit club drama behavior?
No.869005
>>868944
It needed JS for the read feature too (too bad, it's useful when you just want to check the quality).
No.869008
>>868987
I don't think it will be a "muh sekrit club" thing, but it will be very vulnerable to any of those nodes going down. Also I'm not sure how happy the IPFS gateways will be if we start trying to pipe 130 Mbit/s of traffic through them 24/7.
The basic problem is that unless most people are willing to run specialist peer-to-peer software, the hosting cost will always be centralized somewhere.
No.869014
>>869008
Indeed most people will not be willing and may not even be capable on a hardware or financial view. For a group the size of 8/a/ I imagine 5 to 10 full users would be more than enough. In this thread alone there maybe 3 to 5 of us that would consider a full node and if we include 4/a/ surely that number will double and probably grow further.
No.869025
>>869014
I'll host a node, but I don't have 6 TB of free storage laying around and I can't provide more than about 8 Mbit of upload bandwidth.
Hopefully the other nodes will have better hardware than I do.