What Techne adds
Building on distributed, permissioned data usually means handling all of this yourself.
Identity across servers
Each person's account lives on their own PDS, which can be anyone's server. You resolve handles and run OAuth against each one.
Schemas
Records need shapes every app agrees on, and any writer can send anything, so each record has to be checked.
Indexing the firehose
Records are spread across many repos. To query them you follow the network and keep your own index.
Who may read and write
Public records are easy. Private ones need rules for who reads each one, enforced wherever it is served.
Admission and the managing app
A shared space needs someone to decide who is in, and only records from admitted writers count. Spaces and permissions
Merging versions
Many sources describe the same park. Someone has to choose which fields to trust and keep one version.
We've taken care of all of it
Building on Techne is as simple as an ordinary app. Sign in, read, write.
Reads come from every author, already indexed, checked against the lexicon and merged into the curated version. Private records come back only to people the space admits.
Quickstart walks through each step.
Every app makes the data better
Every app adds to the data, and every app gets the benefit.
- Beacon adds an eventSomeone posts a meetup at a cafe.
- Commons enriches itIt links the event to its place and fills in what is missing.
- The SDK reads the curated versionOne record, filled field by field from the sources.
- Every app gets the better dataIncluding yours, with no extra work.