Self hosting has the advantage of keeping your encrypted vault local and under your control.
Self hosting has the advantage of keeping your encrypted vault local and under your control.
Self-boting is against ToS. You have to be careful when interacting with the Discord API. Maybe there is a way to run the discord website to fetch text messages.
Maybe inversely because of the increased heat of the tightly packed components.
Generally, I think it is better to use a general server OS like Debian or Fedora instead of something specialized like Proxmox or Unraid. That way you can always choose the way you want to use your server instead of being channeled into running it a specific way (especially if you ever change your mind).
Liking and commenting isn’t possible through any client to my knowledge. Freetube is a nice frontend app available on linux. Follow existing tutorials for how to export subs from YT then import your subs in the app.
That is not how security works. You must protect against known and unknown attack vectors. I am only pointing out weaknesses of Docker and other linux containers that share the kernel with the host or/and run with Root. I’m not saying anything original or crazy, just read up on the security of these technologies and their limits. I am not a malware designer, I am a security researcher.
Look into gVisor and Kata Containers for info on how to improve the security of containers.
Here are some readings for you:
https://redlib.tux.pizza/r/docker/comments/eakd50/help_can_i_safely_run_malware_inside_a_container/
https://www.csoonline.com/article/1303004/vulnerabilities-in-docker-other-container-engines-enable-host-os-access.html
https://www.panoptica.app/research/7-ways-to-escape-a-container
https://blog.trailofbits.com/2019/07/19/understanding-docker-container-escapes/
https://www.securityweek.com/leaky-vessels-container-escape-vulnerabilities-impact-docker-others/
https://www.cybereason.com/blog/container-escape-all-you-need-is-cap-capabilities
It is not speculation, it is reducing attack surface. Security is preemptive. Docker/Podman are not strong isolation solutions. Rare does not mean we shouldn’t protect against the chance of kernel vulnerabilities. The linux kernel around 30 million lines of code long and written in a memory unsafe language. Code isn’t safe just because we dont know the vulnerabilities, this is basic cybersec reasoning.
Docker/Podman and LXC linux containers share the same kernel with the host machine. Root in the container is root period (in the case of rootfull containers). Even without root, much of the data on your machine is readable from any user. With a exploit to escape the container (which are common) the malicious program has root on the machine. This is a known attack vector against linux containers. VMs are much better for isolating untrusted software from the host OS.
Idk how to decide what is safe or not, but as a warning, Docker containers can escape trivially and have access to the kernel.
VSCode (or the base app used by it) is open source (see: VSCodium). It has a similar relationship to Chrome and its base Chromium, where assets and tweaks are added to brand the product. You may have been trying to say “a great open source, VSCode alternative” and I misunderstood. Just commenting to remove ambiguity.
AGPL for the WIN!!! Sadly licensing only works if we have competent laws to protect small developers. The enemy doesn’t play by their own rules.
It seems more nuanced than that. Reading over the pull request I saw that brought up, but the “they” was referring to a developer receiving a feedback from the application in some way.
Here is my explanation:
Situation: User asks for gender inclusive language reasoning not everyone is male. Dev responds saying that the user is trying to advertise their personal politics in the project pull-request, suggesting that by personal politics they mean “inclusive pronouns”.
Reason it is transphobic: Note the Dev does not mention cis women, they dont mention women at all (but it isn’t like women are accused of pushing an agenda related to inclusive language). It is heavily implied to be trans people because of the dogwhistle language. Trans people are the main targets who are accused by others of pushing an agenda when it relates to personal pronouns. At the very least it is male-centric, which apparently from the context of the PR was making some contributors uncomfortable. If the Dev had said, “I got other more important stuff to do, someone edit the text and request a merge”, no one would be talking about it. It was his immediate 0 to 100 response accusing the user of pushing a political agenda. They dont need to say the words “I am transphobic” to say something transphobic.
Another app with mentioning, Simple Time Tracker
Thanks.
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 do agree with this. I dont want to discount Brave (just) because of their CEO. Fuck CEOs. Brave has done some iffy things in the past, but their Chromium patches are general decent for privacy.
Firefox resistFingerprinting does more to preserve user privacy (through normalizing of many metrics) and allow for the possibility of a crowd of fingerprint-identical users, the only legitimate way to protect against advanced deanonimizing scripts. Maybe if Mozilla enshittification of Firefox makes a worse, unfixable, and inferior product to Chromium, these patches could lay groundwork for more thorough protections. The reason we have strong protections in Firefox is because of upstreamed code from the Tor Uplift Project, with their code designed for a stricter threat model (in my opinion) than what Brave intends (aka out of scope).
WebCord supports it.