How do I compile from source? I would like to see that in the readme
How do I compile from source? I would like to see that in the readme
Sorry, misunderstood. Proxmox Free broke my containers on updating a while ago.
Now I use Docker-style application containerizing, but I think LXC (the base technology powering Incus/LXD) is useful in a number of situations and perfectly viable for use. I think Incus-containerized applications are easier to upgrade individually (like software updates of your apps, no need to recreate the container image) and gives a closer to native experience of managing. You do lose out on automated deployment of applications from widely available image sources like docker.io, but the convenience-loss is minimal.
If incus works for yoy, use it. Proxmox locks you out of the option to choose your base server distros.
I remember updating (maybe a year ago now) and it making all my containers unaccessable.
DivestOS is the most thoroughly degoogled of the android ROMs (it removes the most proprietary binary blobs). DivestOS is also decently security hardened, better security hardening than any other Android ROM other than GrapheneOS. But since it removes more of these proprietary blobs, it further reduces the attack surface of the ROM. Both GOS and DivestOS are good options. As commented by another user, /e/OS falls behind on security updates often, which is quite bad for a security or privacy focused OS.
I assume they mean proprietary code blobs.
If they want proper anonymity, the user needs to protect against fingerprinting from the duckduckgo website (Tor or Mullvad). If by anonymity you are meaning from OpenAI, then duckduckgo needs to be running user’s text prompts through a paraphrasing LLM to normalize text and avoid deanonimization using writing-style Fingerprinting.
I watched it and I thought it was alright. I have no context for anything outside the video but what he said seems to make sense. Idk anything about FUTO other than they are at least source available for their apps which is enough to be able to inspect their claims about privacy and security.
My take on non-profit source available licenses (I know nothing just stream of thought):
I am I’m favor of an “open” source license minus profiting off of your forks, which I understand makes the resulting license not open source. In a capitalist system, the capitalist class will take every opportunity to parasitically take where ever possible. Nothing free in a capitalist system, including living. Free development comes at a cost, even iif made purely out of passion.
Most of the code I will ever publish will be open source, with the exception of some big and very unique passion projects that I wish to stay nonprofit. Any person who forks it owns their code, but is limited to donations (just in the same way I’d adhere to the license). Source available at least means people can inspect it for badware, which is good for privacy and security. Allowing forking and community collaboration is important. But some greedy corporation stealing your code without contributing back is gross. In an ideal world we wouldn’t care about the perceived costs to our time by developing and releasing code for free because money would play no part in our ability to continue existing or as a way to measure our “worth”. Why freely enable thier behaviour just to maintain some pure ideological boundaries. They dont deserve to profit off of our labor and passion.
Unofficial MCPE launcher is the only way to run bedrock on Linux
Many mechanics, and bugs, and features. Redstone is very different because the bug/exploit parity doesn’t exist and even obvious features are different (Redstone attaches to pistons). When they add a new mechanic, the bugs are different and unique to each game. Like because cauldrons can hold potions in bedrock, you can (idk if its changed) use the newish block dripstone to increment the potion fullness, duplicating it.
I assume it has documentation, otherwise you can look at the Flatpak docs to see the equivalent terminal commands that are available in the GUI. Flatseal is pretty intuitive in my experience.
On linux for the Obsidian Flatpak, you can deny it having internet and filesystem permissions using Flatseal.
Not a fan of your variable formatting within that string. You are banished from the mickey mouse code house. /s
How recently. I tested with Mullvad and it gave me a notice.
They block VPN users.
I just read through the unofficial Flathub Flatpak for Signal and it is very simple. It fetches the .deb from Signal’s website, installs it in the sandbox, and uses a launcher script to tell the OS some basic toggles like should it start minimized or should it display a tray icon. In the script it makes use of zypak, which to my understanding is to tell electron (chromium) to allow sandboxing to be handled by Flatpak. Here is the repo and the build instructions is the .yaml file.
Flatpaks are pretty easy to read through. Just go to the links section of Flathub and click the manifest, then read it to see what is done during building.
Its not official, but you can read the manifest to see what is done during building.
deleted by creator
Thanks.