Deleting a circle is highly destructive. It removes the group chat
alongside history, as well as the user list. It should definitely be
protected by a confirmation dialogue, I have no clue why it wasn't.
Fixes#153.
Prosody changed its role scheme to only support a single primary role
for each user. In addition, the names of the built-in roles have been
changed. We thus follow those changes to be compatible with the most
recent trunk.
One open question is whether we should switch admin -> operator here,
too (operator being a server-wide admin), but so far there's no need
to.
At the same time, we can also drop the CSS used for that makeshift tab
box. I always felt a bit uneasy about it, a11y-wise, so it's good
riddance.
Fixes#99.
This allows user agents to do smart things like filling in the current
password only where it makes sense or integrate nicely with a password
manager.
Fixes#94.
Dependency versions are generally not useful, unless you are developing
or otherwise outside of a normal release situation: If you are on a
normal release, we can figure out the dep versions by looking at the
docker image.
To reduce the amount of information displayed and the amount of
information which needs to be conveyed in case of problems, we only show
the web portal and prosody versions to admins, unless debug mode is
enabled.
The behaviour that versions are only shown to logged in admins (unless
debug mode is enabled) remains unchanged.
Fixes#115.
Someone who registers via the web might also be interested in the web
portal.
Thanks to Jonas and Matthew for feedback on draft commit and help with
whatever this template syntax is.
Also no thanks to git for not actually having draft commits as a concept.
Mercurial is so much nicer to work with.
The button was broken because it was classified as popover, which
means that the JavaScript code will mess with it. In reality,
*that* button was supposed to point at the actual market:// URL.
So we just remove the class and associated data here to fix that.
Fixes#89.
This helps with removing those users from circles, to avoid them
popping up in peoples roster again.
Even though removal from a circle also only partially works
(roster entries are for instance not cleared), this helps with
ghost users reappearing all the time.
This is useful in situations where the admins of the Snikket
server (i.e. those who care for the docker containers) are not the
same people as the people who are admins of the Snikket service
(i.e. those who care for the users).
This aggregates the user actions behind a single "edit" button on
the list view, making it less crammed. It also offers the
functionality of actually editing the user, mind.
Also in preparation for #42.
Requires https://hg.prosody.im/prosody-modules/rev/5bc706c2db8f.
This checks the avatar size on the client side (if available) and
on the server side against a configuration-defined limit. The
default limit is set to use the same value as in the original
report, as no sensible limit value is known.
Fixes#67.
This allows future App versions to also work with the invite page
without having to screen scrape the content.
Fixes#56 (at least for the portal side of things).
Tester feedback has shown that desktop client users will also
click that button because they are, in fact, not on mobile.
This button speaks more to the users intent (sending the
invitation to the mobile device) after having (hopefully) read
the text above.
Fixes#38.
