MudMan

My Windows machines seem to be just fine with the couple of NFS shares I use for easier cross-platform mounting on boot. It comes at the cost of some security, though, so I use it to share unimportant stuff I want to mount very freely, like some media libraries. I use SMB for the rest.

I’m curious, what’s the issue with NFS on Windows for you?

Ah. That’s more of an accessibility issue than an advertising issue, then. I imagine even without ads a bunch of modern websites expecting higher resolutions and smaller scaling factors will look cramped.

I was not kidding before, if you have vision problems that don’t play well with desktop views, mobile versions of websites tend to be a LOT friendlier to large text sizes. Have you tried setting your browser to a vertical window and calling up the phone version? On Firefox at least you can set the resolution of the phone you’re emulating and zoom it all the way up. The setting is buried in the developer tools, but there are tons of tutorials out there (TLDR, press F12, look for the button that looks like a tablet/phone). I’ll try to add an image of what it looks like on my device for the site you shared.

What resolution are you browsing at? I have a hard time showing that ad at all in my setup, but I’m not even at 4K and I get a HUGE picture of the rocket in question and still see more text than you show in the screenshot. That’s what? 720p?

I man, don’t get me wrong, ads are annoying, there’s a reason why I have so many layers of blocking I couldn’t even shut them all off to test this, but you seem to be browsing at what I’d call… legacy resolutions. You’d almost be better off twisting that screen 90 degrees and asking for the mobile version. Or, you know, you could lower the UI scaling in your display settings.

It’s telling the guy went “what did Brave do now?”, though.

Maybe telling that we have a couple meme opinions in our head for these recurring arguments and we don’t particularly consider anything else, but telling nonetheless.

For me it got particularly bad back when I was running Manjaro and the GUI package manager showed you multiple package types for the same software all the time. Three metronomes is bad, but three differently packaged versions of Steam is worse and potentially unrecoverable.

Gonna raise the notion that a good, usable piece of software would not require much, if any level of awareness on this front, since most users aren’t willing or able to have that awareness in the first place.

The way this should work is you click on things you want in a package manager and then those are present and available transparently whether you use them or not. That goes for all OSs.

Hell, even Android’s semi-automatic hybernating of unused apps is a step too close to my face, as far as I’m concerned.

Yeah, we’re almost there. If you buy a pre-packaged box with Home Assistant you’re most of the way there. If you look under the hood most commercial NAS options and even some routers are scraping that territory as well.

I think the way it needs to work to go mainstream is you buy some box that you plug in to your router and it just sets up a handful of (what looks to you) like web services you can access from anywhere. No more steps needed.

The biggest blockers right now are that everybody in that space is too worried giving you the appearance of control and customizability to go that hard towards end-user focus… and that for some reason we as a planet are still dragging our feet on easily accessible permanent addresses for average users and still relying on hacks and workarounds.

The tech is there, though. You could be selling home server alternatives to the could leaning into enshittification annoyance with the tech we have today. There’s just nobody trying to do an iServe because everybody is chasing that subscription money instead, and those who aren’t are FOSS nerds that want their home server stuff to look weird and custom and hard.

Yeah, that’s exactly where it comes from. And it fits just fine for people like you, doing it for a living. It’s just a bit obnoxious when us normies dabbling with what is now fairly approachable hobbyist home networking try to cosplay as that. I mean, come on, Brad, you’re not unwinding after work with more server stuff, you just have a Plex and a Pi-hole you mess around with while avoiding having actual face time with your family.

And that’s alright, by the way. I think part of why the nomenclature makes me snarky is that I actually think we’re on the cusp of this stuff being very doable by everybody at scale. People are still running small services in dedicated Raspberry Pis and buying proprietary NASs that can do a bunch of one-button self-hosting. If you gave it a good push you could start marketing self-contained home server boxes as a mainstream product, it’s just that the people doing that are more concerned with selling you a bunch of hard drives and the current batch of midcore users like me are more than happy to go on about their “homelab” and pretend they’re doing a lot more work than they actually are to keep their couple of docker containers running.

