Essentials? Difficult to decide, it depends on why you are even selfhosting in the first place.

At a first glance and looking at my attempt at a homelab:

• some sort of basic web service (eg.: nginx + PHP setup)
• some sort of repo manager service (I do Fossil, but I hear most people use eg.: Gitea)
• XMPP server
• Jellyfin server
• Minetest server

and can even be extended to act as a Unified Push distributor.

wait wait wait wait.

That works? Teach me how!

Oh yeah totally. But while one could argue we are owed security, we are not owed updates. (And when we do, they’re offered to us via “buy another phone”, such is Capitalism).

FLACs

on a phone

in SD card

¿??? it’s not like you’re going to be able to autism at a -0.0002dB disparity on the trumpets channel with those audio chips, why not just store the files there as opus or MP3 for ~6x more capacity? (not to mention faster overall reads)

Security is not a state but a scale, and is gauged against everything else.

From the perspective of a privacy / security zealot, a smartphone is SOL as soon as they lave the factory, as not only not even OTA updates keep them safe (and you can argue that with some manufacturers such as Samsung, OTA does is the primary risk vector!) but they can eg.: ship with unfixable vulns at the hardware level that would lead to ditch the whole thing anyway.

So long as there isn’t something like a state-funded program for citizens to renew their phones every ~2 years for fully open ones, I’d not worry much. After all, the other option would be not using a phone because current ones are a PITA and just as vulnerable from the other end.

I can’t see any of the graphs. The show as a black box.

This despite disabling Canvas Blocker on the page for testing. According to my briwser, loading the resources from “cdn.jsdelivr.net” is blocked due to a CORS failure.

Aren there by any chance image dumps of the charts in any normal graphics image format? Or even jpeg-xl, for variety.

My primary phone belongs to my work.

So it’s not yours. Looks from here that’s the one issue you have to solve before everything else.

No one says you have to upgrade your phone OS to the latest Android. You can just keep using the Android (and/or Custom ROM) that works.

requests Google Static

requests Cloudflare

Nice try, fed.

Some of the best stuff in the world looks like it’s 20 years past a prime that isn’t, because they’re truly good eternal.

Yes.

Next up!

ICANN approves use of .awesome-selfhosted domain for your network

Hmmm maybe that’s the one that tries to do everything on its own instead of using the stuff I’ve already set up. Had similar issues with eg.: Nextcloud.

I’ve been looking for an alternative “the actual XMPP service only, nothing else that can be sourced by the host” container setup but there doesn’t seem to be any.

You can, but honestly no idea how to handle stuff like the certs from that point on. Most other software on docker lets me eg.: just bind-mount the host’s directory with the certs I want to use - or just not even know about SSL in the first place and just let me reverse-proxy the access in (like, say, a simple static page web server).

But, like I said, the last times I tried to get into it, it tried its darnest to get in my way. If that’s changed since then, that’d be great.

While I like it conceptually, the two times I tried to install it I felt it was far too opinionated for me to get it to work correctly, like other software “bundles” of its kind that want to take control of the entire process of setting up ports, networking, storage, certificates etc…, instead of just hanging down from stuff that I have already prepared for it (like my own domain with my own cert).

Like, as a piece of software it’s something I’d absolutely use… if someone else sets everything up for me.

Here’s two things:

1. You can not steal an idea. (aka “just because you had an idea doesn’t mean it’s yours”)
2. You can not steal profits that were never had or intended to be had in the first place (aka: piracy vs “abandonware”)

Considering that:

It’s open source, but you can’t redistribute binaries of it you can only compile it for your own personal needs and you can’t commercially use it for free

Then it’s not Open Source. So, which is it?

OK, in that case, let’s say I reimplement Fraunhoffer’s FDK-AAC. It’s open source, but you can’t redistribute binaries of it, you can only compile it for your own personal needs and you can’t commercially use it for free.

The only midly-relevant question here becomes: did you use their source code to implement yours, or did you use public knowledge of the algorith etc (up to and including “white boarding”) to reimplement it? If the former, if the software is actually Open Source at best I could see a case for misrepresentation, but not for theft, because the source code is made available openly, you are not breaking that (that’s what “steal” is).

Second, if your implementation is better than theirs, including eg.: because of having a better license, then the rules of the market apply: the better product wins (that’s the same argument corps would use to try and break you if the case went the other way around, so it’s only fair you can also use that; at least, law’s supposed to be blind to order-of-parties). You are also not stealing profits because, besides the fact that potential profits by definition can not be stolen, you are also aiming at a different market eg.: people who wouldn’t have bought Fraunhoffer’s in the first place because of the license etc. If you are selling cheese sandwiches, you can not sue “stolen profits” from someone who is selling bacon sandwiches just because their clients asked you for bacon sandwiches and you said no.

steal

No. You are freely providing the source code.

I mean that’s its whole point, yes?

And this is why the trick is learning and focusing the technologies that stick at a “lower level” of the stack, and that have been battle-tested by years or even decades so it’s understood that they won’t just “go away”. Like eg.: learning C or Fortran instead of learning ${niche_language_of_year_20xx}. For the docker bracket for example the near equivalent would be hmmm I’d say (s)chroot.

Then again from here to around 5 years docker will the the schroot of its tech bracket.