Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New TEP: define unofficial (but commonly) supported torrent fields #12

Closed
josecelano opened this issue Sep 19, 2023 · 0 comments
Closed

New TEP: define unofficial (but commonly) supported torrent fields #12

josecelano opened this issue Sep 19, 2023 · 0 comments

Comments

@josecelano
Copy link
Member

Originally, some torrent fields were included in the BitTorrent client's implementations but not defined in any specification (BEP). It's what we call "Original unofficial specification"

Some of them were described here.

It would be nice to describe them in a proper way and later include links to the BEP in the documentation wherever those fields are used.

cc @da2ce7
@torrust torrust locked and limited conversation to collaborators Feb 1, 2024
@josecelano josecelano converted this issue into discussion #14 Feb 1, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@josecelano