>>/9127/
It is not a bad idea, potentially a great one, but so is the anchor system. I'd like to see how that works out first. A no for the moment from me. There is a risk of splinting not being justified except during high workloads anyway. 

 >>/9130/
> IF there is a split, that, I would say, is the basis of it: how and what, here. The human-readable summary of what was saved, in /cerb/

It would honestly make sense for it to be the other way around, /go/ being the human readable summery, the library, while /cerb/ being the actual operations center. [spoiler[not that my opinion counts for much.[/spoiler]

> I'll have some old .flv files for the webm thread soon, however this place sorts itself out.

This is one of the things I personally enjoy about /go/ (and sometimes /endpone/ in general). I  think the high caliber posts, fandom analysis/retrospectives and nerdy aspects and code, random things being dumped to look at deserve a highlight. Both have been part of /go/ and can coexist without much effort. 

 >>/9136/
> 764.82 GiB, from_gdrive-reskey-adder.user.js_file

Wow, that is a big file! How do you do it? I mean, most data plans I know of usually cap out at some point even when they say unlimited.