trickle VS LMS

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

For those that dont know if you add an album that has multiple album artists ( artist 1;artist b) then plex/plexamp instead of showing the album in both artists pages and showing both artist tags as clickable (same way EVERY streaming service is serving music right now) it populates a new artists page named "artists a;artist b". They keep adding trash features that none cares about or even asks and don't even have a basic feature that projects like Lightweight Music Server already have.

Just wanted to give quick plug for my music player app Supersonic! It's a client for Subsonic API-compatible servers, so it handles the UI and playback while the server (Gonic or LMS would be good lightweight choices for localhost-only setup) handles the library management/metadata indexing. It's a quite young project but I have lots of plans for continued improvement and new features (and would gladly accept contributions)!

If you're concerned about power usage You can start with just a raspberry pi or something similar running something like Lightweight Music Server which uses a subsonic protocol. Then any app that can connect to a subsonic server like ultrasonic (not sure if this one specifically available for iOS). That's how I started before moving onto Plex and Plexamp.

Good time to move your library to something else like LMS https://github.com/epoupon/lms

I use LMS (Lightweight Music Server) to stream my music to desktop and mobile. It supports the Subsonic API for clients, scrobbling to ListenBrainz, has a nice web UI, and for some reason is the only music server that supports volume equalization with Replaygain.

Not sure if that would fit your needs but https://github.com/epoupon/lms has a radio mode that automatically feeds the play queue with similar tracks. Just seed with some tracks (a whole album, a discography, a single track, etc.) and hit play.

LMS - LightWeight Music Server https://github.com/epoupon/lms Super fast with a good set of features. Seems to be well coded in general.

Hmm, that link shows me my IP address is banned (I assume from the time when the provider I use had dynamic IPs so a whole range is banned). Anyway - is it this? https://github.com/epoupon/lms

https://github.com/epoupon/lms has a built in recommandation engine to help you find similar tracks (in your collection) to what is in your current play queue.

Maybe Substreamer has a problem with a specific server? The server I used is here (open-source): https://github.com/epoupon/lms/blob/master/INSTALL.md