# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 15
# self = https://watcher.sour.is/conv/gzzdgpa
The day will come when I’ll have to dig up *why* every process can interact with every other process’s file descriptors by means of /proc/$pid/fd on Linux (if it’s the same user). Is there a legitimate reason for that … ? (I know about hidepid, but that doesn’t help here.)
The day will come when I’ll have to dig up *why* every process can interact with every other process’s file descriptors by means of /proc/$pid/fd on Linux (if it’s the same user). Is there a legitimate reason for that … ? (I know about hidepid, but that doesn’t help here.)
The day will come when I’ll have to dig up *why* every process can interact with every other process’s file descriptors by means of /proc/$pid/fd on Linux (if it’s the same user). Is there a legitimate reason for that … ? (I know about hidepid, but that doesn’t help here.)
This is why the PID Namespace controller exists in Linux 👌
This is why the PID Namespace controller exists in Linux 👌
This is why the PID Namespace controller exists in Linux 👌
@prologic Hmm. That would require me to put each and every process into its own namespace, wouldn’t it? I don’t think that’s practical. 🤔 Or maybe I’m misunderstanding.
I’ve never really thought about this, to be honest. There’s no procfs on the BSDs, so I guess that a) it’s not really necessary, b) there should be plenty of rants from BSD users on this issue that I could read. 😅
@prologic Hmm. That would require me to put each and every process into its own namespace, wouldn’t it? I don’t think that’s practical. 🤔 Or maybe I’m misunderstanding.
I’ve never really thought about this, to be honest. There’s no procfs on the BSDs, so I guess that a) it’s not really necessary, b) there should be plenty of rants from BSD users on this issue that I could read. 😅
@prologic Hmm. That would require me to put each and every process into its own namespace, wouldn’t it? I don’t think that’s practical. 🤔 Or maybe I’m misunderstanding.
I’ve never really thought about this, to be honest. There’s no procfs on the BSDs, so I guess that a) it’s not really necessary, b) there should be plenty of rants from BSD users on this issue that I could read. 😅
@movq Yes but this is easy with unshare
@movq Yes but this is easy with unshare
@movq Yes but this is easy with unshare
@prologic Hmm, I’ll have to look into it. 🤔 Probably not what I meant, but interesting nontheless. 👍
@prologic Hmm, I’ll have to look into it. 🤔 Probably not what I meant, but interesting nontheless. 👍
@prologic Hmm, I’ll have to look into it. 🤔 Probably not what I meant, but interesting nontheless. 👍