Email vs Capitalism, or, Why We Can't Have Nice Things - Dylan Beattie - NDC Oslo 2023

[@DylanBeattie]

Folks, the thing missing from the end of the talk is one person's email address, which I thought was funny, and wanted to share with the audience, but didn't want to put on KZbin. It's about 45 seconds of content. That's it. No massive conspiracy. No secret discussion of Google, Outlook, etc... it's was just a fun little joke to end on that I didn't want to end up on KZbin. No, I'm not going to tell you what it is. But it involves the top-level domain for Austria, in case you have a hunch what it might be. ;) Oh, and those of you saying "but where's the bit about capitalism?" It's the bit of the talk where I talk about unsolicited commercial emails, spam filtering, the influence of marketing on digital communication... y'know?

[@KimKozak]

No massive conspiracy? Ahhhh.... Where are we going to get enough anger to find motivation to stop turning a blind eye to everything?

[@belst_]

one the slide with the zoho email where they say, relay not allowed, you accidently still had the protonmail host part in the rcpt to.

[@vvill-ga]

I think the + feature is fairly common, I know I've used it on Microsoft 365 at least

[@bobnob4393]

Thank you for that. Really wanted to like but you already had 69 of them so couldn't

[@VaibhavKaushal-qt9pr]

I am so not going to tell anyone else about this video because doing that would enable them to understand email so easily and I would be jealous of them! Just kidding. Totally gonaa share it with my peers. This is the most astoundingly simple explanation of email....kinda like the one you had with "Plain Text" which I absolutely loved!

[@rightwingsafetysquad9872]

I wish we could go back to when the Air Force threatened people for sending spam.

[@irgendwieanders2121]

Use the navy - still a large air force and they can float airfields around the world...

[@goldfishpartyy]

Yeah dude just tell the Navy to do it 😂

[@KainniaK]

If only somebody back then would have invented reusable proof of work we could have fixed the problem from the beginning.

[@rodh1404]

@@irgendwieanders2121 Send in the Marines!

[@jrstf]

I don't consider it spam if the from address is for real and not changed with each email sent.

[@dfs-comedy]

