Post

I need opinions on a HappyView feature: inspection for atproto spaces. TL;DR - should the dashboard be give admins a clean view into spaces content? More deets in the thread. 🧵 #atproto

3 reposts13 likes

I agree with everything Once Spaces launch, there needs to be very clear communication so users do not misunderstand that it's not E2EE (like I hope no app would try to mislead anyone but hey we never know) Admins need tools to help them moderate or Spaces will become a nightmare very quickly

And it's like we have to trust the PDS admin if you are not self-hosting, since they will have a rotation key for our accounts and the power to be evil, but we trust they won't abuse that power And like we trust app devs while authorizing access too OAuth page so far is doing a good job for Spaces

This would be ideal, and I can do this for the instance admin. There's no mechanism (yet) for alerting the spaces admin, tho. That would be on the app to implement, or on us to define as part of the spaces spec. FWIW, I think this would be an excellent thing to add to the spec.

Would be nice if this also attempted to pull the discoverable appview privacy policies for the ones which you can detect is used by users in the space (and making a note that there may be unknown appview instances and clients accessing it).

The feature is almost ready! 👀

Trezy@trezy.codes

Scope the new space explorer coming in the next HappyView release. 👀 #atproto

I started writing a thread to encompass all of the info from here and the Bluesky thread, but I realized there was way too much for another thread. 😅

Trezy@trezy.codes

Am I Building the Torment Nexus? I built a tool that lets HappyView operators browse the contents of atproto spaces, and the moment I saw it working I got a pit in my stomach. Here's what the community had to say about whether it should exist, and what it needs to look like if it does.

Basically, spaces are fully accessible to server admins. This is the same for spaces hosted by HappyView, as well as spaces on your PDS. If somebody has access to the database, they can read anything in your spaces.

Wait really? I thought it's PDS hosted space, and therefore only the PDS admin has access. I didn't realize spaces also has access. If they do, HappyView should provide the admin overview

Theoretically, there's a separation of concerns here: • user = which apps can do what • PDS host = which app/user combo can access what data (read or write) • space host = which users belong to space (read access to view) • appview = which users belong to space (write access to view)

Unless I've misunderstood @dholms.at, the protocol: • prevents a standalone space host from forging user credentials to con my PDS host into allowing the wrong user/app to access my data (proactive) • lets me revoke credentials for appviews which overshare the data I let them access (reactive)

Yeah, the intent is that the repo host (the user's PDS in most circumstances) holds the space data. However, spaces isn't generally available yet so HappyView provides a polyfill for the time being that allows operators to implement spaces, even for users whose PDS doesn't support it.

Since it's a polyfill, HappyView is acting as a repo host for users' spaces. That said, when an AppView is the authority for a space it'll still index the data from that space and have a fully readable copy. Basically, this will likely be a concern for /all AppViews./

From a technical perspective, this is not surprising. Spaces are not encrypted. They provide access control, not privacy. If you want privacy (even from admins), you need some form of E2EE.

From the perspective of a server operator, it actually makes a lot of sense. The operator of a PDS needs to be able to moderate the content on their PDS. We don't need bad actors creating spaces just to store their CSAM. That would be Very Bad™.

Having access via the database is one thing, but having a tool for a clean view into that data feels like a whole different ball game. So here's the question: Is it too skeevy for HappyView to provide an interface for browsing space data?

Yes, admin view into spaces content AND like Discourse and other multi user systems you should add audit logs for admin actions.