Files
pyMC_Repeater/repeater/web
agessaman f38e3561e8 fix(api): refuse identity changes the next boot could not load
Names are unique across the repeater, rooms and companions at boot, so
create_identity and update_identity now refuse a name another identity
uses (including "repeater"), and creating a room with another identity's
key is refused as updating one already was.

A refused room update restores the live entry in place rather than
emptying and refilling it, since the identity manager holds that dict and a
concurrent config save could catch it with no name or key. A bad settings
value is refused too, undoing a rename made earlier in the same request.

An ACL request's identity_hash may be a JSON number, and 0 means hash byte
0 rather than every ACL.
2026-10-02 10:57:24 +01:00
..
2026-07-24 15:52:01 -04:00