I'd say it's more than tangentially related. The blog post is about Richard Stallman, his life, and his contributions; it seems strange to not acknowledge the recent controversy surrounding him.
> Unlike Google they actually listen to their users. They were awesome during youtube-dl debacle.
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.
I've had success with Ubuntu, Arch, and Neverware on my old plastic Macbooks. All of them were pretty easy to install and I have no major when complaints using them
This is a quick little project I've spent the past few days working on. This page lets you study and observe the functions from Swift Algorithms[0] in real time.
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.
That's totally fair. I wish Spotify gave us more granularity in the data we ask for, I don't think we need the blanket permissions a user has to grant us (as someone who just deleted their Facebook and soon Google accounts, this is really important to me).
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.
That's definitely something we're focusing on more now. Like qnsi mentioned, last.fm does a pretty good job of that -- I've been a fan since high school.
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!
Very good point. I think that's where something like last.fm really shines.
Starting off, we focused heavily on comparisons but have branched out since. For example, the stats page you're first taken to gives you some analytical information about your own music. Strengthening out this page with things like music evolution, recommendations, rankings, &c is foremost priority.
Currently, we have friend links that deep links into creating a friendship (e.g. mine is https://smtn.es/125.ferda-bruh). Pivoting this to share your statistics and music tastes is an interesting idea -- it definitely helps introduce the platform to new users and personalise the platform for existing users.
I appreciate the feedback! I definitely think adding some examples to the homepage is a good feature.
This idea was something we, a group of college students, felt was missing from our social interactions. I agree, it's a bit clunky to set this up mid conversation.
I, personally, find that this works really well with existing friends or when forming new friends online through things like Instagram or Tinder.
To your point, we're always looking to expand our use cases and reduce the first time friction.
I'm in no place to recommend technologies to chose (I'm no expert) but the documentation argument is a good one. There are a lot of articles from the past few decades introducing different odds and ends with PHP. Additionally, PHPDocs are great but they're nothing in comparison to the tutorials and examples provided by things like ReactJS' or Vue's official docs.
When I first joined, the existing codebase was already built out in PHP on a LAMP stack. I was really opposed to it at first but I've learned to love it since. The safety, speed, and size of a compiled language on the web is something most modern frameworks can't compete with.
I, personally, have built a ton of in-house APIs here aiming to "modernise" php and am really proud of the outcome. It's nowhere as safe, readable, or dynamic as something like a Rust or Swift but PHP is definitely a strong competitor for the modern web (IMO).
I'm one of the developers on the SameTunes team. We've spent the whole summer working out of a house to build this platform. We're really proud of the work we've done and hope you all enjoy using it.
With SameTunes you can view interesting statistics about your taste, find your music compatibility with friends, and discover new music!
I just finished building a dsl to generate html (with css styling) purely in Swift. It's still a little rough around the edges but, as I'm using this for my personal website, it'll continue to improve. Let me know what you think!
I'd say they can -- especially with the Gen Z group. Snapchat is used to produce videos, images, and texts for either: all your friends (stories), a select subset of your friends (private stories), a subset of that subset (subsequent private stories), specific friend groups, etc.
With TikTok, you're publishing to the world; with Snapchat you're publishing to your world.