Cross-gateway Social Feeds with Moderation & Custom Preferences

[charleslavon]

[charleslavon]

from @gabehamilton

Overview

The stream of all social actions (posts, comments, likes, follows, etc) needs to be joined with the stream of moderation actions to form the base stream or base streams per jurisdiction. This cannot be done client side because we don’t want to send illegal content to users even if they don’t see it.

This should then be joined with streams of weights: Ratings, Labels (hashtags), User Content Preferences; and possibly split by gateway. This can be done server side (indexers) or client side or both.

Interconnected Features

• Moderation
• User’s personalized feed: Ratings and Reputation, Labels, User’s preferences
• Gateways
• Search
• Self-Tracking

Decisions

1. Base indexer needs to handle Moderation actions.
2. These generate deletes in the tables queried by Feed components.
3. Search needs to be fed by the same indexer.
4. A moderation group (community) can make moderation decisions for a jurisdiction

Open Questions

1. Do we want ActivityPub compatibility?
2. Do we want BlueSky compatibility?
3. Which data needs to be private? - probably User Content Preferences
4. How will we anonymously process it on servers? - profile tied to token - what if it becomes identifiable?
5. Or when you load does it take some time to ‘building your personal feed…’
6. Can we pre-calculate base content streams so most users do not receive illegal content?
7. Should these be per-jurisdiction or do we want to start with one?
8. Is there a multi-tenant aspect to communities?If I’m a major customer and running my own gateway then I want my own stream of social data. Is that my own copy of the social.near contract? A hashtag probably isn’t sufficient unless it is automatically added. We want each community to have their own moderation, so where is this division made? How do I stand up a new community: by gateway, by creating a group in a groups widget?
9. Should each community’s moderators be a DAO?
10. How do jurisdictions and gateways interact?
11. On the CustomerX gateway, Can moderation groups (communities) choose to be downstream of another community? Moderation decisions would flow down but could be overridden. Don’t want the base moderation, choose the raw feed as your upstream.

User Preferences Storage Options

• On Chain in social.near contract.- Pros: One place for all data, easy to implement.- Cons: No privacy
• Anonymous Hash (from client side) on chain in social.near contract- Pros: One place for all data, easy to implement.- Cons: tied to device
• Encrypted, on-chain in social.near contract - Pros: One place for all data. - Cons: More work to implement (multiple keys). Lack of forward secrecy.
• Localstorage- Pros: Private, easy to implement- Cons: tied to device
• Per gateway backend app. - Pros: Private, easy to implement. Notification settings using same approach - Cons: Each gateway needs to stand up their own backend app.
• Fractal private storageNeeds investigation.- Pros: Encrypted and on a private chain- Cons: Only available to i-am-human members.