Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#602 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
15/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
api, authorization

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)

Lingua principale
JavaScript
Stelle
259
Fork
54
Merge medio
1m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di soundcloud/api

Tutte le issue di soundcloud/api

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.