Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Terms question before registering an app: analysing a signed-in artist's own tracks, and keeping their own track metadata

Abierto
  • ¿Algo no está bien?
#602 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
javascript
Área
api, authorization

Línea de trabajo

Start by reading the API Terms of Use clauses on AI input, User Content, metadata retention, and following lists, then check the repository’s issue guidance for how the team handles policy questions. The issue asks SoundCloud to decide whether these three uses are permitted; it provides no code entry point or test. Done means an authorized team member answers each question or points to an approved approach.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hi SoundCloud team,

I'm Brody Montag, a house producer (Monty, co-founder of PB&J Sounds) and developer. I'm building drop, a free tool that helps producers choose labels for a finished track and prepare each demo submission. Before I take out Artist Pro and register an app, I want to check these uses against the API Terms of Use.

How drop would use the API:

  • Sign in with SoundCloud (Authorization Code flow). The artist sees their own profile, links and own tracks in drop, and confirms what drop may use.
  • drop lists the artist's own tracks as cards. When the artist asks, drop measures tempo, key and style tags for one of their own tracks, so it can describe the track and suggest labels.
  • Today drop does this from the artist's own master file on their computer, not from SoundCloud. No audio from SoundCloud is stored, shared or used to train anything.
  • drop never posts, comments, follows or messages on the artist's behalf.

Questions:

  1. May drop analyse the audio of the signed-in artist's own tracks, at that artist's request, with audio-analysis models (tempo, key, genre tags), given the clause on User Content "as input to any artificial intelligence technology"? Nothing is generated from the audio and no model is trained on it. If not, is there an approved way?
  2. May drop keep the artist's own track metadata (title, tags, duration, artwork URL and the private track's secret link) for as long as the account stays connected, so the artist can use that link in a label's demo form? drop deletes it all when the artist disconnects.
  3. May drop keep the list of accounts the artist follows, for the same period, to suggest labels and DJs the artist already likes?

A yes or no to each would help a lot. Thanks for your time.

Brody Montag (brodymontag.com)

Lenguaje dominante
JavaScript
Estrellas
259
Forks
54
Merge medio
1 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de soundcloud/api

Todos los issues de soundcloud/api

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.