Sami Tikka
6K posts

Sami Tikka
@sti
Old unix geek. I work for WithSecure but my opinions are my own.
Finland Katılım Nisan 2007
364 Takip Edilen222 Takipçiler

@straceX genuinely curious... why do you need an infinite stream of zeros to just... generate zeros?
like I imagine that /dev/zero is an infinite loop yielding 0's, so... like... couldn't you just do that loop?
honest question.
English

Check out amazon.science/publications/a… and pages.cs.wisc.edu/~yxy/cs839-s20… for all the details there.
English

#yle voisi maksaa kirjeenvaihtajille sen verran palkkaa että he voisivat raportoida hotellihuoneesta tai edes jostain sisätilasta. Onhan se jännää nähdä katuelämää vieraista maista mutta kirjeenvaihtajan sanomiset jäävät katumelun alle.
Suomi

@BananaInYourPie @valigo That brings back memories 15 years ago when an admin truncated tables in the staging database.
And few minutes later found out the window was connected to production database.
English

@BananaInYourPie @valigo No worries. If you delete the symlink, only the symlink is deleted, not where it points to. And /bin and the files in it would have been owned by root which means a user cannot delete them.
Unless you are root, of course.
English

@valigo If it makes you feel any better, years ago, a colleague was working on ("very important system") - a full sci cluster of nodes (SSI).
Through some brain fart, they had a hard symbolic link inside their directory to "/bin".
Similar mistake. Restore from tape was necessary.
English

@dani_avila7 More robust: turn on /sandbox and configure it to block the files that are sensitive.
English

If you don't want Claude to read your .env files
Just add this to your .claude/settings.json

Mari@Tech_girlll
DON’T LET CLAUDE READ YOUR ENV FILE DON’T LET CLAUDE READ YOUR ENV FILE DON’T LET CLAUDE READ YOUR ENV FILE DON’T LET CLAUDE READ YOUR ENV FILE DON’T LET CLAUDE READ YOUR ENV FILE
English

@theo Demise of terminals has been predicted many times but they are still here, maybe stronger than ever.
English

@0xTengen_ Why don’t you use Claude’s built-in RAG feature, “projects”?
English

> Claude usage limit reached. Your limit will reset at 7pm
> barely 40 mins in and the context window is already maxed out
> feeding it heavy docs burns tokens like crazy
> paying $200/mo for the Max plan but limits still choke you
> mfw you realize you're paying for the AI's "amnesia"
> discover the notebooklm-py tool by dev Teng Ling
> guy reverse-engineered Google's internal protocols > now you have a CLI to control NotebookLM straight from the terminal
> Google digests up to 50 sources per notebook for free (and 300 on Pro)
> all the heavy research and processing happens with zero Claude token cost
this is pure gold for anyone using Claude Code, read the original article and bookmark it
hoeem@hooeem
English

@mal_shaik You can’t trust LLMs. You need to set up permissions to only allow what you are comfortable for the AI to do. Use /sandbox
English

@aakashgupta The application bundle is read-only. Any data files or cache files created by the application are written to $HOME/Library/Application Support (or Cache) directory. There is nothing that cleans them up. But I guess usually those files are not huge.
English

Let me explain exactly why Apple still uses drag-to-install in 2026, because the joke here accidentally proves Apple right.
A macOS .app is a single self-contained folder disguised as a file. Every dependency, every framework, every resource lives inside it. Drag it to Applications, it works. Drag it to Trash, it's gone. No registry entries. No leftover DLLs. No uninstaller that misses half the files.
Windows installers scatter fragments across Program Files, AppData, the registry, system32, and a dozen temp directories. Uninstalling a Windows app is an archaeological dig. Five years later you're still finding config files from software you forgot you owned.
Linux is worse. Dependency hell is so common they named it. Entire package managers exist to solve the problem of "I installed something and now nothing else works." Flatpak and Snap were invented specifically to copy what macOS bundles already did natively.
The macOS bundle architecture came from NeXTSTEP in 1989. Steve Jobs brought it to OS X in 2001. The core design hasn't changed because the core design was correct. An app is a folder. Installation is a copy. Removal is a delete. Three operations that map perfectly to how humans already think about files.
The drag-to-install window with the arrow isn't lazy UX. It's the entire thesis of the system made visible. You are literally just moving a folder. There is no "installation" step because there's nothing to install. The app is already complete.
Every other OS eventually tried to get here. Windows got MSIX. Linux got Flatpak. Mobile figured it out from day one because phones shipped after Apple proved the model. The pattern everyone else converged toward is the pattern this tweet is calling outdated.
The funniest part: the app being dragged in that screenshot is Claude. An AI that can write code, analyze documents, and reason about complex systems. And the most advanced step in getting it onto your machine is holding down a mouse button and moving your wrist two inches to the right.
That's not a design failure. That's a 37-year-old architecture so good that the most sophisticated software on earth still ships inside it.
Noah Cat@Cartidise
it’s 2026 and this is how you install apps on macOS
English

@PaulTassi I dunno. I pressed the WPS button in my WiFi router and my printer and added the printer in Linux using the built-in GUI. I think it used to be more difficult.
But I agree it still prints on paper using laser like they did in 1980s.
English

@strager > gave complete project
> uses uv, good
> claude, make changes
> leave for a while
> literally uninstalled system python, installed a different version, symlink to it because "python" wasn't working, install global packages manually from pyproject.toml
> nothing works now
English

@Guptha933907 @__karnati Process with that high cpu usage is probably not doing many system calls, so ltrace might be more useful than strace.
English

@__karnati First: top → confirm it’s real
Second: ps -fp <PID> → understand the process
Third: strace -p <PID> → see what it’s stuck doing
No deploy + 14 days uptime screams loop or dependency issue
English

It's 4 am. Your phone wakes you up.
'High CPU on prod-web-01. 98% for 10 minutes.'
You SSH in. The server is crawling.
"htop" shows one process eating 97% CPU.
It's your own application.
There's no recent deploy. Nothing changed.
The process has been running for 14 days.
What are your first 3 commands?
Walk me through your debugging brain. 👇
English
















