viktorelofsson

7 ms·

31.
by viktorelofsson 10y ago
No, it does not, sorry. I've been asked this before and perhaps it's something I should prioritize :)
32.
by viktorelofsson 10y ago
Yeah, that's what I'm planning in order to keep it small and tidy.
33.
by viktorelofsson 10y ago
I've split the project in two parts, PicoTorrent and PicoTorrentCore. PicoTorrentCore is cross-platform and builds on GCC4.8. The linux directory contains build scripts to build on Linux, which is used for the TravisCI builds.
34.
by viktorelofsson 10y ago
Oh, yeah, it seems as it is CMake standard to put the if-expression inside the else-parenthesis as well. It is not an elseif.
35.
by viktorelofsson 10y ago
Yes, that's a good suggestion. The readme is due for a rewrite so I'll make sure to mention that somewhere up top! EDIT: the parent post was edited, and this comment was written for the original post.
36.
by viktorelofsson 10y ago
It should be correct - or at least, it works for what I use it for :) What is odd about it?
37.
by viktorelofsson 10y ago
It's been a few releases in the last 168 days when I announced PicoTorrent on HN and I'd like to get some input on both the progress as well as the new WebSocket API. You can find the relevant API documentation at - http:/&#
38.
Show HN: PicoTorrent 0.10 released – WebSocket API included(github.com)
38 points by viktorelofsson 10y ago|26 comments
39.
by viktorelofsson 11y ago
Hi, the reason PicoTorrent is 20MB installed is that we ship the PDB file in the installer. In the future, the PDB file will be optional. The actual executable is around 5,5MB. We ship the PDB file with the installer to help with issues now
40.
by viktorelofsson 11y ago
The PicoTorrent executable is somewhere around 5-6MB. RAM and CPU usage should be low to tiny if I haven't made a mistake and leak memory all over the place :) The reason our executable is so much bigger is that we have a few indirect
41.
by viktorelofsson 11y ago
Interesting! I did not know this. If their tweaks work, I guess Deluge may have a performance advantage. We follow the latest vanilla libtorrent sources (not bound by releases), and try to keep our C++ as close to the Windows API as possibl
42.
by viktorelofsson 11y ago
Great suggestions! Actually, one of the inspirations for PicoTorrent came from this blog entry, http://blog.libtorrent.org/2012/01/seeding-a-million-torrent... . I haven't had a chance to test it with a millio
43.
by viktorelofsson 11y ago
This is true, however we still run PicoTorrent under the default libtorrent peer ID which is whitelisted on a few private trackers as well.
44.
by viktorelofsson 11y ago
Both are built on Rasterbar-libtorrent and should provide equal performance if configured the same, which I would definitely see as a goal. Feature wise, PicoTorrent is lacking. Most popular features will be implemented, along with a plugin
45.
Show HN: PicoTorrent, a tiny BitTorrent client for Windows(picotorrent.org)
58 points by viktorelofsson 11y ago|21 comments
46.
by viktorelofsson 12y ago
Done and done! https://github.com/hadouken/hadouken/wiki/Getting-started-on...
47.
by viktorelofsson 12y ago
In what regard? I only have numbers for Windows, and mostly memory-based numbers which will vary depending on load. Here's some recent numbers I pulled, - It idles at ~1.5-1.8MB with no torrents. - With 10 seeding torrents, it runs at
48.
by viktorelofsson 12y ago
I'm gonna try to address everything at once here :) (Private) trackers are very picky about what clients they allow. This leaves me with few alternatives when it comes to BitTorrent libraries, Rasterbar-libtorrent being one of them. Ra
49.
by viktorelofsson 12y ago
Author here, some background information. I'm a C# developer by trade and currently in the end-phase of a total rewrite from C# to C++ for this project in order to get it running cross-platform as well as increase performance. This is
50.
Show HN: Hadouken – a cross-platform, extensible BitTorrent daemon(github.com)
12 points by viktorelofsson 12y ago|10 comments