oats

Google is not breaking the (German) law here, it actually is your responsibility as a user to not spy on people. Failure to do so means up to three years in jail, for a first offender most likely a fine. And your device that you used to break the law might get confiscated.

The later was already the case when people used radar warner apps (banned on Germany as well) and lost their smartphone for that.

No, the user breaks this law, not the manufacturer. So the loophole for google is, they don’t care about you.

I didn’t check the actual law, always a good idea to do so.

So, §201 StGB actually covers both, it is forbidden to “aufnehmen” (record) as well as “mithören” (spy on). Bonus, its forbidden to cite transcription (im Wortlaut mitteilen).

Its an old law, going back to video cameras with magnetic tape and actually tapping a phone line. So it was used quite often, including the mentioned fake surveillance cameras, that didn’t record or even view anything but seemed to the public they did.

When dashcams became a thing people would be sentenced for using them. These days you can use dashcams, but never save for more than 24h or show the recording to anyone but the police/court.

I guess the law is a relict of living next door to Stasi, but its really just a guess of mine.

Not a lawyer, but as far as I got it, the storing isn’t the punishable part, the recording is.

You can’t have security cameras filming public spaces (like the road in front of your house). Even if its dummies, as people couldn’t tell the difference whether the camera actually films them or not.

Illegal in Germany. You may not record conversations, if you try to enter something like that as evidence you’ll get punished as well.

I suspect there are many countries with laws like that, and if your phone actually disables the feature when you enter them or just let’s you hang to dry…

Extremely simplified:

Your file system consists of a whole lot of blocks to write data to. Let’s say you have a block size of 512kB, so a 4MB file would span 8 blocks. A 3.7MB file would span 8 blocks, too, as the remaining space can’t get used otherwise.

Now to get what file exists on which blocks, there’s a large index table, consisting of a number of index nodes (shortened to inode). Each inode saves multiple data fields of a file, like its name, owner, creation data, and the files blocks.

If you link a file to a second name (hard link) a second inode will get created that points to the same blocks.

That’s about it. Used to be important to chose the right inode size and count on filesystem creation for the average data you’ll save on the filesystem, as inodes have a fixed count, and the index table takes disk space, too. Too many inodes and you waste space that you could use for precious data, too few inodes and you can’t save new files even when you have free data blocks. With growing disk sizes people just went with massive indexes, who cares about a few wasted megs.

Modern filesystems (like ext3 and up) introduced journals, which complicate things.

You mean like in your kitchen? Too much metal, you’ll damage your magnetron.

You could use thermite and melt it to a pulp. Dangerous as well, though.

Really, just encrypt. Your CPU has AES extensions, performance impact is negligible. Simple, clean, and a protection against involuntary decommission as well.

You can lazy umount, which blocks new accesses and actually unmounts when it can

You used Solaris when cortana was already a thing? That’s great! :D

My university ditched Solaris like 20 years ago. Still have fond memories of cde lol

“I’ll get to it, eventually” would ruin the meme but be more fitting, in my opinion.

Had multiple occasions where people fought against filling disks and just couldn’t see why. Well, that 10 gig log file you deleted two weeks ago? It’s 20 gig now, and still being written to.

lsof shows stuff like that.

Nah, they just throw away the block markings, absolutely.

Overwriting a SSD is difficult as well, better encrypt the drive and trash the key when you decommission.

Well actshly, rm removes the inode, not the file. If it’s still in use it’ll stay on the disk until the last fd is closed.

• with most file systems that are usual on linux

I do use German key layout, as I’m used to that for decades.

And German number, currency, date, address formats, as the English are just whack

The end key becomes ende. Over 30% increase!

Aim for the knee

Don’t know what your mobile OS is, I set my Android to English and use HeliBoard for the keyboard app. It even remembers what app should get Swedish, German, English layout and word suggestions.

Dunno, isn’t logo older, with the whole frigging language translated?

When I started computering, there where no localised systems. When they started translating, the German was often misleading, incomplete, or just didn’t fit in the button or whatever. So I stuck with English. Somewhere along the line I switched to en_UK, though.

And yeah, in this day and age I have no clue how good the translations are, because I never checked them.

Yes, the clients (Desktop, Web, Browser, Mobile, CLI) are published by Bitwarden under GPL3 license, so you can always fork them.

Bitwarden could delete the repos, but the code is out there.

I have fiber in my basement and could book gbit. Upstream is still nerfed, currently I have 250mbits down, 50 up

Edit: disregard that, just checked with my ISP and apparently I have an old plan, and could book 1 gig symmetric. For thrice the cost, though