I ran an email security / antispam company for 19 years. We saw the most horrible abuses of standards you could imagine, and had lots of special-case code to handle them. (I'm now happily retired...)

[@dfs-comedy]

Haha, as I watch this video, I recall the endless arguments I had with people who "validated" email addresses with code that rejected valid email addresses.

[@sasukesarutobi3862]

If there's one thing you can guarantee about standards, it's that no matter how clearly and precisely you define anything, you will still get a raft of different implementations from companies who all insist that they follow the standard.

[@vibue2415]

I started programming last year. A Mail validity checker would seem to me like a bunch of if/elif/and/or statements (like a logical statement) and to me it seems not that difficult. But when I’ve learned something in programming then things are hole lot more complicated! What is it with email validity checker?

[@photinodecay]

@@vibue2415 it needs to be recursive and it's VERY complex. Most people who try to write them have also never read the standard. Probably don't even know it exists.

[@snowwsquire]

@@photinodecay i've seen an email validator that didnt work cause the email was on a subdomain

[@Corinth1311]

"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH', the paint wouldn't even have time to dry." Terry Pratchett, Thief of Time

[@DylanBeattie]

Yes! That's it. I thought it might have been Douglas Adams but couldn't remember for certain where it was from...

[@wrongtown]

GNU Terry Pratchett

[@electroflame6188]

@@wrongtown GNU Terry Pratchett

[@ohitshammy]

@@electroflame6188GNU Terry Pratchett

[@Woolbox]

Enlightening and entertaining as always! Minor nitpick: When you telnet'ed into your Zoho SMTP server, you supplied a Proton Mail recipient, and rightfully got a "relaying disallowed" message (28:45)

[@bripbrap]

I was just about to comment this!

[@Iamdebug]

From what I can tell this domain is installed at all these providers. You can do that and it's not an issue but whatever DNS responds with will be your "primary" provider. This is why the telnet to the providers, it forces the initial connection open to each provider.

[@Woolbox]

@@Iamdebug The Zoho SMTP server would not (and should not) accept incoming emails to a Proton recipient. Otherwise, it would be an open relay. A somewhat common misconfiguration back when, others than service providers, ran mail servers.

[@Iamdebug]

That's not at all what I said. Nothing in the footage I saw showed Proton at Zoho. All domains are installed in all providers and providers are isolated, they simply don't care if another provider has your domains also installed. If DNS doesn't forward you to it the other systems essentially doesn't exist. @@Woolbox

[@antoinelatrille9542]

I love how you demistify email. From a techie point of view I always heard more senior people telling me how hard it was to understand email and smtp and dkim and so on, and I went to believe that. You just broke that apart plus added an history lesson above. Thanks a lot!

[@dinoscheidt]

Dylan is great, but don‘t fall for the Dunning Krueger Effect. This talk scraped one atom layer of a one ton block of email mess 😮‍💨

[@JimBob1937]

@@dinoscheidt , definitely. In-depth email configuration of the many hacks, bugs, dealing with misconfiguration of other servers, and so on, could fill hundreds of hours of video.

[@Objectified]

He didn't break it apart. He tied together a thin layer of narrative that fits his presentation.

[@riecknicholas]

MKBHD's video of the secret history of the internet is an excellent additional "reading"

[@CottidaeSEA]

Email hurts me emotionally whenever I have to work it.

[@Felinaro]

About dark-themed email clients: the most important thing, designers must remember: its unacceptable to define color just for fonts or background. If you are altering colors, you MUST specify BOTH of them: background AND foreground. Both or neither! Because you dont know whick colors are default in viewer.

[@bryanreynolds4243]

Back in the day, I had a richard for a team lead. I wanted to go to every site I had control of and give him fore and back colors as the same.

[@PhysicsGamer]

You also don't know which one the customer's software is configured to override. Could be both, even. So even if you specify both it could look totally different.

[@Carewolf]

Better yet: Dont specify either in email. Respect your clients.

[@jeffrelf]

Amen, @@Carewolf.

[@gosnooky]

I'm a dinosaur, and I had all my system colors set to a custom dark theme back in the Windows98 to XP days, before it became a thing. Easily 75% of web form input fields had the color or background explicitly set to the default black and white, respectively. This made everything white on white or black on black. This was so irritating, and I dealt with it for years. Thankfully things improved.

[@MatthiasYReich]

When you mentioned the problem with dark mode, all I could think was “well, let’s stop with the annoying formatted ‘pretty’ emails, and have them just send text”. I’m already annoyed with logos etc in emails I receive

[@BenCaesar]

Dylan is amazing at teaching. I know nothing about this but could follow along and enjoy. Really powerful skill

[@SpaceShot]

This was wonderful. Dylan is becoming our modern day Internet historian. We sorely need talks these that explain why we are at the place we are. At once i am always in awe of how simplicity worked in the early Internet and how we are forced to keep the thing going on the face of threats of all kinds. Thank you.

[@colbyboucher6391]

...God I wish the era of people using _the internet itself_ as social media would come back. Neocities is pretty much carrying the torch by making everyone's little garbage HTML website discoverable.

[@binchamers]

ActivityPub and all the new federated social media is people finally realising that having social networks be centralised is a terrible idea! I would really love to see what Dylan's thoughts on it and the networks built on top of it (Mastodon, Lemmy, Pixelfed, etc.) are

[@masaufuku1735]

IMO Email is a perfect demonstration of why ActivityPub can't accomplish what a lot of folks hope it can. If it gained real popularity, the costs of running servers would quickly outpace the capacity of independent not for profit servers - in fact, it's that's already happened with just the influx from twitter's bullshit, resulting in some servers shutting down entirely while many others closed registrations - and it wouldn't take all that long before a handful of profit driven service providers were hosting the vast majority of accounts, just like we see today with email. And those handful of providers would begin to put up wall after wall to block small self-hosted instances from interacting with their users, using (rightly or wrongly) the specter of spam, harassment and accountability as justification - just as they do with email. That isn't to say that abandoning siloed social networks in favor of ActivityPub based networks wouldn't be a net positive, merely that the benefits of doing so under capitalism have been vastly overstated by a lot of evangalists. Email would definitely be a lot less useful if it were strictly controlled by a single profit-driven multinational corporation instead of loosely controlled by a handful of them - but it would be vastly better if we got rid of the profit motive that drives those multinational corporations to be so shitty in the first place.

[@chosenone6158]

After suckerbergs entry into fediverse with instagram threads, I'm not so sure we won't have Activitypub messed up as well in some time.

[@katrinabryce]

In practice, email is a Microsoft/Google duopoly with Yahoo having still a surprisingly large market share.

[@climatechangedoesntbargain9140]

Matrix is a protocol for federated messaging

[@morgan0]

i hope someone forks lemmy so it’s not controlled by genocide-deniers, because the idea is good, just the people behind it at the moment are not

[@olehomelchenko]

23:33 small correction, Protonmail has the same feature as Gmail, you can add "aliases" after + sign before @ sign and they all will all effectively redirect mail to the same address

[@cbrunnkvist]

I noted that discrepancy too; "sending" would of course work if he registered "rocket" and then just addressed rocket+whatever, but I suppose the point of the segment was to show that a MAILBOX cannot have a "+" in, and he didn't want to (=strictly, one can claim "shouldn't be forced to-") register just a single word address. Brings up another question: does it still map +x to "Label: x" in the GMail app, and does +x+y+z map to "Label: x", "Label: y", "Label: z"?

[@arthurdent8086]

Each time I see one of your talks online, I am ever more impressed with just how much of a wealth of knowledge you offer, and I thoroughly enjoy learning from you!

[@jayishappy]

Whatever the subject is, I know I'm gonna have a great time watching your presentations

[@Keisuki]

"And that's the end of the bit that's going on youtube" The person uploading this: "Now, that's where you're wrong"

[@IanBLacy]

It does end there, it ends exactly there. Was it cut down after the fact?

[@Keisuki]

@@IanBLacy It used to not end there. They must have edited it. I don't remember a thing of what he said after this point though

[@mr.rabbit5642]

​@@Keisuki Nooooooo 😢 I gotta look for the recordings elsewhere I guess :(( Was kinda curious why nobody's commenting on the cut tho

[@MCasterAnd]

I find it really funny that E-mail wants to be SO backwards compatible to the point where they are using 7-bit ascii. Yet, if you try to send an email, you will find that half of your friends will not receive it because it was flagged as spam and silently dropped, for some of them the HTML won't be rendered properly, for some it has ended up in the spam folder, and others can't read it because the text is in black and they use dark mode on their phone. Brilliant. Yeah, we REALLY needed that ascii 7 with the MIME work-around... lol

[@zamplify]

There's a difference between sending email and sending email over the Internet.

[@gFamWeb]

@@zamplify The Internet is the global network of computers. All email goes over the Internet. I believe you mean something like Web-based clients and such.

[@ketchup901]

@@gFamWeb Not all email goes over the internet. You can send email on your LAN or even on the same computer without routing it through the internet.

[@richmondrobinson3259]

@@gFamWeb Local email services that never reach the public internet are a real thing.

[@Mavendow]

@@ketchup901 The internet refers to all computers which are capable of networked communication. That's why it's called InterNet. InterNetwork. Inter- meaning "between" and -network meaning "to connect." It's the thing between computers we use to connect. The correct term is the WAN, or Wide Area Network.

[@ya64]

I cracked up when the screenshot with the dark mode came up! I been there, creating emails templates, making sure that it looks good on every email client that the company uses and then the QA guy just destroys you because he's using dark mode. We had to export every asset again with transparency. Fun times!

[@Dev-sl7fo]

img { background-color: white; }

[@leftaroundabout]

@@Dev-sl7fo arghhhhNOOO... it burnss our eyesessss!! Seriously, I will never understand how people are happy with bright backgrounds. Everything should be dark by default, and then for reading long texts or in bright sunlight one should simply invert the colours and use e-ink displays.

[@LeifNelandDk]

I would love if our national TV dr.dk would enable dark mode. You sit in your cosy living room with dimmed light, select their app, and bam!! 60" of #FFFFFF blinding light with a tiny logo fills the entire room.

[@leftaroundabout]

@@LeifNelandDk du burde se på NRK i stedet, der er bakgrunnen en fin blå! Bonus: alle snakker mye tydeligere enn på dansk tv...

[@error9900]

Excellent talk. Very entertaining AND very informative.

[@LucasOe]

Beautiful spam choir!

[@blazed-world]

Awesome presentation, very lively and informative! 🔥

[@SuperSmashDolls]

The guy who said "The net interprets censorship as damage" being universally censored by the Internet at large is hilarious and depressing in equal measure.

[@jamesphillips2285]

49:00 seriously considering parsing HTML e-mail because looking through that crap gets tedious. I have been resisting HTML e-mail because I feel it weakens any security guarantees of signed messages (since different clients render HTML differently).

[@ped7g]

HTML mails were/are huge mistake... Usually doesn't even deliver on the look-good side, and ruined so much stuff. Just because some people think using few extra asterisk and ascii-art tables is NOT enough to emphasise text. :( (also my email client renders them in a way you wouldn't expect if you haven't been using text terminal ever in your life... yes, I'm reading my emails in text mode with alpine email client and html mails are sort of stripped down to text-only form for me, in nice green font over black background of text terminal)

[@jamesphillips2285]

@@ped7g When I was still on dial-up lynx was my favorite browser. It was like 5x faster than any other browser because it was not downloading superfluous crap. I finally moved to graphical browsers in the 2010's.

[@MrDadidou]

Amazing talk through and through, with one remark: 55:40 this is misleading because Gmail is such a behemoth in the mail world that it's starting to setup standards that everyone has to comply with.

[@_skyyskater]

My first real job was writing HTML marketing emails for American Express, New York Times, and Time Warner at a digital creative agency called Digitas back in 2004. Although I was greatful for the job and they were very nice to work with, writing these emails was the most boring and tedious job I'd ever had. And even then, that HTML was out of date and limited. Certainly interesting.

[@lubricustheslippery5028]

And when you get an e-mail with html. You directly se it some crap that is not specifically written to you and immediately deletes it.

[@hueco5002]

I’ve been in marketing automation since 2011. Nothing has changed - emails still have to contain bloated, dated html that makes accessibility devices cry. Still doing client specific fukkery because Microsoft.

[@victor-ling]

Using plus '+' in an email address is not unique to Google. Office 365, Protonmail and Fastmail all support using plus in the email address the same way. (I am not sure about Zoho mail because I have never used it)

[@hounddog5]

Zoho supports plus as well.

[@lyleseaman4414]

It's called "the sendmail hack" because it's that old

[@boomknuffelaar]

Great talk! Had a good laugh, and some flashbacks..

[@rustkitty]

ProtonMail supports plus addressing too, they just call it "+alias". Also they have this feature called "catch-all address" which is a more general version of the same thing, because every address you didn't already register for that domain will be delivered to the catch-all address instead. For example single apostrophe and underscore works just fine, though single dash doesn't.

[@thewhitefalcon8539]

The Protonmail *signup* results (not the sending results) make sense if you remember Protonmail is supposed to be some kind of secure service so it probably puts an emphasis on not allowing weird things just in case. At 28:46 you made a big mistake - you DID ask the Zoho server to relay mail to the Protonmail test domain (pm) instead of sending directly to the Zoho test domain (zh)

[@DylanBeattie]

Ooops.

[@santiagomorales9129]

@@DylanBeattie what happened after the video cuts? did you talk about Gmail, Azure, AWS, etc? or did you sacrifice someone's first born child? or was it a round of questions? if the latter, thank you, I hate when uploaded lectures/talks have those xD

[@richardmccormack2486]

Really insightful piece. And wonderful delivery

[@dr.c2195]

16:13 I thought he was going to use the keyboard layout as an example. The common staggered qwerty layout is unwieldy and inferior to a non-staggered layout, but we keep the staggering for people who are used to using old typewriters. And those typewriters needed the staggegering because otherwise the hammers would get in each others' way. The staggering is also a case of backwards compatibility reaching insanely far back into the past.

[@milomoisson]

At 36:16, you said that in the original SMTP spec, methods could have been used to better track senders and include spam protection in the standard itself. Do you have examples of such methods or ideas that could have been implemented ?

[@Zeturic]

The number of sites that still reject Gmail plus aliases when setting up accounts is disappointing. For that matter, the "canonical" form of my gmail address has a period in it, and some sites even reject that.

[@user-xl5kd6il6c]

@@techtutorvideos No way you did that, all special characters are removed on gmail. If you have dots on your email, your email is the same without the dot, and as the video explained, the + is used just for alias.

[@pappalamma]

23:30 Proton mail supports subadressing (that + thing in local part), and office365 does it as well - thus you cannot use + character in standalone email address...

[@ferinzz]

and this is why corporations are having so much trouble figuring out how to create their own 'metaverse' that only they can own. Because the baseline of all of our primary communication methods has been free for anyone to use.. And they have to somehow compete with that. As a dev, it would maybe be beneficial to have some standards that finally update and drop the cassette tape. But as an end user, why?

[@entx8491]

Drop the cassette tape?

[@santiagomorales9129]

@@entx8491 16:25

[@IanBLacy]

The other reason they’re having trouble getting a good meta verse is because the concept is inherently flawed

[@Objectified]

.... no.

[@SioxerNikita]

Metaverse as a concept is flawed from the beginning... A centralized service that you interact with through an avatar? Well, I can tell you that shopping online is generally more efficient than walking around a store... Because... I can't search, I can't scroll fast through a list, etc Metaverse is trying to do the inconveniences of real life and add it to the internet

[@alexanderpodkopaev6691]

Amazing talk! Useful advice. And kudos for reminding me of late 90ies when I had to telnet 25 to quickly check mailserver works.

[@alejandro3244]

Super informative and entertaining!!!

[@JasonSpears]

I think plus addressing predates gmail by some years. It is supported in sendmail starting with version 8.7.

[@QW3RTYUU]

Hey! You forgot IRC as an open protocol for communication :) Nice talk, liked it, was very informative. Now I understand raw mail!

[@kiffeeify]

Ane awesome talk! Thank you so much, I am very amused and a lot more informed now :)

[@jalvrus]

I started my career in the 1990s and did a lot of work with email of various types. At that point, RFCs didn't always carry a lot of weight. People just did what worked for them. Lots of things tended to comply with some of the RFC, but often omitted parts or added proprietary extensions. The original SMTP RFC contained a bunch of dumb stuff (like quotes and comments) that very few people bothered to support. Also, bang paths.

[@EyMannMachHin]

Hey! What's wrong with bang paths? (UUCP admin from the early 90s here ;)

[@Skyben2]

Thanks for giving me a good time by watching this!

[@seanys]

Excellent talk, Dylan. Thank you.

[@JonathanPeel]

I have just tested... Sending from the work 365 mail I could single-apostrophe-at my personal domain, and... I did get it. From now on, this is the address I am sharing with people.

[@MarkFaldborg]

Wonderful talk and good history lesson.

[@LilFaerl]

No, Non-dark mode on any site/program/app/screen thingy should be illegal with capital punishments.

[@SXsoft99]

Should be as default dark mode

[@andresross1537]

I'm confused by the title email vs capitalism. Is it because capitalism caused the spam? or was there something else I missed?

[@Gunth0r]

Finally a nice overview on e-mail. Thanks! I set up my own mail server one time but dealing with Microsoft and google was just too much, especially because I didn't know enough about what I was doing.

