1300+ entries in 0.033s
phf: i
http://btcbase.org/log/2017-03-01#1620670 << i've had similar experience before. girl does that "can i be an extra person in your tribe" thing, hovering, circling, eyeing. so me and my girl will approach, just for the girl to run away in panic. we call it gazel hunting. i've noticed the more "selling it" girl looks, the more likely she's to panic when approached by guy AND girl. incidently i don't know any strippers who look like strippers off work. but i've m
☝︎☟︎ phf: i kind of want a way to link useful assets to a patch on btcbase. right now if you have a readme.txt inside a patches folder you get that included as a prelude for a patchset (
http://btcbase.org/patches?patchset=fg). i think it would be handy to include wires over ssh link somewhere on the wires patch page..
phf: unrelatedly, someone ported franz's clim2 to ccl, but instead of using ffi to motif backend, they used an original generas clx backend, that is still there. the result is ugly, broken on mac's x11, but works, and potentially could be improved and optimized by interested parties.
http://glyf.org/screenshots/clim2-clx.png phf:
http://btcbase.org/log/2017-02-16#1614694 << i watched a lot of "classics" in pirate quality, and i prefer it that way. notorious example is Alien, where between the original print and the pirate shit copy you could barely see anything, which made the experience more terrifying.
☝︎ phf:
http://btcbase.org/log/2017-02-10#1613027 << i was waiting for that. first article i open mentions that the gold is there to put it out of moscow's reach, mentions european financial troubles and the lack of trust in trump in three paragraphs. almost can admire the fuckers, sort of like reading particularly gnarly piece of soviet propaganda
☝︎ phf:
http://btcbase.org/log/2017-02-10#1612963 << mosh works over udp, and mitigates latency, dropped packets, and interrupted connection all the way to doing transparent roaming, so benefits are only seen on hardware in question: can still do useful work even over very dodgy connection
☝︎☟︎ phf:
http://btcbase.org/log/2017-02-10#1612714 << is handy, but i can't bring myself to replacing safety critical ssh with it. i've had plenty of opportunity to test it though, and it's best option for when you're trying to connect to server over a public wifi running over cell network off a generator
☝︎ phf:
http://btcbase.org/log/2017-02-07#1612232 << umd is a giant h1-b clearing house, when you take away that, there's nothing left. at a recent career fair i saw huge lines of azns and indians at google and facebook booths ("our wait time finally dropped below an hour so i could get away and grab lunch")
☝︎☟︎ phf:
http://btcbase.org/log/2017-02-07#1612175 << if we're sticking to unix, should really be able to specify which random device to use, with /dev/random being fallback. of course they Solved it on Plan9 (tm), you can bind whatever endpoint as /dev/random in your process
☝︎ phf:
http://btcbase.org/log/2017-01-27#1608382 << this is the official acknowledgement of the receipt. likewise i saw it the first two times you posted it, but didn't realize that writing the nth copy of the logreader that you embarked on is a high priority republic business. seriously, what's with the attitude?
☝︎ phf:
http://btcbase.org/log/2017-01-24#1606341 << optimization strategy is when you have a slow algorithm somewhere in your architecture (you put it there because it was a reasonable tradeoff at the point), but you can replace it with a faster algorithm without leaving too much damage on the architecture (alf calls it "scaring")
☝︎☟︎ phf:
http://btcbase.org/log/2017-01-23#1606170 << no, and i think it's a combination of "scaring" and complexity. takes a lot of effort to build one from scratch. clim's beach actually tried building one, SICL
https://github.com/robert-strandh/SICL which is closest to "compartmenalized", but i'm not sure where it is. probably heavy WIP stage. (and reading the ilc slides it seems like it's beach/mcclim style overengineered)
☝︎☟︎ phf: apropos,
http://btcbase.org/log/?nick=phf will highlight all the messages from and to nick (it's half baked, like it doesn't get preserved when you switch pages, but i have the logs bookmarked that way, so that i can see if i got mentioned at a glance)
phf:
http://log.mkj.lt/trilema/20170120/#295 << i can also just expose a heartbeat endpoint (or even a udp port) that scriba can check at interval. can also have a heartbeat pm. a111 gets a PING message from scriba, responds with PONG
phf:
http://btcbase.org/log/2017-01-14#1602646 << actually this makes no difference if i do or if i don't. the correct solution that's sitting on my laptop is to explicitly check for exhaustive anticedents, and then render a missing link if there's one missing
☝︎ phf: typically people recommend
http://www.gigamonkeys.com/book/ and it's a sort of "rails for beginners" kind of book, but i think best cl option is
http://www.norvig.com/paip.html. norvig's paradigms of artificial intelligence programming. it's not so much about "ai", but about some very useful symbolic algorithms, written in ~very elegant~ lisp code
phf:
http://btcbase.org/log/2017-01-08#1599317 << actually btcbase is broken in that respect. i keep filename from the first appearance, and then track hunk relationship through hashes only. which will break if there's hash collision
☝︎ phf:
http://btcbase.org/log/2017-01-08#1599371 << i've been thinking about this problem, because range select is very handy, but i haven't figured out a way to make it not confusing. specifically the "stickiness" where you catch a range and can't get rid of it. can implement the traditional select semantics like shift-click to activate a range?
☝︎☟︎ phf:
http://btcbase.org/log/2017-01-07#1598294 << scheme83 is like a "canticle for leibowitz" artifact. "published design" is overstatement of the century. scraps of published memos and reports spread over out of print conference proceedings, the bulk of actual technology needed to recreate probably somewhere on a TAPE. i don't know where you got that mask generator runs on scheme83. the entire production stack was for mit cadr
☝︎☟︎ phf:
http://btcbase.org/log/2017-01-07#1598258 << you know those guys that periodically stop by lisper venues, and they don't really program, but they want to use LISP to build an AI, because metacircularity of code is data is giving them mystical visions..?
☝︎☟︎