This commit configures Hard Lounge as a dedicated webchat client for
SuperNETs IRC, requiring only a nickname to connect.
- Set `public: true` to enable public mode (no user accounts required)
- Set `lockNetwork: true` to lock connections to irc.supernets.org only
Users will automatically connect to irc.supernets.org:6697 (TLS) and
join #superbowl upon entering a nickname.
- Added simplified connect form for public + lockNetwork mode
- Form now shows only the nickname field when both settings are enabled
- Hidden fields: server, port, TLS, username, realname, channels,
leave message, authentication options
- Added CSS styling for proper spacing on simplified form
- Pinned to Node 20 Alpine (from lts-alpine) for compatibility
- Added py3-setuptools to fix distutils module error with Python 3.12
- Fixed file ownership with --chown=node:node on COPY commands
- Moved USER node directive after COPY to fix permission issues
- Pre-create /var/opt/hardlounge directory with correct ownership
The TS rewrite dropped the form that was expected to be passed
as props.
That lead to the password change being borked, as the fields
were always set to "null".
We don't need a form, can just use refs here.
https://github.com/thelounge/thelounge/pull/4649 broke existing
themes by removing the colored-nicks class from chat.
Considering that we don't bump the major version, keep backwards
compatibility for now
Currently, in `ChatInput.vue` we call `upload.abort()` which removes the event listeners, which are never added back. This effectively permanently disable uploads if the user navigates away to Settings or any other non-chat pages, and back.
Moves the binding to `mounted()` so that they're properly rebound when a chat window is in view, and also adds an `unmounted()` for clarity.
This should also fix an edge case if the page opens up on a non-chat page and there was never a ChatInput to unbind it, such as login page or add network pages.
PR #4649 introduced a regression on the Morning theme as the `#chat.colored-nicks` CSS selector was removed from Default but not Morning. The result is that Morning no longer had nick colors.
Prior to this, the search is still racy but one tends to notice
this only when the DB is large or network is involved.
The user can initiate a search, get bored, navigate to another chan
issue a different search.
Now however, the results of the first search come back in and
hilarity ensues as we are now confused with the state.
To avoid this, keep track of the last search done and any result
that comes in that isn't equal to the active query is garbage and
can be dropped.
This means we also apply the collapsing to normal queries,
which might also collapse other things like joins / quits
which may be undesired by some
Fixes: https://github.com/thelounge/thelounge/issues/4583
The only thing that cares about user colors is the user component.
Putting a class value on the chat component seems to be the wrong
place.
This also allows us to remove various css selectors so that we
don't need to be that specific.
After all whatever has that class needs to be colored, we don't
care where it is.
During a search, we get the results from oldest --> newest.
When we hit the more button, we get the results of the second batch
in the same order.
However, logically to the first batch everything is older, so we
need to prepend it to the result array, not
append.
msg DB logical ID
A 3 5
B 2 4
C 1 3
D 3 2
E 2 1
F 1 0
