ALPN is the process, not the protocol

[thkoch2001]

https://github.com/n0-computer/iroh-blobs/blob/main/src/protocol.rs#L353

const ALPN should be renamed for example to ALPN_ID or PROTOCOL_ID.

ALPN is the negotiation, the process of agreeing on a protocol, not the protocol.

I think it is important to get names right and wrong naming is a usability issue. Wrong names hinder learning and communication.

See also n0-computer/iroh.computer#286

[rklaehn]

Currently we use just ALPN in all iroh protocol repositories. This is similar to what is done in quinn examples and many libraries using quinn or QUIC in general. See for example https://github.com/hyperium/h3/blob/master/examples/client.rs#L11 .

Strictly speaking you are correct that the bytestring const is better named as an ALPN_ID, but I am not sure if this is really confusing for anybody. In any case, if we change it we will change it at the same time in all our protocol repos.

[thkoch2001]

I've watched "A tour of iroh" (again) this morning which talks about ALPNs and now I watch "Unlimited, free file transfer, no account required" where @b5 spells ALPN as "Application Level Protocol Name".

At least me I was confused this morning and went all the way to the RFC to find out what these ALPNs are.

The confusion is one thing. The other thing is that I have a hard time building up trust in a project when the authors seem to be sloppy with details.

I understand that you still have backwards incompatible changes in your roadmap thus I thought you might consider changing this too before a stable release.