Pin messages in the chat group, also known as message pin has been updated on the phone Viber before, but now computer users have the opportunity to experience this interesting feature. Help team members quickly read important messages, without having to spend time searching.
Just update to Viber 7.9.5.8, then follow the steps below to pin messages to the top of the conversation easily:
Step 1: Open the group chat, right-click the message you want to pin, select Pin . Any member of the group can pin a message, not just the Admin.
Step 2: Immediately a message box will appear asking if you want to pin this message to the top of the chat group? If yes, select Pin .
Step 3: Now you will see the message has been pinned to the top of the conversation already, any group member can view this message easily.
Step 4: When you want to unpin a message, just click the X icon next to the pinned message, then click OK in the Confirm Pin confirmation dialog box, the message will disappear.
Step 5: After removing the pin, a message will appear in the chat interface.
Step 1: When you want to pin a new message, click the i icon in the upper right corner of the group chat interface, select Pin New Messenger.
Step 2: The Pin New Messenger dialog box appears, enter the message content you want to pin to the top of the conversation, and then press Pin.
Step 3: When the Pin this messenger dialog box ? appears, simply click on the Pin to confirm.
Step 4: So that new message will pin to the top of the conversation, so that all members see easier.
Pin message feature useful when group chat too crowded members, discuss many issues at once, making important messages easily lost. So why hesitate any longer to experience this feature only!
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.
