Red panic button

We’ve shown you how to hack your Wii for homebrew software, emulators, and DVD playback , now it’s time to safeguard your Wii against bricking and fix some annoyances—like that stupid “Press A” health screen.

The thing about console modding and jailbreaking—save for the rare company like Amazon that doesn’t seem to care —is companies will play a game of cat and mouse to try and knock modded console out of commission, undo your awesome mods, or even brick your device. Although extreme moves like bricktacular-updates are rare once you modify your device you have to be vigilant in protecting it against updates that could hurt your sweet setup. Today we’re going to walk you through hardening your Wii and giving it the best brick protection available.

What You’ll Need

For this tutorial you will need the following things:

• A Wii with a softmod and The Homebrew Channel installed .
• A Wiimote and a GameCube Controller .
• An SD card at least 1GB in size .
• The zip file of hacks and tools. [Mirror 1] [Mirror 2] **Caution: These three links are currently unavailable**Updated 2/20/16

If you already softmodded your Wii you should have all these things on hand already, including an SD card in the Wii with the Homebrew Channel and accompanying /apps/ folder in place. Download the zip file above and extract it to the root of your SD card. The files will automatically extract to the correct directories.

Backing Up Your NAND

Don’t panic, we won’t be opening up your Wii with a screwdriver. The photo above is just to give you a tangible view of what we’re doing when we back up the NAND. Deep in the swirly whirly forest of capacitors, chips, and traces seen in the photo above are various flash memory modules (NANDs) that contain critical software. When we back up the NAND we are copy the contents of these important chips and securing a copy we can use to restore the machine later should anything bad happen.

To backup the Wii NAND we’ll be using the BootMii application. If you do not already have the BootMii application installed you need to repeat the steps in our softmod guide (or whatever softmod tutorial you used) in order to call up the HackMii installer once again.

When you go to install BootMii you have two options. You can install BootMii as Boot2 or an IOS. If your Wii will allow you to, installing it at Boot2 is ideal as it gives BootMii a deeper control over the Wii which makes recovery easier in the event of a brick. Wii units manufactured before 2008 should have no problem installing BootMii in the Boot2 slot, newer Wii units may be forced to install as an IOS. Don’t be discouraged if you have to install as an IOS, we’ll still be able to backup and restore your Wii.

Once the installation is complete, return to the main menu of the HackMii and restart your Wii. If you were lucky enough to have a Wii which allowed for Boot2 installation you can simply reboot your Wii at this point—from now on whenever you boot your Wii you’ll be presented with the BootMii menu.

If you don’t want that to happen (if you have kids or roommates for example you don’t want messing around with a powerful tool like BootMii) you can, once you’re done with this tutorial, rename the /BootMii/ folder on the root of your SD card to something like /BootMii-Disabled/ . Rename it in the future if you need to use BootMii again.

If you installed BootMii as a IOS, just exit the HackMii installer and return to the Homebrew Channel.

Click the “Launch BootMii” icon to  load the BootMii loader. Whether you rebooted or went through the Homebrew Channel, you should see the following on your screen:

At this point we’re going to need the GameCube controller. ( Note: If you’re ever in a bind without a GameCube controller you can navigate the BootMii with the Wii Power and Reset button. It’s awkward, but it works if you’re desperate.) Plug in the controller and use the directional pad to navigate over to the last icon, the two gears. Press A. You should see the following screen:

Here you can backup and restore your NAND to your SD card. A NAND backup is typically 500-600MB in size so if you didn’t heed our advice earlier to use a 1GB or larger card now is the time to grab a bigger SD card. Select the first icon, with the green arrow, and press A. The BootMii Backup tool will load, press A again to confirm you want to backup the NAND. Your screen should look something like this:

Now is the time to go browse How-To Geek’s front page , get a snack, or otherwise kill some time. The backup might not take forever but it certainly feels that way, it’s like watching a hard drive defrag. Come back in 20 minutes and check on it once it’s backed up and verified the NAND.

If you notice the “Factory bad block” message when you return, don’t panic. It’s common for there to be bad blocks in the NAND. A NAND backup with a back block error will work perfectly fine for a restoration later on. When the backup is complete, exit BootMii.

At this point you’ll want to take the SD card and copy the NAND backup files to a safe location.

Insert the SD card in your computer and copy the keys.bin and the nand.bin files—backing them up to a CD-R wouldn’t be a bad idea. You can also leave a copy on the SD card for safe keeping, just change the .bin extension to .bak .

