Making it even easier to register domain names. Rebuilding your friend network between the DNS names of friends, family and other associates. Sharing photos and videos and birthday reminders.
I feel like it's marketing all of the technologies of the early web that enabled these things, but with great UX and an order of magnitude less complexity for getting all of it setup.
Disclaimer: I am building such a "social technology" around domain names, letting users truly own the database of their interaction with a service, https://github.com/plurid/deserve
Having a DNS domain is akin to going into a public town square and setting up your stall selling whatever vegetables you grew in your garden. But just as the individual farmers were run over by large corporations who invented the hyper-market, just as so the individual users have been fleeing, increasingly in the past 15 years, to be under the umbrella of big-corp-du-jour.com. Making another-service.com with the façade of a "public town square" is just making another hypermarket.
And also, it's called a "public town square", with accent on town, as in "group of houses" [1], because it's meant for a relatively small population. There is perhaps a reason we don't have "public megacity squares" (stampedes and crowd crushes aside). And there is perhaps something inherently wrong when an individual has 100+ million "followers": in a public town square a stall could not sell vegetables to 100+ million people since there aren't that many people in the town in the first place.
A public square is "an open public area in a city or town where people gather". DNS is far too abstract to even remotely resemble a public square--just like "capitalism" or "zoning laws" are too abstract to resemble a public square.
Nor is foo.com a digital public square (just like your house isn't a physical public square). Public squares (digital and physical) are places where people already gather.
And yes, precisely, "foo.com", or "twitter.com", or "tiktok.com", cannot, by definition, be digital public squares: they are just stalls, booths, were we go and check certain vegetables.
the town = the TCP/IP suite of protocols (UDP, QUIC, etc. included)
the public town square = DNS
a booth selling vegetables in the public town square = a domain, "foo.com", publishing whatever their opinion is about reality and everything else
A great lie told again and again by "social media" domains is that they are "platforms", but a platform is meant to sustain something else beyond itself. "foo.com", "twitter.com" are merely individual booths, where all the value is owned by the person/company owning that domain, irregardless of how "easy" it is to "post" on "foo.com" and how difficult it is to setup a new booth/domain on DNS: DNS is that platform we have been hearing ad nauseam.
And even more, a domain, such as "foo.com", or "twitter.com", or "tiktok.com", is fundamentally someone's estate, owned by a master [1]: it's a glaringly obvious contradiction in terms to say that a domain could ever be a "public town square".
Entering and adding value to someone else's domain is akin to belonging to a feudal master, a technofeudalism if you will [2]. And some tehnofeuds are great, I personally enjoy "github.com", but believing that "github.com" is a "public town square" for code, not backing up your work in other places, it's at the very least irresponsible.
[1] https://www.etymonline.com/word/domain#etymonline_v_13918
DNS itself (in the form that gets used publicly) is controlled by a few actors -- arguably the 'true' owners of all the domains that are leased from them. This is underscored every time new TLDs are released and people have to scramble to secure their names and brands. In that context alone, DNS also can't qualify as the public square.
Discoverability and noise filtering are the hard problem.
However, now, after we, the users, have created such Leviathans [1] as Google, Meta, and so on, we, the developers, must go back to the drawing board and solve discoverability, noise filtering, payments [2], and much more at the protocol level. Which is not even a new or outrageous idea, even Mr. Jack Dorsey seems to agree to this [3].
[1] https://en.wikipedia.org/wiki/Leviathan_(Hobbes_book)