choocroot

That's what I've been dreaming for ages!

I've been musing about a system/software that could listen on my PC's audio and control/adjust/mute the volume when it detects ads.

Such a system could also work for video content played on a PC!

This system could also be implemented on a dongle-like Raspberry Pi that would take the PC's audio output (3.5mm jack in/out), process the audio, and play back the "clean" audio to it's jack output: that could be seen as an audio firewall.

I think that working with analog audio (instead of official radio's streams) is the way to go to avoid legal issues: they cannot plug the "analog hole"!

« Note the download isn’t going to hover exactly at 1.0K/sec — > the actual download speed as reported by wget is an average over time. In short, you’ll see numbers closer to an even 1.0K/sec the longer the transfer. In this example, I didn’t wait to download an entire 4.2GB file, so the 10.5K/s you see above is just wget averaging the transfer speed over the short time I left wget running. »

Wrong: you see 10KB/s download speed because you are not throttling the incoming packets but the outgoing packets!

So, what you are really doing is rate limiting outgoing ACK packets to 1KB/s, which delays your outgoing ACKs, hence preventing the remote server from sending you data at full throttle.

You can see that with a tool like "bwm-ng" to see Rx/Tx speed, and you'll see exactly 1KB/s on Tx, and something variable on Rx.

The incoming rate will fluctuates depending on the TCP window setting used by the server which translate to how many non-acknowledged packets are allowed to be sent by the server.