Nick nick22985
| const { APIMessage, Structures } = require("discord.js"); | |
| class ExtAPIMessage extends APIMessage { | |
| resolveData() { | |
| if (this.data) return this; | |
| super.resolveData(); | |
| const allowedMentions = this.options.allowedMentions || this.target.client.options.allowedMentions || {}; | |
| if (allowedMentions.repliedUser !== undefined) { | |
| if (this.data.allowed_mentions === undefined) this.data.allowed_mentions = {}; | |
| Object.assign(this.data.allowed_mentions, { replied_user: allowedMentions.repliedUser }); |
This guide provides instructions for an Arch Linux installation featuring full-disk encryption via LVM on LUKS and an encrypted boot partition (GRUB) for UEFI systems.
Following the main installation are further instructions to harden against Evil Maid attacks via UEFI Secure Boot custom key enrollment and self-signed kernel and bootloader.
You will find most of this information pulled from the Arch Wiki and other resources linked thereof.
Note: The system was installed on an NVMe SSD, substitute /dev/nvme0nX with /dev/sdX or your device as needed.
Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.
And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.
If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.