| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | arti-client: 0.47 -> 0.48HEADmaster | tv | 8 hours | 1 | -5/+5 |
| | | |||||
| * | api: a stream opened with a token ends with it | tv | 37 hours | 1 | -3/+3 |
| | | | | | | | | | | | | | | | | | | | | | A token was checked when a request came, and a stream answered to it (the dashboard's events, a subscription's links and messages, the store's streams) then went on for as long as the client kept it open: past the token's expiry, past its user's tokens being revoked, its user disabled or removed, its session ended. Now a middleware inside `login::bearer` (`login::streams_end`) ends a streaming answer (`text/event-stream`, `application/x-ndjson`) to a request with a token at the token's deadline, its expiry, or as soon as the document no longer takes it (`token::still_taken`, the checks `verify` makes of the document, now its own function): looked at when a change touches protocol data (the root, a switch, among it), and when a session ends on the node itself in a swarm without a registry (`AppState::session_ended`). No polling: a timer for the expiry, and the changes as they come. The client reconnects with the token it has then; a refreshed token is a new one, so a stream lasts a token's lifetime at most (12 hours by default). `futures` is a dependency of every build now (for `take_until`), not only of libp2p's and Tor's. | ||||
| * | measure deflated chunks | tv | 6 days | 1 | -0/+2 |
| | | |||||
| * | api: add application/vnd.continuum.* scalar types | tv | 9 days | 1 | -0/+2 |
| | | |||||
| * | config: use individual transport enable flags | tv | 10 days | 1 | -4/+4 |
| | | |||||
| * | add links messages | tv | 11 days | 1 | -0/+2 |
| | | | | | | | | | | Introduce two new wire messages, LINKS and LINKS_REPLY (swarm::links). A member answers with its links: for each peer, the transport, whether it’s relayed, the RTT, and whether it’s dormant. It answers members only, at most every 5 s. This bumps wire::VERSION to 7. Every build answers, with or without the feature, so every node needs this patch before the map shows anything beyond its own node. | ||||
| * | use rustls with ring for reqwest | tv | 11 days | 1 | -2/+5 |
| | | |||||
| * | make mycelium optional | tv | 11 days | 1 | -2/+7 |
| | | |||||
| * | libp2p: add UPnP support | tv | 13 days | 1 | -1/+1 |
| | | |||||
| * | libp2p: keep fastest connection | tv | 13 days | 1 | -1/+1 |
| | | |||||
| * | bump libp2p & libp2p-stream | tv | 13 days | 1 | -2/+2 |
| | | |||||
| * | add dev profile and quick/sim aliases | tv | 13 days | 1 | -0/+10 |
| | | |||||
| * | add tor transport | tv | 14 days | 1 | -1/+17 |
| | | |||||
| * | add challenge handshake | tv | 14 days | 1 | -0/+2 |
| | | |||||
| * | add support for public libp2p infrastructure | tv | 2026-10-27 | 1 | -1/+1 |
| | | |||||
| * | use libp2p mDNS | tv | 2026-10-27 | 1 | -1/+1 |
| | | |||||
| * | register relays in member list & use AutoNAT | tv | 2026-10-27 | 1 | -1/+1 |
| | | |||||
| * | add libp2p relay support | tv | 2026-10-27 | 1 | -1/+1 |
| | | |||||
| * | use libp2p identify protocol & announce alt addrs | tv | 2026-10-27 | 1 | -1/+1 |
| | | |||||
| * | add libp2p transport | tv | 2026-10-27 | 1 | -1/+4 |
| | | |||||
| * | add transports option | tv | 2026-10-27 | 1 | -0/+2 |
| | | |||||
| * | introduce node keys | tv | 2026-10-27 | 1 | -0/+1 |
| | | |||||
| * | replace utoipa by static openapi.yaml | tv | 2026-10-26 | 1 | -1/+0 |
| | | |||||
| * | cleanup Cargo.toml (fixup) | tv | 2026-10-24 | 1 | -6/+1 |
| | | |||||
| * | add configuration files | tv | 2026-10-24 | 1 | -0/+1 |
| | | |||||
| * | cleanup Cargo.toml | tv | 2026-10-24 | 1 | -2/+2 |
| | | |||||
| * | add tokio-console feature (fixup) | tv | 2026-10-24 | 1 | -1/+4 |
| | | |||||
| * | edition = "2024" (fixup) | tv | 2026-10-24 | 1 | -1/+1 |
| | | |||||
| * | add Cargo.toml | tv | 2026-10-19 | 1 | -0/+40 |