Once you’ve secured the files in some fashion the backup process is complete. In the future should your exploits in homebrew software and Wii modding lead you down the road to brickdom, all you’ll need to do is use BootMii to reverse the process and reinstall your working NAND backup.

Reinstall the Trucha Bug to Supercharge Your Wii

Early versions of the Wii OS had a bug, known as the Trucha Bug, which allowed for the running of unsigned code. Nintendo has long since patched the bug but that didn’t slow down the homebrew community. We’re going to restore the bug in order to expand the power of your Wii and the range of homebrew software it can run.

Boot into the Homebrew Channel. If you followed the instructions in the “What You Need” section, your Homebrew menu should look like this (you may already have other homebrew installed, so don’t worry if these four items are in a different order or split across two pages).

To start, we need to install IOS36. Click on it to start the installation process. It’s totally automated and will install IOS36 and return to the Homebrew Channel menu.

For our next step, you can choose one of two options depending on whether or not you already have additional WAD files in your /WAD/ directory.

If your /WAD/ folder is empty , save for the WAD files we extracted at the beginning of this tutorial, select the YAWM Multimod batch. It will automatically install all the WAD files in the /WAD/ directory and then return to the Homebrew Channel menu.

If you have older WADS from other projects in your /WAD/ folder , use the Multi-Mod Manager to selectively install the WAD files.

If you’re selectively installing the WAD files select the WAD menu from Multi-Mod Manager and use the + key on your Wiimote to select all the cIOS files and the IOS80 WAD files. Press A to bulk install them. Exit back to the Homebrew Channel.

At this point in the tutorial we’ve backed up the NAND, activated the Trucha Bug (which we’ll need for the next step), and installed updated IOS files which will make future Homebrew and modding adventures a breeze.

Installing Priiloader and Armoring Your Wii Against Bricking

The Priiloader and BootMii are similar applications but with significant differences under the hood. Both load when the Wii starts, but where as BootMii is limited to backing up the NAND and functioning as a basic launcher, Priiloader is designed to alter what happens on your Wii. By loading before anything else the Priiloader allows you to change system wide settings on the Wii, turn off updates, and otherwise streamline and protect your Wii.

Time to return to the Homebrew Channel, if you’re not already there. Select Priiloader 236. When the Priiloader runs there is a high probability you’ll get a few yellow lines of error code in the process:

Ignore these errors, everything installed fine and you’re ready to dig into the Priiloader settings.

Turn your Wii off. Hold down the reset button, while the Wii is off, and then press the power button. Your Wii will boot but instead of taking you to the Wii Menu it’ll take you to the white Priiloader menu seen at the beginning of this section.

Use the GameCube controller to navigate down to System Menu Hacks. Press A. Inside the System Menu Hacks you’ll see a screen that looks like this, minus our highlighting of course:

By default everything is disabled, we recommend you toggle on “Auto-Press A at Health Screen” (because pressing A every damn time the Wii starts is extremely annoying), “Block Disc Updates” and “Block Online Updates” (because you didn’t do all this work just to have Nintendo undo it) and “Region Free EVERYTHING” (because some day somebody might bring the European version of Hello Kitty Adventure Island Party City 5 to your house and you’ll want to play it). If you want to read more about the additional settings and determine if you should enable them or not, check out the full documentation for Priiloader here .

Once you’ve enabled the settings you want, save them and restart your Wii. At this point, especially if you have other people using the Wii, you may want to move the apps we used outside of the Homebrew App folder to a backup folder on the SD card in order to keep children or derpy roommates from mucking about in your Wii.

---

Your freshly tweaked Wii now has the best brick protection available. In the rare case that you do brick your console with some aggressive modding, you’ve got a backup NAND on hand to restore it. Happy modding!

If you’re less than delighted with the default screensaver pack on the Kindle relief is just a simple hack and a reboot away. Read on to learn how to apply a painless jailbreak to your Kindle and create custom screensavers.

Note: We originally published this article last year, but we’ve updated it to work with the latest version of Kindle, so we’re republishing for everybody.

Unlike jailbreaking other devices like the iPad and Android devices—which usually includes deep mucking about in the guts of your devices and the potential, however remote, for catastrophic bricking—jailbreaking the Kindle is not only extremely safe but Amazon, by releasing the Kindle sourcecode , has practically approved the process with a wink and a nod.

