* Initial plan
* Initial analysis of inline chat moderation 500 error issue
Co-authored-by: gabek <414923+gabek@users.noreply.github.com>
* Fix inline chat moderation 500 errors by supporting Authorization header tokens
- Modified RequireUserModerationScopeAccesstoken middleware to check both Authorization header (Bearer tokens) and URL query parameters
- This fixes the issue where inline chat moderation from the web UI was failing with 500 errors
- Maintains backward compatibility with existing code that uses query parameter tokens
- The fix aligns the chat endpoint behavior with the integrations endpoint which already supported Bearer tokens
Addresses the wiring issue between OpenAPI spec and API implementation identified in issue comments.
Co-authored-by: gabek <414923+gabek@users.noreply.github.com>
* Fix inline chat moderation 500 errors by adding nil pointer checks
Co-authored-by: gabek <414923+gabek@users.noreply.github.com>
* Fix nil pointer vulnerabilities across all OpenAPI endpoints
Co-authored-by: gabek <414923+gabek@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: gabek <414923+gabek@users.noreply.github.com>
* make a new function to generate appropriate to and cc apub objects
* use new addressing function to set "public" message addressing appropriately with the followers collection
* early return from sending federated message if federation is disabled
* cleanup old addressing code, apply new addressing mechanism to live notifications as well
* linter fix
* Update activitypub/outbox/outbox.go
---------
Co-authored-by: Gabe Kangas <gabek@real-ity.com>
* WIP
* fix(test): fix ap test failing
* fix: fix unkeyed fields being used
* chore(tests): clean up browser tests by splitting out federation UI tests
