Compilation File

[KainsChylde]

Heh, "It's not difficult to make them at all, you'll have to learn a little C# scripting" he says I couldn't script my way out of a wet paper bag with a T3 connection and every tutorial known to man. Hell, HTML color codes confuse me.

[prideslayer]

Everyone says that, before they decide they just want a "taste". Next thing you know: full blown addiction. I'm actually rather happy FOMM is in C#. I don't know that language either, but it's a great one to have on the resume, so I'm happy to get into learning it. FOMM itself is written in C#, though the code itself is pretty ugly.

[Halstrom]

Everyone says that' date=' before they decide they just want a "taste". Next thing you know: full blown addiction. I'm actually rather happy FOMM is in C#. I don't know that language either, but it's a great one to have on the resume, so I'm happy to get into learning it. FOMM itself is written in C#, though the code itself is pretty ugly.[/quote']

Yep, you know your gone when you listen to the internally leaking toilet cistern tank and think "if that was a virtual toilet, I'd code that so it couldn't happen"

Or "How the hell do I get access to my dashboard with a Laptop to change the coding on this stupid door chime of my car?"

[KainsChylde]

So I've hit a bit of a snag. The file is WAY too big to upload here, and mediafire and rapidshare both refuse to work for me. I am open to suggestions(as long as sais suggestions can handle a 280+ mb .7z file).

[somerandomdude]

So I've hit a bit of a snag. The file is WAY too big to upload here' date=' and mediafire and rapidshare both refuse to work for me. I am open to suggestions(as long as sais suggestions can handle a 280+ mb .7z file).

