[Desktop] IPv6 support for the desktop client

Resubmitting  the same idea as:

https://community.spotify.com/t5/Closed-Ideas/Desktop-Support-IPv6-end-to-end/idi-p/1240314

https://community.spotify.com/t5/Closed-Ideas/Desktop-Desktop-client-IPv6-support/idi-p/1667179

https://community.spotify.com/t5/Closed-Ideas/Other-IPv6-Support/idi-p/4469460

submitted previously by @sdstrowes

 

It would be highly desirable to make sure that the desktop client can work on Ipv6-only networks as they are becoming operation reality (a number of large entrerprise networks like Cisco and Microsoft have piloted IPv6-only corporate networks).

 

As it's been mentioned in the previosuly posted incarnations of this idea, the mobile client works just fine and Fastly supports IPv6.

Thanks!

 

Updated on 2019-06-18

Marked as new idea, which is a repost of this inactive idea.

Comments
Rock Star 22
Rock Star 22
Status changed to: New Idea

Updated on 2019-06-18

Marked as new idea, which is a repost of this inactive idea.

bananenware
Newbie

My colleague cancelled his subscription because of the lack of ipv6 support of the (linux) desktop client. I'm thinking about it. IPv6 is here and very relevant. 

apecat
Regular

I voted for this and as an IT professional I'd like to fully support this. But I'm wondering what kind of insanity major plumbing work like this will cause, in terms of removal of my favorite random features. Because not all Spotify APIs or microservices can support v6 clients or for whatever reason.

 

What's next to go? Last.fm support? Searching for Facebook friends to follow? Collaborative playlists? Showing unavailable tracks in playlists?

 

"Fun and exciting", like how the miserable 2015 revamp of the desktop client to Chromium wrapped garbage removed the audio volume normalization toggle for a while, caused truncation of play history for JS performance reasons, or how you no longer could change active playlists by right clicking on one in the list.