Motivation
PDS SLD.TLD Abstraction
A domain comes with an SLD mywebsite.com and a TLD mywebsite.com both are a requirement to form a functioning DNS.
It is a fundamental core part in how a PDS operates, and over 30 million PDS accounts have been created. This is a great achievement, however, several billion people understand accounts to not come with a DNS and only have a username/handle, their @.
An apps purpose is to deliver value to the user, if there is no value, the app dies.
We think, that it is an app builders responsibility to abstract away technical complexities, that includes .SLD.TLD domain endings for handles. Because billions of people are familiar with @usernames we should focus on providing a familiar experience, while ensuring the user has created a self custodial account on a PDS. It is the apps job to educate the user in a later time about the users account benefits (interoperability with the AT Protocol, complete control over their data, etc.).
Self.surf was created to achieve this, allowlisted apps can create PDS accounts for new people without having to explain what .self.surf is used for. The app can educate the user in the Account Settings about their complete handle.
We understand that this is not a preferred approach for all ATP developers, but if you are interested in providing a familiar user experience (signup without redirecting to a new url, usernames without .SLD.TLD, you are welcome to inquire to join self.surf).
Sufficiently Decentralized
Self.surf is currently only gating access to approved apps, our requirement is that your users must be over the age of 18, everyone is welcome to fork and change the rules.