mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #365] Unofficial libspotify update. Will it ever happen? #241
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#241
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @OneBobone on GitHub (Aug 25, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/365
Sorry if I am in the wrong forum, but I believe this group is the most comptent for the question above. I like many, have a player depending on libspotify that has lost key functionality.
Do you think that it is foreseeable that someone writes a “libspotify wrapper” around librespot and makes it happen?
It would be very valuable for many!
https://github.com/plietar/librespot/issues/209
@OneBobone commented on GitHub (Sep 13, 2019):
Anyone have some smart insight?
:-)
@kingosticks commented on GitHub (Sep 13, 2019):
Yes, it would be a good idea. If nothing else it would breathe new life into pyspotify. I'd love to do it if I had the time, which sadly I don't right now.