Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Transmission 4.0.0 beta 1

github.com

Post reply on HN
Print view View original

121–130 of 262 posts

Re: Transmission 4.0.0 beta 1

#121

Post by yaddaor »

lynguist wrote: post #87
diegoholiveira wrote: post #5

After Netflix and others streaming services, I stop using Transmission. What’s the current usage of BitTorrent?

That doesn’t make sense to me. There are 200,000 movies, and Netflix and others catalogue 2000 of them. If you think of a movie to watch there’s literally 1% chance that it will be available for streaming. I have almost never watched a movie I seeked out on the streamers. It’s the other way round, the streamers offer me some movies and if I’m interested I watch it. But their catalogues are laughably small. Completely…

Nitpick, but you are off by about one order of magnitude for the number of movies available on Netflix. It's closer to 20,000.

Re: Transmission 4.0.0 beta 1

#122

Post by daptaq »

denton-scratch wrote: post #109
xpressvideoz wrote: post #101

Earlier quoted context omitted.

FYI, transmission-cli is considered deprecated by the Transmission developers. Using both transmission-daemon and transmission-remote is the recommended approach. Actually, transmission-cli uses transmission-daemon internally and they share the same configuration. transmission-cli is still useful for one-off downloads, but I still prefer the recommended way because I'd like to seed older torrents some more time.

> transmission-cli is considered deprecated Wah! Bad news! I like to kick off a download from an SSH shell. Now I have to find out what transmission+remote is.

You could also check out rtorrent: http://rakshasa.github.io/rtorrent/, but I remember reading that development has stalled on that project.

Re: Transmission 4.0.0 beta 1

#124

Post by aol1306 »

denton-scratch wrote: post #109
xpressvideoz wrote: post #101

Earlier quoted context omitted.

FYI, transmission-cli is considered deprecated by the Transmission developers. Using both transmission-daemon and transmission-remote is the recommended approach. Actually, transmission-cli uses transmission-daemon internally and they share the same configuration. transmission-cli is still useful for one-off downloads, but I still prefer the recommended way because I'd like to seed older torrents some more time.

> transmission-cli is considered deprecated Wah! Bad news! I like to kick off a download from an SSH shell. Now I have to find out what transmission+remote is.

aria2 can download a torrent from a magnet link given as CLI parameter.

Re: Transmission 4.0.0 beta 1

#125

Post by defrost »

MaxMatti wrote: post #114
captainmuon wrote: post #112

Good to see it being in active development. But the one feature I'm waiting for is a network whitelist. For example, it should never connect over my home or office network, but only via anonymous VPN. (Edit: I know you can do this already with firewall rules, or containers, but I don't trust myself to not make a mistake. Ideally this should be part of the OS. You should be able to right-click somewhere in the window…

I'm using namespaced-openvpn to restrict transmission to one network and you could limit the amount of concurrently active files to one, effectively downloading them sequentially. Or do you want to download each file sequentially?

I would hazard they are asking for file-block sequential downloads from start of file to end, so they can start watching a movie while it is still downloading and be assured that the first parts of the moview are present without gaps ...

This goes against the general cluster inter-peer everybody swaps what they have so far w/out reference to file position for maximising transmission within a swarm design of the torrent protocol.

Re: Transmission 4.0.0 beta 1

#126

Post by captainmuon »

tambourine_man wrote: post #113
captainmuon wrote: post #112

Good to see it being in active development. But the one feature I'm waiting for is a network whitelist. For example, it should never connect over my home or office network, but only via anonymous VPN. (Edit: I know you can do this already with firewall rules, or containers, but I don't trust myself to not make a mistake. Ideally this should be part of the OS. You should be able to right-click somewhere in the window…

I have to agree with them, it’s antithetical to what torrent is about.

Depends on what torrent is about. For me, it is about watching shows that you can't officially watch where I live yet. Once I week, I hit up a site and, click a magnet link, and a couple of minutes later I can watch my favorite show. (The cost of the VPN is incidentally about the same as a streaming subscription. I think for this reason it is tolerated by the powers that be.)

I don't expect torrents to be available for a long time. Only very few people keep the torrent entry in their client alive for long, even though I keep around all the files. This is as opposed to eMule and older systems, where you can download any file in the user's media folder.

Re: Transmission 4.0.0 beta 1

#127

Post by netheril96 »

hrbf wrote: post #32
netheril96 wrote: post #20

As a Chinese, I really need the anti leeching capabilities, as too many people here use Xunlei that only download but never upload. Sad to see that the maintainers skip this again.

It’s probably impossible to track that with any meaningful precision. Historically it’s the (central) tracker that implements the bookkeeping.

It’s quite easy to block Xunlei. First, they identify themselves in the connection. Second, no matter how much you upload to them, they always report zero progress.

The maintainers reject the proposal to block by client ID. But they never consider the second method.

Re: Transmission 4.0.0 beta 1

#128

Post by politelemon »

haunter wrote: post #67

Love Transmission but went to picotorrent a few years ago, even smaller footprint https://github.com/picotorrent/picotorrent Sadly it’s Windows only

There does seem to be a docker image for it through

https://hub.docker.com/r/picotorrent/server

but last updated 2 years ago, so not sure what's going on there

Re: Transmission 4.0.0 beta 1

#129

Post by netheril96 »

yaddaor wrote: post #117
netheril96 wrote: post #81

Earlier quoted context omitted.

There are already GitHub issues like this. The maintainers simply close them.

As is their right and somehow even their duty if it is not in alignment with the project's philosophy or goals. You can create a fork and implement the feature or pay someone to implement it for you. That's the wonderful benefit of free software.

So is my right to complain on HN.

Re: Transmission 4.0.0 beta 1

#130

Post by ifqwz »

KennyBlanken wrote: post #8

This release is really important if only because it supports BitTorrent V2 spec. Transmission has a huge market share, particularly in open source circles. Lack of support for the V2 spec has stopped many open source projects from migrating their torrents to the V2 spec, because transmission clients won't work. Please support and use other open-source torrent clients, because Transmission's long-standing history of g…

No post body was provided.
Post reply on HN