Exeem does not rely on a centralized server right? How can it be down?
Exeem does use a Centralised server that why no serious filesharer is even touching it
Exeem only begins a connection to the Exeem network when it begins an operation. On Exeem's initial connection to the Exeem network, it bootstraps. It does this by doing a DNS lookup on four FQDNs, all of which as of January 22, 2005 point to the same IP address. Exeem then connects to this IP address on port 1026, sends an Exeem packet with function "6". The server responds with a list of 20 or so Exeem Superpeers to connnect to. Subsequently, when one does a search or new files research, the Exeem client connects to these 20 hosts and does a search, or a request for new files.
http://www.infoanarchy.org/wiki/inde...Exeem/Protocol
ya when i noticed the seeds i was upping were no longer upping i gave up on it
to bad its not truely decentralized and the coders have not heeded my request for them to stop violating GNU /GPL as they base the program of a opensource program yet are not sharing the code back! if they were surley this network would not be 'down' like it is becuse people who cared would quickly act to make sure it was unstopable..
Kind of funny that your opposition can also easily be applied to your favorite network, ain't it?Originally Posted by AussieMatt
And for the record ALL p2p networks rely on centralisation of some kind even if only for peer discovery.
Not all p2p networks - gnutella can actually live without the gnutella web caches, but the program ends up going through a huge list of localled cached IP addresses. However, web caches are used because it substantially increases the connection speed (a few minutes compared to 20 some minutes without)
what happens when those huge lists of localised cached ip addresses expire? will their client quit connecting just like all of those kazaalite users we've seen complain recently of similiar maladies?
or like waste 1.5 ips that expire too
this is a problem of decentralization the chached ip tryout delete times? x tries? maybe a backup non deleted list for those times of high network stress thou i know these files would get BIG.
as long as you can find a way to import active nodes into your client it will be able to connect
eXeem.node.fix.feb28-reg.zip
good workaround. Thanks for sharing that. The point I wanted to get across was that all p2p networks require a way of discovering other peers and usually this is from centralised sources such as webcaches, or messageboards posting updated ip listings or even gateway servers that distribute and control access to the network.as long as you can find a way to import active nodes into your client it will be able to connect
One example I stumbled upon recently was after reinstalling a version of kazaalite that I had not used in 2months it wouldn't connect...the cached list of ip's stored in the registry (all 200 of them) had expired so it had no starting point.
My initial thought to remedy this problem was to go to FastrackCentral (no http link for this site pls) where I was going to look for and install an updated peer cache of ips in the form of an .snl file (can't remember the correct extension) but its the default extension for exported supernodes lists in kazaa supernodes.
It was there that I found a post by a very astute user who noticed Imesh had a static server (supernode server) something like 'supernode.imesh.com' (don't want to use the exact name) but it was clearly obvious it was owned by the imesh p2p program owners and it acts as a gateway to the network by distributing supernode lists.
All I had to do was take that ip and the port number...punch it into kazaasupernodes and as soon as kazaalite connected to that working ip address it was instantly updated with a fresh list of working kazaa ips.
If attention was turned to that particuliar ip address it would be shut down by interested parties currently involved in litigation with the fasttrack networks.
I'm amazed it was overlooked already.
you mean the one at fm2.imesh.com:1214
lol
that's the one...i wonder how long it will be before it is changed or goes down now?
as long as you can find a way to import active nodes into your client it will be able to connect
hmm
nuff said
btw ourthing send me those thingies via thingies.
cheers
The problem with Exeem as it currently stands is that it it connects to one IP based in Texas .Other networks like Gnuttella ,emule ,MUTE ,Ants even IRC have multiple IPs they can connect to if needed by way of peer discovory .Exeem has a single point of failure at the moment and sends encrypted info back to this centralised server .The encryption seems to be to protect the codebase as quoted Ashton who was the Kazza developer for Mac and the developer of X-factor who has been reverse engineering the exceem source and is looking at releaseing a open source Exeem client in the near future, there are also many other decentralised torrent aplications being developed so its just a matter of time for this network to be exposed .
how does a brewery operator know so much about p2p? I'm astounded. Really I am.
Posting Permissions
Reply With Quote
Bookmarks