Warning
This tutorial is outdated! I do not recommend using this method anymore, as there are better tools now.
For better alternatives, try out:
Using GitHub with SAML SSO integration often adds some hurdles to command-line authentication.
Warning
This tutorial is outdated! I do not recommend using this method anymore, as there are better tools now.
For better alternatives, try out:
Using GitHub with SAML SSO integration often adds some hurdles to command-line authentication.
Source: Jackett/Jackett#1576 (comment)
From the Jackett page, click the "add indexer" button so that the pop up window with the full list of indexers appears.
You'll then need to open your browser's development toolbar (in Chrome just hit F12) and go to the JavaScript Console and enter the following:
////hack to add all free indexers in Jackett
$(document).ready(function () {
EnableAllUnconfiguredIndexersList();
-----BEGIN PGP SIGNED MESSAGE----- | |
Hash: SHA256 | |
### 密钥库证明 | |
我在此声明: | |
+ 我是 gledos,这里是一个证明凭证。 | |
+ 我有两个公用密钥,不过2018年3月21日生成的密钥我已经丢失且没有妥善设置过期时间,造成了现在遗憾的处境, | |
该没有人拥有的密钥指纹为 [48C5 BDC6 AEF2 F5A0 F791 B10B 8986 D7B4 D939 CCED](https://pgp.mit.edu/pks/lookup?op=get&search=0x48C5BDC6AEF2F5A0F791B10B8986D7B4D939CCED) |
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill
) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
[global] | |
font = Iosevka Term 11 | |
# Allow a small subset of html markup: | |
# <b>bold</b> | |
# <i>italic</i> | |
# <s>strikethrough</s> | |
# <u>underline</u> | |
# | |
# For a complete reference see |
Locking down a linux machine is getting easier by the day. Recent advancements in systemd-boot have enabled a host of features to help users ensure that their machines have not been tampered with. This guide provides a walkthrough of how to turn on many of these features during installation, as well as reasoning for why certain features help improve security.
The steps laid out below draw on a wide variety of existing resources, and in places I'll point to them rather than attempt to regurgitate full explanations of the various security components. The most significant one, which I highly encourage everyone to read, is Rod Smith's site about secure boot, which is the most comprehensive and cogent explanation of UEFI, boot managers and boot loaders, and secure boot. Another incredibly useful resources is Safeboot, which encapsulates many of the setup steps below in a Debian application.
iperf3
serverwg-quick down wg0
/etc/wireguard/wg0.conf
fileI got problems installing Matlab R2022a on Arch. Running the installer throws the following error: | |
``` | |
terminate called after throwing an instance of 'std::runtime_error' | |
what(): Failed to launch web window with error: Unable to launch the MATLABWindow application. The exit code was: 127 | |
fish: Job 1, 'sudo ./install' terminated by signal SIGABRT (Abort) | |
``` | |
I fixed it by running the following commands. |