Clean the printing surface with dish soap and tepid water, and adjust your z offset. It appears to be too low from what I can see, but it’s hard to tell from a few pictures. It’s not supposed to be 0, and will depend on your specific printer, extruder, … You should aim to have fully filled squares, with no apparent “scars” on the surface left by the hotend moves. A nice rule of thumb is to be able to barely move a sheet of paper between your plate and the hotend freely without feeling friction (make sure to clean the tip of the hotend before). If after these steps it still produces these results, maybe there is an issue with you bed planarity, but most likely your pla has gone bad (I’ve even seen sealed bags go bad over a few years), try with a freshly dried filament, or a new roll from a reputable source

IIRC zip can, but doesn’t by default. Source : wasted 8 hours trying to figure out why something didn’t work anymore (had to switch from tar to zip because stupid security system wouldn’t let me transfer the tar file)

Random idea that might work: Try to install ReFind from windows, it should work and allow you to boot from random thing more easily. Then try using it to boot from the SD card. Don’t forget to turn off secure boot. If that doesn’t work, the right idea is indeed to “burn” the media on a partition, however you will also encounter some amount of headache with this option: an installer is not a single partition, but multiple ones. You could try only having the “main” partition on disk, and use refind to boot it too.

TL;DR: ReFind could help you. Turn off secure boot.

Most actual poisoning techniques don’t actually work that well. When I end up with a PDF, I usually strip out the existing text layer, apply a denoiser and a few other preprocessing steps to correct common errors, then a layout / reading order detector, and finally OCR the different blocs. This is against the most common poisoning techniques, and one of the most efficient, called : someone printed a document, forgot about it for 3 years, then scanned it slightly tilted (and dirty, crumpled, …), and the scanner decided to apply its crappy OCR.

Using screenshots of the PDF also avoid any kind of font face poisoning, and anti copy protection.

If you really, really need to protect your PDF, please consider accessibility first, then what would work imho is to use the scripting features of pdf to actually render your content on the fly. That would probably mess up most of the “automatic” processes.

Graphene user here ! The privacy and security gains are quite huge. Play services are more or less regular apps, with the sandbox offering limited access. Some of the “advanced” security offered by graphene triggered a few times for me, sometime highlighting something sketchy in some apps.

Also, you can disable the internet permission for apps, which can effectively block a lot of stuff (ex : you install a supposedly offline game, but it stills asks for the permission: denied).

If your main concern is not depending too much on Google, your options are limited, and very, very flawed depending on how far you whish to go (went far down this rabbit hole, came back). One less “extreme” way, using graphene, is to install play services and everything dependent on a separate user account, and clone app from this account to the one you will use. Since alternate accounts are sandboxed and not running when not logged in, when you use your phone from the main account, you will effectively be almost goggle free.

Almost, because the main remaining privacy hole is notifications. A lot of things goes through GMS in order to reach your phone without melting your battery