[@Rx7man]

I am always looking forward to the next piece from Dylan.. I'm not even in the tech field but modestly tech savvy and enjoy the humor and education in each one, everything from Rock star programming to the Art of code

[@Whatthetrash]

Fantastic talk! So good! :)

[@vttale]

Email subaddressing with the plus sign in local part was in use long before Gmail even existed, at least since the late 80s/early 90s by the Andrew system at Carnegie Mellon. Source: I'm old. PS: Oh, regarding it not being "part of email standard" you are basically right, but as with many Internet standards, it's complicated. RFC 5233 describes subaddress filtering, including "One common way of encoding 'detail' information into the local-part is to add a 'separator character sequence', such as "+", to form a boundary between the 'user' (original local-part) and 'detail' sub-parts of the address, much like the "@" character forms the boundary between the local-part and domain."

[@SteinGauslaaStrindhaug]

17:22 Most naive email regexes in Stackoverflow would probably match the first two, sometimes the third and fourth too. But when I when I first considered the problem of validating email addresses I realised that the spec allowed so much the only thing I really could be sure of was that a valid email contains an @ symbol and at least one character before and after it. But of course then the clients complained that it accepted "somename@gmail" etc. without the top level domain; so I decided that it was better to add another technically incorrect requirement that an email should have at least one period with at least one character before and after that period in the host name part; with the assumption that anyone who legitimately have an email without any periods in their host name is probably much rarer than idiots who forgets the top level domain name of their email. So whenever I have needed to make my own email validation; it would usually accept all of these except the ipv6 one.