Yeeeeah, I have less of a problem for that, because… well yeah, people host stuff for you all the time, right? Any time you’re a client the host is someone else. Self-hosting makes some sense for services where you’re both the host and the client.

Technically you’re not self hosting anything for your family in that case, you’re just… hosting it, but I can live with it.

I do think this would all go down easier if we had a nice marketable name for it. I don’t know, power-internetting, or “the information superdriveway”. This was all easier in the 90s, I guess is what I’m accidentally saying.

This is a me thing and not related to this video specifically, but I absolutely hate that we’ve settled on “homelab” as a term for “I have software in some computer I expose to my home network”.

It makes sense if you are also a system administrator of an online service and you’re testing stuff before you deploy it, but a home server isn’t a “lab” for anything, it’s the final server you’re using and don’t plan to do anything else with. Your kitchen isn’t a “test kitchen” just because you’re serving food to your family.

Sorry, pet peeve over. The video is actually ok.

And maybe I could get to some more in-depth solution that sorts it out, but that’s me spending time on a problem that a) I shouldn’t have to, and b) I have a functional workaround for already.

Communal troubleshooting is the nature of Linux desktop, but also a massive problem. You shouldn’t need communal troubleshooting in the first place. It’s not a stand-in for proper UX, hardware compatibility or reliable implementation. If the goal is for more people to migrate to Linux the community needs to get over the assumption that troubleshooting is a valid answer to these types of issues.

Which is not to say the community shouldn’t be helpful, but there’s this tendency to aggressively troubleshoot at people complaining about issues and limitations and then to snark at people actively asking for help troubleshooting for not reading documentation or not providing thorough enough logs and information. I find that obnoxious, admittedly because it’s been decades, so I may be on a hair trigger for it at this point.

The other option is to just use Windows, which is the issue with these types of hardware incompatibility. I also have an ASUS laptop that won’t use their slightly weird speakers correctly and, again, that whole thing makes it much less practical to boot into Linux instead.

I tried fiddling with the Windows settings, but that didn’t fix it immediately, and the sound is clearly wrong on Linux even with a power cycle. And googling for it I’m not alone in having issues and support for the thing is patchy. I mean, rebooting should have fixed it anyway. There’s no reason why either OS wouldn’t initialize those things on boot.

I am not particularly commited to the thing, so I wouldn’t buy an upgrade. The only reason I have it is at some point I ended up with a motherboard that wouldn’t do 5.1 out of the box, so I got something relatively affordable to slap in there. It sounds noticeably better than integrated audio, though, so now that I have it I’d like to use it, even if I’m not on the problematic old motherboard.

But again, I dislike the tendency to recommend functional hardware or technical support. It’s kinda frustrating. And frankly, it works on Windows, so if I was looking for a fix, that’s right there. The onus is on Linux for support in this type of setup where the issue is not on the Windows side that’s a reboot away.

That’s fair, and I don’t have a problem with that. I’m just annoyed by the tendency of the community to react to criticism with technical advice, which I find to be a frustrating crutch.

FWIW, the card is a Sound Blaster X AE5 (that name sure has aged poorly), and I’ve had similar issues with it in both a Manjaro and a Bazzite install.

Nah, it’s just not supported. Or rather, it’s poorly supported so it sounds worse than in Windows and it just doesn’t want to properly dual boot without a power cycle. Honestly, I haven’t checked if the soft reboot issue has been reported. Pretty sure it hasn’t. I could be nice and go find where to file a bug, but I haven’t gotten around to it and, frankly, there are enough other problems with this particular setup that nobody is fixing and are getting dismissed with “it’s the manufacturer’s fault” that I’m not particularly inclined to go out of my way.

We don’t talk enough about how spotty new motherboard support is for Linux, either. At least sound is a recurring talking point. But yeah, newer motherboards often don’t pick up networking and audio hardware out of the box and need a lot of troubleshooting. Everybody is so proud of how well Linux revitalizes old laptops but nobody likes to talk about how that’s because they’re old, and newer stuff may not work well or at all. Early adopting hardware platforms on Linux can be a “going on an adventure” Hobbit meme experience.

