Quote:
|
I asked moak to explain his post and his great ideal for gnutella which he spoke of. Which im still waiting...
|
Sorry, it seems that moak left the GF, if you want to know why (if you don't already know), please come to the irc channels and ask him.
Quote:
|
You just posted bashed programs and the network today.. and on topics that dont concern you.
|
You just asked for what's wrong with the network, and i listed some facts that are discussed in many threads, they are not only my opinion...
Quote:
|
Like "spyware" worry about your own box. Many people know about spyware but just dont care.
|
If someone really doesn't care, he can install as much as he want, but i c it on this pc (a multi user pc) where i have to remove accidently installed spyware (e.g. by my sister) every 2 days.
The problem are not people who don't care, the problem are people wo don't KNOW it!
If you'd install a programm, would you uncheck "CommonName Toolbar" for example (or would you try to remove it if it's automatically installed)?
Quote:
|
What about programs like xolox and others that dont or wont partcipate?? And how do you stop programs from implementing "bad" features on a open network?
|
The first question is easy- if you want to implement it, you can do it, if you want to add your ideas, you have to be member of the small community of developers, and if the protocol doesn't fit your needs, you don't have to use it.
bad features...hm... i haven't thought much about that yet, maybe it could work like this: If a member of this community implements a bad feature, he'll no longer be a member; if someone else implements a bad feature, his client will simply be incompatible.
Quote:
|
100% compatible is impossible.
|
I know it's not possible, but it should be a main goal to get near the 100%.
Developers don't need to implement all features, but if they are to far away from the other clients, they are incompatible because some features are *NEEDED*
They then have to search a solution, e.g. finding another protocol, or impementing these features.
Quote:
|
(Developers.net)> Good idea but how will the developer net get enough users on it to sustain the net and be large enough to accurately portray the current network..
|
That's really a problem, maybe we could switch some clients into a both-net mode, that they use the normal net, and have some ports free for building a test net, which is not directly connected to the user net (it would be about 1% more CPU usage to the users) - that's the price for new updated software.
Quote:
|
Whats the GDC? If you mean the GDF then it think your wrong. Look at the second paragraph of the next question.
|
No i meant GDC, the GnutellaDev Community, founded in #gnutelladev. It was a try to collect some developers and develop the clients with equal feature decisions etc.
Quote:
>To come to a conclusion, my opinion is, that all not-commercial developers should leave the GDF and meet at another place to discuss and decide equally (e.g. Polls) what to do.
There is no reason to do that since the GDF is an open and free place for everyone started by gnutellahosts.com and a idea like that really goes against what the GDF is suppose to be. It allready is a neutral place if some programs dont partcipate then thats their decision they can live with it.
|
There is a reason to leave the GDF, i repeat it: Vinnie!! Look in my posting you quoted to get the answer why he's the reason.
Quote:
|
Polling to see what is done i dont think should be used on a regular basis because its slow, and because its an open network people wont change their mind because the poll says otherwise. Being an open network is really gnutella's greatest strength and greatest weakness..
|
i forgot to say, pollings should be made in the member area, where the developers are, and here it is how it could work:
Someone has an idea, say SuperduperGIGApeers. He writes a description about it. Then, it will be discussed and changed in CHAT or FORUM, with a time limit, let's say 2 weeks. Then there's a poll where every member can chose what's best for him. At the end, say another week later, it's ready for implementing into the Developers.net, or if noone wants it, it will not be used.
Any questions?