[@f.d.3289]

One of the best things about this lecture is that I finally understood why I have ALWAYS hated HTML e-mail, and up to this day, forcing plaintext mail is the first thing I do when I set up a mailer. I never really knew why I hated them. But when I heard "table within a table within a table", I knew that even without knowing exactly why, my coder brain just knew it was crap. Thanks, Dylan :)

[@qlum]

Great talk, as someone who has to deal with e-mail, troubleshooting clients writing mail templates sometimes It truly is a pain to work with.

[@TheodoreRavindranath]

Amazing!

[@JonathanFrost]

Fascinating!

[@aimeekeel]

Extremely useful info. Thanks!

[@PierreThierryKPH]

Is the full version elsewhere?

[@andrerenault]

I vaguely want to know what happened after the youtube version ended…

[@sfdntk]

You know a talk is truly excellent and the presenter is an engaging speaker when you're already familiar with all of the concepts being communicated but you still watch the full hour and love every minute of it. Amazing work, Dylan!

[@RichardBronosky]

45:55 "floating point boolean" LOL! I love this guy. ☮️❤️🌈

[@zamplify]

Best talks in the business, hands-down.

[@enverhaase8562]

38:12 if you also wanted to know what it was that is base64-encoded there: it is "funwith:email", so a colon between login and password.

