jesopo
jesopo
If we leave it up to the server to just ignore them in certain circumstances, servers are still going to be hit with a LOT of data in big channels...
can I send `delivered` and `read` (#347) in the same `TAGMSG`? only thing that really makes sense for a bot.
I agree. Added a nice small implementation of this in jesopo/bitbot@6a67c37d that does both `+draft/delivered` & `+draft/read` in one `TAGMSG` on private `PRIVMSG` and `NOTICE`
I still think that we can only support this in-channel if the server tells clients when they should stop sending `delivered` and `read` - not sure this is worth the...
server aggregation gets a :+1: from me but I think that will need a slightly larger conversation than is in-scope for this PR - as I understand it servers mostly...
for what it's worth; this change would have `KeyError`ed BitBot prior to https://github.com/jesopo/bitbot/commit/807e239a2bc5a1e3ac57c0338f560d49edc3de8c
this appears to be quite similiar to https://github.com/solanum-ircd/solanum/pull/13 `solanum.chat/realhost` cap which adds: - `solanum.chat/ip` msg tag which shows either a non-vhost user's IP to everyone or shows vhost user's IP...
I've added two pieces to the gist: - in `rationale`: > additionally, people abuse mechanics for account name changes to avoid extbans (e.g., `+b $a:jess` to ban the account name...
my concern is how we get the IRCd and services to work together to translate account names and IDs back-and-forth. if we have e.g. an extban for "account ID" that...
so are we relatively content with the gist as it currently is?