| @media -moz-pref('browser.nova.enabled') { | |
| :root { | |
| --chrome-window-gap: 0px !important; | |
| --chrome-block-radius: 0px !important; | |
| --chrome-content-separator-color: unset !important; | |
| } | |
| .tab-background { | |
| border-radius: 8px !important; | |
| } |
| /* Iconic Firefox (https://gist.github.com/emvaized/a379d61ed8970e5711ca7278a39c1895/) */ | |
| /* Author (c) 2025 emvaized */ | |
| /* Based on https://gist.github.com/qaz69wsx/83a90423163b65a8344b2e60fc356a58 (no longer available) */ | |
| /* For better compatibility with dark mode, enable `svg.context-properties.content.enabled` in `about:config` */ | |
| /* General styles */ | |
| :root{ | |
| --uc-popup-menu-icon-color: color-mix(in srgb, currentColor 75%, transparent); | |
| } | |
| .subviewbutton:not(.subviewbutton-iconic, [checked="true"], [targetURI])>.toolbarbutton-icon, |
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
| # /etc/ssh/ssh_config | |
| # | |
| # All my hosts are reachable by IPv6 only. IPv6 addresses don't get spammed with SSH login probes. | |
| # But what if I need to connect from a network which has no IPv6 enabled? | |
| # Setup an SSH jump host which is reachable over IPv4 and use that only if the target host is unreachable by IPv6 | |
| # | |
| Match host *.example.net,!ipv4.example.net !exec "ip route get $(host %h | grep 'IPv6 address' | awk '{print $NF}') &> /dev/null" | |
| ProxyJump ipv4.example.net |
| @(set "0=%~f0" '& set 1=%*) & powershell -nop -c "type -lit $env:0 | out-string | powershell -nop -c -" & exit /b ');.{ | |
| " Steam_min : always restarts in SmallMode with reduced ram and cpu usage when idle - AveYo, 2025.08.23 " | |
| $FriendsSignIn = 0 | |
| $FriendsAnimed = 0 | |
| $ShowGameIcons = 0 | |
| $NoJoystick = 1 | |
| $NoShaders = 1 | |
| $NoGPU = 1 |
Important
Working on the latest supported Windows versions. Run Windows Update before following this guide.
1. Open Powershell > RUN AS ADMIN
2. Paste in irm https://gist.github.com/ave9858/c3451d9f452389ac7607c99d45edecc6/raw/UninstallEdge.ps1 | iex and press enter
3. Microsoft Edge will be completely uninstalled.
On Dual Display setup, I found it frustrating that the cursor is not bounded to sides of the display anymore. For example reaching the "close window" button needs precise muscle control whereas before you could simply crash again the top & right screen border and smash that window.
So I keep both display separated and created an AutoHotKey script to shift the cursor from my first to my second display on a press of a button.
| -- Forked from https://gist.github.com/garoto/e0eb539b210ee077c980e01fb2daef4a. | |
| -- Only tested on Windows. Date is set to dd/mmm/yyyy and time to machine-wide format. | |
| -- Save as "excessive-history.lua" in your mpv scripts dir. Log will be saved to same folder as mpv.conf. | |
| -- Make sure to leave a comment if you make any improvements/changes to the script! | |
| -- Not much testing has been done. | |
| -- *Changes made from original* | |
| -- logs only path, no title | |
| -- logs to where mpv.conf is |
| -- autosave.lua | |
| -- | |
| -- Periodically saves "watch later" data during playback, rather than only saving on quit. | |
| -- This lets you easily recover your position in the case of an ungraceful shutdown of mpv (crash, power failure, etc.). | |
| -- | |
| -- You can configure the save period by creating a "lua-settings" directory inside your mpv configuration directory. | |
| -- Inside the "lua-settings" directory, create a file named "autosave.conf". | |
| -- The save period can be set like so: | |
| -- | |
| -- save_period=60 |
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
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 e
