Skip to content

Communication protocols that can be built on hinter-core #18

@bbenligiray

Description

@bbenligiray

It would be really simple to implement a rudimentary DM feature to the helper and I can imagine that being very handy for use cases where peers don't have a traditional DM channel (which we didn't come to experience yet) or that has become unavailable for some reason:

When Alice wants to chat with Bob, she can find the messages from Bob in peers/bob/incoming/.chat and she can find her messages to Bob in peers/bob/outgoing/.chat. However, she doesn't view or edit these files manually. Instead, she uses the helper, which parses them (possibly only the last N lines using tail) and interleaves them according to their UTC timestamps to display the correct order of messages, and she uses the helper to append a new message to peers/bob/outgoing/.chat as a new line in JSON Lines format.

This file-based design is intended to easily support alternative clients and AI integration. The base helper functionality should be fairly limited in comparison.

As a note, the peers/*/outgoing/.chat directories will not have an equivalent under entries/ (like regular report drafts) so the helper should not modify (i.e. delete) peers/*/outgoing/.chat while syncing reports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions