Yep, it must be a cool thing, but i don't think that it is a good idea.
1) All this p2p stuff has a listening port. (requires configuration, upnp
and so on)
2) Some protocols requires pre-configuration. For ei dc++ requires hub and
unique nickname.
3) In p2p world it's good to sid what u've
Yep, magnet - it's an URI. It's has some information about resource, but
doesn't specify how to get it.
The problem is:
1) i'm web coder and i'm not good at c++.
2) I want to discuss this to implement a proper idea, may be someone have
better ideas, or he knows why this shouldn't be done this
On Sat, May 16, 2015 at 1:31 PM, Vladimir Perepechin
vovochk...@gmail.com wrote:
Hi everyone :)
I was thinking about implementing my idea
https://forum.kde.org/viewtopic.php?f=83t=126352 .
While digging sources i've understand that my idea was incorrect, and there
is nothing to do with
El Dilluns, 18 de maig de 2015, a les 22:52:27, Vladimir Perepechin va
escriure:
Yep.
The use case is following:
magnet links are used by absolutely different applications:
1) Torrent (ktorrent)
2) DC++ (eiskaltdcpp)
3) eDonkey
Every application uses magnet links, but! Magnet links for
Yep.
The use case is following:
magnet links are used by absolutely different applications:
1) Torrent (ktorrent)
2) DC++ (eiskaltdcpp)
3) eDonkey
Every application uses magnet links, but! Magnet links for every app are
different. ktorrent can't handle links for dc++.
The problem is that
El Dissabte, 16 de maig de 2015, a les 21:31:49, Vladimir Perepechin va
escriure:
Hi everyone :)
I was thinking about implementing my idea
https://forum.kde.org/viewtopic.php?f=83t=126352 .
While digging sources i've understand that my idea was incorrect, and there
is nothing to do with
