We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Hacker News·Jun 19·5 min read
There Are No Instances in ATProto
TL;DR
A common misconception is that ATProto, a protocol for decentralized social media, has instances like Mastodon. However, ATProto does not operate on the instance model; instead, it allows users to publish content on their own platforms, which can be aggregated by various applications.
✦ Why It Matters
Understanding ATProto's structure enables engineers to design more effective decentralized applications without relying on instance models.
Key Takeaways
- Explore decentralized content publishing options with ATProto.
- Avoid misconceptions about instances when using ATProto.
- Consider flexible content management strategies.
- Utilize aggregation tools for broader content reach.
Full Summary
ATProto is a decentralized social media protocol that differs fundamentally from platforms like Mastodon, which rely on instances—separate servers hosting user content. In ATProto, users publish their content on personal blogs or platforms, which can then be aggregated by applications such as Google Reader or Feedly.
This separation of hosting and aggregation means that content does not reside within a single app but is instead a projection of the broader blogosphere. The article emphasizes that the confusion arises from applying the instance concept from Mastodon to ATProto, which does not support this model.
By clarifying this distinction, developers can better understand how to utilize ATProto for decentralized applications. The implications for engineers include the potential for more flexible content management and distribution strategies without the constraints of instance-based architectures.