Thank you, yeah this came to mind, but I just wanted to check!

Yeah but how would your friends even consume such data, maybe having a shared key, but then the question is how to revoke access...

One more questions, would I get in trouble if I uploaded a lot of content. Not saying that I would but I'm just wondering what's the procedure here.

Or are we still in such early stages that those things didn't happen/weren't figured out?

*nods* got it.

Maybe

Doesn't there exist any way to check "stats" or capabilities of a PDS before even uploading?

A cool, yeah that makes sense. It's just that I stared for the bluesky oauth screen for the whole week and that got in my brain.

But then how does this play out when a user is signed in into my application using their bluesky account? If the GPS trail is stored on my PDS, it isn't really fully in their control.

First cross application post for me! Man the atproto universe has crazy potential. Can't wait to work on this 😼

Looks really cool at first glance, will defo take a deeper look later!

What incredible timing, I just started playing around with atproto and decided to use SvelteKit. This will be very useful to check code out and to learn something new.

As I learn more about this tech, hopefully I'll find answers to this questions.

And of course ask many more questions.

The tech is amazing, fast developing and looking promising for the bright future. 🚀

4. Data access: When I self host a PDS and a lot of people are using Bluesky, meaning data needs to be displayed many times, will my PDS be queried several times? Mby causing DOS?

We figured that there must be a "cache" where Bsky stores all events in their DB when they are read from the firehose.