arsome

I'm sure our extremely divided society will benefit greatly from configurable echo chambers.

You can take advantage of QListView to handle high item count lists and it'll just request the data it needs when it needs it, scales to millions of rows without issue, you really don't want to draw it yourself.

You weren't learning anything from Vice either.

I think YouTube is the counter argument to this - long form content from passionate people has taken off pretty good there. Perhaps it's just me, but it seriously makes the rest of social media look like an absolute trashfire by comparison.

Not useful, but artistic in nature. A number of magazines used to have illustrators do something similar in cases where there was no appropriate imagery.

Software patents do not provide the benefits other patents do. Name a piece of software that would likely not have been written if it wasn't able to be patent protected. Now compare that with other industries like pharmaceuticals, textiles, chemical processes, etc. Software is different because it's more straight forward engineering than explorative science. If an implementation is obvious to anyone with the prerequisite knowledge, it's not patentable and there's really not much, if anything, in the software realm that meets that criteria.

As long as you don't overspend on weird. Being weird is great until it isn't.

I'm not so sure that detracts from their reputability, does Rtings seem less reputable because affiliate revenue is part of their income?

This is just news trading, you're just really fast because you're the headline.

Yeah, the LED swap kits are contributing their part to the brightness war too.

DEP does nothing to prevent OpenProcess() and WriteProcessMemory() from working or prevent applications from loading a dll which reaches into the main process's image to patch it. DEP tries to prevent exploitation from taking place within a single process by ensuring say, a buffer overflow can't just call the value you loaded into your webpage, not running software tampering with the memory of other running software using APIs which allow for the purpose.

Even if the page is marked as non-writable, execute only, you can pause the process, change the permissions and resume it or do it at image load time without issue.

Windows applications using the old/standard win32 api don't have sandboxing between them at all and any application is free to tamper with any other to an almost limitless extent. It's incredibly powerful, in both good and bad ways.

Certain advanced firewall tools with IDS style features can hook these calls and notify you when an application is attempting to do something like this.

Judging by some freight hopping videos, they're still around on cargo trains, perhaps just less numerous.

These are not applied on disk, they're injected at runtime. Just open the process and write to its memory directly.

Doubt it'd actually work - remember, humans.

I think the "random but actually meaningful" route is better. If you want it to get checked, grandma's name comes off fake name generator, not line noise from a CSPRNG.

Yeah I would be much more concerned about things which cause exponential time increases, like developers who brute force search lists instead of using dictionaries than how they declare their dictionaries unless I was at the point of profiling and the dict() constructor was somehow near the top of the list.

The GE Trivection oven again? Really?

I've tried Kagi, Brave and DDG for extended periods and ultimately their results are even worse in most cases and leave you going "hmm, I wonder what Google would give me".

It's the enshitification of the entire internet, not just Google unfortunately.

Doom code has been opened for a while under the Doom Source License originally.

https://doom.fandom.com/wiki/Doom_Source_License

Perhaps if you're downloading full dumps, but distribution of individual books is often done via IPFS.

But that could change over time with further understanding. No point panicking today over something not known to be harmful. The effect size is clearly very small. If I wanted to better my health in an actually measurable way I'd be much better served by dropping alcohol and refined sugars than worrying about microplastics.

I'll happily sign up to be mega-dosed with them for a trial, but they've tried that in mice and found pretty much no issues.

Isn't there also limited to no evidence of harms from these in humans?

Kobos are pretty trivially jailbroken if you're looking for a similar competitive device.

I mean assuming you're hitting about 3.5 drinks like that, you'd need to be doing it 5 nights a week to hit 15 and qualify as heavy drinking.

As pointed out by the parent comment, one strong 16 Oz can is already 2 drinks. Having 2 of those in a night or even slightly weaker ones puts you in the 3-4 drink range. I'm sure I'm not the only one with a habit of having 2 of those a few nights a week to tie a long day off.

You probably see this attitude a lot because of modern C++ features that do make it a lot easier to write safer code. However that is not absolute.

Just the other day I had used std::sort on and std::vector. Pretty simple stuff, figured there can't be a way to screw that up, but my app kept crashing in the sort call because it was trying to write past the end of the array. Turns out if your comparison function doesn't perfectly follow strict weak ordering sort will just blow the bounds of your array without checking.

It already is quite difficult to recover to this level, even for a relatively small malware codebase this probably took hundreds of man-hours to decompile into a meaningful state.

To protect it beyond a basic level - You can try but it's a cat-and-mouse game. A sufficiently skilled reverser will drop a debugger on your program, execute the code until it's past any decryption and then dump it from memory. So better schemes to obfuscate applications have been developed, like VMProtect, which makes a simple virtual machine with a custom instruction set and uses it to obfuscate your application. It's of course possible to break that as well, but it takes more time and requires more skill.

How about all add-ons as specified by developers instead of this trashfire?

Restricting add-ons in this way seems more like a Google move than a Mozilla one.

I mean the entire point and value of that whole data siphon thing is literally the ads.

I pirate everything anyways, why in the hell would I pay for YouTube?