Would be neat if 005 announced a BACKLOG command, to dynamically fetch more backlog (instead of getting the whole backlog all at once).
I have no idea how such a BACKLOG command would work, but I think it'd at least take a nick/channel argument, a line count, and maybe require server-time or message-ids to be enabled and stuff (otherwise the server would have to keep track of how much backlog the user has requested, which wouldn't be the end of the world but eh, sounds painful).
Backlogs wouldn't be automatically fetched when a client connects - clients would have to explicitly request them. This would save bandwidth.
(Why not post this on IRCv3? Well because I'm banned from IRCv3. And this isn't very useful for your standard IRCd, it's more useful for bouncers.)
Would be neat if 005 announced a BACKLOG command, to dynamically fetch more backlog (instead of getting the whole backlog all at once).
I have no idea how such a BACKLOG command would work, but I think it'd at least take a nick/channel argument, a line count, and maybe require server-time or message-ids to be enabled and stuff (otherwise the server would have to keep track of how much backlog the user has requested, which wouldn't be the end of the world but eh, sounds painful).
Backlogs wouldn't be automatically fetched when a client connects - clients would have to explicitly request them. This would save bandwidth.
(Why not post this on IRCv3? Well because I'm banned from IRCv3. And this isn't very useful for your standard IRCd, it's more useful for bouncers.)
<!-- github-sync-id:203824085 -->
Keep posting nonsense here, and you'll be banned here as well.
This doesn't belong here. It's not a ZNC issue.
Also, this is duplicate of https://github.com/ircv3/ircv3-specifications/pull/292
> Well because I'm banned from IRCv3
Keep posting nonsense here, and you'll be banned here as well.
<!-- github-comment-id:275878926 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Would be neat if 005 announced a BACKLOG command, to dynamically fetch more backlog (instead of getting the whole backlog all at once).
I have no idea how such a BACKLOG command would work, but I think it'd at least take a nick/channel argument, a line count, and maybe require server-time or message-ids to be enabled and stuff (otherwise the server would have to keep track of how much backlog the user has requested, which wouldn't be the end of the world but eh, sounds painful).
Backlogs wouldn't be automatically fetched when a client connects - clients would have to explicitly request them. This would save bandwidth.
(Why not post this on IRCv3? Well because I'm banned from IRCv3. And this isn't very useful for your standard IRCd, it's more useful for bouncers.)
This doesn't belong here. It's not a ZNC issue.
Also, this is duplicate of https://github.com/ircv3/ircv3-specifications/pull/292
Keep posting nonsense here, and you'll be banned here as well.
Neat. Would be very useful for my IRC-based twitter client. Can you fast-track it?