DC++

cologic

http://dcplusplus.sourceforge.net/forum ... php?t=2292

cologic

Ugh, please not another fucking protocol extension to appease meddling ops.

cologic

Look at the "Popup private messages" option, which accomplishes your "Close all windows exept hub windows" request in a slightly different manner.

cologic

Dj_Offset produced an interesting reworking of the DC protocol ; it even lacks blatant spelling errors. It: Removes the silly lock/key system. Identifying clients is done with a command for that purpose, rather than hijacking a system that's spectacularly failed to keep unauthorized clients out of H...

cologic

a little late but if you are still having any problems with rollback incosistency change the rollback to 0 in settings, for some reason rollback messes up sometimes in every program I've used to transfer. KaZaa, FTP, WinMX, Grokster, eDonkey, napster, ICQ, AIM, Messenger and a few others. Thanks fo...

cologic

It's a style, not a lack of intellegence.

intelligence

veteran like Gargoyle

This isn't a metaphor, and thus should be:

veteran such as Gargoyle

Finally, "quote" isn't a noun, so:

But the quote was

should read as

But the quotation was

cologic

My main issue with SSL is that (1) implementing such a complex protocol oneself, especially when openssl has had such security issues and was written by more competent people than many in this thread (including me), is stupid., and (2) there are no GPL-compatible libraries for it I've found on Windo...

cologic

0.161 or so. and I remember the introduction of extended tags in order to placate ops, at a time when DC++ wasn't quite so dominant.

cologic

Okay, for those who want to look at a slightly prettier version of the code: <fake prompt> cat blah.c | cpp | astyle # 1 "<stdin>" # 1 "<built-in>" # 1 "<command line>" # 1 "<stdin>" # 9 "<stdin>" char _DAH_[]="ETIANMSURWDKGOHVFaLaPJBXCYZQb54a3d2f16g7c8a90l?e'b.s;i,d:" ;main ( ){char * _DIT,* DAH_,*...

cologic

cologic

So far, the general tone was "the more, the better"; which is true from a purely technical point of view, but becomes false past a certain point from a global point of view. The real question is : Where is that certain point ? Obviously, the distributed hub concept doesn't need to be scalable beyon...

cologic

each slave hub handling 500 users Each slave must effectively handle 1,000 users - 500 clients, 499 other slaves, and the master. Thus, a connection which can handle 500 "users" will handle no end-user clients, but the 499 other slaves and the master, each of which will require as much bandwidth as...

cologic

Usually by the time I notice, they're downloading already.

cologic

The feature works beatifully for me, though I've heard many compaints about its ineffectiveness by others.

cologic

I figured if it was hard coded into the program that would force people to abide by the priority flag rules it would only work if it were with some form of nmdc... with dc++ being open source then those saavy programmers would be able to fake priority a flags on all their different sources so never...

cologic

they are guarenteed 1 slot by priority if someone elses slots are taken up by multisourcers. What mechanism guarantees them this? It could work... it really could... Sure, if people suddenly ceased being selfish. And as for the switch that hub owners could turn on and off... that was for the "leech...

cologic

This is precisely the type of suggestion I had hoped to avert with my previous post (read the last couple of paragraphs of that to see what I mean). Its fundamental flaw is that is relies on users to voluntarily relinquish slots, when they have no incentive do to so, and plenty of incentive to keep ...

cologic

Because currently search requests are non-deniable. This behaviour is implicit in the protocol, but more importantly are implemented with stupid bots on the hubs. No search results from certain search requests - too bad, then you must be using a leech client. Unfortunately, I think it is "too late"...

cologic

These two threads contain further information, and may answer your question. Please read them before further commenting. (Search for UserIP to find others.)

cologic

This thread discusses the issue at length, though as a mandatory 'feature'; I would imagine the responses to its being optional will be different.

cologic

How about limiting the ability to download a file from multiple people to around two or three total. I think even just that would be a big help. If this feature makes it in, no such limitation will stick - don't plan for it. FIrst if this enabled all download slots and such control is handed over t...

cologic

You canÃ‚Â´t just discuss in one topic a change of a protocol, The way your all talking is a whole new p2p network. Not if the extra messages among the hubs necessary to maintain the multihub network are filtered out before the users ever see them; in that event, the client can't distinguish this v...

cologic

I'd left this thread for dead, but:

Ok, IÃ¢â‚¬â„¢m going to use only facts and leave the arguments to you:

Ha. Ha. Ha.

cologic

If we have multiple hubs, every hub sends its chat/search/myinfo and whatever to the other hubs, and then that hub has to send that to it's connected clients. Every hub will send out more data, requiring more bandwidth and we have not solved the bandwidth issue, rather the contrary. A multihub netw...

cologic

The hub will need to have (for say 500 users/per hub): * Roughly 256 MB of RAM for uncompressed filelists in RAM It wouldn't store filelists, per se; what it really needs is a mapping from hash values to lists of users. * Recieve filelists if anyone connects or does a "/refresh" It should receive a...

cologic

I didn't mean to imply a hierarchical $Supports statement - though I can see the case for one, that's not what I'm proposing here.

Rather, Meta just happens to be one of the $Supports arguments, and order doesn't particularly matter.

