VojVoj

VojVoj er et verdidrevet sosialt nettverk som tar utgangspunkt i dine interesser og det du får verdi fra. Oppdag relevant innhold, finn mennesker med felles interesser og bygg verdifulle forbindelser.

VojVoj is a value-driven social network shaped by your interests and what brings you value. Discover relevant content, connect with people who share your interests, and build meaningful relationships.

Vi bygger VojVoj for å skape verdi og verdifulle koblinger mellom mennesker.

We are building VojVoj to create value and valuable connections between people.

Åpne appen Logg inn

Versjon 1.5.103 · beta-kanal · bygg 45fc5e8 · /version · /v1/version

Dette er bygget, og dette er ikke

Retningen over er produktets retning. Det som står under er hva denne deployen faktisk gjør i dag — og hva den ikke gjør ennå.

Ikke bygget ennå

Komme i gang

VojVoj kjenner folk etter det identitetsleverandøren din bekrefter, og ingenting annet. Det finnes ikke noe passord her, og ingenting å huske. Innloggingen skjer hos leverandøren, og det er det eneste stedet et passord skrives.

Kommer du tilbake senere, er /ui en kort, stabil vei til appen — den peker på samtalen, som selv avgjør om du er innlogget.

For utviklere og drift
Status
serving
Build
45fc5e8
Release
1.5.103 beta
Cell
eu-north / cell-1
Uptime
3h

What you can look at

Endpoints that exist and need a token

These are built and running, and they are not broken when a browser reaches them: each refuses a caller without a token, which is the point of them. A visitor with no token gets 401, and one holding a grant that does not reach a route gets 403. A caller holding a token minted for vojvoj-api, with a grant this deployment's policy recognises, is answered rather than refused — measured on the deployment that is answering this request rather than assumed.

What the platform does today

The API, the capability broker and the MCP gateway are running, each on a loopback address of its own. Only the API is exposed: the broker and the gateway hold authority and answer agents and operators directly, so publishing them would publish the authority surface itself rather than a way to use it.
Dependency detail, metrics and every address stay on loopback, where an operator is — /status names a process and whether it answers, never where it lives.
Which parts of this page are live: the version line above, the cards in this section, what is said about authentication, and every figure on /status are read from the running process or from what it can reach, and report unknown rather than guessing when they cannot be read. The rest is prose, and prose is what went stale last time — so it is kept to what the running process can be held to, and the claims that were withdrawn are pinned by a test that fails if one comes back.