| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
description after an update
|
|
|
|
frequency/member/ban/signal lists
|
|
tearing issue in fast terminals such as ghostty
|
|
have an issue (effects all popups and anything else that uses them),
seems to be an issue in charm
|
|
|
|
|
|
|
|
|
|
|
|
|
|
make things not static so they color changes)
|
|
empty, it wouldn't show the empty chat message
|
|
strings instead of the frequency strings
|
|
on start to avoid "insta-reading" messages of the top isgnal)
|
|
|
|
|
|
on start, then managed by the client and stored once on client exit
|
|
the signal already open, it will be added as the first signal
|
|
"signal" and it's variants as this is the new terminology for "user
signals" which are direct messages between 2 users
|
|
|
|
so the client can use it to persist notifications
|
|
|
|
|
|
end of the line and that line is the last line, it wouldn't delete
anything
|
|
|
|
|
|
got to the top message but then more messages have been added
|
|
new messages in the frequency/receiver
|
|
|
|
|
|
|
|
|
|
components have updated instead of before so the view will reflect the
update in case any of the updates change the notifications
|
|
and sends the info to the client when it connects
|
|
they separate
|
|
|
