#kotlin#chrome#compose#compose_desktop#compose_multiplatform#desktop#desktop_app#download#download_manager#downloader#downloadmanager#firefox#kotlin#kotlin_multiplatform#linux#windows
AB Download Manager is a free, open-source desktop app that helps you download files faster and more easily by splitting downloads into multiple parts, boosting speed up to 500%. It lets you organize downloads with queues and schedulers, so you can set downloads to run automatically at certain times. You can also control download speeds to avoid slowing your internet. It works on Windows, Linux, and Mac, and integrates with popular browsers through extensions. This tool makes managing many or large downloads simple, efficient, and customizable, saving you time and improving your download experience.
https://github.com/amir1376/ab-download-manager
Betterfox
Set of about:config options for Mozilla #Firefox
It aims to improve browser settings for privacy-conscious users.
Betterfox is also capable of significantly increasing Firefox browsing speed.
https://github.com/yokoffing/Betterfox
Still a Windows user? Know a Windows user?
Consider switching to Linux for these possible reasons.
https://fosspost.org/7-reasons-to-switch-to-linux-from-windows/
#Linux#Windows#OpenSource
How do I find themes?
Android themes: You may use the app or search for: Telegram or Telegram X
The app has every theme divided by color/app (Telegram/Telegram X) and will always point you to the latest versiona of the selected theme.
—Sempiternal is missing because Google will probably send me a DMCA takedown because of the album cover—
Desktop themes: Use this telegraph page: https://telegra.ph/Amoled-Black-Theme-Hub-05-23 or search for #Desktop
More, unreleased, stuff: Beta testing group: https://t.me/joinchat/AwxPmUL72NOOJUIdfzXEVA
Take the following quiz about the #Linux command line (20 questions) and see how much you would score in these very basic questions!
https://quiz.fosspost.org/quiz/introduction-to-linux-command-line-quiz/
Take the following quiz about software management in #Linux! Learn the basics of apt/dnf/zypper/rpm/dpkg in few minutes: https://quiz.fosspost.org/quiz/software-management-from-the-command-line/
http://www.djangocrew.com/blog/how-startstopget-google-compute-instance-python/
In this post we gonna tell you about How to start/stop/get for the #google compute instance with python.
Sometimes we don’t want (or need) a compute engine instance running 24hs every day but we need to run #task/s periodically. To solve this we can have an app engine task runing using cron service to start the VM instance. Once the VM has started, it can have a startup script that runs the actual task it was needed for and then stops the machine.
#REST#Linux#Windows#requests
#Linux devices have a unique identifier called machine-id. Here is how to change it.
Posted on February 24, 2021
What is a machine-id, and why should you randomize it? From the machine-id man pages, it is defined as:
This ID uniquely identifies the host. It should be considered “confidential”, and must not be exposed in untrusted environments, in particular on the network. If a stable unique identifier that is tied to the machine is needed for some application, the machine ID or any part of it must not be used directly.
https://www.man7.org/linux/man-pages/man5/machine-id.5.html
In an effort to promote privacy, having a unique and unchanging identifier tied to your device seems like the wrong approach. It’s quite possible that poorly coded or even maliciously coded software could fetch this ID from your system. Let’s make sure that even if that does happen, that the value is constantly changing so that your device can not be uniquely identified as your device.
This is an incredibly simple and quick adjustment to your default Linux system. What we’re doing is showing you how to either adjust this value manually by hand, or by running a cronjob to change this value every minute with a new, randomized value.
Before we begin, a disclaimer: We’ve tested this on our own work desktops and development environments and I’ve tested it on my daily driver desktop. We have not found that anything has ‘broken’ because of this, but this is untested in many environments and may not be suitable for your use. It’s always reversible if you later wish to continue with a single, uniquely identifying ID attached to your device(s).
Debian / Ubuntu systems
To check your machine-id, open up your terminal and enter the following:
cat /etc/machine-id
The output should look a little something like this:
a9976154f0084a3782892638656ad9fd
You’ll note that this value is also stored in /var/lib/dbus/machine-id and that a symlink between the two exist. Any change to one file, will be reflected in the other.
me@virtbox-testing:~$ cat /etc/machine-id a9976154f0084a3782892638656ad9fd me@virtbox-testing:~$ cat /var/lib/dbus/machine-id a9976154f0084a3782892638656ad9fd
If you reboot your device, you’ll notice that this value remains unchanged. So, let’s change it ourselves!
Method 1: Manually.
Method 2 is automatically, every minute, as ran by a cron-job. If you don’t want to fully commit to that, you can change your machine-id by hand manually whenever you feel like it.
Step 1, remove the old machine-id file.
sudo rm /etc/machine-id
Step 2, recreate the machine-id file.
sudo systemd-machine-id-setup
Step 3, confirm that /etc/machine-id (and /var/lib/dbus/machine-id) now show a new value, different from the original.
cat /etc/machine-id && cat /var/lib/dbus/machine-id
That’s it! You should see two lines in your output with matching IDs that differ from the original machine-id you had in the beginning.
me@virtbox-testing:~$ cat /etc/machine-id && cat /var/lib/dbus/machine-id a78badce3e73beced163bbef7e55232a a78badce3e73beced163bbef7e55232a
You’ve changed your device’s uniquely identifying machine-id. This change will survive device reboots and will remain the same until you create a new one.
Method 2: Changing every 1 minute, automatically.
If the above didn’t satisfy your needs, than feel free to automate the creation of a new machine-id by creating a cronjob entry that will generate a new ID every minute.
Step 1, open up your crontab file.
sudo crontab -e
Step 2, enter at the bottom of the file the following:
*/1 * * * * sudo rm /etc/machine-id && sudo systemd-machine-id-setup
Save and Exit.
Step 3, wait a minute and confirm that your machine-id value has changed:
cat /etc/machine-id && cat /var/lib/dbus/machine-id
You should see two new matching values, that differs from the original value you had at the start. Wait a minute and run the step 3 command again, and you’ll see that these values have changed.