In tempus, the setting is called “continuous play”. In feishin, it’s called “auto-dj”. Both settings are turned on by default, so you shouldn’t have to do anything.
Scrobbling helps because every played track goes into played history, and play counts help dynamic song selection more and more over time.
I don’t use the ratings, but I’ll “heart” songs I like.
I scrobble my playing from navidrome using listenbrainz and tell my two clients Tempus and Feishin to use the scrobbled data to build dynamic playlists. If I start with a particular song or album, the mix following that is usually kept in the same mood, only strays into weird stuff once in a while, but no more that YouTube Music used to.
I mean, there’s a difference between not gatekeeping when talking about cloudflare and completely waving Cloudflare’s banner on your front lawn.
So yeah, I wouldn’t have phrased it the way original comment was phrased, but holy cow, bro… Cloudflare is far from perfect and the people that will have existential problems with Cloudflare are very likely to be self-hosters.
Yeah, that’s fine too. I’m being facetious, I don’t actually care that much. I just know B at this point, 30 years later.
Haha, I don’t really know, it just seems easier to remember.
B or death.
So long as my mortal body can pull drops, it will be B. Or you’re fired.
My friend, I am a daily user of tempus and it is amazing.
Late to reply here, but I set this up and it’s pretty great. The space savings is cool, but what I like is the compatibility with various Jellyfin player apps is much better. I had a number of files with over twenty subtitle tracks all labelled “undetermined”. Using subtitles on these episodes on certain (Roku) versions of Jellyfin player was an unpleasant experience. Muxarr cleaned that all up.
Could be.
Speedtest (the ookla one) uses a bunch of traceroute and compares hops to pick a peering point, but they display your public IP on the test page and probably use some icanhzip or other service to know that. It should come as no surprise to you that most north American ISPs pay Ookla to prefer peering points in which they have a heavy presence.
Icanhazip is an older service, I’m surprised cloudflare didn’t just kill it, they built their own when they were standing up 1.1.1.1.
Could also be some other tooling on your lan built before the Claude days.
The back story of icanhazip is OK, but I want to know where you picked it up in your logs… Incoming on edge? Something in your network dialing out?
You’re a programmer, what would you recommend?
Hah! By trade, I’m a sysadmin, my daily is security reviews at the planning and governance level.
I spent a good 6 years working in a Dev shop, and I picked up a lot of habits there, learned a ton about rest APIs, etc.
Setting up a vault for secrets (Hashicorp’s vault is a popular one) might be a bit overkill for your needs in a homelab, but it’s a great way to inject some security into python, bash scripts, which I think is useful, because lots of us start with scripting and move from there.
The basic mechanism is you set up the vault, define pools, etc and then use a token request instead of putting the secret in the script itself. There are tons of examples for each language and mode, but i just use a vault command in the script, throw the output in a variable and that’s pretty much it.
Secrets management in Dev and devops work is really interesting, if you ask me. All the way from the IDE to prod, there are many ways to leak passwords, api tokens, paths no one should know, etc.
Edit: I hope you didn’t take the vault comment as an admonishment, I meant it to be an interesting suggestion.
Edit 2: sometimes I wish I could go back to more technical stuff, that’s pretty much my reason for doing homelab stuff.
Well, it’s not super difficult. I sort of mash my way through getting data by api by just using curl and then clumsily filtering the output.
You’ve already got the mechanism to get the data, I think your solution is fine. My way to do it is just a relic from my time working with a bunch of devs.
I would have just baked an api call to navidrome in a shell script with an interpreter like js and some bash variable manipulation and called it directly from motd.
For security, you may want to look at vault for secrets management so you don’t have to expose plaintext secrets in your script.
I’ve been working solo on this project for the past year
The commit history is three weeks old, so that becomes difficult to believe.
deleted by creator
Davx5 is just a bridge between calendar apps and dav providers. One calendar has this function built-in. Any issues showing content on the right time zone, etc would be in the client, not davx5.
OK, I get where you’re coming from.
This has been an issue for a very long time, partly caused by the lie we were all told, that the internet would free us. And we were OK with Google et al taking the helm.
Clearer?
Not really. Most of your statements have no relative reference, so they are really ambiguous. Example:
The community sometimes talks about sovereignty like it’s binary, but it’s a dial,
Great start! And I agree, we should welcome all shades of self-hosting, whether that’s someone just starting or a hardcore digital off-grid self-hoster.
But then comes the next part:
and we should be thinking harder about who’s turning it.
What does this mean? Are you saying we all have different tolerances and preferences for how much we value digital sovereignty? Are you suggesting that we are all at the mercy of the Powers that Be and that they “turn the dial”?
One thing I think would have helped would have been to indicate that your topic is AI-focused. For me, I went into the reading with the impression that you were talking about self-hosting in general.
Well, from my second reading of your post, you make a number of observations, but it’s not clear whether you support AI, or whether you support self-hosting.
Generally, most posts have a point to make or an opinion on a topic, some will summarize their ideas into a cogent question for discussion.
None of that is present here. You give what amounts to be an opinion, but counter it with “on the other hand” and we dont end up knowing what you actually think.
You have already identified the problem in the logs.
You have a fake drive with firmware that says 1.8tb but are actually much lower.
This means an inode is mapped to a non-existing sector. Get your money back, if you still can.