sasalzig

First of all, this is probably a bad sign for the health of your drive, you should look at the dmesg output and SMART diagnostics of the drive. There's a package called smartmontools or something like that. Also make a backup now if you haven't yet.

If it's just the filesystem that's borked try fsck like that other person said.

I like Taler, but it's specifically designed to not give anonymity to sellers. In order to verify that you got a valid token (meaning it was issued by an accredited bank and was not already spent) you need to deposit it with the bank.

Now if you get money from a friend you trust has given you a valid token, then that's not an issue. You can just use it to pay for stuff and nobody will know how you got that token. A seller however will want to verify the token immediately or they might end up giving stuff away for free.

I guess for donations it could work since you're not giving anything in return and so can't be scammed, but it's obviously a bit of a problem since you could be sitting on worthless tokens. You don't know what funds you have until you try to spend them, and people will probably get pretty annoyed with you if most of your tokens end up being fake. Not sure how one might protect themselves against this sort of spam.

You think FairEmail is too cluttered but like K9? 🤔

K9 is the most insane mail client, it's got hundreds of settings! I was so happy to ditch K9 when I found FairEmail.

As I said, every file read from disk, be it an executable, image or whatever gets cached in RAM automatically and always.

Having said that, if you read a file using read(2) (or like any API that uses read() internally, which is most), then you end up with two copies of the file in RAM, the version your OS put in the disk cache, and the copy you created in your process's memory. You can avoid this second copy by using mmap(2). In this case the copy of the file in the disk cache gets mapped into your process's memory, so the RAM is shared between your copy and the disk cache copy.

You can also give hints to the disk cache subsystem in the kernel using fadvise(2). Don't though unless you know what you're doing.

Does that stuff still happen? I didn't try this but I had kinda hoped this stuff got fixed with the introduction of systemd.

This doesn't explain what a disk cache (afaik often refered to as page cache) is, so here goes: When any modern OS reads a file from the disk, it (or the parts of it that are actually read) gets copied to RAM. These "pages" only get thrown out ("dropped") when RAM is needed for something else, usually starting with the one that hasn't been accessed for the longest time.

You can see the effect of this by opening a program (or large file), closing it, and opening it again. The second time it will start faster because nothing needs to get read from disk.

Since the pages in RAM are identical to the sectors on disk (unless the file has been modified in RAM by writing to it), they can be dropped immediately and the RAM can be used for something else if needed. The downside being obviously that the dropped file needs to be read again from disk when it is needed the next time.

They're a sucker who's gonna get fleeced. If they answer that they know the game is rigged (as most of them will), but that they totally understand how this works, they're a super sucker who'll get double fleeced.

Not an expert, but from my understanding of how this worked for the Mario 64 project:

• Take the ROM and run it through a disassembler.
• Rewrite (by hand) the assembly in C, one function at a time, with the goal of producing a bit-for-bit identical instructions when compiled using the same tool chain as was used by the Nintendo devs back in the day.
• Since you now have a reconstructed version of the C source code, you can easily do with it what you can do with any C codebase, like port it to PC or add features, that would be difficult or impossible to do with the MIPS assembly.

I like how that material design stuff looks on my Android. Bite me.

To the people complaining they can't figure out what is or isn't a button: How often really does that happen to you? Even the computer illiterate somehow manage on their Androids and websites.

Windows 9x, which gets brought up in these discussions as an example of some sort of perfection, had plenty of "buttons" that had no 3D effect, including menus, icons in icon bars, systray icons and desktop icons. WordPad originally had all the icons up in the icon bar with a 3D effect. It looked like shit and Microsoft stopped doing that in 97 at the latest.

There are considerations other than clarity of intent, like not distracting people from the content with all that ornamentation.

My suggestion would be to put a picture of a baroque church as your background to even out the minimalism if it bothers you so much.

I know all that. That doesn't answer how this is supposed to work at all.

I don't understand what the endgame is supposed to be here. In order to achieve its stated goals (demilitarization, denazification, catching their list of enemies), Russia needs to occupy (which they said they won't, which makes no sense). There's no way Ukraine's govt can agree to or implement these demands.

So Russia will in fact need to occupy Ukraine and install a puppet govt. But how the are they ever going to get out of there ever again? That new government will get removed as soon as they leave.

So long term occupation it has to be, which will be a total disaster and that's on top of the sanctions. Russia just fucked itself, no? How does any of this make sense?

I'm not disagreeing there. Care to revise your statement that Ukraine was neutral prior to the invasion or are you just going to ignore that?