Recent submissions

Comment · 7 days ago
Invalid deployment target. Your app targets iOS 9.0. iOS apps must target iOS version from 13 to 27.2 to be uploaded to App Store Connect or submitted for distribution.
Comment · 1 month ago
Comment · 1 year ago
Comment · 1 year ago
> ad tap (just clicking an ad, potentially a misclick aiming for a tiny X button, with no Install button even visible on screen)

> AppLovin’s X’s are unusually tiny, so mis-taps are especially likely

This is why I use Intent Intercept - https://f-droid.org/en/packages/de.k3b.android.intentinterce...

It tells me exactly what's about to happen from my tap(accidental or intentional), and gives me the option to undo my tap.

Every privacy/security conscious Android user should have Intent Intercept installed on their devices already.

Comment · 2 years ago
Comment · 2 years ago
Title needs changing to "Uncovering Every Lie in MKBHD's Apple Propaganda Video".
Comment · 2 years ago
Question for rsync users on linux. Does your rsync preserve creation times --crtimes ?

I'm aware ext4/3 filesystems don't store creation times. But I want to use rsync on Linux to sync files between an NTFS(supports creation times) and a Btrfs partition(also supports creation times) without losing the creation times.

Currently rsync just sets the creation time to the modification time on the destination directory. Which is not what I want.

When I use `--crtimes` I get a "This rsync does not support --crtimes (-N)" error.

Weirdly, just using `cp -a` works. But it doesn' t have any of the checksumming and differential copy bells and whistles of rsync.

How do you rsync on linux while preserving creation times(on supported file systems)?

Comment · 2 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton