Without it a peer cannot check the key log: a leaf is filed under fnid: once an account claims an address, so a verifier that does not know the address computes local:<audience>/<id>, matches no leaf, and refuses the send as an unlogged key.
/e2e/keys has always carried it, but the send path fetches bundles only when a device needs a session established (so it does not drain one-time prekeys per message). Every later send saw the directory alone. On Android that surfaced as "Something went wrong reaching that server" while the relay was answering fine.
Without it a peer cannot check the key log: a leaf is filed under `fnid:` once an account claims an address, so a verifier that does not know the address computes `local:<audience>/<id>`, matches no leaf, and refuses the send as an unlogged key.
`/e2e/keys` has always carried it, but the send path fetches bundles only when a device needs a session established (so it does not drain one-time prekeys per message). Every later send saw the directory alone. On Android that surfaced as "Something went wrong reaching that server" while the relay was answering fine.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Without it a peer cannot check the key log: a leaf is filed under
fnid:once an account claims an address, so a verifier that does not know the address computeslocal:<audience>/<id>, matches no leaf, and refuses the send as an unlogged key./e2e/keyshas always carried it, but the send path fetches bundles only when a device needs a session established (so it does not drain one-time prekeys per message). Every later send saw the directory alone. On Android that surfaced as "Something went wrong reaching that server" while the relay was answering fine.mentioned in commit
5d5ed0b97fmentioned in commit flamenet-messenger-android@6ed7931b8bdac418716e4792ff89ddb793b25c77
mentioned in merge request flamenet-messenger-android!91
mentioned in merge request !83