apps/server · scn-chat · Tangled

ATProto-based AI Assistant Chat interface.

scn-chat apps server

2 folders · 2 files

pouriade.com · Cover the web UI spec's acceptance criteria with tests and tick them off. New tests cover the server redirecting signed-out users before rendering, a viewer being sent from the settings to the login page while a shared chat still opens for them, creating a chat, uploading a PDF and sending it as an attachment part, scrolling to the bottom on send, syncing in a message written from another client, deleting an API key, and the background sync switch. The tool details test now checks that each summary is collapsed. · 4w ago

Judge a NAT64 address by the IPv4 address inside it, rather than refusing the whole 64:ff9b::/96 range as private. On an IPv6-only network, DNS64 gives every IPv4-only host a NAT64 address next to its IPv4 one, and the guard refuses a host when any of its addresses is private. So sign-in failed at the callback, with "Refusing to connect to private network address 64:ff9b::d8c6:4f01", since resolving the identity reached the PDS, the handle, and plc.directory through the guard. Every other guarded fetch failed the same way. A NAT64 address hiding a private IPv4 address, like 64:ff9b::7f00:1 for 127.0.0.1, is still refused.

Cover the web UI spec's acceptance criteria with tests and tick them off. New tests cover the server redirecting signed-out users before rendering, a viewer being sent from the settings to the login page while a shared chat still opens for them, creating a chat, uploading a PDF and sending it as an attachment part, scrolling to the bottom on send, syncing in a message written from another client, deleting an API key, and the background sync switch. The tool details test now checks that each summary is collapsed.

Merge main, bringing in the admin area from admin-ui: settings in the database instead of config.yml, roles, registration and access with viewers and suspension, plugin instances, and admin models. The server merges as is, apart from three fits to this branch: app.ts passes the app name from the settings store to Start with each request, in place of admin-ui's index.html templating; the viewer sign-in check looks for this branch's /shared/ links instead of /s/; and the development URL is port 3000, where the server serves the web app.

Implement initial buildout of core features.