54 lines
1.5 KiB
Python
Raw Normal View History

# retoor <retoor@molodetz.nl>
import base64
import time
import requests
from tests.conftest import BASE_URL
from devplacepy.database import get_table
_counter_api_auth = [0]
def _signup_api_auth(password="secret123"):
_counter_api_auth[0] += 1
name = f"apiauth{int(time.time() * 1000)}{_counter_api_auth[0]}"
email = f"{name}@t.dev"
session = requests.Session()
session.post(
f"{BASE_URL}/auth/signup",
data={
"username": name,
"email": email,
"password": password,
"confirm_password": password,
Add the trust and safety subsystem and the App Store compliance work Implements the moderation and consent obligations a social platform carries, so the web version and any client that speaks to it enforce the same rules. Moderation core (services/moderation/, database/moderation.py): a reportable target registry, the content filter and its choke points, the report queue with atomic resolution, enforcement actions, consent tracking, maturity gating, and account deletion with a grace window. Surfaces: POST /reports plus the member report list, /admin/moderation and the per-report admin view, /workspaces, terms acceptance at /auth/terms, consent and account deletion under /profile, the report button and dialog partials, the maturity gate, and the moderation stylesheet and ReportDialog client. Every user-generated surface stays reportable by construction: new content tables are registered in REPORTABLE_TARGETS or listed in UNREPORTABLE_TABLES with a reason, and the registry test fails the suite on anything left unclassified. Docs: community guidelines, content moderation, intellectual property, privacy, terms, contact, and the admin-only moderation operations page, plus the moderation API group and the Devii moderation actions. Compliance record: applecomp.md is the requirement register, applechanges.md the gap analysis against this codebase, and appleimpl.md the implementation design they resolve to. Tests cover the report flow, admin moderation, consent, account deletion, terms acceptance, workspaces, and the registry invariant across the unit, api, and e2e tiers.
2026-08-09 00:18:20 +02:00
"birth_date": "1990-01-01",
"accept_terms": "1",
},
allow_redirects=True,
)
return session, name, email, password
def _user_api_auth(name):
return get_table("users").find_one(username=name)
def _key_api_auth(name):
return _user_api_auth(name)["api_key"]
def test_regenerate_invalidates_old_key(app_server):
session, name, _, _ = _signup_api_auth()
old_key = _key_api_auth(name)
_, target, _, _ = _signup_api_auth()
resp = session.post(f"{BASE_URL}/profile/regenerate-api-key")
new_key = resp.json()["api_key"]
assert new_key != old_key
old = requests.post(
f"{BASE_URL}/follow/{target}",
headers={"X-API-KEY": old_key},
allow_redirects=False,
)
assert old.status_code == 401
new = requests.post(
f"{BASE_URL}/follow/{target}",
headers={"X-API-KEY": new_key},
allow_redirects=False,
)
assert new.status_code in (302, 200)