>>937546
I'm not at all trying to discourage him from trying; I'm trying to get him to understand the benefits of _prototyping_. He should push the limits of a first attempt and then learn from that. Follow it up with some better design choices.
If he doesn't know how to measure his network capabilities or know how to raise his connection cap, he's not going to know how to backup his database and share it.
I'm recommending he take careful stock of his hardware options so he understands what will fail first and why, followed by starting a sample server and opening it up for some initial testing and troubleshooting of initial problems. Once he knows how it all fits together and can adapt to changes, he can look into how to export his data.
> If his hardware dies then that's his fault and can fuck off for using botnet hardware in the first place.
If it takes off running botnet hardware and no backup then it's both a security liability for users here and a waste of time if the data is lost or if he exposes himself and gets caught by authorities. A small server for friends won't attract much attention but an 8ch server is going to have a target on its back from Day 01.
Plus it'll be over residential lines. That's another consideration.
You imply you want P2P services not controlled by botnet devices but you think it's okay to just tell everyone to use a service hosted by an inexperienced user on hardware that's guaranteed pozzed through similarly cucked networking equipment.
I'm here trying to tell him that, hey, you can learn all this stuff and then apply it to make a decent semi-public tracker, but start small so the first time it blows up it doesn't impact anybody else. You learn way more from screwing up something like this a couple times than from calling it a day and hosting it with no maintenance or consideration for where to go.
He should just make his own thread where he can ask questions and we can debate solutions and he can apply what he thinks is feasible. At least that way it would be collaborative and he'd learn a lot.
If it ends up taking-off then we can look into some CSS hacks to make integration easier with the site. We'd need to have a discussion about the best way to keep things anonymous while keeping out Feds and malicious users.