garrepi
Joined 6 years ago
Joined 6 years ago
I wouldn't say they were "awesome" during the youtube-dl stuff. They were slow to respond and non-transparent about what was happening behind the scenes.
Also, user's have been calling for GitHub to terminate their contract with ICE for a long time now[0] to no avail.
GitHub is better than most, no doubt, when it comes to "listen[ing] to their users" but they still have a ways to go.
The HTML/CSS was generated using HyperSwift[1] and the DOM control/manipulation is done with SwiftWASM[2].
That is to say, this is very close to being written 100% in Swift.
[0] https://github.com/apple/swift-algorithms [1] https://github.com/johngarrett/hyperSwift [2] http://swiftwasm.org
We've reached out to a lot of local artists here in Atlanta and hope to use the platform to recommend and share their content to those interested.
Hand curating playlists is also a big feature we've been toying with. That's where something like Apple Music's hand crafted playlists are usually a lot stronger than Spotify's computed playlists.
I haven't heard of Calmradio, it's exactly what I've been looking for! I've resorted to listening to music through a cheap FM radio to try and break out of the algorithm hell Spotify tends to put me in.
Thanks for sharing!
We, SameTunes, have an advantage when it comes to calculating a user's affinity for songs, artists and albums. Last.fm ranks your music by tracking how many times you've played (or "scrobbled") a song, songs by an artist, etc. SameTunes uses additional data Spotify publishes (like position in a created playlist, occurrences in your liked music, etc) to build a more well rounded representation of your music taste in the past and present.
There are definitely features we can, and plan to, add to help better portray this data to a user.
Through the Spotify API we are given locational and positional data on some music objects. Your proposal to structure songs as vectors opens up a lot more flexibility for storing, weighting, and manipulating that data.
The way in which the overlaps are calculated is crucial to our platform, something like feeding the dot product into a weighting matrix would leverage this structure really well.
Your proposal is very similar to how comparisons are currently computed on SameTunes. But, leveraging existing mathematical theorems and restructuring the algorithm with linear algebra in mind would help a ton with some of the noise and normalisation issues we've experienced.
I really appreciate you taking the time to draft that out!