planish

On phones Android is pretty typical, and on desktop Unix is also pretty typical because MacOS is it. But non-Mac Unix on the desktop is pretty unusual, and stuff built for Mac specifically often won't work on other Unixes.

I'm going to go with "be normal".

Linux is unusual in a way that Windows is not. In a lot of areas (games, interfacing with weird hardware), Linux uses up one of your three innovation tokens in a way that Windows doesn't. You are likely to be the only person or one of a very few people trying to do what you are doing or encountering the problem you are having on Linux, whereas there is often a much larger community of like-minded people to work with who are using Windows.

Sometimes the reverse is true: have fun being the only person trying to use a new CS algorithm released as a .c and a Makefile on Windows proper without WSL.

But that's kind of why we have Wine and WSL: it's often easier to pretend to be normal than to convince people to accommodate you.

I have had pretty good luck with this actually. You can get e.g. Matlab for Linux no problem, and even weird company-specific tools I want I usually find to be available. But then I guess most of the commercial software I want to use is software for people like me. I don't bother trying to use e.g. MS Office even on platforms it runs on, I don't do professional CAD, I don't do professional graphic design.

If only I had a personal shitty Linux developer.

It's not that products are "to blame" for not shipping Linux/FreeBSD/RedoxOS builds. Building for a platform requires work and, for a capitalist, users to separate from their money. If the sales aren't there the builds won't be there either.

I guess the thing Windows can do here that Linux can't is "be very popular".

If you try to light the Earth on fire, the worms that live in it will come stop you.

I think you can keep doing the SMB shares and use an overlay filesystem on top of those to basically stack them on top of each other, so that server1/dir1/file1.txt and server2/dir1/file2.txt and server3/dir1/file3.txt all show up in the same folder. I'm not sure how happy that is when one of the servers just isn't there though.

Other than that you probably need some kind of fancy FUSE application to fake a filesystem that works the way you want. Maybe some kind of FUES-over-Git-Annex system exists that could do it already?

I wouldn't really recommend IPFS for this. It's tough to get it to actually fetch the blocks promptly for files unless you manually convince it to connect to the machine that has them. It doesn't really solve the shared-drive problem as far as I know (you'd have like several IPNS paths to juggle for the different libraries, and you'd have to have a way to update them when new files were added). Also it won't do any encryption or privacy: anyone who has seen the same file that you have, and has the IPFS hash of it, will be able to convince you to distribute the file to them (whether you have a license to do so or not).

I think that Ventoy has some kind of mechanism to let you do a persistent Linux live environment. Maybe try that?

Maybe that's when I mostly stopped getting the wrong page of stuff.

I took one passing look at how the thing is built, found out it's "basically all websockets for some reason", and stopped expecting it to work properly. Whenever it breaks I think "this is why you don't use websockets when you can just send a goddamn server side rendered web page or make an AJAX POST request" and I feel vindicated instead of annoyed.

Refusing to do normal human tasks to the point where it interferes with your ability to meet your life goals is sort of definitionally mental illness.

Because to put a build in F-Droid you need to write a build script to build the whole app from source on F-Droid's VMs. You can't, for example, fetch binary dependencies from Maven. You need to build them from source as part of your build process.

Android Firefox fetches a bunch of stuff from Maven as part of its build, some of which is proprietary libraries from Google to e.g. talk to Google Play Services or to Google's trusted-hardware stuff, and some of which is the whole Gecko C++ source tree. Mozilla doesn't want to pay their people to maintain two separate build systems for Firefox, one of which has to jump through a bunch of hoops.

https://computer.rip/2023-07-29-Free-Public-WiFi.html