The more I think about it, the more I like the idea of interfacing with APIs using the filesystem - the world needs more FUSE apps
-
-
Replying to @yoshuawuyts
not sure that FUSE is the best way though -- I hear it causes kernel panics on OSX
1 reply 0 retweets 1 like -
Replying to @hackergrrl @yoshuawuyts
I've been using named pipes and userland programs for this instead: https://github.com/noffle/twitter-fifo …
1 reply 0 retweets 1 like -
Replying to @hackergrrl @noffle
ohhhhhhh, yesssss - I like this approach very much!
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
it's more limited, but way more stable than fuse and no extra system packages needed
2 replies 0 retweets 0 likes -
Replying to @hackergrrl @noffle
feel that would be great for streams of all sorts; imagine feed readers, databases commands, etc - I love love love this concept
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts @noffle
named pipes are super cheap perf-wise right? Goes through a virtual device in /dev or smth right?
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts @noffle
oh man, custom user group for an application; gets a bunch of named pipes in the dir; chroot and only access those files - extra sec
1 reply 0 retweets 0 likes
but even without chroot - just having all bits that an application touches in the same repo is sooo good for discoverability
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.