Feature Request: Improve Official API Support for Third-Party Desktop Clients
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- api
Línea de trabajo
This is a feature request for SoundCloud's public API rather than a change to this repository's code, and it asks for several new endpoints (playback history, likes, reposts, comments) plus OAuth scopes. There is no specific file, test or entry point to start from, and done would require a decision from SoundCloud's API team. It is not a suitable first contribution.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature Request: Improve Official API Support for Third-Party Desktop Clients
I would like SoundCloud to improve its official API support for third-party applications, particularly native desktop music players.
Currently, developers face difficulties implementing reliable social interactions and playback-history synchronization without relying on undocumented endpoints, browser automation or other fragile workarounds.
Requested Features
1. Playback History Synchronization
- Allow authorized applications to report tracks played by users.
- Record playback start time and listening duration.
- Synchronize listening activity with the user's actual SoundCloud account.
- Make tracks appear in Recently Played.
2. Likes and Unlikes
- Provide reliable API access for liking and unliking tracks and playlists.
- Ensure changes synchronize immediately with the user's SoundCloud account.
3. Reposts and Undo Reposts
- Support creating and removing reposts.
- Allow third-party clients to synchronize repost status with SoundCloud.
4. Comments
- Provide reliable comment creation and deletion.
- Support timed comments with playback timestamps.
- Ensure comments appear on the original SoundCloud track.
5. Official Third-Party Client Support
- Provide stable and documented endpoints for social interactions.
- Avoid requiring embedded browsers or browser automation.
- Ensure authorized applications can perform these actions using OAuth authentication.
Why This Matters
Native desktop applications offer an alternative listening experience with lower resource usage, better system integration and customizable interfaces.
However, without reliable API access, developers are forced to depend on undocumented website endpoints and browser-based workarounds, which are fragile and can break whenever SoundCloud changes its frontend or anti-bot systems.
I am developing a lightweight native desktop SoundCloud client, and I would like it to provide the same account synchronization experience as the official SoundCloud application.
Thank you for your consideration.
- Lenguaje dominante
- JavaScript
- Estrellas
- 262
- Forks
- 52
- Métricas de merge de PR
- Sin PR fusionados en 30 d
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de soundcloud/api
-
Dificultad 3/5 Medio día Aptitud para principiantes 52/100
soundcloud/api#610 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
soundcloud/api#607 · 5 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 44/100
soundcloud/api#606 · 6 comentarios ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
soundcloud/api#605 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 15/100
soundcloud/api#600 · 4 comentarios ·
Todos los issues de soundcloud/api
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
parse-community/parse-server#10871 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Jump in core size from v2.11.2Posiblemente ocupada @caolan-tether la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
holepunchto/hyperbee2#126 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
521xueweihan/HelloGitHub#4270 ·
-
Adopt browserslistrcAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
accessibility bug embed
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
quarto-dev/quarto-cli#15306 ·
Los mantenedores suelen responder en 1 día