A while back I swapped out my crusty old GTX 960 for a RX 7600 and honestly, other than removing the old nvidia drivers and installing the Vulkan drivers, I had to do nothing else and I have 0 issues or complaints.

What makes you say that ?

I am currently rocking a Shanling M2X which I bought secondhand for €75,- from the local classified ad websites.

Officially supports up the 512Gb but according some reviews it can do up to 2Tb microSD cards ( https://headfonics.com/shanling-m2x-review/ ). I currently have a music collection of about the same size. The Shanling M2X can drive all the IEMs I throw at it, has enough file system support to read just about anything and has WiFi and Bluetooth. Although the WiFi can only be used to wirelessly sync files (which can be a pro but also a con, depending on how you look at it).

However if you don’t feel like going secondhand, Shanling offers a whole bunch of devices meant for offline playback of local files.

To be completely fair, without the “receipts” (ie, screenshots or something else point towards proof) my comments shouldn’t be considered anything more than hearsay.

Personally, this experience is something that’s sticking out like a sore thumb. Most people I interact with online, even people I haven’t interacted with before, I start out with the assumption that they come from a place with good intentions. And then there is a person, that immediately goes against that, especially on a platform where I didn’t expect it.

Edit: grammar

Yeah I think so… I couldn’t find myself as well because I wanted to get the wording correct for my post.

Closed source isn’t a crime. However trying to ruin a company with exclusionary tactics can be. Linux kernel devs and Wayland devs have all conspired to harm a company.

NVIDIA kinda shoot themselves in the foot on Linux and excluding themselves. Refusing to support generally supported APIs like;

• VA-API

NVIDIA rather wants the OSS community the use their VDPAU or NVENC / NVDEC API’s. Whilst everything and dog uses VA-API.

• GBM

Not true anymore (for driver above 495), but in the past NVIDIA refused to support GBM (for Wayland) and rather have compositors use EGLStreams instead of GBM.

Next to that modern NVIDIA hardware (GTX 900 and 1000 series) on the opensource Nouveau drivers cannot be reclocked because it needs some magically blessed signature by NVIDIA. NVIDIA refuses to supply that signature for that hardware but did release it for 1600 and up series.

That’s just two things where I am like, dafuq are you doing NVIDIA…

I whole-heartedly agree with this one and I am genuinely not surprised about the behaviour of Vaxry.

To give some context around this, ThatOneCalculator (aka Kainoa, the person behind Firefish) and I maintained the AUR package for hyprland-git back in 2022. When I initially made the AUR package file, it wasn’t great (and there were a lot of points to improve these packages) but it worked mostly. Of course there were edge cases where building broke, especially this was my first bigger AUR package to maintain. With it being a -git package in the AUR, breakage is to be expected.

Fast forward about a month, a month and a half. Hyprland rolled out some big changes which caused some build errors. But because my personal life got in the way, Kainoa got sick (IIRC) and I had troubles getting the build scripts working again, so it took a few days to get this resolved.

Vaxry came complaining to comment section of the AUR package “when are you gonna get of your lazy ass and fix this shit” (or something similar to that meaning, I can’t find the original comment anymore). After that, I promptly disowned the package and let Vaxry handle it himself.

Because fuck that shit, as package maintainer, I refused to be treated like this. If you think it takes too long, sure, fine, ask if I need help, offer support, anything. But just don’t be an asshole towards people, that offer your software to a wider audience.

Yes you can, it won’t be great though.

I used to maintain a Linux distribution called “OpenWM8650” (back in 2011 / 2012) which was specially aimed at the WM8650 and WM8505. It would run off the SD card. Which wasn’t great, but the flash onboard support was horrible at best.

Maybe you can find some old information on it, on XDA because the website for the initial distribution is long gone.

datab

Theoretically, support for that could be coming… Emby (where Jellyfin is based on) always used their own layer for interacting with a SQLite database. All that custom made logic is currently being swapped out for EF Core. EF Core is a DotNet library for interacting with databases and EFCore that also supports MySQL, PostgreSQL, SQL Server besides SQLite.

So my guess is that, once all that work is completed, support of other database can be added.

For a little bit of context. I am currently running Jellyfin on Btrfs and there is quite a performance impact due to CoW. If 2 clients decide to browse the libraries, both clients grind to a near standstill with regards to being able to see things. So I am following this work with quite some interest.

That will work as long as EF lenses are still available… But Canon already took some lenses out of production.

So basically, that’s gonna be a dead end path.

As a current Canon photographer (700D owner) going mirrorless is definitely the future. Canon and Nikon have basically given up on DSLRs. (https://www.engadget.com/why-nikon-and-canon-have-given-up-on-dsl-rs-133042286.html).

However, I want to highly stress out to avoid Canon for mirrorless. The reason behind it is that Canon has been “defending” their mirrorless mount relentlessly. Meaning, that no other 3rd parties without Canon’s blessing can make lenses for the RF mount. (Source: https://petapixel.com/2022/09/06/canon-confirms-its-going-after-lens-makers-for-patent-infringement/)

So unless you wanna spend big bucks on Canon approved lenses, I’d go with either Nikon, Sony or one of the other mirrorless brands.

Fun fact, Sony is actually quite permissive in the licensing of their E mount. So they will basically let everyone make lenses for the E-mount.

Debian Woody > Red Hat 7.0 > Slackware 9.0 > Slackware 10 > Debian > Ubuntu > Mac OS > Ubuntu > Arch.

At least for desktops and laptops.

For servers I’m still primarily running Debian (and one instance I’m running Arch).

The reason why I settled on Arch is primarily because the combination of bleeding edge and being stable enough for daily driving it. The AUR also adds sooo much, that there is nothing I really don’t need to manually install anymore.

For servers, I basically want a rock stable system. Hence why I’ve chosen Debian Stable.

For all the oldies in the room, Lindows / Linspire (me included)

Trying to merge Wine with Linux into one ““convenient”” package was overselling it at best and worst a lie. Back in '08 / '09 I tried to run it, just to see how good (or bad) it was. It was basically Debian with KDE and their special sauce on top to ““easily”” run Windows binaries. Especially in those day, WINE wasn’t as good as it is today. I think you can fill in the rest ;-)

I wish I could give you more upvotes because you deserve all the upvotes

You mean something like RCS?

Hehe yeah, that’s always fun. The bare concrete. At least it’s better then Germany, where you have to bring your own kitchen…

When I had the viewing of my current apartment, they said they were gonna give me a 10 litre bucket of white paint. Even tho the place didn’t look that badly painted, but more because they always did that.

Yeah I think it’s the same… new apartments come with almost everything including the proverbial kitchen sink.

My current place (built in 2008) has a kitchen that includes an microwave oven, fridge and stove top. The only thing it doesn’t have is a dishwasher.

As a fellow Dutchy… my current place is the first place I ever lived in that came with a combination oven and microwave.

Previously I’ve always had to supply my own microwave / oven ;-)

Oh this guy is my inner spirit nerd.

Same…

Usually it isn’t hard to implement…but that largely depends on the backend.

Might take a crack at this, this weekend.