![](https://leminal.space/pictrs/image/4953c6b6-e1e1-4628-b918-67e43277f0b3.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
It’s also second only to .com in terms of query volume in ICANN’s Magnitude statistics with 980 mil vs .internal’s 60 mil. Not sure if that makes it a de facto standard, but it’s close.
He/him
It’s also second only to .com in terms of query volume in ICANN’s Magnitude statistics with 980 mil vs .internal’s 60 mil. Not sure if that makes it a de facto standard, but it’s close.
I also use Navidrome + Symfonium. It’s a great combo.
From what I’ve seen, there’s no real performance difference with a gaming distro. What they tend to offer is an out of box experience that is more tailored towards gaming than a regular distro (think ‘game mode’, Steam, Proton, and maybe Lutris pre-installed, Nvidia drivers if you need them).
Is this how we crack fusion?
It’s a signage display.
I’m running Pop! OS on a Surface Pro 5 and it works pretty much flawlessly with the Linux Surface kernel installed. That said, 99% of the time I’m using it with the keyboard attached so I haven’t done much testing of it in ‘tablet mode’, nor with a stylus.
Not BBC but tangentially related, I enjoy the rolling stream of old crime and mystery radio plays that Audio Noir does. Worth checking out.
We’re back up and running - now on v0.19.2 of Lemmy. This major version bump introduces new features like user-level instance blocking and a new scaled sort algorithm.
The image service back-end upgrade is partially complete. I anticipate another short period of downtime in the next week or two to complete the required changes.
As with any major changes to the back-end, I recommend clearing your site data and logging back in.
I can also see that some changes to the Lemmy UI code may have degraded the Leminal Space theme. I hope to have these issues cleaned up over the next couple of days.
Having thought more about this issue over the past couple of weeks, and having read some of the arguments of others (Erin Kissane’s persuasive blog post in particular), I have reconsidered my position on this and cannot in good conscience allow this instance to federate with Threads or any other Meta entity. Defederation is effective immediately.
EDIT: The below information is no longer current. See the updated comment.
The current Defederation Policy is outlined here, and Threads doesn’t meet the criteria for defederation at this time. However, I want to be clear that I am no way a fan of Meta, their business model or their practices. I am sympathetic to many of the arguments for pre-emptive defederation and believe it will require further consideration going forward. I am open to putting defederation to a vote in the future.
My feeling is that we take a watch-and-act approach and see how things pan out after federation. There are a few reasons for this:
Not sure what could be causing that. I usually use Connect but just tried Jerboa and had no issue. I would try clearing the app data and logging in again.
Navidrome with any of the many Subsonic streaming apps (I like Symfonium on Android).
Sorry, I meant that I don’t think it will be worth the hassle to remain federated with Threads etc. if they implement federation, but no, we haven’t preemptively defederated at this stage. I’m leaning towards doing so but will take on feedback from other users first.
Welcome!
There’s no policy around Meta services at the moment, but this will be have to be revisited if and when they implement federation. My gut feeling is that it won’t be worth the hassle.
Not OP, but I also use Navidrome, hosted as a docker container on Synology NAS with reverse proxy for streaming outside the house. Have found the Symfonium app (paid) to be a great replacement for Spotify.
Worth pointing out that the current version of Return YouTube Dislike doesn’t seem to be working while you’re logged in. I’m sure it will be fixed soon.
Anyone else hear fireworks at 4am? Random.
Server upgrade was completed with less than five minutes downtime. An additional CPU core was added with RAM and block storage doubled. The latter was particularly necessary due to the growth of the database since inception.
Cool. How about leaving it there?