Re: a brief pondering

[Phillip Hallam-Baker <[e-mail]>]

At the meta level, now would be a really good time for IETF to announce
what we would like ISPs to deliver as the base connection for fast,
reliable work at home:

* IPv6 with a block of at least 256 addresses available to the customer.
* Support port forwarding.
* etc.

Applications really should be connecting peer-to-peer for two party
communications. A reflector becomes pretty much inevitable for n>2 of
course.


On the usability side, something that is really pissing me off is having to
search through multiple menus to find out what the call sign for a user is
on various apps. By call sign, I mean 'that which I type in to connect to
someone not in the contacts directory'.

Don't expect me to 'remember' because I am having to fix this for someone
else. Alternatively, it may be six months since I last used the app. And
no, it is not obviously their email address (many people have six or more)
or their phone number (again, they can have multiple).

There is a school of 'usability' where the user is insulated from the
information they actually need to perform their task lest it confuse them.
The dirty secret of usability engineering is that most of the focus is on
hyper-optimizing the experience for the first fifteen minutes of use. That
is the average length of a demo before a sale.

A related problem is working out where to enter the call sign.


On Mon, Mar 23, 2020 at 5:11 PM Michael Richardson <[e-mail]> wrote:

>
> Narelle Clark <[e-mail]> wrote:
>     >> Which leads me to a question: what can this community (and
> similar/adjacent ones) do
>     >> productively together to help? What new things are happening on the
> network from
>     >> which we can learn and quickly adapt/improve?
>
>     > We can keep the internet running. That's what I'm being told to do!!
>     > And we're onto it.
>
> And there is more: people are now noticing when jitter and bufferbloat
> actually matter, and ability to send A/V directly from end to end point
> really does matter.
>
> I just wish that more of the tools/platforms were:
> 1) supporting IPv6
> 2) providing better diagnostics as to what path a particular speaker was
> using.
> 3) am I having a problem transmitting, or are they having a problem
> receiving?
>
> I think that we will see a direct relationship between using IPv6, and
> seamless/trouble-free communications.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT
> architect   [
> ]     [e-mail]  http://www.sandelman.ca/        |   ruby on
> rails    [
>
>
>