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.
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.
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.
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 remember updating (maybe a year ago now) and it making all my containers unaccessable.
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.
Not a fan of your variable formatting within that string. You are banished from the mickey mouse code house. /s
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.
Self hosting has the advantage of keeping your encrypted vault local and under your control.