"mpc" is ambigous.

[chrisalbertson]

MPC can also stand for "Model Predictive Control". One has to read the readme past the point of needing to scroll before one sees which use of "MPC" is addressed by this repository.

Solution: Place the words "multi party computing" near the top of the page.

Seriously, pretend you think MPC is "model predicitve control" or even "macro particle creation" and see if the readme still makes perfect sense. It does. The text is too generic

[xingpz2008]

This issue doesn’t make sense at all. If you’re the target audience of this repo, it is no doubt that MPC is one of the most commonly used words in this field to you, otherwise you should not comment on the unfamiliar field with the claim that this word is ambiguous.

[chrisalbertson]

The problem is not that a member of your community would not know what “MPC” stands for. But rather, there are at least three unrelated uses of MPC and Google finds your repository for the other uses It is possible that a person uses the term “MPC” many times daily in his normal work, but it has nothing to do with Multi-Party Computing. The problem is Google directs to your page for any use of “MPC” and there are two other common uses (1) the Akai MPC musical instrument, (2) Model Predictive control and (3) your use of it. This might confuse a lot of musicians who are looking for Open Source “MPC Software" who need to read the entire README.MD before finding your GitHub has nothing to do with this: https://www.akaipro.com/products/mpc-series.html Same for control engineers, The page belo.w is all about “MPC” but it would only take you one second to see the page is not for you. https://www.do-mpc.com/en/latest/theory_mpc.html I think it is common practice to fully spell out a term before the first use of an acronym. Most style guise suggest this.

…

On Dec 6, 2024, at 1:15 PM, Pengzhi Xing ***@***.***> wrote: This issue doesn’t make sense at all. If you’re the target audience of this repo, it is no doubt that MPC is one of the most commonly used words in this field to you, otherwise you should not comment on the unfamiliar field with the claim that this word is ambiguous. — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQKNRUTKADJZRK6HPC523L2EIHWJAVCNFSM6AAAAABTEAIXMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRUGE4DONJRGU>. You are receiving this because you authored the thread.