I personally only use navidrome’s web UI for full random, or listenBrainz when I know what I want to play. LB’s Navidrome integration is brand new so there’s some instances where the played track isn’t the correct one, although it does help a lot if the track is properly tagged.

Although I don’t like using random really much. My collection is vast, and some albums are really just there to be played every 5 months. That’s why I prefer radio that actually recommends my most listened to tracks first, then lesser listened after a while of not listening to them

What!? And then next you’ll tell me they are not wombs either?! I don’t believe you

My latest setup is probably too complicated for what I need… But it works.

• The music server is a Navidrome server

• I play those files using ListenBrainz so that I have centralised public playlists and being able to play tracks rereleased in multiple albums.

• To add files to Navidrome, I use a local copyparty for a webui, as well syncthing to have a subset of the library always locally available in case of the server crashing or internet outage

• When I don’t have the mood for any particular playlist, I use Alistral to generate a radio based on my listening habits

• Of course 99% of the files are tagged using MusicBrainz Picard

Best part, the whole stack is foss software! And self host able too. I just don’t self host listenBrainz as I prefer the public instance

I am guilty of this but for a different reason: setting up debugging for clis in rust is hard

I love the debugger. I use it all the time I can. But when debugging cli it’s a pain as you need to go back in the launch.json file, remake the argument list, then come back to run debug, find out why tf it doesn’t find cargo when it’s the PATH… again, then actually debug.

TBF, if your step by steps instructions works, it doesn’t matter how complicated the command is.

Oh come on! I at least type the beginning so that it filters the history

Rust made me have an habit of using snake_case… .rs

Knowledge of your passwords

Uh… What password?

I kinda hate the push towards passkeys. If you have two factor Auth, going to passkeys makes you go back to 1 factor, aka less secured.

There’s also more and more 2FA fatigue attacks going on, and they can affect passkeys too, and if you don’t have a 2FA that involves the user writing a code on the 2FA device, passkeys could be quite possibly worse than passwords

TBH I thought it was for refactoring type safety. Making sure that the type is understood and not ready to just change wildly accidentally.

I do love rust. But I do like making fun of it too.

Although I don’t see how rust is immature? Unless I missed the joke?

I don’t get it either. OP might be angry at compile time (Couldn’t be worse than rust)

This is also part of my death, because it’s much easier to not deadlock when you are FIFO.

Personally I went for the nuclear option, and any transaction is sent as a tokio task to make sure the transaction keeps getting polled despite other futures getting polled. Coupled with a generous busy timeout timer (60secs) and Wal mode, it works pretty well.

Probably should also put the mutex strategy (perhaps a tokio semaphore instead?) although due to lifetimes it might be hard to make a begin() function on my DB pool wrapper.

… Congratulations. You nerd snipped me. Time for it to go on the todo stack.

Hyped for it too, but wouldn’t use until sqlx suport. Compile time checked queries are just so good. I don’t use rustsqlite for that reason alone (you often don’t need async SQLite anyways)

Tbh trigger performance isn’t that much of a concern unless you need to write lots of data, which most usage don’t need.

Also try check statements instead or even re-evaluate your schema to prevent them if you really need to.

Personally my death would be multiple write transaction deadlocks. Sadly it doesn’t play that well with async code, like with sqlx (rust).

I 100% agree… If you don’t need portable databases. For those, everybody like SQLite (even if it can be annoying sometimes)

Well it really depends on your use case because as a daily driver I never see any buggy page. Not even the enhanced protection thing is blocking pages

I really like librewolf. Does need some getting used to and actually learn to manage profiles (which it sadly remove the new profile browser for some reason?), but pretty great and “just works”

In french “GPT” sounds like “I farted”. They stole the cringe as well

Been maining Linux mint for 3 years now. I did distrohop once to nobara to see if the grass was greener on the other side, but had to revert due to Nvidia.

… The grass wasn’t green, but tasted exactly the same. Apart from Nvidia (which isn’t a distro issue but more shitty company that can’t make things right), the only noticeable changes is going from cinnamon to KDE.

There’s no “stupid distro” nor “smart distros”. Everything is valid. (Although I’d argue that Linux mint is the best beginner distro, to let people get into Linux gently before eventually trying something else)

You’re looking for !fuck_ai@lemmy.world