In the past I've recommended onions for port forwarding. It's more simple than alternatives and using the network is free.
The authors or Tor really don't want their network used for torrenting though. They do support JS, and by extension I would argue the authors intended for their users to be able to use YouTube. In comparison to video, git traffic is insignificant. I don't see anything wrong with it, but then again, users of torrents don't usually have issues downloading without port forwarding.
You can also assume you are compromised and use a solution like a Faraday cage. If you're trying to detect advanced spyware, it might be better to check network activity from outside the device like what network activity is the router managing for the computer.
The traffic seems well ranked still. Maybe concerns of algorithmic censorship? As an example, X.com now promotes posts from premium users, and then has an extra promotion mode for premium+ users. (Normal users are now much less visible than premium users)
I don’t know what these people are doing who seem to claim it’s wonderful. Every single time I have tried to use one, it’s been completely clueless about the problem and wastes my time producing slop. I almost want to keep my code closed source because of how awful it is at generating anything. Maybe they’re just doing very simple web design or something, I don’t know
I even have started to hate Google and felt like their search engine is becoming very bad. Yandex has been returning more results and Google feels censored and replaced by generative AI answers.
Sometimes it's specific to the application. As an example, yt-dlp is redistributed by Canonical, and they usually maintain stable packages, but their versions seem to lag like 6 months. This might be related to their desire for stability, or maybe just align to their release cycle. I don't know.
The issue is that yt-dlp needs to be updated more frequently because websites break their methods of downloading, so the version that follows the latest version seems to work better.
I don't think using PPA's is usually recommended, (like in the photo) so I think I would recommend flatpaks first if the developer of the application maintains one themselves. (and you want to follow later releases.) Though, the first time I had to use flatseal to fix an application, I felt like flathub was a failed platform.
The 580 drivers might just be the default for nvidia. I have two computers with nvidia GPUs that are like 10 years apart in age, but both look like they're running 580 drivers.
I don't really know what's wrong with the networking though. Maybe try updating from terminal if you haven't? sudo apt update && sudo apt upgrade
I have bindings on super + period and super + comma for an emoji flatpak. Usually at least one of them works. This is the flatpak I use. I still have to press ctrl + v afterwards, so the experience isn't perfect.
The version I have was copied from stackoverflow. It doesn't work very well, it makes a rough estimate to get the video file size under the set value. As an example
bash
resize video.mp4 10
Which then resizes the video to 10 megabytes if possible.
What does your ~/.bashrc look like? My last change was modifying a playlist command
bash
playlist https://www.youtube.com/@YouTube/videos
or
bash
playlist /home/username/Videos
or just from any directory with files
bash
playlist
And then takes all the videos found at the url or at the path (including within folders), adds them to a playlist, shuffles them, and plays them from mpv.
bash
playlist() {
param=""
# If the first parameter has a length more than 1 character
if [ ${#1} -gt 1 ]; then
param="${@}"
else
param="."
fi
screen mpv $param --shuffle --ytdl-raw-options-add=cookies-from-browser=firefox --loop-playlist=inf --no-keepaspect-window --no-auto-window-resize
}
bash
alias code=codium
alias files=nautilus
alias explorer=nautilus
alias rust="/path/to/.cargo/bin/evcxr"
alias sniffnet="export ICED_BACKEND=tiny-skia; /path/to/.cargo/bin/sniffnet"
alias http-server='/path/to/.cargo/bin/miniserve'
alias iphone='uxplay'
alias airplay='uxplay'
alias watch='screen mpv --ytdl-raw-options-add=remote-components=ejs:github --ytdl-raw-options-add=cookies-from-browser=firefox --no-keepaspect-window '
alias twitch='watch'
alias timeshift-launcher="pkexec env WAYLAND_DISPLAY='$WAYLAND_DISPLAY' XDG_RUNTIME_DIR='$XDG_RUNTIME_DIR' /usr/bin/timeshift-launcher"
alias update="sudo apt update && sudo apt upgrade -y && sudo flatpak update -y && sudo snap refresh"
alias resize="path/to/resize/videos/resize.sh"
playlist() {
param=""
# If the first parameter has a length more than 1 character
if [ ${#1} -gt 1 ]; then
param="${@}"
else
param="."
fi
screen mpv $param --shuffle --ytdl-raw-options-add=cookies-from-browser=firefox --loop-playlist=inf --no-keepaspect-window --no-auto-window-resize
}
gif() { ffmpeg -i $1 -f yuv4mpegpipe - | gifski -o $2 ${@:3} -;}
After thinking about it for a moment, if you don't want to pay for a VPS, I think you can run a hidden service with Tor then just use the onion address to ssh back into the computer. I found this guide. I haven't done it, but it seems like it should work.
I run an ssh connection to a VPS I pay like $5, which forwards a port there. The screen in the following command isn't required, but I have it so I don't have to keep the terminal window open.
For remote computers connecting back, the first ssh connects to the VPS and forwards a port to the remote computer. Then the 2nd ssh connection uses the forwarded port to complete the ssh connection to the computer behind the IP that can't port forward.
In the past I've recommended onions for port forwarding. It's more simple than alternatives and using the network is free.
The authors or Tor really don't want their network used for torrenting though. They do support JS, and by extension I would argue the authors intended for their users to be able to use YouTube. In comparison to video, git traffic is insignificant. I don't see anything wrong with it, but then again, users of torrents don't usually have issues downloading without port forwarding.