cologic

The best suggestion I've heard to far involves: $Supports <blahblah, the usual DC++ supports> Meta <additional specific metadata types supported>| for example, neglecting the blahblah parts: $Supports Meta TTH| where TTH is tiger tree hashing. One more new client-client command seems necessary: $Get...

cologic

We can stay online for almost 24 hours with over 1000 people. There are some stability problems, but it seem to work a bit now:). This would seem to argue pretty strongly that client knowledge/involvement is not, in fact, necessary. The PtokaX guys told, they could imagine the thing, but they also ...

cologic

Change #1 is obviously needed in the client, since in the normal protocol the client only listens to the Server IP. It is impossible for another IP(computer/connection) to send the search request to the client, as they would not be recieved. (not even sent). Which is as it should be: clients connec...

cologic

http://dcplusplus.sourceforge.net/forum ... php?t=2312[/url]

cologic

Could someone explain again what the role of the client is in relaying? If you want to involve it in any substantial way in this, I'd like to see much more acknowledgement of the security issues. Further, much as it kept getting brought up, I see absolutely no need for any client-side modifications:...

cologic

You mean like ADL search?

cologic

The hub could use that information to decide which users to which the search request is forwarded - if a user's known not to have a particular file, then don't send him the search.

That said, I do find that direction of discussion odd in a thread title "Distributed DC".

cologic

Read this thread before commenting further, for the sake of not forcing people to spend time repeating old arguments, please.

cologic

PRIVMSG and NOTIFY are used by CTCP, so my description includes that; that's probably the easiest way to transfer arbitrary, non-chat messages between users. DCC, however, also related to CTCP, however, I dislike: it's not indendent enough from the IRC server in its operation.

cologic

But, another solution that keeps in mind the availability of more CPU and memory would be to do some of the tracking on the hub. Some say it's a bad idea legally to track filenames and locations on the hub, but it's very much a grey area. I'd say a good compromise would be to keep track of hashes o...

cologic

I notice a tendency here among some to want to recreate IRC, to some degree. I've been toying with the idea of just going all the way with that and implementing DC-on-IRC as a set of modifications to IRC clients, with the following changes: Nearly the entire client-hub protocol is ignored, and the I...

cologic

the advantages for hub newcomers and users not on super-fast connections Users on faster connections should be able to open more download connections - they can better handle the bandwidth it'd use. Restricting the number of download slots a user has will result in suboptimal slot usage on the hub ...

cologic

I'm claiming that ops on the DC network have shown a tendency to exert as much control as is practical. If DC++ were to allow them to expect users to display their download limit, many of them would apply similar reasoning as you that it's something else about which they can make a rule, so why not?...

cologic

To me a DL slot indicator is merely a means by which to offer more options for OPs to choose from in how they decide to run their hubs I don't want ops to have an expectation they can run their hubs in some manners. I think all users have a right to keep their DL slot info private if they so desire...

cologic

Heh. I'll shut up now.

cologic

$UserIP or $MyIP what difference does it make, he's supporting both. I would prefer to keep the size of the protocol hubs and clients are expected to support small (if MyIP doesn't catch on, it's relatively useless; if it does, it's yet more redundant baggage that has to be implemented by anyone wa...

cologic

Conflicted here - I recognize this as something of a tangential topic to the thread, but not really substantial enough for a new one. Oh well, anyway: http://dev.direct-connect.nu/dcext/ lists some software which supports $UserIP - it's slightly more supported than MyIP, but more importantly, it's a...

cologic

in case clients only support one of the 2, then I might as well support both

Heh my client does.

But your client is the only one you've listed that supports MyIP - why not just change your client, to be compatible with the expanding UserIP-using DC world?

cologic

On some ocassions we had to reset the router too. Um, you weren't running the hubs on the same connection, behind the same router, were you? That'd be kind of useless... With an advanced relayServer it would be possible, that it could act as a HUB. Clients could simply connect to it, every command ...

cologic

How does the bandwidth usage break down more specifically? About how much is used by each of searching, chat, and administration? Argh, stupid Java implementation hung IE on the Mac just now, lost an almost complete post. Anyway, I'll try to do more than glance off the question: Total messages: bun...

cologic

Regexes without backtracking?

cologic

1. (The easier one...: Hubs shouldn't let users/clients be relays, Hub owners should setup relay servers and let some users connect to them. Okay, I have no issue with this, but it sounds much more like what I suggested anyway than this system of, for example: $Supports ... DDCP| $ddcReady2Relay 12...

cologic

No, Clients cant be trusted. You are asumming that people would naturally want to report others. Trusting a client is like trusting another human being to be honest. Huh? Yeah, clients can't be trusted to act kindly towards other clients competing for slots; if provided a way to say "look, evil cli...

cologic

HaArD: we not only want to connect the chat, but tu expand the maximum user limit on the HUB. The linux HUB, which we are running now supports this thing, the problem is: each HUB runs well with 600-900 users, but in linked mode each can hold just a few hundred, above that they get out of sync in j...

DC++

Search found 306 matches

Dj_Offset's DCTNG

Metadata support in the client-client protocol

Idle thoughts about IRC