Absolutely! It works fairy well. A little clunky since the Linux support is bolted on after, but it's not noticeably worse than the macOS experience. The extra options it offers over what tidal ships to macOS are also nice.
These non-native electron apps are all kinda junky for native music listening anyway. (This is a problem with Spotify's desktop app as well)
Tbh, podcasts through a "storefront" is a poor way to experience them. It's meant to be decentralized via RSS feeds. Tho having some cross-device metadata about what you've listened to is definitely helpful.
I've been using Pocket Casts for a long time for that more refined experience and ease of use between listening devices. Their new owners are ethically complicated nowadays (Automattic), and the cost for their pro features is a bit high unless you are a podcast fiend (I was grandfathered in from their old mid-2010s pricing scheme that was pay once/own forever), but it's a good app (for now).
This is great to see. I ended up moving to Tidal from Spotify, and even though there are some nice to have features missing from Tidal (an equivilant to spotify's sync between devices/speakers as well as a better Android Auto experience), it's a far superior experience.
Quobuz is also on my radar, but they've traditionally lacked in the music catalog space. I need to give them a try again now that it's been a few years.
That said, Tidal barely has Linux clients and I don't think I've seen much movement for Quobuz on Linux, unless I've just missed it.
Absolutely, it's expensive. Definitely better to share it with family and friends to equalize the cost.
I only consider it because I listen to a ton of music, my university degree was music, and I spend a lot of money on music generally.
Not FOSS, but something I've been considering is Roon. I switched to Tidal from Spotify (which is a legit improvement imho)
They have a self hostable option and the idea is to mix your personal library, Tidal, Quobuz, and recommendation engines into one app.
I did a similar jump a while back, actually went quite well, at least via docker. I kept the old image on hand in case I needed to revert.
But yes, backup first.
I think this is pretty easy to BS through though.
For sure. So far I've only used it for one batch of interviews so I'm not 100% set on it, but we used it as our last round to narrow down between a few finalists and we were already confident they were not people who would BS the excercise.
Yup, this is what I've always done for interviews.
Technical questions are purely to see what background someone has and how they explain or reason their way to some sort of answer. Its also nice to see if someone will say they don't know something but offer their best guess, which is always a good indicator. I'll usually provide the answer right away after they've answered, both to boost confidence for correct answers and because a quick explanation has a tendency to ease tension, especially if they then relate it to some other knowledge they have or suddenly recall the info with a little help.
The other thing I do is ask questions about disagreements with previous coworkers or managers. If someone starts explaining themselves into being superior to others, it's a red flag. Its nice to get an idea for how someone resolves conflict or what kinds of complications they've run into, but I mostly just want to see how they view themselves compared to others.
I know my approach is sometimes strange to others doing hiring with me, but it's all pulled from my time as an education major (I switched out after 3 years to another degree) and real world teaching experience. Good teachers ask questions to understand how a student learns and what they know broadly, not to get an exact percentage of points. (State/district testing requirements aside)
A new thing I've been trying instead of live coding is having people map out a loose architecture for some sort of API data process or frontend data process, then walking us through it. Its more or less a pseudo coding excercise, but it takes the stress of actual language knowledge away. I'm not sure if it'll stick long run, but it's been an interesting experience.
May the Great Green Arkleseizure bless the author
Fwiw, they've open sourced the specification behind canvas, so there's a good chance any OSS Obsidian "forks" that pop up if they do enshittify will be able to support it.
Thats absolutely possible via the underlying WebPayments API. The payment "wallet" is linked in the HTML (at least for web pages, RSS, podcast RSS, etc) so someone could design an app that reads these links as QR codes.
The whole point of WebPayments is that and payment solution that you (the "spender") wants to use which is compatible can be used to send money to any compatible wallet.
Whether the payment solution is via government backed, banking systems, or crypto, all it needs to be is compatible.
Yep! It's a good app overall, even has some improvements over what is shipped on macOS.
https://github.com/Nokse22/high-tide is new and promising for a better experience overall. I'd always prefer native over electron.