The new Viber allows users to pin important messages so team members can read them right away, without having to search manually. However, you must be an administrator of the group to pin the conversation to the top.
The pinning feature in chat group supports both Android and iOS platforms. You only need to update to the latest version, then follow the steps below to pin messages to the top of the conversation easily:
Step 1: Open up a Viber group conversation, press and hold on the message that needs to be highlighted, and then select Pin in the list of options. When the message Pin confirmation dialog appears, select Pin to agree. The message will then be pinned to the top of the conversation.
Step 2: When you want to remove a pinned message in group conversation, just click the X icon next to the pinned message in the top corner of the conversation. When the Delete Pin dialog box appears , click OK to unpin the message. So the message will no longer appear at the beginning of the conversation.
Step 3: You can also pin the conversation to the top to open it quickly when needed. Just hold down the group you want to pin to the top, select Pin to top or tap the name of the chat group you want to pin, then select Pin to top . When you return to the Viber chat list, you will see this group chat appear at the top, with a pin icon. When you want to unpin chat group just do the same, then select Unpin this chat and you 're done.
So you know how to pin important messages and pin conversations to the top. However, this feature can only be used in group chats. The latest Viber also allows Reply messages in group chat extremely convenient.
I wish you successful implementation!
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
