Zhymabek Roman ZhymabekRoman

Chat GPT "DAN" (and other "Jailbreaks")

Think twice before abandoning X11. Wayland breaks everything!

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.

Feature comparison

Creating an AUR Package

Maintainer: Keil Miller Jr

How to create and manage an AUR package.

The following link should be read:

Русская шпаргалка по Smali

Приветствую, любители реверс-инжинирить Android. Перед вами шпаргалка по Smali - аналогу ассемблера для Android-приложений.

Изначальный текст на русском взят отсюда. Там текст появился из машинного перевода официальной документации.

В итоге, оформил сухой текст + поправил небольшие опечатки и корявости перевода. По поводу замечаний и предложений можете писать либо мне в ЛС, либо оформлять PR на Gist.

	Begin by enclosing all thoughts within <thinking> tags, exploring multiple angles and approaches.
	Break down the solution into clear steps within <step> tags. Start with a 20-step budget, requesting more for complex problems if needed.
	Use <count> tags after each step to show the remaining budget. Stop when reaching 0.
	Continuously adjust your reasoning based on intermediate results and reflections, adapting your strategy as you progress.
	Regularly evaluate progress using <reflection> tags. Be critical and honest about your reasoning process.
	Assign a quality score between 0.0 and 1.0 using <reward> tags after each reflection. Use this to guide your approach:

	0.8+: Continue current approach
	0.5-0.7: Consider minor adjustments
	Below 0.5: Seriously consider backtracking and trying a different approach

	#!/bin/bash
	# completely disable/uninstall snap on ubuntu 24.04 (ubuntu noble numbat) and install firefox from .deb only

	sudo snap remove --purge firefox
	sudo snap remove --purge snap-store
	sudo snap remove --purge gnome-42-2204
	sudo snap remove --purge gtk-common-themes
	sudo snap remove --purge snapd-desktop-integration
	sudo snap remove --purge bare
	sudo snap remove --purge firmware-updater

	# Optimized picom.conf configuration (tested on an NVIDIA card)
	# Gits URL: https://gist.github.com/jamescherti/59f61eeaf17ccc16e1eab2c98d699d31
	# License: MIT
	# Maintainer of this picom.conf: James Cherti

	#################################
	# Shadows #
	#################################

	# Enabled client-side shadows on windows. Note desktop windows

	// ==UserScript==
	// @name Medium Paywall Bypass
	// @namespace Violentmonkey Scripts
	// @run-at document-start
	// @match ://.medium.com/*
	// @match ://medium.com/
	// @match :///*
	// @grant none
	// @version 2.4
	// @inject-into content

	// ==UserScript==
	// @name Spotify Ad Muter
	// @version 1.2
	// @namespace http://tampermonkey.net/
	// @description Detects and blocks ads on Spotify. Automatically mute Spotify ads. Turn sound on again after the ad.
	// @match https://.spotify.com/
	// @grant none
	// @run-at document-start
	// @downloadURL https://gist.github.com/marcbelmont/1ea63270867a4e8786dd5f172d8d4489/raw
	// @updateURL https://gist.github.com/marcbelmont/1ea63270867a4e8786dd5f172d8d4489/raw