Short version is it's going better. We can take a break. Still some work to do. I'm required
to talk about myself first and then about my employer. My work involves me fixing bugs,
talking like this, doing technical support, lots of things. I do it because I really care
about the email and about having one internet come into the entire world. I think that's
an important goal for society. Some of the work I do I do really because the Chinese should
not have their own internet world up from the rest of us. I used to be a Linux person
back when that was really rare. It's really hardening to see how what was a rare back in 1992
when I first installed Linux has become totally come in place. Linux devices everywhere
I live everywhere I stay. Right, I work for ICANN, which is the organization that manages
the DNS roots, but also a lot more. When you send packets, those packets are rooted to ISPs.
Those ISPs have numbers. We assign those if we were to make a small mistake, some part of
the net would break. Basically, it's a set of databases that have to be up all the time 100%.
There are ones that matter actually have been up 100% for 20, 30 years now.
No downtime at all. Perhaps I shouldn't say so, but a colleague of mine complained last year
that she was one of only two people able to do some critical work and the other one was on an
airplane. She got pulled out of beds to type something. In one sense, it's boring, it's
getting countries to agree that the web should be one, that our routing should be one,
our DNS should be one. In another sense, it's incredibly technical and exciting for people
like me. Enough. I've done my duty. What I work with is unicoid addresses in email and to
some degree in the DNS. Actually, yes, addresses in the DNS. This is an example of one.
You can see that there's a unicoid string, non-asky string in the domain there. You can see that
just plain UTF8 in the subject and in the body. There's no encoding of anything and there are
two syntax errors in that message, not three. So the question is, can any of you spot the errors?
Right. The domain should have been puny codes. Wrong. You can do it like this,
assuming that the software supports LFC 6531 and later, which was not the case 10 years ago
beginning to be majority now. The code had been supported that last week.
The syntax errors are the missing from field required and the missing date.
I would say that the features are that there's no mine encoding anywhere.
The only thing that you need to do with the modern style is to specify the content type that the
character set is UTF8. Not all software supports this, but since Gmail supports it,
who cares about the rest, right? I actually have presented on this and someone in the audience wanted
to test it and it turned out that every person in the audience used either Office 365 or Gmail.
Not sure what to say about that, but it saved me on that day because everyone was able to use it.
I'd like to have some more support. This is Gmail, the screenshot, yes, that is C.
It's the message from data mail. How many of you know about DoveCotes, K9 mail?
Amarvis, I think. DoveCotes and data mail is a company that forks things like that and then sells it to
the biggest customer is the state of Rajasthan and there are big Indian customers.
In order to get nice Indian addresses, I am required to hide them in a little bit, but what you say
here is a top level domain. DoveBarat, the Hindi word for India. India as a country has
15 top level domains, one for each of the alphabet that are in common use there, official languages.
They have 15 because they have fairly large economy and some people speaking English and some people don't.
It's a society where it's perfectly possible to be a lawyer, for example, and pretty much not deal with English.
In my past existence, I was a contractor at an accountant. The accountant might work entirely
in Bangladesh if that was in co-cutter. This is meant to give people the choice.
The people who want to use English, find the one, people who want to use Malayalam,
Bangladesh, Hindi, can use that, their choice, not push by the computers.
This time I wanted to talk more about higher level stuff. I took, I removed the parts where I speak
S&TP. S&TP is simply to just send you debates. We're getting to the point now where open source
has quite a lot of support. The four open source IMF service that I have on the top there,
account for something like 90% of deployments. Cyrus is most of the remaining 10%. They all have
support rates, which is great for test days. It means that if you have an email client,
it has become much simpler to test that this works.
You also need S&TP service of course. Again, the majority have support now. It wasn't like that
five years ago becoming okay. Does anyone here like to write code in JavaScript?
Okay, well, minority. I'll not talk about that then, but it does exist. Email engine is under
say? Okay, excellent. Very nice work. It was a joy to test email engine.app. That's him.
Do I? Well, I'm everyone's friends, so I can say more than humans. That SQ male and the other
fork. I guess the SQ male people don't agree with the other four people about what
more than humans is, but they both have support rates. So fine. There are a couple of
do we clients today? Excellent. There are a couple more. If you go to China, then Michael's big
competitor, a company called Core Mail, has a 50% of market and a fine client.
All this means that testing is simple. Oh, by the way, I need to say that. These are not
complete lists because it would be forbidden for me to make any sort of complete list. I can give
examples, but my boss beats me if I'm making complete lists. Also, since everyone uses libraries
these things, including email engine, which uses nodes. I've done some work on this. All the
people have done more. Most languages these days have a built in library or a common library.
In JavaScript, no, there's not built in, but everyone uses no right.
In Go, there's something built into everyone uses immersion, PHP, everyone uses symphony. All of
these have good support these days. Except for Shell, which I wanted to show, this is a transcript
that sends email. It sends value email. And that's all that's needed. Again, you see, I specify
the content type, text plane, charge it. You don't need to do anything more. There's no my
time encoding to do. It's just become pleasant. Oh, well, the date is needed to be valid,
but that's not speaking SMTP, that's right. It's speaking to user as been sent mail
with minus T option, which will add a date. Sorry? Or the assumption was that for submission,
which is connecting to port 587, or these days for 65, you're not required to add a date?
I don't remember. I should remember, I reviewed that RFC, but I don't remember.
You are not required. There is a should in the RFC that says that the submission service should add
date and message ID. I also wanted to talk a bit about developments now.
Three standard draw immunizations are working on this. I like to think that two of them are
working on it because I've tested people nicely. First, the ITF, which is kind of my home,
it's sad to say that some people don't want to have email address that can contain all
of UTF8. Some people don't like to see soft hyphens in email addresses and protest against it
and don't want to implement that in their codes. So we have a couple of documents with me as older
to restrict that little bit. So that, for example, web forms don't need to accept soft hyphens
in email addresses in order to accept these extensions. The rough syntax is pretty much that
if people can read it, if there's someone who can read it, then it's legal. If not, there's not.
So mixing something like Tana in the local part, Tana is a language spoken on the
Maldives, with, say, Canadian, I forgot from the name, Canadian Indians use, in the
domain, would not be legal because there's no community that uses that combination.
We have some documents to just fix bugs and to be able to use UTF8 in the main context.
And then there's a fund document to help Quebec have a domain spelled in French and one in English
because Quebec has an accent in French. Further, the web bosses are adapting the HTML standards
to support web forms. Extremely important because people enter their email addresses in so many forms
and lost a note least. You see the sentence here does not contain a URL. However,
the magnificent program that I used to make these slides is called Outlook. No, it's not
this called PowerPoints. Recognize that this is a URL. The way that happens is not standardized now
and it is slightly different. If you post this, for example, to Facebook,
it will be recognized as a link. However, if this were a dot i and the main,
then Facebook wouldn't recognize it for reasons. The unique of the consortium is working on
something thorough to make a sensible standard for that which also covers email addresses,
covered books, links and email addresses. I would hope that when that comes out a bunch of PHP,
Ruby, Python and Markdown Software is updated to recognize the main uniformly.
Right, I'm also required to have contact stuff at the end. Please do email me for anything about that.
Particularly if you have a problem relating to any of this, I need to know about all the problems.
I wish there were fewer. Yeah, that's pretty much all I wanted to say. They extended my
talk a little bit after you. Oh, right. And required to have this as well. Even the Twitter link.
Right, and the question was, in the link recognition graph, do I know where a
unicorn is doing some sort of database look up to recognize the mains? In the present graph,
they are not. They use a fixed list which is supposed to be updated in every unicode version
from the iana. Since unicode is updated fairly often, I think this is a reasonable solution.
They also have a similar set of tables for which characters are permitted there. For example,
if there's a parenthesis around all this, then they have similar tables published along with
unicode that say what kind of characters are parenthesis that should go around the link and what
should continue the link. It's all really thoughtful but published with unicode versions not every week.
Yep. Sorry, I was not here from very good in the beginning with the presentation,
but I have a question. Why do you think that unicode being a address is good? Why? Because
whole world, the whole everything that I use is an ASEAN support ASEAN. How are you guys liking an
address or something like you have there? Oh, we are going to open the slash. How will I type that
in my keyboard? How am I going to contact you? The question was, why do I think that unicode
need an address is good and lots more but that's the gist of it. The short answer is that
ASCII disenfranchises a lot of people. We currently have some, actually I don't care very
much about that particular group. We have about 20,000 domains in Russia that are used primarily
for email. Now they could use ASCII, but it's a society that largely uses Cyrilic. Over in China
we have six digits and I care more about that because I personally really do not want to fragment
the internet into two along the great work firewall. It's important to me personally that we have
one internet and that people, and that people's software can send email to other people's software.
Towards the end of the question, why should you be able to do that when you cannot enter the
Chinese email address? The answer to that part is that the 300 million Chinese who
pretty much cannot type any A to Z except you would not be able to read your email at
your email anyway unless you know Chinese. So if you can communicate with these people
then you are able to type something that they can read. If you cannot type something that they can
read then it really doesn't matter where you could type their email address. For communication
you need email address, you need subject, you need body text, you need all of those. Having one of
them doesn't get you anywhere. But you need to do the same applies also to numbers, you know
the we use the numbers, we have generic phone numbers, you can call it whole. And it doesn't
the same question, it doesn't the same apply to film numbers and the obvious that the film
numbers are pretty much bulldozing across the world and they are pushing the Arabs to use
to use Arabic digits. That's right, even in the countries that didn't use Arabic digits to begin with
they are pushing everyone to use digits by force. Is this good or bad? Well,
I'm part of team email. I would like people to use more email and fewer phone numbers.
But obviously they can use phone numbers. If people want to communicate by WhatsApp they can do that.
I'm part of team email and I have my opinion.
Well, I should, if you down those, where do I have those? If you don't know the PDF, those two
are links. If not, I'll paste the links in the chat room afterwards. And I should repeat
to the questions, sorry. In the back? Question was are
including other than UTIF8 supported? No. There is only UTIF8. This was a design decision.
The wasn't experiment. The bugging was too hard. After that test that it was pretty much
decided that the only way forward is to say everything is UTIF8. We don't have anything to say
which part is UTIF8 and which part is not. I'm not sure exactly what the Chinese government
thinks about this. They have their own almost UTIF8. But that's how it is.
In front? What about Windows? Question was what about Windows?
Microsoft popular management issued a decree to everyone some
six or seven years ago saying Windows is for everyone on this website. It's active in a
couple of years. Microsoft software will support this completely. No if no but do it and it was done.
Microsoft had more mail clients, more mail service than they could count. They did it for all of them.
Really quite impressed. Then management started to forget about it and our bugs are creeping in.