If you want open source adoption to continue to be low, please, keep making comments like this.

If you want people to switch, the apps need to be appealing not a chore. And relearning a workflow you’ve fine tuned over decades is a serious chore and may even be detrimental to your job.

Yeah as others have hinted at this is going to be easier with a router/network level feature.

I’m sure there’s a way to do this by setting up a special virtual interface, limiting the bandwidth on that interface and then using iptables to redirect the apt traffic to that interface or something to that effect but I’m not a network engineer and I don’t have the experience to help with something like that. There might also be a way to do this with cgroups to limit the bandwidth but again that’s above my level of expertise.

Lmao I’m in the NYC area and my whole house shook. I’m right there with you. Thanks for the explanation!

Okay honest question, when you merge a PR in GitHub and choose the squash commits box is that “rebasing”? Or is that just squashing? Because it seems that achieves the same thing you’re talking about.

Why are you on lemmy.kde.social just to bitch about KDE?

Git = bittorrent

GitHub = the pirate bay

Code = content

Even that’s not the perfect analogy but it’s better than the OP.

Bottom right

Yes, you can self host: https://github.com/etesync/server

Yes, you can self host: https://github.com/etesync/server

Maybe if Snap or Flatpak had a solution for downloading the same libraries for every package.

It also brings up security issues. Instead of relying on 1 vulnerable package to be updated, I now have to make sure every single snap or Flatpak that uses that library is updated.

This typically takes MUCH longer than waiting for the distro maintainers to patch a library. (Your milage may vary depending on the distro of course)