fstrim.service is disk tool (that's supposed to only be run once a week, not every time you boot) that automatically cleans up old deleted SSD data. https://opensource.com/article/20/2/trim-solid-state-storage-linux
It looks like it's running too often, or on the wrong devices, every time you boot your computer. You can actually safely disable it; https://askubuntu.com/questions/1165128/fstrim-is-causing-high-boot-time but it's worth looking into why it's taking so long and being run so often.
Running this should show you the log results of fstrim doing it's thing without actually doing anything;
sudo fstrim --fstab --verbose --dry-run
These two will show the status of fstrim and it's autorun service;
systemctl status fstrim
systemctl status fstrim.timer
I got most of this from a quick google search; https://duckduckgo.com/?q=fstrim.service+systemd+slow You can do the same for the other major time-takers on your boot list. For comparison, here's the top results of my semi-fresh install of linux mint;
dageek247@mintPC:~$ systemd-analyze blame 2.237s NetworkManager-wait-online.service 2.077s systemd-binfmt.service 2.003s systemd-resolved.service 1.976s systemd-timesyncd.service 1.916s fwupd-refresh.service 1.365s logrotate.service 1.326s NetworkManager.service 933ms fwupd.service 401ms blueman-mechanism.service 334ms udisks2.service 263ms apt-daily-upgrade.service 254ms dpkg-db-backup.service 229ms dev-nvme0n1p3.device 215ms accounts-daemon.service 201ms power-profiles-daemon.service 199ms polkit.service 197ms smartmontools.service 183ms rsyslog.service 173ms ubuntu-system-adjustments.service 169ms systemd-udev-trigger.service 156ms user@1000.service 155ms proc-sys-fs-binfmt_misc.mount 146ms ModemManager.service 132ms apparmor.service 123ms avahi-daemon.service 121ms bluetooth.service 114ms grub-common.service 111ms lm-sensors.service 106ms switcheroo-control.service 105ms secureboot-db.service
Ah. You're likely in the wrong job for it then. They are incredibly popular in any sort of digital paperwork job.
That's androids fault. Their login input detection is spotty, and has been for a while now. https://9to5google.com/2024/10/06/android-autofill-password-manager-problems/
They website advertises mobile support. https://www.teamspeak.com/en/features/overview/
I did a little bit of initial testing, and it looks like there's a couple issues for my use case. Screensharing is currently restricted to official servers only (so, not available to self-host). The channels are all audio first, and there is no such thing as a text-only channel.
The new teamspeak is neat, but it's not quite there yet as a discord alternative.
Man who runs behind car gets exhausted.
Man who runs in front of car gets tired.
Man who goes to bed with itchy butt wakes with stinky fingers.
I'm at two as well. Finasteride for hair, and vitamin D because my doctor recommended it.
I had thought the vitamin D pill was actually kinda useless when i first started taking it. I was fine before i started taking the pill, right? Due to me being lazy and prescription address changes lagging behind a move, I ended up skipping out on that pill for two months. Turns out, vitamin D is like, a minor anti depressant or some shit because I was exhausted all the time near the end there before I started retaking the pill.
Honestly, this one. Handbrake was made as a wrapper for ffmpeg anyways.
Permanently Deleted
It's not the "native" defines how or when you learned to speak a language. It's that how and when you learned a language that makes it "native".
As a bonus, since this is English, "native language" also changes definition based on context. If you are filling out a form and they are asking demographical information, your native language is Cantonese. If you are filling out a resume and want to describe how well you speak English, then you can read/write English at the native level.
If you are in a casual conversation and someone asks what your native language is, then your answer will likely include a whole or part of the above story, to avoid confusion and to encourage more discussion. Essentially, both Cantonese and English fit your "native language" definition in that context.
Fun fact! This abbreviation is so widespread that even government forms use it! They very specifically added the -ez suffix to show that this version is less of a pain in the ass to fill out compared to the old one.
Probably the latter. Doesn't matter which it is though; they advertise both on their website.
Because I told them I used torrents. Their FAQ literally has a page with instructions for setting up torrents. Still does. I didn't think it'd be an issue for them.
I don't know about 'locked' so much as 'hard to get running with headless linux'. I looked into it two or three times and was stymied by the various ways it went wrong.
In comparison, windscribe had me choose a port on their website, and then I used that in my docker run command and it just worked.
The strong other half of my reasoning was port forwarding being locked to GUI. I use a lot of scripts to keep my server restart process simple.
The unban was just to check if the refund process would go through. Since it didn't then I did a chargeback.
About 8TiB upload and 2TiB download over the course of this whole mess. I don't have exact numbers because WRT stopped counting for some reason, but I can infer based on January numbers.
Wasn't sure if this was the right place, but I figured someone should know about this. For what it's worth, I would actually recommend windscribe if you don't plan on doing torrents all the time, or you have sub 1gbps internet. Just sucks that I hit their "unlimited" internet limits on my home connection.
They have a page on their site about chargebacks. They're confidant they'll win them, but they still ban because it costs them money. I've done one anyways; as far as my reading of their tos goes, I was in the right. Might as well make this experience cost both of us money, instead of just them.
Their guide for using torrents with their service; https://windscribe.com/knowledge-base/articles/using-windscribe-with-torrent-clients/
Their FAQ on bandwidth and chargebacks: https://windscribe.com/knowledge-base/articles/why-did-my-account-get-disabled/
Torrenting is not allowed on Windscribe
I switched to windscribe last month because the proton CEO starting spewing politcal BS, and I wanted port forwarding that wasn't locked behind a shitty GUI.
As far as I was concerned setup was super easy, the VPN speeds were great, and port forwarding worked really nicely. The whole price for a fixed server and port forward, + unlimited data was a bit much (at $95/year) but for the ease of use and speeds I was getting, I was happy to stick with them.
My setup is a always-on server with a 1gbps connection, where yes, I fucking seed my shit, all of it. I have about 30TB of linux ISOs and counting, and it's rare that my combined upload speed is less than 1MBps, ever.
Which lead me to getting banned from windscribe with no notice or warning in the middle of last week. This lead to me having to spend tracker points to avoid HnR, and i'm also unable to grab any new ISOs until I find a new VPN provider that won't ban me for actually using the service full time.
I did shoot them a
Those are the work of the devil, obviously.
'remove investments, have fun for the short time the world will exist'
I don't see this is being a good financial choice unless you honestly believe that nuclear war is about to go down. If the measles gets as serious as covid, it still wouldn't be a good idea.