Orpheus.network News

[Anna Kushina (櫛名アンナ)]

Torrent Grouping and API Tokens

Torrent Grouping

The torrent grouping setting/feature has been worked on and fixed such that it should now work the way it did previously, before the behavior was last changed, and similar to other Gazelle sites. We encourage people to go into their user settings to adjust the settings to their desired settings.

We have also taken this opportunity to update the wording on the "Torrent grouping" setting to indicate that it applies ONLY to the torrent search / browsing page, not any other page on the site. When this setting is disabled, it means that each row on the page will correspond to exactly one uploaded torrent. Enabling it will show you the entire group that the uploaded torrent belongs to.

"Torrent group display" affects all pages where groups are shown, such that setting it to "closed" will have all groups load as collapsed (and opening a group will then show all formats expanded as well), and vice-versa for "open". Ctrl/Cmd clicking on +/- of the torrent groups will now work as expected from reading the pop-up such that on the artist page, it will open/close only groups of that release type (e.g. "Album") and on all other pages will open/close all groups on the page. Ctrl/Cmd clicking on the +/- of an edition will cause all editions to open/close.

Site API

Our API is now accessible through an API token, which has launched today. Usage of the API remains the same, but now, if your account has 2FA (which it should!), you can use the new API token system to access the site while leaving 2FA for site access. For now, the token system, while we are confident in its workings, should be considered "beta". It will leave beta once we bring online endpoints for uploading, downloading torrent files, filling requests, and adding tags, which is coming soon.

To get a token, head on over to your User Edit page and scroll to the bottom where you will see a table of all your existing tokens along with a link underneath to generate a new one. You then give that token a name and you will be shown a page where you can copy your token.

Usage of the token is simply using the Authorization header like so: Authorization: token <token_value>. For full details on our API, we suggest heading over to our documentation on it.

Discuss this post here