Installing the jailbreak and the screensaver hack to replace the default screensavers is so simple we promise you’ll spend 1000% more time messing around making fun screensaver images than you will actually installing the hack.

The default screensaver pack for the Amazon Kindle is a collection of 23 images that include portraits of famous authors, woodcarvings from centuries past, blueprints, book reliefs, and other suitably literature-oriented subjects. If you’re not a big fan of the pack—and we don’t blame you if, despite Emily Dickinson being your favorite single lady, you want to mix things up—it’s extremely simple to replace the default screen saver pack with as many custom images as your Kindle can hold. This hack works on every Kindle except the first generation; we’ll be demonstrating it on the brand new Kindle 3 with accompanying notes to direct users with older Kindles.

Applying the Jailbreak

Note: We’ve updated the mirrors in the Jailbreak and Screensaver section to the Jailbreak and Screensaver hack for Kindle OS version 3.1. The file numbers in the following screenshots are from the prior version of the hack, however, the same exact steps are used just with the 0.6 Jailbreak and the 0.20 Screensaver hack (instead of 0.4 and 0.18, respectively).

If you’ve sweat through jailbreaking your iPhone–all the while praying you’re not bricking it–you’ll love how simple the Kindle jailbreak is. The first thing you need to do is download the Kindle Jailbreak pack from one of the following mirrors:

[Mirror 1] [Mirror 2] [Mirror 3] [ Mirror 4 ]

The tiny 48k ZIP file holds all the jailbreak installers and uninstallers for all version of the Kindle.

The important part of the filename is the found after the 0.4.N portion. DX is for the Kindle DX, DXi for the Kindle DXi, K2 for the Kindle 2, and K3 for the Kindle 3. The suffixes for each indicate what kind of Kindle it is within that subset. The K3G, for example is the US Kindle with 3G service, the K3GB is the UK Kindle with 3G service, the K3W is the Kindle 3 Wi-Fi only, and the K2i is the International edition of the Kindle 2. Start with your base model and select the file with the suffix that matches your country and data connection. In our case we’ll be jailbreaking a Wi-Fi only Kindle 3 so we pick K3W_install.bin .

Mount your Kindle on your computer as a USB device—it should mount automatically when you tether it to your computer via the sync cable. If it doesn’t mount right away slide the switch next to the Kindle data port back and forth to wake it.

If you’d like to play it extra safe you can backup your Kindle books at this point. We haven’t had any issues with the library vanishing but if you want to skip the hassle of resyncing all your books or you’ve made a bunch of custom collections and don’t want to deal with recreating them it’s easy enough to backup the entire library. To backup your Kindle library simply copy the /system/collections.json file to a safe location before proceeding with the jailbreak. If anything goes wrong just copy the file right back over. Backups created or ignored, it’s time to jailbreak.

Extract the appropriate file for your Kindle to the root directory of your Kindle. Once the file has transferred, eject your Kindle and unplug the data cord. Once you’re back into regular browsing mode, navigate to the Update menu by pressing Menu Button –> Settings-> Menu Button –> Update Your Kindle .

The Kindle will ask you if you want to continue, click OK. At this point the jailbreaking begins and can take anywhere from 30 seconds to 10 minutes or so. First it will tell you that it’s updating, then it will flash the screen and notify you that the update was successful, and then it will switch to the man-reading-beneath-tree default Amazon Kindle startup screen. Once the wait is over your Kindle will restart.

Note: If you’re jailbreaking a Kindle 2 there is a high probability you’ll get a failure message with a U006 error at the bottom of the screen at some point during the jailbreak process. Don’t panic, just leave it alone until it restarts by itself, it doesn’t effect the outcome of the jailbreak at all.

A few button clicks and you’re done. Your Kindle is now jailbroken and ready for some custom screensaver goodness.

Installing the Custom Screensaver Hack

Note: We’ve updated the mirrors in the Jailbreak and Screensaver section to the Jailbreak and Screensaver hack for Kindle OS version 3.1. The file numbers in the following screenshots are from the prior version of the hack, however, the same exact steps are used just with the 0.6 Jailbreak and the 0.20 Screensaver hack (instead of 0.4 and 0.18, respectively).

Enabling custom screensavers is as easy-peasy as jailbreaking your Kindle. Again you’ll need to download a ZIP file—this one a Herculean 1.1MB compared to the 48Kb jailbreak archive.

