Would like to see a setting to enable or disable emails for account creation. Email verification is nice for private trackers, but a basic user/pass authentication method is great for semi-private trackers that want to deter its users from spreading the torrents to public forums but don't want to collect and store emails, whether due to privacy or security reasons.

Option for new users to only be able to register with a generated invite link.

Original image links extracted from the README:

• 
• 
  I think that this may be the result of implementing the changes to the repository structure.

Error notification can be optimized to make it look better for some errors

Torrust Index should have an option for manual account activation.

Guests will then be able to signup for an account and optionally verify their email. But they won't be able to login until a Torrust Index admin activates the pending account.

Hi there,

When you run the tracker with no config file, it generates a config file with the following token:
admin = "MyAccessToken"

However, when you run the backend with no config file, it generates a config file which references the following token:
token = "MyAccessToken"

They should ideally match, ie both be "token" or both be "admin".

Torrust needs at least one administrator account. On first boot it should show an install wizard to create an admin account and to set the tracker/website config.

doesn't work whether logged in or out, not sure if you're aware so opening this just in case.

Allowing users to create pages using markdown

This is a fairly big proposal, so bear with me :)

I think there's a cool opportunity to build (optional) support for IPFS into Torrust, given how young the project is. IPFS is an emerging technology for sharing and distributing files, which is sort of a blend of BitTorrent with Git and traditional web technologies.

Here's what I'm imagining - instead of "Torrent" to refer to each individual package of content on the site, we refer to them as "releases" (or something similar). The "Upload Torrent" function becomes simply "Upload", and when you go to upload something you get the additional option of pasting in an IPFS CID. The upload button would turn green upon uploading a torrent file or typing/pasting in a CID (or both).

