AT Protocol works like the Web, where each user is a website and each application is a search engine. The apps crawl the network of hosts and aggregate activity. We have over 100 outside hosts and at least 3 aggregating apps out there. It’s a different model than ActivityPub, which is more akin to email.
We never said no algorithm. I don’t know where that meme comes from. We have an open system for algorithms, which we and 3p devs can operate. We have a default algorithm for every user called Discover. It was one of our main concerns to have an answer to algorithms in a decentralized network.
For DID PLC, the likely solution is to move the registry into a nonprofit which will maintain it, similar to ICANN. We also support the Web DID method, and if folks like this remain concerned we’re open to other DID methods. It’s important, but roughly similar to DNS or TLS issuers; supporting infra to the application network.
AT Protocol works like the Web, where each user is a website and each application is a search engine. The apps crawl the network of hosts and aggregate activity. We have over 100 outside hosts and at least 3 aggregating apps out there. It’s a different model than ActivityPub, which is more akin to email.
We never said no algorithm. I don’t know where that meme comes from. We have an open system for algorithms, which we and 3p devs can operate. We have a default algorithm for every user called Discover. It was one of our main concerns to have an answer to algorithms in a decentralized network.
For DID PLC, the likely solution is to move the registry into a nonprofit which will maintain it, similar to ICANN. We also support the Web DID method, and if folks like this remain concerned we’re open to other DID methods. It’s important, but roughly similar to DNS or TLS issuers; supporting infra to the application network.