[Mirror 1] [Mirror 2] [Mirror 3] [ Mirror 4 ]

The contents of the screensaver hack archive look almost exactly like the contents of the jailbreak hack. Use the same naming convention we used for the jailbreak to locate the screensaver hack for your device. Again we’ll be selecting the file with the suffix K3W_install.bin to go with our Wi-Fi only Kindle 3.

Tether your Kindle with the USB sync cable again and copy the appropriate file to the root of the device. Again, navigate to the Update menu by pressing Menu Button –> Settings-> Menu Button –> Update Your Kindle . This process will look exactly like it did when you jailbroke the device. First the update screen, then the confirmation of update, then the reboot of the device.

When the reboot process is completely, again tether your device with the sync cable. The root directory should have a folder labeled /linkss/ .

If you don’t see this folder that doesn’t mean the screensaver hack failed to install. You may need to do a hard reboot. Reboot your Kindle by navigating, from the main library screen, with the following button combination: Menu Button –> Settings-> Menu Button –> Restart . Tether and check the root directory once the restart is complete.

The inside of the /linkss/ folder looks like the above screenshot. The only areas of relevance to the end user are the /backups/ and /screensavers/ folders and the autoreboot file. If there are any screensavers from the default screensaver pack that you were particularly fond of you can retrieve them from the /backups/ folder—we won’t make fun of you for keeping the Jules Verne screensaver, he’s a sexy beast. If you don’t want any of the default pictures to be part of your new screensaver pack you can ignore the folder.

The /screensavers/ folder is the real area of interest. Here is where you’ll be dumping all your fancy new screensaver images. By default the files in the screensaver folder will play in alphabetical/numerical order from start to finish, one per wake/sleep cycle of your Kindle. If you would like to randomize the order just create an empty file in the /screensavers/ folder named random to randomize the play order.

After you add new screensaver images you’ll need to restart your Kindle to see them in the screensaver cycle. If you want to skip manually restarting your Kindle you can copy the autoreboot file and rename the copy to reboot . After you eject your Kindle from the computer it will automatically reboot 10 seconds later.

Creating Custom Screensaver Images

You’ve got the jailbreak installed, the screensaver hack installed, all that’s left is to load up your /screensavers/ folder with pictures of your choosing. Goodbye Jane Austen, hello Wonder Woman.

Kindle screen savers are 600×800 for the regular Kindle and 824×1200 for the DX. When creating images for either device you want to work in 8-bit grayscale and save the images as .PNG files—the screensaver hack can handle both .JPG and .PNG, but we prefer saving them in a higher quality format.

The screenshot below shows how the prior settings look in Adobe Photoshop but the process can easily be adapted for any image editor capable of changing the image mode.

Because we’re discarding the color and downgrading the quality, conversion can have mixed results. Images with simpler patterns and not a lot of fine gradients— such as the How-To Geek logo we used for the first photo in this guide—translate well to the Kindle’s screen. What you seen in your image editor is strongly representative of what you’ll see on the Kindle screen; if it looks bad in the editor it won’t look any better on the Kindle.

While you could write a batch script in Photoshop or similarly equipped editors that would crop and change the image settings for you it’s better to do the work by hand. The Kindle has an oddly shaped screen as far as most images online are concerned. Most cool wallpaper and screensaver images you’ll find online are sized for standard and widescreen monitors and will need a careful cropping to look awesome on the Kindle screen.

When I surprised my wife with a Kindle I outfitted it first with dozens of Wonder Woman screensaver images. With careful cropping and attention to the detail and color palette of the image prior to cropping it’s easy to create some really awesome images. If you’re a Wonder Woman fan yourself, you can grab a copy of 66 various Wonder Woman images here .

Update: If doing the work by hand seems too arduous, How-To Geek reader Insomnic recommends using the Manga-to-Kindle conversion software Mangle to convert the images —it doesn’t distinguish between comic book pages and screensaver images and converts both admirably. Reader Groff makes it even easier on the image-editing adverse among us; visit this Kindle Wallpaper tumblr to find a wide variety of pre-sized and converted images. Thanks for the tips guys!

Uninstalling Screensaver Hack and Jailbreak

Although we’re sure you’ll be perfectly happy with your jailbroken Kindle and swanky screensaver hack if there is any reason you’d like to restore it to stock—selling it on eBay, returning it for service, whatever—doing so is simple.

