EventExpirationDialogDeletes your events in this room if there are more than X newer messages unless otherwise protected. Set to 0 to disable. ../qml/dialogs/EventExpirationDialog.qml:9594 | ||
EventExpirationDialogAlways keep latest X events ../qml/dialogs/EventExpirationDialog.qml:9615 | ||
EventExpirationDialogThis prevents events to be deleted by the above 2 settings if they are the latest X messages from you in the room. ../qml/dialogs/EventExpirationDialog.qml:9616 | ||
EventExpirationDialogIf this is turned on, old state events also get redacted. The latest state event of any type+key combination is excluded from redaction to not remove the room name and similar state by accident. ../qml/dialogs/EventExpirationDialog.qml:9638 | ||
FailedThe verification was accepted by a different device. ../qml/device-verification/Failed.qml:9731 | ||
FallbackAuthDialogFallback authentication ../qml/dialogs/FallbackAuthDialog.qml:9776 | ||
FallbackAuthDialogOpen the fallback, follow the steps, and confirm after completing them. ../qml/dialogs/FallbackAuthDialog.qml:9791 | ||
FallbackAuthDialogOpen Fallback in Browser ../qml/dialogs/FallbackAuthDialog.qml:9799 | ||
IgnoredUsersIgnoring a user hides their messages (they can still see yours!). ../qml/dialogs/IgnoredUsers.qml:10390 | ||
ImagePackDeleteDialogAre you sure you wish to delete the sticker pack '%1'? ../qml/dialogs/ImagePackDeleteDialog.qml:10435 | ||
ImagePackSettingsDialogPack from parent community ../qml/dialogs/ImagePackSettingsDialog.qml:10853 | ||
LoginPageYou have entered an invalid Matrix ID e.g. @user:yourserver.example.com ../../src/LoginPage.cpp:12797 • ../../src/LoginPage.cpp:12803 • ../../src/LoginPage.cpp:12867 • ../../src/LoginPage.cpp:12999 | ||
LoginPageThe selected server does not support a version of the Matrix protocol, that this client understands (%1 to %2). You can't sign in. ../../src/LoginPage.cpp:12910 | ||
LoginPageYour login name. A mxid should start with @ followed by the user ID. After the user ID you need to include your server name after a :. You can also put your homeserver address there if your server doesn't support .well-known lookup. Example: @user:yourserver.example.com If Nheko fails to discover your homeserver, it will show you a field to enter the server manually. ../qml/pages/LoginPage.qml:13123 | ||
LoginPageA name for this device which will be shown to others when verifying your devices. If nothing is provided, a default is used. ../qml/pages/LoginPage.qml:13183 | ||
LoginPageyourserver.example.com:8787 ../qml/pages/LoginPage.qml:13194 | ||
LoginPageThe address that can be used to contact your homeserver's client API. Example: https://yourserver.example.com:8787 ../qml/pages/LoginPage.qml:13197 | ||
MessageInputWarningDon't mention them in this message ../qml/MessageInputWarning.qml:13693 | ||
NewVerificationRequestTo allow other users to see which of your devices actually belong to you, you can verify them. This also allows key backup to work automatically. Verify an unverified device now? (Please make sure you have one of those devices available.) ../qml/device-verification/NewVerificationRequest.qml:14322 | ||
NewVerificationRequestTo allow other users to see which of your devices actually belong to you, you can verify them. This also allows key backup to work automatically. Verify %1 now? ../qml/device-verification/NewVerificationRequest.qml:14324 | ||