Top all-time · #8924
swick's blog
Personal blog · blog.sebastianwick.netprogrammingsystems
swick's blog is a personal blog at blog.sebastianwick.net about programming and systems. Since 2025, 9 different Hacker News readers have linked it 12 times, most often “Flatpak Happenings”. It is still writing: the last post was on 2026-10-18, and you can follow it by feed.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for posts on Linux app sandboxing and Rust safety. The comments discuss Flatpak permission handling and the limits of Rust in catching rename-related syscall bugs, quoting the posts.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Welcome to my blog!
Most-linked posts?
- Flatpak Happenings3 people · 3 mentions · first linked 2025-11-05
- How Hard Is It to Open a File?3 people · 3 mentions · first linked 2026-04-24
- Best Practices for Ownership in GLib2 people · 2 mentions · first linked 2026-01-22
What Hacker News says?
(2/3) Flatpak is very far from a sufficient sandbox when app developers define their app's permissions, users either need to interact with the `flatpak` CLI, install a third party app or be KDE Plasma users in order to edit app permissions, many permissions are granted superfluously and users who mean to revoke them really have no way of knowing what is necessary for an app's correct operation, nor do apps themselve…
Comment linking /posts/flatpak-happenings/
on “The Advantages of Mobile Linux over AOSP (LineageOS, CrDroid, GrapheneOS, etc.)”Submitted Gnome 49 Backlight Changes as a story · 6 points
HN discussion> For example, Unix's `rename` syscall takes two paths as arguments; you can't rename a file by handle And then there’s renameat(2) which takes two dirfd… and two paths from there, which mostly has all the same issues rename(2) does (and does not even take flags so even O_NOFOLLOW is not available). I’m not sure what you’d need to make a safe renameat(), maybe a triplet of (dirfd, filefd, name[1]) from the source, (…
Comment linking /posts/how-hard-is-it-to-open-a-file/
on “Bugs Rust Won't Catch”Submitted Flatpak Happenings as a story · 5 points
HN discussionSubmitted Blender HDR and the reference white issue as a story · 4 points
HN discussionSubmitted XDG Intents Updates as a story · 3 points
HN discussionSubmitted Best Practices for Ownership in GLib as a story · 2 points
HN discussionSubmitted Flatpak Happenings as a story · 2 points
HN discussionSubmitted How Hard Is It to Open a File? as a story · 1 points
HN discussionSubmitted How Hard Is It to Open a File? as a story · 1 points
HN discussionSubmitted Best Practices for Ownership in GLib as a story · 1 points
HN discussionSubmitted Improving the Flatpak Graphics Drivers Situation as a story · 1 points
HN discussion