search

starlinglab / integrity-backend

Backend server for registering and configurable processing of authenticated assets in the Starling Integrity framework.
MIT License
10 stars 3 forks source link

Adopt new configuration schema and implement new file structure with Collection directories #73

Closed benhylau closed 2 years ago

benhylau commented 2 years ago

Task Summary

📅 Due date: N/A
🎯 Success criteria: Decide on file structure for Collections.

File structure chart: https://app.mural.co/t/starlinglab7814/m/starlinglab7814/1645818950661/a7fde68442959d82fbb968f2f825964cc1db86aa?sender=ub3a421c048efd7d270741703

To Do

☝🏽 from perspective of the backend (this repo) we have defined the requirements for files to be dropped for processing. Bringing them to the right format to "drop off" will be responsibility of Collector clients.

We also discussed moving HTTP API server (i.e. POST handler) out to become a standalone Collector client. This may spin off to a future issue.

benhylau commented 2 years ago

Bots

Platform Scope per Docker instance Collections per Docker instance Channels per Collection Join
Slack Workspace 1 Many Added by Workspace admin then auto-join by invitation to each channel
Telegram Bot Account* 1** Many Depends on channel type***
Signal Phone Number 1** Many ?

Can have many Bot Accounts per phone number Possible to split into many, but requires content inspection Telegram has different types of multi-user "channels":

Telegram screenshots

signal-2022-03-15-120725_001 signal-2022-03-15-120725_002

benhylau commented 2 years ago

@anaulin is working on:

See: https://hackmd.io/ALDXEZWjTDeyeoF7cE1AYg?view

anaulin commented 2 years ago

The one remaining piece of work on this is moving the "legacy" actions to use the new system, which is now being tracked in: https://github.com/starlinglab/integrity-backend/issues/79