Shouldn't write permissions for collections be more restrictive?

Another concern I have is that once I authorize an app, it technically has access to read and write data to any collection in my repository.
I understand the need for broad read-access to support interoperability and cross-referencing, but why should my music app have write access to my git host?

My understanding is that once I choose a PDS, it will host all of my data for every application operating on the atmosphere. I believe that the majority of people will use the bsky PDS. I'm curious about how this will scale and about it potentially becoming a single point of failure.

Great explanation, completed the workbook exercise as well. XD

I thought I had to have my own PDS to use my domain as a handle, but that’s not the case, which makes sense. Self hosting is a beast to tame; I'll do it some other time. Now, I want to build something simple with atproto to understand its workings better.

As far as I have understood by the article, there doesn't seem to be a concept of private posts. Will it be a deal breaker for those coming from a traditional social media platform? 🤔

I'm new to atprocto, and this was my first detailed read into the technology. It was an engaging read. It was impressive, and I'm excited to host my own PDS soon and also contribute to tools for building it.

I found it fascinating that how no one around me talked about threads being part of the federated network when it launched, even though everyone around me works in tech. For us it was just meta capitalizing on the twitter chaos.