Make sure to keep a copy of the two archives you downloaded for this hack, the jailbreak and the screensaver hack. Whatever files you used to install the jailbreak and the screensaver hack will have an accompanying uninstall file.

In our case we used the K3W_install file to install the jailbreak on our Wi-Fi only Kindle 3. To remove the jailbreak we simply repeat the process outlined above in the jailbreaking section but with the K3W_uninstall file. To reverse the process just work backwards, first uninstalling the screensaver hack, then the jailbreak. Restart the Kindle and you’re back to stock. You don’t even have to reinstall the old screensaver images as they’re stored in a ROM chip onboard the Kindle and will appear automatically upon removal of the screensaver hack.

---

Now that you’re armed with a jailbroken Kindle and the know-how to start cranking out some awesome screensaver images. If you create an image (or a whole batch) that you’re particularly proud of share a link in the comments.

The font options included with the Kindle are certainly serviceable, but why limit yourself? Today we’ll show you how to easily swap out the font files on your Kindle for a completely customized reading experience.

Why customize the font? Why not! It’s your ebook reader and if you want the font to be crisper, thicker, look like it belongs on Star Trek, or pack more words per line, there’s no need to let Amazon’s design decisions stand in your way. Today we’re going to show you how you can install new fonts on your Amazon Kindle with free tools and about 20 minutes of tinkering (most of which will be spent waiting for the Kindle to reboot and rebuild the fonts).

What You’ll Need

For this hack you’ll need the following things

• A Jailbroken Kindle (not jailbroken yet? No problem, see our notes below)
• A free copy of the NiLuJe’s Fonts Hack
• A Kindle/Micro USB Sync Cable

If your Kindle isn’t already jailbroken, don’t panic. It’s a free, simple, and easy hack to execute. If you’ve already hacked your Kindle for custom screensavers , you don’t need to worry about jailbreaking as you did so to enable the screensavers.

If you need to jailbreak, you can download the latest jailbreak here and then follow the jailbreaking steps in the Kindle screensaver guide to get up to speed.

Applying the Font Hack

In order to apply the font hack you first need to download the appropriate pack for your device. Unlike the other Kindle hack packs that include all the BIN files for every Kindle, the files for the font hack are a little bit larger and the packages have been split.

If you are using a K2 (Kindle 2), K2I (Kindle 2 International), DX (Kindle DX US), DXI (Kindle DX International)  or DXG (Kindle DX Graphite), you need to download the K2 Pack here.

If you are using a K3G (Kindle 3 3G US) , K3W (Kindle 3 Wi-Fi)  or K3GB (Kindle 3 3G UK), you need to download the K3 Pack here.

In our case, we’re using the Kindle 3  3G (K3G) so we’re grabbing the K3 Pack. Download the appropriate pack for your device, download it, and extract it. Within the resulting folder you’ll see a BIN file that corresponds to your Kindle device. In our case it’s the update_fonts_5.0.N_k3g_install.bin

Plug your Kindle into your computer via the sync cable. Once mounted, copy the appropriate BIN file over to the root directory of your Kindle. Safely eject your Kindle.

Once you’ve copied the file and ejected the Kindle, it’s time to install the update. While it only takes a few minutes, we strongly suggest having a full battery or plugging your Kindle into a wall charger before proceeding (we’ve had mixed results using the computer as a charging source during updating, so we advise against it).

To install the update, navigate to the update menu by pressing Menu Button –> Settings-> Menu Button –> Update Your Kindle. The Kindle will confirm that you do indeed want to apply the update. Click OK.

Your Kindle will go through the update process which can take anywhere from 30 seconds to 10 minutes. When your Kindle restarts, the hack will be applied. You can confirm the hack either by mounting your Kindle and looking for the \linkfonts\ directly in the root or by just turning the Kindle back on and checking to see if the main menu fonts are different (don’t feel bad if you end up checking for the directory anyway, the first time we applied the hack we found ourselves second guessing if the fonts were really different).

Note: If you end up not liking the results you get from the Font Hack and want to return the the Amazon defaults, just repeat the steps above using the *uninstall.bin file.

Changing the Hacked Fonts

By default, the font changes aren’t super dramatic. The fonts included in the font pack are intended to subtly improve the default Kindle fonts. If you’re looking to mix it up with something more distinct, you can do so by swapping out the fonts in the \linkfonts\fonts\ folder. Before you rush to do that, however, we have some guidelines and resources to share in order to make your font tinkering headache free.

