[dameis]

>I am so happy that my IG posts arent available on my HN or that my IG posts arent being easily cross posted to a service I dont want to use like truth social.

ATProto apps don't automatically work like this and don't support all types of "files" by default. The app's creator has to built support for a specific "file type". My app https://anisota.net supports both Bluesky "files" and Leaflet "files", so my users can see Bluesky posts, Leaflet posts, and Anisota posts. But this is because I've designed it that way.

Anyone can make a frontend that displays the contents of users PDSs.

Here's an example...

Bluesky Post on Bluesky: https://bsky.app/profile/dame.is/post/3m36cqrwfsm24

Bluesky Post on Anisota: https://anisota.net/profile/dame.is/post/3m36cqrwfsm24)

Leaflet post on Leaflet: https://dame.leaflet.pub/3m36ccn5kis2x

Leaflet post on Anisota: https://anisota.net/profile/dame.is/document/3m36ccn5kis2x

I also have a little side project called Aturi that helps provide "universal links" so that you can open ATProto-based content on the client/frontend of your choice: https://aturi.to/anisota.net

[verdverm]

Except that a lot of the app builders in ATProto seem to think the protocol was designed to make their lives easier when bootstrapping their network from Bluesky userbase.

(Imo, that is a perverse interpretation, it's about user choice, which they are effectively taking away from me by auto importing and writing to my Bsky graph)

re: the debates on reusing follows from Bluesky in other apps instead of their own