…and create a perfect device to disseminate more microplastics as the bond breaks down.

Get a better job so you can afford better drugs. This is “Minimum Wage Methy”, and you want to be “Salaried Methy”.

Gotta say… This is not how you’d generally do any of this. Where you get this info?

When you go to print, just look for the link that sends out the print job to your system settings. That bypasses the browser print stack. Probably solves your issue right there.

I print a number of label sizes on a Brother Laser as well, and have zero issues. Most of the media size and handling is done by the printer itself, and the software has little to do with it…for the most part.

1. What specific printer is this?
2. Can you upload an image of the misprint to illustrate what’s happening?
3. Have you tried forcing the system print dialog when printing versus just using whatever Firefox gives you?
4. Can you print a proper label with any other programs, or do they all behave similarly?

I think it’s more about closing a backdoor to free product that was generally out of reach for most people a few years. Free API access for devs has been a thing forever for the most part, but the barriers are now lower for people to abuse it.

Yes about profits in the sense they don’t want people getting free access to content, but I don’t think this is designed to net them a bunch of money or anything.

This is going to become more of a standard due to people vibecoding their own clients for every dumb thing.

It’s not the CPU. All that will do is consume CPU and raise your energy bill.

1. Get some sort of resource monitor running on the machine to collect timeseries data about your procs, preferably sent to another machine. Prometheus is simple enough, but SigNoz and Outrace are like DataDog alternatives if you want to go there.
2. Identify what’s running out of control. Check CPU and Memory (most likely a memory leak)
3. Check logs to see if something is obviously wrong
4. Look and see if there is an update for whatever the proc is that addresses this issue
5. If it’s a systems process, set proper limits

In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.

This is just poor security. Not like in TV/Movies where an “AI” was found “breaking layers of firewalls and encryption” or whatever 🤣

Somebody fucked up. Plain and simple.

https://gist.github.com/camullen/0c41d989ac2ad7a89e75eb3be0f8fb16

Just cut Windows out as much as possible and run everything in WSL. Setup everything to boot straight to all your WSL layers, and aside from the absolute shit Base OS, it should be the same.

Okay, but give a little look into where your disk is using space.

du -hsc /

And work from there.

It depends on where that storage was used. Some details would be useful.

At its core, you shouldn’t need to keep any previous layers than the one you’re using for the OS.

You also technically don’t need snapshots for anything but your personal file space.

Not sure what the Frame means with any of this. It’s going to be running the same stack as Deck, which is KDE. It’s also not going to be any sort of headset for your PC, at least at the outset.

As for your other Dr questions, it’s all just personal preference. The Desktop is just window dressing on a compositor and window manager anymore. If you’re comfortable without all the system helpers and convenience of using either Gnome or KDE, you can just run a WM like Hyprland or Sway instead.

There are many other NVR options out there. Try Shinobi.

Also, check and see if that memory is upgradeable for cheap, and whether it has an HDD or SSD. May be worth switching that if cheap.

Ain’t nobody gonna buy your stupid Nazibots either, di ckhead. You are universally despised.

Are you just SAVING as these file extensions, or EXPORTING as each type of file extensions.

Not the difference, and see in the File menu that you need to use the EXPORT function to change actual file type.

1. What’s a PFP?
2. What format are you uploading them in?
3. What app are they generated with?
4. Do they also look corrupted on other devices you may have handy?

How is this a “Glass House” situation?

Just flipping through…this person is either not a seasoned “Software Developer”, or possibly self-titled.

All of the confusions and problems described here would immediately be identified by someone who has experience in building and debugging software. The logic is confounding.

Why a dev who had moved to MacOS would even need a justification to just then move to Linux is also very confusing.