[/quote']

 

Public Dropbox

lol

 

Probably a bad idea for the ease factor, but a torrent might work as a last resort. I'd seed.

[KainsChylde]

I know nothing of torrents. There are mods here that use mediafire and rapidshare links in the thread. Click, new window, download. Is a torrent that easy?

[somerandomdude]

I know nothing of torrents. There are mods here that use mediafire and rapidshare links in the thread. Click' date=' new window, download. Is a torrent that easy?

[/quote']

 

I think they are easy...then again, I'm in school for network engineering.

 

It's the large choice of torrent clients and setting them up that will be the most difficult for people. It's not the worst option, but it's certainly not the best, especially when some are already struggling to keep up with Sexout. I know not everyone is as proficient with tech as I.

 

Once everything is set up though, it's just a click or two to download a torrent file, which is why it could be an okay option.

[prideslayer]

Torrents are easy to setup. Someone would have to run a tracker, unless you just want to upload the torrent files to random trackers and cross your fingers.

 

The problem with torrents is twofold. First, they are atrociously ill-behaved network applications. Opening at a minimum dozens, and often hundreds or thousands of simultaneous connections, they can easily crash a consumer grade router or switch just by overwhelming its state table. Your bandwidth will take a hit no matter what, and you will receive bogus connections attempts for days (if not weeks or months) after you turn your client off, making your firewall scream bloody murder. Even if you use the bandwidth limiting in the torrent software, that just limits the actual file transfer traffic. It does (and can do) nothing about all the people connecting to say "hay gimme this!" just to be denied due to bandwidth restraints.

 

Second, there's really "no stopping" what sort of files your torrent client is used for. When you connect to the network, you serve as a proxy for everyone else, that's how the system works. Not only does your system become a server for whatever you're downloading (which is what makes torrents so cool and fast to download stuff), but you're also a proxy for whatever your "neighbor" his hosting, via the anonymous connection methods in the system, designed specifically to defeat finding pirates -- though torrent users and authors will complain (and loudly) that torrents "aren't just for warez". This means you may unknowingly be serving anything at all, from harmless recipes to child porn to classified government material.

 

So personally, I don't use them. I'm waiting patiently for the next p2p file sharing system to come along. One that has real access controls (both ingress and egress) as well as less focus on anonymity.

[KainsChylde]

Ok, short version of long answers: Torrents not for Kain. Gotcha. Next?

[prideslayer]

Usenet? Long before torrents.. long before the web.. there was usenet. Split up the file, uuuencode it, and post to usenet. Upside: really easy, zero risk, unlimited file size.

 

Downside: There are probably half a dozen people here who have the foggiest idea wtf I'm talking about, so ease of use is right out the window.

[somerandomdude]

Torrents are easy to setup. Someone would have to run a tracker' date=' unless you just want to upload the torrent files to random trackers and cross your fingers.

 

The problem with torrents is twofold. First, they are atrociously ill-behaved network applications. Opening at a minimum dozens, and often hundreds or thousands of simultaneous connections, they can easily crash a consumer grade router or switch just by overwhelming its state table. Your bandwidth will take a hit no matter what, and you will receive bogus connections attempts for days (if not weeks or months) after you turn your client off, making your firewall scream bloody murder. Even if you use the bandwidth limiting in the torrent software, that just limits the actual file transfer traffic. It does (and can do) nothing about all the people connecting to say "hay gimme this!" just to be denied due to bandwidth restraints.

 

Second, there's really "no stopping" what sort of files your torrent client is used for. When you connect to the network, you serve as a proxy for everyone else, that's how the system works. Not only does your system become a server for whatever you're downloading (which is what makes torrents so cool and fast to download stuff), but you're also a proxy for whatever your "neighbor" his hosting, via the anonymous connection methods in the system, designed specifically to defeat finding pirates -- though torrent users and authors will complain (and loudly) that torrents "aren't just for warez". This means you may unknowingly be serving anything at all, from harmless recipes to child porn to classified government material.

 

So personally, I don't use them. I'm waiting patiently for the next p2p file sharing system to come along. One that has real access controls (both ingress and egress) as well as less focus on anonymity.

[/quote']

 

Some of that is worst case scenario, but yes, the multiple connections are the biggest problem since the users themselves have to host it. There would be lag in some cases, especially for those in low bandwidth countries.

 

And actually, now that I think about it, having to upload a new torrent for each new update is a really bad idea. Forget I said anything. I'm just being a dumbass.

[prideslayer]

I think what I want to do, in my FOMMalike thing, is add support for a remote package/mod installer definition file. So you could say just download an xml file that would list all the packages (zips, fomods, etc) the mod needs, and then the program would fetch them for you itself.

 

This would be a small file to download and be easy to maintain. Some mods (like sexout) wouldn't need maintenance, since the download link is (usually) always the same. Others like SCR that put the version number in the filename would need to have their entries updated, but doing that would be a lot easier than downloading, extracting, and then recompressing the mod into a new archive to upload somewhere.

[snarfies]

Torrents are easy to setup. Someone would have to run a tracker' date=' unless you just want to upload the torrent files to random trackers and cross your fingers.

[/quote']

 

You don't need to specify any valid trackers with a DHT-enabled torrent client - which is pretty much all of them. Personally, I use open trackers such as http://openbittorrent.com/, which also lists alternatives.

 

See also https://torrentfreak.com/common-bittorrent-dht-myths-091024/

 

The problem with torrents is twofold. First' date=' they are atrociously ill-behaved network applications. Opening at a minimum dozens, and often hundreds or thousands of simultaneous connections, they can easily crash a consumer grade router or switch just by overwhelming its state table. Your bandwidth will take a hit no matter what, and

[/quote']

 

I have never, ever, ever experienced such a thing, and I've seeded quite a few anime titles that I've subtitled myself, plus a few other things. Actually, I have a number of things on perma-seed from a FreeNAS box right now (FCOM Superpack 6.4.2 for example).

 

Second' date=' there's really "no stopping" what sort of files your torrent client is used for. When you connect to the network, you serve as a proxy for everyone else, that's how the system works. Not only does

[/quote']

 

So, you are saying a torrent client will just upload/download anything and everything wether you tell it to or not? Gonna need to see some proof of that one, because I'm pretty sure no modern torrent client works that way.

[prideslayer]

Torrents are easy to setup. Someone would have to run a tracker' date=' unless you just want to upload the torrent files to random trackers and cross your fingers.

[/quote']

 

You don't need to specify any valid trackers with a DHT-enabled torrent client - which is pretty much all of them. Personally, I use open trackers such as http://openbittorrent.com/, which also lists alternatives.

 

See also https://torrentfreak.com/common-bittorrent-dht-myths-091024/

 

If you try seeding through just DHT with a magnet, chances are it's going to take a while before anyone here finds "you" through interconnected swarms unless you are extremely well connected. You don't need to use a tracker but they do make things easier.

 

The problem with torrents is twofold. First' date=' they are atrociously ill-behaved network applications. Opening at a minimum dozens, and often hundreds or thousands of simultaneous connections, they can easily crash a consumer grade router or switch just by overwhelming its state table. Your bandwidth will take a hit no matter what, and

[/quote']

 

I have never, ever, ever experienced such a thing, and I've seeded quite a few anime titles that I've subtitled myself, plus a few other things. Actually, I have a number of things on perma-seed from a FreeNAS box right now (FCOM Superpack 6.4.2 for example).

 

I doubt your level of experience with torrents if you've never experienced it, because it's quite common. Everything from cheap hardware (netgear, dlink) overheating to slightly more expensive hardware (cisco/linksys) not having the memory to keep track of state tables (meaning you must disable SPI). Windows has limits on the number of fully open and half open connections as well, and these are routinely run into by people trying to increase their torrent download speed by raising the number of connections allowed. This alone isn't bad, but the net effect is that other network applications (like say your browser) stop working until the torrent client quiets down. Unrelated to bandwidth saturation.

 

Second' date=' there's really "no stopping" what sort of files your torrent client is used for. When you connect to the network, you serve as a proxy for everyone else, that's how the system works. Not only does

[/quote']

 

So, you are saying a torrent client will just upload/download anything and everything wether you tell it to or not? Gonna need to see some proof of that one, because I'm pretty sure no modern torrent client works that way.

 

You know, I was thinking of Gnutella, not Bittorrent, though I though I remembered torrent clients like Az...(something) beginning to implement something similar.

 

It's not that it is set to just "upload and download anything and everything" but that requests can be routed through intermediate nodes, as an anonymizing feature. A asks B for some chunk.. B asks C (who isn't connected to A), and so on. When the chunk is found, it's returned back along the same path. No particular hop knows if the node they are sending the response to is the actual node that wants the data, or just another node in the chain. This makes the act of requesting files and even serving them somewhat anonymous.

 

The downside is that every node from A to Z in the chain is "unwittingly" a sort of co-conspirator if A is asking for something illegal that Z has; the something doesn't even have to be illegal in the country (or countries) that A and Z are in, but might be in the country D,E, and F are in.. which exposes them to risk.

 

Maybe this never got off the ground with bittorrent, but I am (was) pretty sure that one or two of the popular clients implemented it as a way to get around NAT/proxy issues where A and C can both talk to B, but not to each other.

[KainsChylde]

Well, unfortunately without an upload solution this concept is officially dead. Sexout is just too big. I have abused google in ways never intended and I am just drawing a blank. Sorry guys.

[wrajjt]

It must be possible to split the zip-archives and upload them one by one to rapidshare/mediafiles/whereever, or using a public torrent tracker such as thepiratebay's?

[KainsChylde]

I went balls-out and tried it. Here's hoping it works.