[@harshitjoshi3082]

Wow this is a great talk 👏

[@juliocardenas4485]

This is one of the best tech talks I’ve seen.

[@jak-sdk1429]

28:38 You said you're not relaying, but it looks like you had a typo? Server was Zoho but the RCPT was @pm.

[@f.d.3289]

Hands down my favourite lecture of Dylan. Seemingly obscure, but full of actually fascinating stuff and totally fun. 33:20 "E-mail was invented by hippies. And hippies SUCK at security." XD

[@Xsiondu]

I have no reason to have enjoyed this talk as much as i did. I'm not a developer, programmer, hell i can't remember the last time i opened an email client. But this talk was very interesting.

[@picahudsoniaunflocked5426]

I love that I jumped when I received an email during the beginning part where he was saying "ok, you're getting an email now". I hate that I was jump-saddened by Young Matty Perry at 33:54.

[@pixi850]

I guess I need to watch more of his videos, glad I stumbled upon someone talking about him on Reddit.

[@adambickford8720]

Great talk! Still feel like it should have tried to sell me something because that's the web now.

[@jeffbrownstain]

Not in the places I hang out.

[@christianknuchel]

About 53:46 : Dark mode is the original default *and* an accessibility feature. It's bright mode that should never have been allowed to happen.

[@sezmonsta]