And you’re right that it’s not so much about audio getting reingeneered again as it getting done right. I just don’t know that the current patchwork barely holding together can be salvaged by bolting more pieces on top. Every time Linux needs to replace something this way it’s a years-long argument between nerds and a whole damn mess (see Wayland still being litigated, somehow). Audio never gets enough attention anywhere and I have very low trust that a new attempt wouldn’t end up in the same mess they have now, at least for a long while. It extra sucks because Windows audio used to be kinda bad, but now it’s… kinda not? So being a dual-booter it’s just an extra reason to make that choice of which boot option to pick from the menu.

We’re not doing this. People in the Linux community are so tweaked by years of bad support that they assume every complaint is a call for help.

It is not.

I know what’s broken, I know why, I know it’s not easily fixable, I have a workaround. This is not a tech support thread.

I don’t need information from users more savvy than me, I need the bad sound firmware they’re loading in lieu of specific support for my audio card to be fixed, or even better, replaced by actual specifically supported firmware so my card works. In the meantime, crappy on-board audio and wasting money on hardware I’m not using it is.

You would friggin’ think.

And yet.

Turns out a DAC is a fairly complicated and self-sufficient bundle of software and hardcore electrical circuitry, so apparently you can mess it up so badly it will remain broken across soft reboots. Who knew!

So in my dual boot setup Linux messes up the dedicated audio card so bad it not only sounds like ass on Linux but it somehow garbles Windows audio until I power cycle the entire thing. It is entirely possible it does permanent damage to the hardware. Some of the electrical clicks you hear from it are genuinely concerning.

Had to plug in Linux audio via the motherboard audio and use different sources for each OS to work around it.

Does change how the meme reads to me.

Also, maaaan does Linux need to completely redo its audio systems from the ground up. It’s so bad that saying that isn’t even that controversial, which is insane in these circles.

I think your read on what people typically do with Plex probably doesn’t align with reality. I also think in the end you’re way less optimistic about the potential of open source software than I am. There are multiple areas where OSS options are either dominant or very competitive, but I am also clearly way less picky about how that gradient of openness to commerciality than you are. We can agree that it’s fine that there are options for both or all steps in that gradient, but there is a ton of snark and all-or-nothing attitude in that community as well.

I will say that If you have a commercial option like Plex and a couple of open alternatives (say Kodi and Jellyfin for the sake of argument) I would prefer one of those to have the type of UX that can compete with the closed commercial product because you can compete with open alternatives.

If jellyfin adopted HA’s model of paid development, I’d be thrilled. But HA’s strategy is actually pretty unique, it’ll take time for that structure to be stress-tested and propagate.

Well, hey, there we agree, then. I’d say that the setup for HA is actually fairly Mozilla-like, and people don’t seem thrilled with THAT, so it wasn’t a given you’d agree. Plex certainly isn’t that. For one thing it’s commercial and closed source. But crucially HA’s commercial branch WILL have a bunch of your data, including voice processing and login info, if you do buy into their paid subscription service.

As for the rest of the argument, most is redundant so I’m not gonna go through the loop again, I am actually busy. But I will add a few things. For one thing, whether I think FOSS is worth “any level of inconvenience” is irrelevant. I do, and I do live with the inconvenience in some cases. But if the goal is for FOSS to be mainstream and a primary choice (and it can absolutely be, there are plenty of examples), then it doesn’t matter what I think. The reason the privacy tradeoffs make sense for Plex is that Plex is an app your family is likely to use. Mine does, and they sure won’t put up with bad UX for the sake of using an open alternative. OBS didn’t crush Xsplit out of the market because of ideology, it did it because it became more powerful, usable and reliable.

And let me clarify I don’t “blow smoke for Plex”. I opened this whole subthread by saying I wanted to use Jellyfin (hence all the testing we’ve been nitpicking about) but couldn’t justify it. I’ve said this above. I’d drop Plex in a heartbeat if Jellyfin was just as good to use for me and the rest of my household. But it isn’t. There’s no reason to blow smoke for Plex, but there is a reason to not delusionally pretend that open source alterantives are better than they are. You’re not going to gaslight normies into using them that way and the complacency just makes it less likely for them to succeed at what they’re trying to do. It is, after all, the year of Linux desktop.