Chatterino2: Mod option to highlight new accounts messages

Created on 5 Jul 2020  路  3Comments  路  Source: Chatterino/chatterino2

What should be added?
A mod option so new accounts messages get highlited.

Why should it be added?
for mods in trainwrecks chat EleGiggle

enhancement

Most helpful comment

The way I could see this work as a Chatterino solution is:
Each Chatterino client would cache each unique user they've seen, and if it's the first time they've seen the user they would poll the Twitch API for information about the user (e.g. the account age) and store that to be able to do operations like this on the user.

The "reasonable" way to do this is either:
a) Middleware cache users in chatterino/api
or
b) limit requests, and only run requests every 5 seconds if there are users. and ensure we bulk users as well as possible.

USER STARTS CLIENT (assuming 2 users per request is max)

 00:00 -> gempir: xd
 00:01 -> gempir: lol123
 00:01 -> pajlada: hello
 00:02 -> zneix: xd
 00:05 -- REQUEST gempir, pajlada TWITCH ACCOUNT AGE
 00:06 -> gempir (2y): hello
 00:06 -> pajlada (2y): hello
 00:07 -> zneix: xd
 00:08 -> newuserxd: hello
 00:10 -- REQUEST zneix, newuserxd TWITCH ACCOUNT AGE
 00:12 -> gempir (2y): hello
 00:12 -> pajlada (2y): hello
 00:13 -> zneix: (1y) xd
 00:14 -> newuserxd (1d): hello

This is, however, a lot of work both to write and for each client to do when the feature is implemented for a very small use case, so take my theorizing with a big heap of salt.

All 3 comments

The way I could see this work as a Chatterino solution is:
Each Chatterino client would cache each unique user they've seen, and if it's the first time they've seen the user they would poll the Twitch API for information about the user (e.g. the account age) and store that to be able to do operations like this on the user.

The "reasonable" way to do this is either:
a) Middleware cache users in chatterino/api
or
b) limit requests, and only run requests every 5 seconds if there are users. and ensure we bulk users as well as possible.

USER STARTS CLIENT (assuming 2 users per request is max)

 00:00 -> gempir: xd
 00:01 -> gempir: lol123
 00:01 -> pajlada: hello
 00:02 -> zneix: xd
 00:05 -- REQUEST gempir, pajlada TWITCH ACCOUNT AGE
 00:06 -> gempir (2y): hello
 00:06 -> pajlada (2y): hello
 00:07 -> zneix: xd
 00:08 -> newuserxd: hello
 00:10 -- REQUEST zneix, newuserxd TWITCH ACCOUNT AGE
 00:12 -> gempir (2y): hello
 00:12 -> pajlada (2y): hello
 00:13 -> zneix: (1y) xd
 00:14 -> newuserxd (1d): hello

This is, however, a lot of work both to write and for each client to do when the feature is implemented for a very small use case, so take my theorizing with a big heap of salt.

Extending chatterino/api to cache some user info, like timestamp of account creation sounds like an excellent idea to me. Might even contain more stuff if we'd plan to cache more user data in the future.

I don't think that a system like this is feasible.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mattbuford picture mattbuford  路  3Comments

nitrousGranola picture nitrousGranola  路  3Comments

TETYYS picture TETYYS  路  3Comments

TranRed picture TranRed  路  3Comments

DatGuy1 picture DatGuy1  路  3Comments