this post was submitted on 18 Aug 2025
886 points (99.1% liked)

Programmer Humor

25885 readers
706 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] CommanderCloon@lemmy.ml 61 points 4 days ago* (last edited 3 days ago) (9 children)

Question 5 is incorrect, name@example is a fully valid email address, even after RFC 2822

The spec of RFC 2822 defines an address (3.4.1) as:

local-part "@" domain

domain is defined (3.4.1) as:

domain = dot-atom / domain-literal / obs-domain

dot-atom is defined (3.2.4) as:

dot-atom = [CFWS] dot-atom-text [CFWS]
dot-atom-text = 1*atext *("." 1*atext)

1*atext meaning at least 1 alphanumeric character, followed by *("." 1*atext) meaning at least 0 "." 1*atext


If tomorrow, google decided to use its google top-level domain as an email domain, it would be perfectly valid, as could any other company owning top-level domains

Google even owns a gmail TLD so I wouldn't even be surprised if they decided to use it

[–] pineapplelover@lemmy.dbzer0.com 3 points 4 days ago* (last edited 4 days ago) (4 children)

I didn't understand this one. How do you have a no dot domain? Like you need to distinguish from example.com or example.wtf

Edit: do you mean if you own .google you can have your email@google address?

[–] DaPorkchop_@lemmy.ml 5 points 4 days ago

Yes, the top-level domain is still just a domain. I'm not aware of any public Internet services which are reachable from a TLD directly, and it's strongly discouraged by ICANN, but there isn't any technical limitation preventing e.g. someone at Verisign from setting up example@com.

load more comments (3 replies)
load more comments (7 replies)