This talk should be compulsory viewing. OMG. So packed with critical context about how things work in Internet land.

[@KainniaK]

This is an amazingly interesting talk.

[@unexpectedkAs]

Awesome presentation! On the last point about corporations owning WhatsApp, Telegram, etc, could the ActivityHub be the email equivalent for modern communication needs?

[@cbrunnkvist]

Classic ASP you say. Which SMTP client COM component did you use in the for-loop @DylanBeattie? :)

[@DylanBeattie]

The first version of that particular system was Server.CreateObject("CDONTS.NewMail"), I think - and then switched over to using CDOSYS on Windows 2000 at some point.

[@benbrist]

Great talk as usual @DylanBeattie One thing - Microsoft have the same +tag tracking on 365 23:26

[@pauljmey]

Summer of Love was 1967 (nice metaphor though)

[@ekaa.3189]

I have ME/CFS. Dark mode allows me to continue to do stuff with computers. Big areas of bright lit pixels like white backgrounds makes me tired faster.

[@mschwage]

Hold on. DNS in 1983? It wasn’t in widespread use. I was a student operator in the digital computer laboratory at the university of Illinois in 1983. At that time our “network” connection was a 9600 baud modem to Purdue twice a day, in which we sent 2 MB or so of email and Usenet postings per connection. Some time later, we got an always on connection of… not sure, 56 kb? Anyway, for years I was typing in all sorts of arcane email paths to send messages. Thank god for ihnp4, which was a gateway to everything! DNS wasn’t adopted for quite some time. The hosts file grew to some 1.2 or maybe 2 MB by the time DNS was rolled out. I was disappointed, because it meant that I wouldn’t be able to look up (grep) for any host I wanted from the hosts file. Of course, it also meant that a single entity couldn’t claim a name that nobody else could use😂. Anyway, I maintain that 1983 was too early for dns to be used. No one was using it, that I was aware of.

[@wChris_]

By the way + tagging is supported by all of them, not just google.

[@lerneninverschiedenenforme7513]

awesome as always!

[@ICountFrom0]

I remember manually assembling mime into files, sometimes waiting quite a while for the middle bits of the email to arrive because I was down the FAR end of a long ! path.

[@SteinGauslaaStrindhaug]

23:41 and 24.34 hmmm... Maybe + and - somehow is interpreted as some kind of wildcard or escape character when they look up wether it's available or not so that it either returns a spurious actual result. Or maybe the it passes the frontend validation but when it asks the isThisEmailAvailable service on the server it will also validate it with a different validation before searching and then reply false because it failed the validation? Maybe the latter is more likely. It could also be the default case in an error handling switch case that happens to trigger whenever you cause an error they hadn't thought were possible.

[@SteinGauslaaStrindhaug]

Btw, having a default incorrect/nonsensical error message is incredibly common. For some reason all servers like to communicate in jargon, weird error codes or just broken English (always English despite the server serving a website in a single non-English language) particularly when something goes wrong (and it's not always your backend programmers fault, sometimes a generic exception will be triggered in some 3rd party library and bubble back to the client); so you rarely want to parrot back exactly the error the backend gave you, you will translate all the messages you know about to something that humans can understand. But since you cannot know all the possible error messages, some times there will be errors that you have no mapping to a friendly translation for; so you'll have to have a fallback error message. The technically correct default, probably should be "unexpected error" or "unknown error" etc. but that's not particularly friendly so your product manager will probably insist that you lie and just map the unknown errors to some specific error that sounds somewhat plausible and would be correct most of the time; and then just log the actual error somewhere. So completely unexpected error codes (i.e. non standard HTTP statuses etc) or missing responses will typically be "translated" into a cautious suggestion that maybe the internet connection is broken (despite the fact that an actual response code normally should indicate there _is_ a connection; you'll never know if some random browser could invent one for network issues), and error codes we haven't agreed on from some kind of isThisAllowed service will typically map to the most common reason for why it's not allowed like this probably is. Pro tip: quite often we will output the raw error message into the javascript log or into a hidden element on the page somewhere in the DOM near the friendly but incorrect message while debugging; and more often than not we forget or "forget" to remove this before going in production so you can often see the raw errors or even better raw errors + some guesses as to what the real error is using the debugger if you're curious. And if not, as long as you can identify the network request that caused the error you can see the raw error using the network tab in the debugger. If the error isn't from a server but happens somewhere in the client code, we're almost _allways_ logging something more than the "friendly lie" in the javascript console; and if it's a truly unexpected error it will usually be a full exception with stack trace etc.

