700+ entries in 0.031s
phf:
http://btcbase.org/log/2018-05-29#1819414 << i could never understand the charges: i always thought that bateman was very earnestly participating in all the games, but it's the world around him that was completely devoid of substance
☝︎☟︎ phf:
http://btcbase.org/log/2018-05-23#1817823 << the taps you're using are for previous release of eulora (which already had some odd issues on mac, but worked). i took a stab at updating them when the latest release came out, and enough targets moved that it was again non-trivial to build the stack. i've managed to hand build it/jerry rig homebrew to build it, but the result out of the box was working even worse (mostly i lost textures entirely). around t
☝︎ phf:
http://btcbase.org/log/2018-05-23#1817293 << i started writing a lispy make-temp-directory but the implementation is not particularly elegant (C concerns are at odds with lisp concerns), you can pouch the ccl bits though. i'm not sure if there's a better way to do errno handling, without relying on private ccl symbols
☝︎☟︎☟︎ phf:
http://btcbase.org/log/2018-05-22#1816718 << hah, i originally watched it for the same reason, and the only thing i even remember is burroughs sitting in the chair, and spitting the "narcotics" prediction in his famous squeaky voice
☝︎☟︎ phf:
http://btcbase.org/log/2018-05-21#1816308 << is there any need for that alternative? from my research static inline is one of the few behavioral commonalities between c99 and pre-c99. it also supposedly works across different compilers, etc.
☝︎☟︎ phf:
http://btcbase.org/log/2018-05-01#1806905 << well my fiat responsibilities are disrupting any kind of reasonable scheduling. i'm not 9 to 5, my fiat work goes through periods of heavy activity that are aligned with particular industry. and right now it's a particular mess, owner had a baby 3 weeks early, 2 weeks ago, another c level is having a baby in a week, and we're in the middle of a release. previous republican work was kind of cutting into some
☝︎ phf:
http://btcbase.org/log/2018-04-30#1806496 << first world "men" don't understand the concept of hygiene, i suspect that as the infrastructure starts failing this would be the number one reason of rapid decay. hygiene not just in a sense of "washing hands", but the idea that there's certain procedures that you have to follow in order to not get fucked over by the environment
☝︎☟︎ phf:
http://btcbase.org/log/2018-04-26#1805634 << i emailed chromeunboxed.com guy "Robby Payne" on recommendation "they will know", haven't heard anything back. actually first time i cold called an online "specialist", not going to try that again
☝︎ phf:
http://btcbase.org/log/2018-04-27#1805906 << asdf3 is pretty much standard in all the lisps right now, you have to go out of the way to downgrade. at the very least avoid implicit uiop dependency and declare it in your asdf file (this is by the way even fare's recommendation, but people ignore it "oh i have asdf3, means i can just throw a sneak uiop:foo all over my code)
☝︎ phf:
http://btcbase.org/log/2018-04-24#1805075 << i did a first pass on the spec over the weekend, but haven't had time to formulate my thoughts. it looks like enough to do a prototype short of three things: handshake process is still work in progress, i noticed that it's missing type of data descriptor values for 4.3.2 (there's a list of data types, but not the values that indicate which type it is), and there's no format description for the encapsulated f
☝︎ phf:
http://btcbase.org/log/2018-04-20#1803946 << that's a good idea, there are different use cases though. i speak much less, so i use the yellow islands to know where i participated in the conversation, this way i know i don't have to reread that whole cluster. it highlights both from:phf and "phf", so i can also say where i was mentioned since the last time i spoke
☝︎ phf: !#s from:ascii refs:5 not:achtung "
http"
phf: !#s from:phf "
http" not:btcbase
phf:
http://btcbase.org/log/2018-04-19#1803375 << i have ipsec subnets to essentially identical openbsd installs, but egress is to wan. i use pf to route specific things through the ipsec subnets. i've never benchmarked it though. it's good enough to watch an occasional regioned youtube, or pull a torrent at 5mbit saturation
☝︎ phf: mircea_popescu: i've been searching from:<nick> "
http://" as a way to remind myself who is who
phf:
http://btcbase.org/log/2018-04-09#1794530 << you can see two lines going into vtools_fixes_static_tohex, one from vdiff_fixes_newline_gcc and another from vdiff_sha_fixes_newline_gcc. they are both from 98BA and either should satisfy the requirement. the other two lines in are from vtools_vpatch only for 7EBF and 02A0.
☝︎ phf:
http://btcbase.org/log/2018-04-06#1793785 << items predates melpa by many years. i suspect first serious item to rely on gnutls was GNUS, but initially integration was done by calling a subprocess and piping things into it. gnutls (as well as dbus, libxml, imagemagick) as linked in library is a more recent phenomenon
☝︎ phf: i believe rainer joswig hosts his websites on some arm box with CL-
HTTP on top of it
phf: trinque: have you seen
https://masteringpostgresql.com? it's by dimitri fontaine, who's a major postgresql contrib, but he also wrote pgloader, a proggy for etl into postgresql, which he wrote in common lisp; you get mentions of clos and naggum and such in his book.
phf: mircea_popescu: the conversation from which you quote the money shot happens in the context of file renames, the part where you call upon me quotes keccak specifically, elsewhere you re-enumerate the list of what looks like target items,
http://btcbase.org/log/2017-12-14#1751799 ☝︎ phf:
http://btcbase.org/log/2018-03-30#1791280 << it's an oversight. i thought that the idea is that my vdiff/vpatch support programmatically whatever manifest format we come up with, but somebody demonstrates how it's supposed to work first. it's not hard to regrind existing tree, manually add a manifest, and then see how it looks on a graph. for some reason i thought that trinque has that experiment in his pipeline, since he also seems to have a clear ide
☝︎ phf:
http://btcbase.org/log/2018-03-30#1791198 << there's already a generation of kids coming up for whom alt-right/feminism is what old people do; they want to be able to post fashwave pictures, while remaining mostly pantsuit. for them facebook/twitter is where they maintain public teacher/parents friendly identity, and mastodon/discord is where they can be themselves. it's basically just another wave of social networks.
☝︎ phf:
http://btcbase.org/log/2018-03-30#1791228 << i'll publish the relevant patchsets on btcbase this saturday; i've read the relevant specs and the issue seems to be straightforward, what is annoying though is that for whatever reason it's not uniform across platforms.
☝︎ phf:
http://btcbase.org/log/2018-03-26#1789697 << not as hot as palm springs (which is full blown summer at this point), but basically spring. it was raining last week, but right now it's a shirt weather. if you're close to the ocean, then it's blowing cold wind. what i'm trying to say is that the weather is excellent, and i'm loathing going back to the swamps.
☝︎ phf:
http://btcbase.org/log/2018-03-19#1788278 << i've discovered similar, my 3g phone barely has signal and doesn't last more than a day in san francisco. presumably because the number of 3g supporting towers is significantly lower here
☝︎☟︎ phf:
http://btcbase.org/log/2018-03-08#1787317 << дневник as typed with jcuken but on a qwerty layout. it's an old derogatory runet term for diary writing, but in this case it's the default category i use that i forgot to change
☝︎ phf:
http://btcbase.org/log/2018-03-13#1787751 << oh duh, missed opportunity. i thought the idea was to integrate trinque's design into code where appropriate, but it makes sense that i could've just used the design for my release.
☝︎ phf:
http://btcbase.org/log/2018-03-23#1789396 << i already fixed it, but took longer than usual because there was a new issue, i haven't seen before. when bot recovers, it asks additional sources for missed messages, which uses timestamp amongst other things for fuzzy merge. the drift between servers exceeded the hardcoded 15s, so the merge was failing out on asserts. goes back to the ntp threads
☝︎ phf: spyked reported another C attribute annotation issue since then
http://btcbase.org/log/2018-03-01#1786600 , but it's yet another compiler/system combination problem, and those who managed to build c vdiff previously should be able to do so still (sans the noreturn and 'no newline' issues)
☝︎