🌍 Lupyd Rust Server Api
Structure Overview
The Lupyd Rust Server serves as the foundational **Social Graph** API. Unlike Firefly, which protects conversational tunnels, this backend drives your interactions, followers array, and rich-text timelines.
Below is the structured, exact mapping of all internal endpoints directly translated from its Hyper request handler architecture. It relies intensely on Protobuf serialization and JWT token structures.
Posts & Social Feed
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
?type=<u32>&users=<csv>&start=<ULID>&search=<str>&hashtag=<str>
Request Body
Returns
Arguments (Query)
ULID strictly in Path URL
Request Body
Returns
Arguments (Query)
UUIDs strictly in Path URL
Request Body
Returns
User Profiles & Social Graph
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
?users=<username1%2Cusername2>&offset=<u32>
Request Body
Returns
Arguments (Query)
?uname=<string>&relation=<Follow|Block>
Request Body
Returns
Arguments (Query)
?start_after=<ULID>
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Interactions & Engagement
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
?id=<ULID>
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Chat Connectivity Bridges
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Arguments (Query)
None
Request Body
Returns
Real-time Notifications
Arguments (Query)
None
Request Body
Returns
Authorization Matrix
The entire backend handles access via the AuthenticatedToken struct. Certain routes like `/vote` or `/user` perform hard checks for permissions dynamically decoded from JWT arrays, avoiding latency checks entirely from the connected Auth0 pool.