29223: [skip ci] WIP: HACKING: proposed abbreviations for review #963
Conversation
This is the first half of my review.
I wonder how much we need to distinguish between forms of speech.
Let's standardise on one word, and then use more later if we need to?
| accel | ||
|
|
||
| accounting: | ||
| acct # proposed |
How do we distinguish "account" and "accounting"?
Do we need to?
acct vs acctng?
| ack | ||
|
|
||
| activate, active, activity: | ||
| ??? |
actvt, actv, actv(t)y?
Also action, which maybe should be:
actn
| adj | ||
|
|
||
| advertise, advertised: | ||
| # switch to American spelling. |
Do we also need abbreviations?
advt, advtd?
| alloc # proposed | ||
|
|
||
| annotation: | ||
| anno |
Means "year" in many languages.
antn?
| arg | ||
|
|
||
| array: | ||
| ??? |
arr?
| distr | ||
|
|
||
| distributor: | ||
| dist |
Duplicate line
| enc | ||
|
|
||
| encrypted: | ||
| ??? |
encd
| esc | ||
|
|
||
| escaped: | ||
| ??? # proposed: no abbreviation |
escd
| ewma | ||
|
|
||
| extend: | ||
| ext??? # deprecate; too ambiguous |
extd
| ei | ||
|
|
||
| field: | ||
| ??? # proposed: no abbreviation |
fld?
Probably not, actually. The abbreviation is too confusing.
| gcd | ||
|
|
||
| handle: | ||
| hnd # proposed |
Not immediately obvious.
hndl
I think these abbreviations would be easier to read and search if we split them up into subject areas
| hnd # proposed | ||
|
|
||
| handshake: | ||
| ??? # proposed: no abbreviation |
hndshk ?
| ht | ||
|
|
||
| hexadecimal: | ||
| hex |
I suggest we merge this with base 16?
| hex | ||
|
|
||
| hibernate, hibernating, hibernation: | ||
| ??? # proposed: rename entirely; it gets confused with dormancy. |
The torrc options start with Accounting, so maybe we should rename them to something like:
- hibernate - accounting_soft_limit_act / accounting_hard_limit_act
- is_hibernating - accounting_soft_limit_reached / accounting_hard_limit_reached
- hibernating - accounting_soft_limit_act / accounting_hard_limit_act
- hibernation - accounting
We might need some other variants in different contexts.
| ??? # proposed: rename entirely; it gets confused with dormancy. | ||
|
|
||
| hidden service: | ||
| hs |
Deprecate, replace with onion service?
Yes, I think this is an important missing piece. Is it fine to still abbreviate 'onion service' as 'hs'? Because we are clearly doing it.
I honestly don't mind.
I think "hs" is a fine abbreviation for code and names that users never see.
The abbreviations for onion service are all longer, because "os" means "operating system".
| hs | ||
|
|
||
| histogram: | ||
| hist |
Conflicts with history?
histgm ?
| rtt | ||
|
|
||
| router: | ||
| ??? # proposed: no abbreviation |
rtr ?
I think rtr is common in some operational contexts
| sb # only in sandbox code. | ||
|
|
||
| second, secret, secure, security: | ||
| sec # too overloaded? |
Yes.
sec for second.
secr for secret, secure, security
| serv | ||
|
|
||
| service: | ||
| ??? # proposed: no abbrev? |
svc ?
Yes, svc is commonplace, e.g., SUNRPC.
| tmp | ||
|
|
||
| timeout: | ||
| ??? # proposed: no abbreviation, or say "delay" instead? |
delay doesn't work for END_OR_CONN_REASON_TIMEOUT
I've maybe seen to or maybe timo, depending on context?
| uniq | ||
|
|
||
| unmeasured bandwidth: | ||
| umbw |
Do we also need:
mbw measured bandwidth
teor2345
changed the title
See 29223.
The text was updated successfully, but these errors were encountered: