This is trippy, I didn’t know Starship was a thing. JFC, I feel like I’ve been living under a rock. I’m reading up on it on their site, and I’m impressed by the range of shell support and customizable options.

This is gonna be really helpful for me, especially for work… I’m constantly switching between several perpetually-open terminal windows used for different things, and it’s real easy to confuse what local dir I’m in and/or what repo/branch I’m connected to. I didn’t realize I needed this in my command line. Thank you for posting this!

Republican candidate for Missouri Secretary of State Valentina Gomez – who rages at all things “weak and gay”

So much Boomer energy. Too bad it can’t be used for anything other than hate.

R.I.P. Steve! He’ll be missed! Thanks for posting this

You’re comparing assholes to oranges

Wow, that is really disturbing. WTF, IG?

I don’t think Tailscale counts as a reverse proxy, but it does support HTTP/3 and QUIC so that suggestion may not apply here. Still, it might be worth double-checking to see if they are disabled. Also, have you tried disabling Tailscale altogether and connecting directly?

the song will abruptly stop playing at about the 1 quarter mark (only skipping the song or restarting will fix)

You aren’t the only one to report halted playback in Navidrome. It appears to be a known open issue that goes back a few years.

One user in particular suggested last fall that the source of the bug may not be Navidrome’s fault. Are you using a reverse proxy?

For those that are still struggling with this issue, I can confirm that (in my case) the problem was related to the HTTP/3 QUIC protocol (not a Navidrome issue). As suggested by a few others in this thread, the issue can be addressed by ensuring that your reverse proxy supports and is configured for HTTP/3 QUIC, or by turning off the QUIC protocol on the client side (browser configuration), or by disabling HTTP/3 (with QUIC) feature on Cloudflare.

deleted by creator

These schmucks keep repeating “RICO” like it’s some dumbass SovCit incantation or something.

This would come in handy for temporary outages or worst-case scenarios where the instance doesn’t come back. Should be interesting to see how it develops

Whoa, trippy. Your comments all have an orange-brown background?

edit: oh wow, mine too.

I’m trying to. That entire instance is run by assholes. It’s the only reason why Ten Forward exists

Ah ok, I didn’t know they could post here, that’s really cool. Thanks for the correction!

!tenforward@lemmy.world for all your Trek meme needs. O’Brien must suffer!

For starters, Lemmy – which uses open source ActivityPub protocols – is decentralized and comprised of thousands of independently-run servers, so it’s theoretically impossible to take down Lemmy completely. If lemmy.world goes down today and never comes back, the “Lemmy” network will still be online because of the other servers like lemmy.zip and sh.itjust.works that use Lemmy server software (which is currently at version .19 or around there).

Worth nothing: Lemmy is part of the Fediverse, which is an umbrella term to describe all ActivityPub software types. Yes, other software packages also use ActivityPub protocols to communicate… for example, Kbin (the “main” site is kbin.social, it’s sorta like their lemmy.world) is a news aggregator like Lemmy and interacts with Lemmy almost seamlessly. There’s also Mastodon, a Twitter-like service that currently Kbin users can interact with (but not Lemmy).

In short: it’s kinda complex at the moment, and many parts of the Fediverse (which Lemmy belongs to) don’t interact with each other directly because they provide different services, but it’s important to note that it’s really hard to take it down completely because the Fediverse is independently owned and run by different people in different parts of the world. Contrast with Reddit, a service that does have many servers but is owned and run by a single company in America.

Edit: I was wrong, Mastodon users can post on Lemmy instances, but Lemmy users can’t post on Mastodon instances. Thanks Baku@aussie.zone for the info!

I’m curious about lemmy.world server upgrades. How do you test something like this? Do you upgrade a private staging server and run scripts that simulate user interaction at scale, or is it more like “fuck it, v.73.9.0.367.12.42.0.9 looks safe enough, just deploy it on production”? I’m trying to think of how you would handle any kind of maintenence for something as massive as lemmy.world, and it makes my brain hurt. Frick.

Best of luck with the upgrade tomorrow, gang!