[ramblings]

stuff that doesn't need a full blog post

[20260528] teehee another project

....As if I don't already have enough on my plate. So there I am, chatting with a coworker, and I realize, "I really wish I could share a music playlist with them, but I'm on Tidal, and they're on Apple Music." And of course there's Soundiiz and TuneMyMusic, but those are playlist converters; they only go from one platform to another. What if I could just make a generic playlist, without any ties to a platform, and let whoever visits that playlist link add it to whatever service they want? So, uh, yeah. That's the plan; a platform-agnostic music playlist service. Right now, the idea is this:

  • No accounts. You click "create new playlist" or "get started" or whatever, and it generates a new blank playlist. This playlist has a unique URL slug, and an edit code. This code is displayed once, and the site'll prompt you to copy that code down somewhere safe because once it's gone, it's gone for good. You can use that edit code to edit the playlist at any time.
  • Tracks can be added in one of three ways:
    1. URL entry, where you paste a URL to a track from any of the supported platforms, and the site'll parse it via an API call to extract the metadata needed (most importantly, the track's ISRC code)
    2. Track search via database (MusicBrainz, I guess?). Input as much information as you can (ISRC code, artist name, track name, which album it's off, etc), and it'll do it's best to match it from the database.
    3. If both (1) and (2) fail, you can manually enter the track's information. The more information you provide, the better the results will be.
  • Playlists are exported to a visitor's platform of choice. OAuth is used in conjunction with a sessionStorage key to temporarily authorize the ability to create a new playlist on the chosen platform and populate it with the tracks in the platform-agnostic playlist. Once the tab or browser is closed, the authorization is revoked. Or at least, that's how I'm hoping it'll work. I've only messed with OAuth once before, and that was... a decade ago? Something like that.

Anyways, work on this hasn't even begun yet, and there's no time estimate for when I'd have it done (if I ever even get around to it). But this is something I'd personally use quite a bit, and maybe someone else would to, so who knows?

[20260505] new phone who dis

I bought a new phone. My current one, a OnePlus Nord N30, has lasted me for a few years now and held up pretty well. But I severely damaged the charging port a few months after getting it, and I couldn't buy a replacement port from OnePlus to fix it, and the repair cost for getting the port replaced would've cost almost as much as the phone itself, so I just... dealt with it. But I'm tired of having to wedge the charger into the port to get it to charge, and I've got the funds to replace it with something else, so why not? I ended up going with the Murena Fairphone (Gen 6), which touts itself as a repairable device that's built to last, and is paired with Murena's de-Google'd Android fork, /e/OS. I did a fair bit of research and review-reading before making the purchase, and there are a few things I'm watching out for, but I'm hopeful that this will be a solid purchase and I can just fix up whatever things I inevitably break on the device.

Also I had french toast for the first time in ages yesterday and holy fuck it was good. I want more.

[20260429] target="_blank"

Oh look it's my first ramblings and the whole reason I decided to make this page!

So, for almost all of my external links, I've been using target="_blank". This is because I personally dislike leaving my current page when I'm not done browsing. Of course, I could just right-click and open in a new tab (or middle-click, or whatever), but I often times forget to. So, I slapped in the target attribute and called it a day. But after reading quite a few discussions on the use of the attribute, and when it's actually appropriate to do so, I've come to the conclusion that I shouldn't actually use it for my site. It's an unexpected behavior that the viewer didn't request, and it disrupts the normal browser flow. So, I'm removing them from my site.