[@ShadowZero27]

i needed to hear this

[@aaronchantrill7338]

Thank you, that was very interesting. I thought you might touch on pgp and gnupg and why nobody ever mandated that system (as far as I'm aware).

[@MarbledPaladin]

Plus sign in email addresses is *NOT* a gmail/google specific feature, it is an *EMAIL STANDARD* specified in RFC 5233 (from January 2008) that was originally specified in the now obsolete RFC 3598 (from September 2003)... google/gmail just happens to be one of the big email providers which happened to support it first but more tech savvy people have ben using it for years (on sites which supports it, not all sites consider an email address with a plus sign valid)...

[@shmoola]

28:45 Well you connect to zoho and send to proton. So relaying?

[@torsten_dev]

For the issue of the logos. Couldn't you do embedded svgs and do css on those?

[@icepicker8528]

Noooo I need to know what happened after the live stream. I need closure on the anecdote.

[@sundhaug92]

Now I wonder what happens if say you provide a mime type alternate for something like pdf or mp4

[@techgeeknzl]

You get either an attachment, or a security breach; depending on your email client.

[@edstercw]

What happened after the talk stopped being filmed?

[@mikev7490]

I've seen a few providers support the + tagging method, it's a very useful feature I wish was made standard.

[@byronhambly]

base64 decode at 38:18 is funwith:email

[@Larzenegger]

Great talk. The + character in the local part of an address seems to have been described in the 2008 RFC 5233.

[@elle305]

at 23:00 you call +tag added to email a Gmail custom feature. that's not true! + tagging is an RFC feature and should be permitted on any proper implementation. most front end validators however are not compliant, so the point is often moot. in fact despite Gmail obviously supporting it, you often can't provide that as an email when signing up for accounts elsewhere. the ignoring of certain characters like spaces and periods is however Gmail specific.

[@elle305]

tbh your political bent is more libertarian in the vernacular sense than toad. and i get you mean just to be disparaging with the hippie comment, but hippies weren't involved (actual hippies were really weird). overall i think you should have let people in on the fact that this was and to some extent still is a huge debate. you kinda hinted that toad has an extreme view and that you're reasonable. i don't entirely disagree with you but i think you did a disservice to the community debate

[@elle305]

last thoughts: the title here mentions capitalism but the connection to capitalism is pretty light and at the end. actually i lived through this era as a working engineer so i love to talk about the political and industry struggles that led to these decisions. open relays were related to a naive or utopian idea about the Internet, but it's not bc they were dopey and closed relays is the right choice. closed relays was forced on us by corporate interests who as you've experience, bully us out of using p2p technologies in many ways.

[@kjkiefcakes1847]

Listen I'm not saying I was bored, because I loved the talk up to the point that it happened, but the giant spike in the graph of my enjoyment over time when you made the Vision joke was amazing.

[@Zheraan]

Is there anywhere we can watch the end of the talk? It was getting interesting as he was talking about how capitalism is ruining it

[@limitless-codes]

I'm wondering what went on the continuation of it.

[@arduous222]

38:50 Such a powerful quote given the ad-blocker ban situation in KZbin.

[@bluebrick5300]

Proton also has the "+" feature that google has