Skip to content

Enhance Authentication, Homeserver, and PKARR Architecture docs#49

Open
gcomte wants to merge 5 commits intomainfrom
docs/enhance-existing-pages
Open

Enhance Authentication, Homeserver, and PKARR Architecture docs#49
gcomte wants to merge 5 commits intomainfrom
docs/enhance-existing-pages

Conversation

@gcomte
Copy link
Contributor

@gcomte gcomte commented Feb 16, 2026

Expand existing pages with richer content: Authentication (participants, relay security, session rework), Homeserver (architecture, event stream details, transport security, running instructions), PKARR Architecture (SignedPacket format, DNS record types, caching, failure modes).


## Data Retrieval and Synchronization
- `GET /events/` — Paginated event feed (cursor-based, 1000 events per batch)
- `GET /events-stream` — Server-Sent Events (SSE) real-time stream
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main difference between these is that /events returns all events on the homeserver for all users. /events-stream allows for a list of users to be specified plus other filters. This is primarily so that nexus can pull events for users from third party homeservers without having to deal with spammy users that they may have.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

obviously SSE is also another difference worth mentioning

Copy link
Contributor Author

@gcomte gcomte Mar 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed it here: 8e5ded7

From a discussion I had somewhere else, it feels to me like the /events endpoint is a bit older and not as thought through as the /events-stream endpoint (which allows for filter for example, like you said). Therefore in this comment I also changed the order to mention /events-stream first and also called the /events endpoint 'legacy'. WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Although ive changed my mind on the "legacy" word since I remembered that it will still be used by Nexus also. Just remove that word and its good


- Homeservers can be operated by individuals, cooperatives, or commercial entities, with the option for anonymous operation, promoting a decentralized and resilient storage ecosystem where users could tune their preferred redundancy while maintaining the benefits of a central Homeserver.
- We do not yet have any mirroring or replication tools available yet. Feel free to build with us!
Pubky hosts use **PubkyTLS** for transport security (TLS with Raw Public Keys, RFC 7250). ICANN hosts use standard X.509 TLS. See [[SecurityModel|Security Model]] for details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think actually that all homeservers expose both, confirm though please

@gcomte gcomte force-pushed the docs/enhance-existing-pages branch from d50d2a9 to dd367d5 Compare February 20, 2026 18:09
@gcomte gcomte force-pushed the docs/enhance-existing-pages branch 2 times, most recently from 0970aed to 0066c38 Compare March 2, 2026 08:26
@gcomte gcomte force-pushed the docs/enhance-existing-pages branch from 0066c38 to 8c42516 Compare March 2, 2026 08:47
@gcomte gcomte force-pushed the docs/enhance-existing-pages branch from 26a5e14 to 8e5ded7 Compare March 2, 2026 09:25
Co-authored-by: tomos <55086152+86667@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants