From our last meeting, we did a speed run through the entire architecture. It felt like PDS hosting would show immediate data sovereignty, but there were very few people who had open or paid signups.
- PDS for Jurisdictions: running a PDS in a particular country or jurisdiction
- PDS for Communities of Interest: Academic / university affiliated hosted was a special case
- PDS for App Devs: running a PDS along with a custom app to provide smooth sign up
Organisation:
- What is the business model (for-profit, coop, something else)
- Jurisdiction
- How to get funding/whats the salespitch for funding
- What does legal responsibility within the organisation look like
- Would this be a separate organisation from an org that runs a relay/appview/whatever
Community:
- What community is the target audience
- What's the size of the community that is targeted
Technical:
- What software is used for the PDS (rsky, bsky one, something else)
- what software is used to do manual moderation (ozone, build something for yourself)
Moderation:
- How is automated moderation handled, related to CSAM scanning (hive, roost, something else)
- How to deal with moderation for lexicons that Ozone does not handle (someone using ATFile to upload the bee movie)
- Structure for getting DMCA requests
- Who makes the guideline on how to deal with (political) takedown demands from governments