An IPFS CID is simply a piece of text that points to a particular piece of content living on IPFS (in fact, it's a hash of the content), much like a magnet link.

For example, the CID for one of my favourite albums is QmRdke7p9ZP8t4GSUxoJmFzJABRhVsWVdgtC9oMEvp7VeT - which you can stream on the web at https://ipfs.io/ipfs/QmRdke7p9ZP8t4GSUxoJmFzJABRhVsWVdgtC9oMEvp7VeT :)

I've made a quick mockup of the idea so far...

When visiting the page for a release, the IPFS CID is displayed below the torrent hash (in the case of a "dual-stack" release, ie, one that lives on both BitTorrent and IPFS). A torrent-only release would look exactly like the current one. An IPFS-only release would look something like this:

What benefits would IPFS support bring, though?

• Global swarms for IPFS downloads - IPFS uses a global swarm by default, which means that when you download via an IPFS CID, you are downloading from everyone in the world on the IPFS network who has that content on IPFS.
• Web seeds - As IPFS-hosted files and folders are accessible via web URLs, and BitTorrent clients widely support web seeds, you can add the IPFS URL as a web seed to each torrent and automatically download from both IPFS and BitTorrent peers when you download a torrent file.
• Streaming - It's trivial to do in-browser streaming with IPFS, as you can simply stream content via a web gateway like ipfs.io. WebTorrent can also achieve this, but IPFS is a lot simpler.
• Diversity - Supporting both BitTorrent and IPFS as first-class citizens means you get the benefits of both and can benefit from both ecosystems.

It also makes it much easier to support something like federation, which I'll talk about more in a separate issue.

Hello @WarmBeer

I have noticed that @BelieveInBunny has proposed a significant contribution to this project! 😄

It would be great to have the contributors agree with a Contributor Agreement. Particularly because out policy of re-licensing the old-code to MIT-0 after five years of publishing.

This kind-of works like an accelerated form of "Public Domain" where old works become freely available to everyone.

Please read this contributor agreement that we use for Nautilus Cyberneering.

The List of Acceptable Licenses for Nautilus may be expanded to better suit the intentions of this project.

expected: http://localhost:8080/torrents/1
actual: http://localhost:8080/categories/test/1

hi all - first off thanks @WarmBeer for this project, we love it. we've it deployed for 6 weeks and we're at around the 8k account mark with ~2-3k created torrents. Our users love it, thank you!

There are some QOL features we'd really love, I was going to create separate issues but figured since it's private-tracker specific it's probably better in one.

1. deleted torrents need to be de-whitelisted from the tracker. for example, if we delete a torrent to replace it with an updated version, the previous version will continue announcing fine to the tracker. this makes it a pain for us to keep our archive sane as we have to check for duplicates every few days. this would be huge for us and our users.

2. user moderation/groups/roles. for example

   1. an uploader role (by default upload would be disabled without this role) we just hid the upload button from non administrators with this patch rpdl-net@1b7aecc but obviously, they could still use the API to upload
   2. a moderator role who can edit torrent description/title, ban users, upload and do basically everything an admin can except change site settings.

3. the ability to edit titles of torrent pages. at the moment if we make a typo we delete and remake, but it's pretty clunky (especially as deleted torrents are still whitelisted). If we could instead edit the title of the torrent page that would be a much easier solution.

4. torrent client whitelisting. this one isn't so important but it'd be a nice feature nonetheless.

5. "download torrent" or "download magnet" shouldn't work if site is private. the torrent won't work anyway but it makes for a poor experience for a new user. We did it here rpdl-net@aa264db and here rpdl-net@b713911 but they're bandaid patches.

6. our aim is to be as clueless about our users as possible. at the moment we replace the entire email column with random 10char strings every hour. if possible we'd like the option of not requiring an email at all upon sign up. it doesn't really bother us if people can't reset passwords etc. maybe something neat like a onetime code for their account that they could use to reset passwords? just spitballing really, if you can think of a better solution we'd be all ears.

7. from an admin point of view, we'd love to be able to track things like, amount of different IP addresses downloading per passkey so we can tell if people are leaking torrents and disable their accounts.

8. tracking user statistics like amount uploaded & downloaded. again, not very important - it's pretty highly requested from our users though - nerding over stats is serious business lol.

that's all i can think of really. thank you so much for this project, it's amazing. we've submitted a few PRs from our fork (and we'll continue to do so if we think they're good for the main repo).

If you ever do choose to accept donations I'd like to send you something to get a case of beer!

Hello,
Just an idea
Adding a trusted uploaders badge can make the big difference in users when they have multiple post of same series by different uploader.

Thanks

Advance user like this

it will be a good idea if it is easy to do

i'm automating a bunch of stuff and one pain point is there doesn't seem to be an API endpoint to verify if the token is good (as they rotate every few weeks).

Could we get something like this to verify API tokens please?

Could be done using the config.toml in the backend (add an option in the settings page)

Nice to have an option to disable Registration or only with invite code. Or Admins can add Users Accounts.

One thing I've been craving from BitTorrent sites can be summed up in one word - federation.

It would be extremely cool if there was a way to synchronise content between private torrent trackers that don't necessarily trust each other, so that for example music that lives on somesite.cd can also be found on othersite.cd.

Implementing this with torrents alone would be somewhat difficult as there needs to be a way for something to be seeded across both sites... enter IPFS. As IPFS web seeds are "global", someone seeding on one site can also provide content to peers on the other site via IPFS.

Actually getting federation working between sites is a hell of a task, but if we can begin thinking about how to accomplish it now and consider it as something to work towards in the future it could be a really powerful feature that differentiates Torrust from other tracker software.

User profile section where everyone can see the post of specific user by clicking on his name from the post.

Deleting a category also deletes all the torrents in that category. A warning for that should be displayed.

Small Feedback button in case poeple find issue, they can report

Need to add comment section for the posts

Hi,

Not sure if I am doing anything wrong but first connection, I try to create a new account and get a 405 not allowed nginx error.
Anyone had this issue ?

Thanks

Hello,
Is it possible to install torrust using cyberpanel, centwebpanel or any other?

Thank

• The TEST and Build badges are not displaying correctly
• Can include the Logo or an image
• Include other badges in the top like Open Source 100%, open for sponsors etc.
• Restructure the content part and include an index with links to each section.

When uploading a torrent where the content is large (around 40gb) nginx gives the 413 error. I'm not sure if the website or the sever is the problem. The torrent file itself is around 3.6mb big.

Hello,
It will be really good idea to add Seeders and Leechers Amount from external and Internet trackers for public trackers

it will make index look more alive and active.

Thank you

https://torrust.com/ is down, can not open the installation documentation.

Need to add a option using which we can let user describe if it is 18+ content.

Adding tags might be a good idea for the last version (not current)

As with any tracker, a RSS feed would be nice to be able to have an easier time grabbing new torrents and seeding them. A separate API key for the feed that's bound to a user and has a long expiration date by default (2mo-6mo) is preferable so as to allow users to just set and forget until the key expires.

When the browser window is smaller, like for example when it is not fullscreen, the upload button disappears.