I doubt Gaussian blur is an accurate model of real-world situations.

At the end of the day if you are worried about the codes being painted over print a few out and paint over them. Then scan with a variety of scanners.

If I had to come up with some more digital tests I would guess that a few of these are more representative of real-world situations:

1. Lower contrast. For example lighten or darken the whole code. This would simulate things like scanning in low light or with glare.
2. Block out sections of the code. This will test error correction levels and simulate partial damage or pockets of extreme glare.
3. Skew the code in various ways. This simulates the perspective shift of people scanning the code from an angle.

Ideally combine them in a bunch of scenarios then try to scan with a variety of scanner implementations.

It also supports iOS.

No, the DRM wouldn’t work at higher levels so you would have the same requirements with regard to 4k.

Please be civil and polite. This type of aggressive comment insulting people because of the tools that they use isn’t welcome here.

You seem to be making this very complex. But it really isn’t. Yes, git doesn’t track renames. So you are working around it by splitting your operation into 2 commits.

1. A pure rename.
2. A file change.

This way 1 is always considered a rename and 2 is just a regular file change with the same path. You may also consider tweaking the default rename detection threshold with flags like --find-renames or options like diff.renameLimit.

Would it be nice if Git tracked renames? Probably. But that isn’t how the data model works so it is unlikely to happen soon. But maybe they could add some metadata.

I think it doesn’t really make sense. Because you can’t “squash” one commit. squash is taking multiple commits and making them one.

When you do a “squash merge” you are really saying “squash all the commits that are on this branch and not the target” then merge.

So you can’t “squash a merge commit” you need at least one additional commit to squash in.

No, but you can still choose to choose software that doesn’t steal and sell your data. You can also support laws that make doing this illegal.

The idea that putting this on your phone is bonkers is bonkers to me. Why would you want to carry around a journal or paper when you have everything on your phone? It can also be more easily backed up and synced.

It shouldn’t be normal that this data is stolen and sold. That is 100% the problem, not the fact that people track things on computers.

You have obviously never tried dereferencing a null pointer.

They are legal if you follow the regulations. The problem with the “rideshare” companies is that they don’t. We should just call them “unregulated taxis” rather than pretending that they are a different service. I think just about every taxi company these days is on some app or another (often the same that call unregulated cabs in countries that actually got their shit together and banned the unregulated ones).

Nah it’s worse. Bitcoin actually has legitimate uses. (Yes, they are a minority of actual usage, but they exist.) NFTs are only useful for speculation, gambling and money laundering.

“Rideshare” is also the least accurate term used to dodge regulations. It is just a taxi/cab. You are paying someone to get you from one place to another. They aren’t sharing their ride, they were never going where you are going before you told them to.

Yeah, downtown there are tons of gas-station brands that are just convenience stores. Surely many gas stations will offer electric charging but since most people will be charging at home the total number of gas stations will surely drop. Some will turn into convenience stores and some will just shut down.

You forgot step 2. Throw sacrificial drive into trash.

This is also likely interesting because console SDKs are usually highly restricted. So not only is the Minecraft code leaked (which is probably moderately interesting) it is likely that the console APIs are quite interesting to emulator developers and reverse engineering for other PS3 games.

Please be polite. If you don’t like a post you can downvote it. If you would like to comment please be more civil.

While Amazon is awful it isn’t just them. It is a systematic issue with our economic system. Our society constantly makes efforts to keep the poor poor so that they are forced to work for low pay resulting in a cycle of abuse. Basically every public company will end up in the same situation and we see that with every large company. If a large public company isn’t shit the CEO will be fired by the shareholders and replaced with one who makes the company shit.

So yes, avoid Amazon, but also talk to your government representatives. The cycle will always continue until the incentives are changed. To properly exit this shit system we need to change our society and government.

I use https://difftastic.wilfred.me.uk/ which is well, fantastic. I have it set up as the default diff for Git and it is really nice.

It’s also super locked down. You are only allowed to use it if Google or Apple says that your device is authorized. So no root, no custom ROMs. Unless your phone is owned by a corporation and that corporation is blessed by Apple or Google you are out of luck. (There are currently ways around this but the gaps are slowly being closed as older devices are phased out.)

I’m also not familiar. But my understanding is that the package maintainers should prevent this situation. Because otherwise even if there are package version dependencies (I don’t actually know if pacman does this) it would just block the update which results in a partial update which isn’t supported. For example if your theoretical unmaintained Firefox blocks the update of libssl but Python requires new functionality you would be stuck in dependency hell. Leaving this problem to the users just makes this problem worse. So the package maintainers need to sort something out.

It is a huge pain when it happens but tends to be pretty rare in practice. Typically they can just wait for software to update or ship a small patch to fix it. But in the worst case you need to maintain two versions of the common dependency. In lots of distros very common dependencies tend to get different packages for different major version for this reason. For example libfoo1 and libfoo2. Then there can be a period where both are supported while packages slowly move from one to the other.