ozymandias117 @ ozymandias117 @lemmy.world

Posts

3

Comments

423

Joined

2 yr. ago

A big thing the other comments are missing is that just running the iptables rule only works for the current boot. You need something to rerun it every restart

ufw is a front end to make it easier to use them

If you want/need more control, you should look into /etc/iptables/rules.d config files

Edit: or depending on what your distro already has, the firewalld comment makes a lot of sense. E.g. that’s Fedora’s default front end

The funny part, to me, is that the command he ran was so dangerous that Pop_OS required you to type out the entire phrase

“Yes, do as I say!”

With correct punctuation, or it won’t continue

If it was just an “Okay” box or a “Y” to continue, I don’t think he’d have gotten as much flak for that one

With an HDD, your operating system can (mostly) directly access bits on the magnetic disks, so you can wipe them by just writing 0 to it over and over (historically, there was a paper saying 7 times would make any bits unrecoverable - this changed as density got higher)

With SSDs, your operating system has very little control over what bits a write is touching, a lot more was moved into the firmware on the flash memory itself

So SSDs need a special command “Secure Erase” to wipe them

Looks like it’s behind an about:config setting, media.webrtc.camera.allow-pipewire

https://github.com/linux-surface/linux-surface/issues/1215#issuecomment-1669374232

Ohhhh I read the congee statement as you shouldn’t eat it, not that you should

Now I understand. Thanks!

Not exactly - I’m wondering if 酸粥 is being discouraged, while the Han are still eating 稀飯

Do you know what the link to Uyghur is?

The Han Chinese people I know from Shaanxi still seem to eat congee regularly

Is there something lost in translation that the Uyghur style congee is different than the Han style or something?

I literally linked you to the Reddit comment, and pointed out that Google’s response used the same measurements as the comment

Are you an LLM?

In this case, it seems pretty likely. We know Google paid Reddit to train on their data, and the result used the exact same measurement from this comment suggesting putting Elmer’s glue in the pizza:

https://old.reddit.com/r/Pizza/comments/1a19s0/my_cheese_slides_off_the_pizza_too_easily/

And their deal with Reddit: https://www.cbsnews.com/news/google-reddit-60-million-deal-ai-training/

It’s also funny to use “giga” in the marketing when everyone else is dealing with petabytes

A “fun” one I ran into was all our tests passing on my desk, but failing in the test farm

After a month, we realized that having an HDMI cable plugged into the unit was corrupting the SD card due to a memory overwrite in the graphics stack

For your analogy, you can’t put more water in a sponge that is completely saturated

Trying to compress a compressed file doesn’t really work - at least not for a meaningful gain in storage size with zip, bzip, 7zip, gzip, xz, lzma…

They’re already using HEIC/HEIF

I would be disappointed if they’re compressing it even more on iCloud. You can’t generally meaningfully compress a compressed file

I’d disregarded compression as a possibility because the wording is “full resolution photos and videos are safely stored in iCloud”

I never made that claim, my man

I just wanted some more information about how the on-device database corruption led to restoring pictures

Those are generally opposites

On spinning disks, it’s significantly easier to restore data after a delete, but it’s not normally as easy on flash storage like they’re using

The article specifically states that iCloud wasn’t related to the bug

E.g. iCloud says it’s using 13.4 GiB to store photos, Settings -> General -> iPhone Storage says I can save 15.5 GiB because they’re backed up on iCloud, and if I use idevicebackup2 to pull everything off the phone, there are 21.7 gigs of photos

I’m wondering if these discrepancies are related to the photo app not actually deleting pictures from the filesystem

Sure, an index makes sense for quick search, but I’m confused why deleting it wouldn’t remove it from the filesystem too

Is that why iPhones seem to have no idea how much disk space they’re using?

I’d still like a deeper dive into how database corruption led to data restoration

It seems like deleting a photo must just be removing the entry from the SQLite database, and not actually deleting the photo?

They also use risc-v since 2017

https://www.anandtech.com/show/15228/samsung-to-use-riscv-cores