consider replacing "Pool" terminology

[plebhash]

Most legacy Sv1 was written under the assumption that all deployments consist of pointing a Mining Device directly to a Pool. That happened before the industry started moving towards more elaborate and optimized deployment schemes.

As a consequence, we see "Pool" written in every place where we need some reference to an upstream Mining Server.

This disregards alternative deployments, where work could be coming from different sources, such as:

• a Proxy
• a Relay
• a Solo Mining Server

So just using "Pool" everywhere is arguably misleading, as it conveys limited functionality and closes UX doors that don't necessarily need to closed.

While this mindset was ossified in the legacy proprietary mining industry, now we are having the opportunity to do things "the right way". So we should leverage that!

A few alternatives to "Pool":

• Mining Server
• Upstream Server
• Upstream
• Server

[rkuester]

I'm sympathetic! In the source, I've been somewhat careful to abstractly call it a "job source." Hi. That said, as soon as it came time for a user-facing name like the environment variables for a Sv1 source, I casually used the word pool 🤦🏼‍♂️. In my defense—it is nice and compact, and everyone immediately recognizes what it means.

Naturally, I'm drawing towards "source", "job source", "mining job source", etc., depending on the context.

Visualizing some options:

MUJINA_POOL_URL	MUJINA_SOURCE_URL	MUJINA_JOB_SOURCE_URL
MUJINA_POOL_USER	MUJINA_SOURCE_USER	MUJINA_JOB_SOURCE_USER
MUJINA_POOL_PASS	MUJINA_SOURCE_PASS	MUJINA_JOB_SOURCE_PASS
MUJINA_POOL_FORCE_RATE	MUJINA_SOURCE_FORCE_RATE	MUJINA_JOB_SOURCE_FORCE_RATE

MUJINA_SRC_URL	MUJINA_UPSTREAM_URL	MUJINA_SERVER_URL
MUJINA_SRC_USER	MUJINA_UPSTREAM_USER	MUJINA_SERVER_USER
MUJINA_SRC_PASS	MUJINA_UPSTREAM_PASS	MUJINA_SERVER_PASS
MUJINA_SRC_FORCE_RATE	MUJINA_UPSTREAM_FORCE_RATE	MUJINA_SERVER_FORCE_RATE

MUJINA_FEED_URL	MUJINA_ORIGIN_URL	MUJINA_INPUT_URL
MUJINA_FEED_USER	MUJINA_ORIGIN_USER	MUJINA_INPUT_USER
MUJINA_FEED_PASS	MUJINA_ORIGIN_PASS	MUJINA_INPUT_PASS
MUJINA_FEED_FORCE_RATE	MUJINA_ORIGIN_FORCE_RATE	MUJINA_INPUT_FORCE_RATE

MUJINA_SOURCE_* feels the most natural to me. Maybe UPSTREAM being second best.

Keep in mind there will be multiple "sources." Not sure yet what the syntax is going to be. Might be better to put all the variables on one line, e.g.:

MUJINA_SOURCE=stratum2+tcp://hash.256f.org:3333;user=foo;allocation=0.60;force_shares_per_min=16

Okay, bikeshedding time. Please give rationale for why, e.g., you object to SOURCE, if you do. E.g., "It makes me think of X, which is confusing."

[plebhash]

I would avoid using standalone source (without job), because it feels too loose.

job source feels ok