Kulmegil
Member-
Content count
175 -
Joined
-
Last visited
Posts posted by Kulmegil
-
-
3rd try, and I hope there won't be any topic cleanup this time
But here goes:
(updated shoot with transfer ongoing)
-
-
Zion++ Blue
-
I'll try Reign of Fire
-
Yeah
-
PS I would like separate detection for limiter higher then 1Mb/s (1000kB/s let's say, coz some people do confuse units).
-
Valkunt starting 0.3.10 works fine with new dc++ based clients (and ApexDC++) both ways.
ShakesPeer 0.9.5 for sure (don't remember if older had own dctag)
SDC++ 1.00 RC9..
PS Generally I banned all clients older then DC++ 0.69 & 0.68 (with small exception for 0.674) based. And I still think I was to tolerant here
DC is P2P network and not museum. Besidedes it's good for overall both security and compatibility imho. -
If I wouldn't prefer extra functionality from FF extenstions it would be Opera. But I do
(I use Opera and FF together, Opera is mostly for secure sites, still FF is primary)
-
-
Final Destination 3 ?
-
If it'snot BCDC++ again... then maybe DC++ stealthy public? :)
-
Just don't ask. There are other peoples in the queue waiting to get the slot also (and for sure I wouldn't like if each user ask me for slot every time he has to wait). Resources like upload are always limited. So stay put and wait for Your turn.
-
Jumping from hub to hub is not the way for DC network. You pick Your best hubs with users having lots of good stuff and stick them (and search some new when necessary). If You want to find some rare file just go to some content oriented hub or use networks like eDonkey with much more "global" serach options.
-
/me vote no, coz me don't want situationes when useres are able to suppress chats and block all pms (next step) and becoming like unresponsive blockheads just taking space on userlist.
Not that I don't see the point in You're arguments... but DC is like P2P & irc-like network in 1. It wouldn't be half as popular if it would be just one of those. So dooon't change it!
-
exactly in:
File >> Settings >> Appearance - Options >> Sort favorite users first
-
But I'm thinking that some ...let's call it that... negligence was made in the past. Why don't we just define something new like $utf8 - something optionally sent by the hub at the very beginning when user is connecting (much like $HubTopic). It say that utf-8 encoding should be used on this hub. It's incompatible? SO WHAT!? Obviously all saying that ADC is next door and it will support utf-8 and it's gonna be cool are right... but if it would be implemented when first Unicode aware DC++ showed up, I'm pretty sure we would be living in Unicode version NMDC today. A shame imho.
There are obviously more fields where breaking some compatybility could lead to better DC world already today.
But the good thing is since that damn ADC is really close much of it will be solved at last.
-
Hunspell (OOo, Miranda, .. Firefox3?), or Aspell are probably the best choices currently. I don't know witch is better and I wouldn't dare to open discussion about it myself (both are open source, UTF8, have lot's of dictionaries...), but probably the one witch is easier to implement. I suggested miranda plugin because I count it would be easiest (convert it to something like peerguardian plugin?). The more difficult it gets the less chance to see it (this century at least:)
As for the resource usage I already posted my observations for IM plugin (uses Hunspell). Impact on memory looks minimal if You don't use the feature.
Whatever the way, it's goal that meters : it's suppose to do spellchecking "as I type", underline bad words and give context menu suggestions. It's the only reasonable way for IM style conversations.
-
It's one of the good ideas in speed mod, but You're promoting a questionable client on apex forum
-
So what's the real chance that few people using single IP will want to download from You at a time (unless You share over 10TB or something). Even IF all this changes that second user will have to wait a bit. World is moving into direction of giving each user unique IP (at least when IPv6 will kick in). Besides it's upto sharer to decide...
-
Did You enabled hideshare option (in addition to not sharing anything)?
PS
I really, really don't get how could people ever vote NO for adding this optional limit. Makes me wonder if they really know what was the question. Since benefits are obvious (to me at least) ... maybe someone can show me at least one argument against it? -
Still max upload slots per IP is wroth considering - probably even in ADC world where users are identified by unique CID (bad clients will give different CIDs on each hub to suck out more slots from You).
Exclude favorite users and "free" stuff (filelists, TTHL's, small files) from limit. And it's quite simple to implement.
wdc likes this -
Turn off segmented downloading, and it'll be gone ;)
-
PS Limiting connections from same IP already disciussed : http://forums.apexdc.net/index.php?showtopic=1011
I'm still voting for "yes".
-
Main purpose of DC is p2p (sharing), chat is only minor feature. SpellChecker would only decrease DC usability (higher memory usage, higher CPU usage etc.).If there should be some spellchecker, it should be implemented as a plugin in hubsoft. For example, some czech hubs warn you via ChatBot if you make some grammatical mistake ;-)
I would say 90% is for P2P and 10% for chat when I was starting. But today it's 50/50 if not less.
As for memory usage...
virtual mem / peak mem usage
16 384 kB / 21 596 kB with spellcheck (2 dictionaries)
10 508 kB / 16 764 kB with spellcheck (no dictionaries)
10 292 kB / 16 672 KB no spellcheck loaded
0.7.0 build #30 Unicode, 24 total plugins, after start - messageing window opened.
I would say it's worth considering at least (depending on difficulty of implementation).
It could be implemented as plugin (like guardian plugin in Zion++)
PS Spellchecking in hub is evil (except badword checking and spam checking) - should be done client side imho.
Game: Guess the DC++ client
in Lounge
Posted
nope, it's quite exotic (let's put a game level a bit higher) but also very old.
It's pub of course.