First, there are some rules regarding which fonts you can swap out and how you have to name them. When you look in the \linkfonts\fonts\ folder you’ll see dozens of fonts. We strongly advise against messing with any fonts except for the following:

If you delete them or swap them out with incompatible files, you risk making your Kindle unusable until you do some manual editing/swapping/rebooting to undo your mistake.

The easiest way to edit the book fonts is to grab pre-made packs compiled by MobileRead users . To that end, a really great resource is this Font Files and Samples site put together by Charles Reace. Charles has gathered up the most popular font packs, hosted them, and included samples of each font taken right from the Kindle so you can see exactly how they look before you go through the hassle of installing them. Just extract them, overwrite the files in the \fonts\ folder, and then restart your Kindle.

Barring using the premade packs, you follow the advice of the Font Hack creator NiLuje in regard to naming conventions and what each font does:

• Sans_Regular.ttf: Used in the Settings & Experimental page for the explanation texts. Also for the dictionnary/note popups.
• Sans_Bold.ttf: Used in the menus, in the top & bottom panel, and as the collection title when browsing a collection, and the inline text in the book & collection browsers (ie. the ‘delete this item’ stuff & co
• Sans_Italic.ttf: May be used alongside Sans_Regular or Sans_Bold somewhere ^^
• Sans_BoldItalic.ttf: Used in the book list, for the collection names
• Serif_*.ttf: Used in the reader, that’s the font family your books will be rendered with.
• Serif_Bold.ttf: Used in the book & collection browser for the book title & author. (NOTE: For these purposes, Serif_Regular is used instead on FW 3.x)
• Mono_*.ttf: AFAICT, nowhere except in the browser, but I may be mistaken. (Might be used in the reader when you’re feeding it a raw txt file or some raw html files, depending on styling).

When replacing files, we recommend renaming the files with the extension .old-tff so you can easily roll back your font changes in case something goes wrong.

That’s all there is to it! You can take the ultra easy route with the premade packs or dig deeper and build your own custom font pack.

As similarly seen with Lil Nas X’s devilish “ Montero (Call Me By Your Name) ” promotion in 2021, conservatives have their satanic panic panties in a twist over last night’s performance from Sam Smith and Kim Petras . The two took the Grammys stage for a performance of their song “Unholy,” which won the award for Best Pop Duo Or Group Performance.

In addition to Petras making history as the first out transgender woman to win in the category, she and Smith stoked the flames of controversy with a fiery, hell-themed performance—much to conservative’s chagrin.

Bone-headed political abomination Ted Cruz added his two cents last night, calling the set “…evil.” Majorie Taylor-Green also tweeted about the performance, fit with a Pfizer conspiracy too dim-witted to even bother breaking down.

Aside from the blatant thematic ties to “Unholy,” Petras says the red-laced performance was inspired by the duo’s experience with religious institutions.

“I think a lot of people, honestly, have kind of labeled what I stand for and what Sam stands for as religiously not cool, and I personally grew up wondering about religion and wanting to be a part of it but slowly realizing it didn’t want me to be a part of it,” Petras tells Variety . “So it’s a take on not being able to choose religion. And not being able to live the way that people might want you to live, because as a trans person I’m already not kind of wanted in religion. So we were doing a take on that and I was kind of hellkeeper Kim.”

Like the discussion around Lil Nas X and his striptease with the devil, conservatives love to ignore storytelling context, opting to spout off nonsense about queer and trans artists pedaling out satanism and immoral lifestyles to—oh my—the children. It all feeds into the conspiracy that Hollywood’s trying to cause the collapse of society and poison the next generation, a dated but enduring theory.

Ultimately it’s boring, cyclical tripe that seeks to villainize artists from the LGBTQ+ community, but it’s not without its consequences. With anti-trans bills ravaging states such as the Cruz-led Texas , the anti-LGBTQ+ rhetoric of the satanic panic unfortunately motivates political repercussions. Over the last year, bills all over the U.S. have emerged looking to eliminate trans-affirming care, and even the mere existence of drag shows .

This form of political violence works on a macro

“What people don’t realize with trans non-binary people in the U.K. is it’s happening in the street. I’m being abused in the street verbally more than I ever have,” they Apple Music’s Zane Lowe . “So that was the hardest part, I think, was being at home in the U.K. and having people shouting at me in the street. Someone spat at me in the street. It’s crazy.”