trickle VS glava

This method could apply to other tools with the same IPv4/IPv6 behaviour, without further modification. Changing the behaviour in the utility directly would only fix it for that one utility meaning that to fix another you need to do the same work again. It is perhaps also safer than modifying such a core component as SSH: if you introduce a bug the trick can be easily disabled until fixed, if you accidentally break SSH you might cause yourself significantly more hassle.

> This sort of negates that advantage

LD_PRELOAD trickery doesn't negate the advantage of having full source access, patching SSH would also have been a perfectly valid option, but is perhaps a better tool for this particular job.

For another use of the trick see https://github.com/mariusae/trickle (the project looks stale, though that may be because it is properly done and there have been no security/other bugs to fix in recent history) which slips its own functions in the call chain to apply user controlled (rather than firewall/routing level) throughput shaping to utilities that don't offer it out of the box.

Have you tried Trickle?

Assuming you're on Linux you could use something like Trickle: https://github.com/mariusae/trickle

install trickle

https://github.com/mariusae/trickle https://www.usenix.org/legacy/event/usenix05/tech/freenix/full_papers/eriksen/eriksen.pdf

Sounds like a job for GLava instead

glava an overkill gpu accelerated audio visualizer for the desktop Example: https://streamable.com/dgpj8

It was just a plug-in for Glava (https://github.com/jarcode-foss/glava) not really worth sharing imo.

[glava](https://github.com/jarcode-foss/glava) closes when I close the terminal, even after running it with the appended `&`. How to keep it running?

A lot of those soundwave things, etc. are just dedicated sound visualizers stuck onto the desktop - in most Linux environments you can put ANY program onto your desktop, not just a static picture. Something like glava (in fact I think it has a desktop option out of the box).

No, but alot of the functions can be through separate applications, per-monitor wallpapers can be done through hydrapaper, visualizers for music can be done through glava, and the stats readouts can be done through conky.

It's glava

GLava?

I've been trying to gather glava working. It seems like it's not being maintained any more, as there are a few compiling problems, but there are merge requests there that fix those. glava seems to run fine on my desktop, but won't run as an obs plugin. It segfaults when trying to load the‏‏‎‏‏‎‏‏‎‏‏‎­OpenGL libraries. Here's the relevant code from glx_wcb.c: typedef XID GLXFBConfigID; GLXFBConfig* (glXChooseFBConfig) (Display dpy, int screen, const int* attribList, int* nitems); static void* resolve_f(const char* symbol, void* gl) { void* s = NULL; if (gl) s = dlsym(gl, symbol); if (!s) { fprintf(stderr, "Failed to resolve GLX symbol: %s\n", symbol); glava_abort(); } return s; } And then this is in the init function: #define resolve(name) do { name = (typeof(name)) resolve_f(#name, hgl); } while (0) resolve(glXChooseFBConfig); I've only shown the first function that it tries to load, glXChooseFBConfig, since it fails on all of them. The call to dlsym() doesn't fail though (s gets returned), and I find that confusing. All this works just fine when running glava out of a console. I feel like I don't know enough about dynamic library linking to figure out what's going wrong. Any ideas?