hekate
flood
| hekate | flood | |
|---|---|---|
| 1 | 47 | |
| 68 | 2,040 | |
| - | - | |
| 10.0 | 7.9 | |
| almost 11 years ago | 17 days ago | |
| C | TypeScript | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hekate
-
Torrent client to support large numbers of torrents? (100k+)
The post in 2015 you have linked is still the best answer as torrent clients have barely changed. Your torrents have to announce every 45 mins or they will die out, so concurrent instances of clients is the answer. You might try to reach out to the authors of Hekate to see if their archived project can be restarted or resolved.
flood
-
Show HN: PikaTorrent, a modern, multi-platform, open source BitTorrent app
Why bake libtransmission into the app instead of just using the transmission daemon's RPC?
What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.
I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]
1: https://github.com/transmission/transmission/blob/main/docs/...
1: https://github.com/jesec/flood
2: https://github.com/ronggang/transmission-web-control
-
Looking for a Multi-User Torrent Client...
Only one that I'm aware of is Flood: https://github.com/jesec/flood
-
Self Hosted Roundup # 29
If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.
-
qBittorrent v4.5.1 release
You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/
-
current state of linux clients that can manage 20k+ torrents (~40tb)
One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.
-
Seedbox With Great Mobile Interface?
You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile
-
Feature rich web ui skin with pages
https://flood.js.org/ ?
-
Looking for a torrent setup to seed 5k+ torrents
If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)
-
Beautiful new BitTorrent app just released in beta
qbitorrent-nox with flood-ui
-
Transmission 4.0.0 (Beta 1) - Resource Efficiency & Code Modernization
Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood
What are some alternatives?
VueTorrent - The sleekest looking WEBUI for qBittorrent made with Vuejs!
qBittorrent - qBittorrent BitTorrent client
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
docker-qbittorrent
flood-for-transmission - A Flood (https://github.com/Flood-UI/flood) clone for Transmission
deluge-web-dark-theme - A modern dark theme for Deluge Web UI with custom accent colours and updated icons.
qbit-matUI - A material WebUI for qBittorrent, written in Angular.
docker-transmission
uptime-kuma - A fancy self-hosted monitoring tool
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
qbt-theme - collection of themes for qbittorrent
watchtower - A process for automating Docker container base image updates.