~emersion/soju#72: message-ids support — sourcehut todo

~emersion/soju#72:

message-ids support

See https://ircv3.net/specs/extensions/message-ids

Not yet clear what the best way to do it is.

Stateful IDs, with an entry per message in the database?
Stateless IDs, which directly reference the message location in the logs (e.g. filename + byte offset)

How should we handle message-ids coming from upstream servers?

Status: REPORTED
Submitter: ~emersion
Assigned to: No-one
Submitted: 10 months ago
Updated: 8 months ago
Labels: enhancement

~emersion referenced this from #12 10 months ago

~emersion added enhancement 10 months ago

~emersion 8 months ago

I believe we need upstream support before downstream support, and we need to keep original message IDs.

Register here or Log in to comment, or comment via email.