downstream

If a flight of locks was completely opened, Gatún would promptly drain out of them, wiping out everything downstream.

The fully developed NTPv4 implementation is intended for secondary servers with multiple upstream servers and multiple downstream servers or clients.

Very few companies that use academically produced bioinformatics software have downstream customers of that software.

I bet it'd be fun to just choose characters at random, with reckless disregard for inadvertent meanings downstream.

It's a huge bullet to byte if you think about the ethical implications downstream.

How clearly is the distinction between internals and interface communicated to downstream users?

In practice, with X-Forwarded-Proto, they don't, unless they can authenticate the downstream hop.

And the authentication layer is almost certainly downstream of the backend storage anyway, so I'm not sure how that would matter.

Do we have to realloc the bucket and move all downstream data down by one?

Since they are cited so often by downstream media, which is a major part of their business model, their content is--by its very nature--somewhat static.

I think automatically terminating downstream forks from the 'problem' without contact and taking several days to respond to support emails is more concerning.

The amount of chaos he produced downstream was unbelievable.

To be fair to Libav, due to being "downstream" FFmpeg has benefited greatly from their improvements, e.g.

Because I've been looking for a simple way to "inject" props downstream with pure components.

Interesting with the highlight of differences between "forward" and "backward" defined workflows (let data/tasks flow forward on success vs require some of the most downstream tasks or targets, and let the engine figure out upstream targets), as these have profound implications for how easy some workflow constructs are implemented.