Some of these Snoopbot networks consist of 150 instances minimum PER bot. I've found 8 Snoop networks this year including what I think is "m_a_v_e_r_i_c e_y_e" I'd consider myself an expert at identifying bad peers. Maybe there can be another option level excluding 'pieces' "6 - Max Info (minus piece transfer)" Initial Bitmap pieces of LOCAL and PEER. One of the main things i'd like is slightly more info in the "Event Log" tab on level 5+. I'm making a wish-list and if devs implement anything, some regular donations will be forthcoming haha! It's only fair?Īlthough this is only a hobby for me as I guess it always has been for the devs? I have suggested several ways Tixati could identify bad and automatically deal with unwanted behavior. Is there anyone on here who can add anything to this? (08) AirISP (RU) Limewire 2.1.0 < joint network trading as SimpleCloud RussiaĪll of the above AntiP2P implementations each have certain flawed 'characteristics' which enables them to be very easily spotted. (07) COMFORTEL (RU) Limewire 2.1.0 < joint network trading as SimpleCloud Russia (06) DTEC-Softlayer libtorrent/1.1.9.0 Self Declared AntiP2P company (Very obvious Peers) (05) NFOrce NL DelugeTorrent 1.3.6 < Fasthosts and NFOrce seemingly combined network (04) FASTHOSTS UK DelugeTorrent 1.3.6 < Fasthosts and NFOrce seemingly combined network (03) Contabo #2 Azureus 2.0.6 Utterly incompetent programmers (Terrible understanding of P2P) (02) Contabo #1 MonoTorrent 0.0.0.8 Total giveaway very lazy setup (01) Amazon AWS libtorrent 0.13.6 Clever setup and absolutely EXTENSIVE 150+ instances minimum BotNet Host Provider Bad Peer Client BotNet type
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |