Private Sign-in and Telegram Bots

The sign-in page no longer shows who has an account on your server, and every Apps Hub profile can now have its own Telegram bots. This release also lets a domain open only Apps Hub or a single public app. mvmOS 1.20.0 Anyone who opened the address of an installation used to see the list of Linux accounts on the sign-in page. Now a new browser sees only a username and a password field. • Tick "Remember this user" (it is on by default) and this browser keeps the users that signed in from it and offers them next time. Untick it and that user is forgotten in this browser. • A wrong username and a wrong password get the same answer. • The page has a larger mvmOS logo and a cleaner look, and it follows the browser language in all nine mvmOS languages. • A domain can be set to open the whole installation, only Apps Hub or one public app. On the last two, every other address answers Not Found, and on a single-app domain there is no switcher to other apps and the other apps cannot be opened. • Modules can listen to every notification that is stored, which Telegram Hub uses. Telegram Hub 1.2.0 Every Apps Hub profile connects Telegram bots of its own. • An Apps Hub bot opens Apps Hub as a Telegram Mini App and delivers the notifications of all your apps, with a list to switch off the apps you do not want to hear from. • An app bot opens only one app and brings only its notifications. • A custom menu bot gives you a menu of buttons you build yourself. • Apps need no Telegram code. Telegram Hub listens to the shared notification system and requires mvmOS 1.20.0. Budget 1.6.6, Calendar 1.3.4, Chat 1.4.3, Shopping List 1.3.4, qBit Dashboard 1.8.2 These apps drop their own Telegram pages and adapters. Their notifications reach your bots through Telegram Hub.