home | log | search | bash | stats | wiki


Matches for pogo, 947 total results Sorted by newest | relevance

Mon Apr 06 01:21:47 UTC 2015  <mircea_popescu>   http://log.bitcoin-assets.com/?date=05-04-2015#1089515 << a man with just one pogo is like the woman trying to get pregnant off a single spermatozoid.

Mon Apr 06 01:21:47 UTC 2015  <assbot>   Logged on 05-04-2015 19:39:37; ben_vulpes: me pogo's at the office

Sat Apr 04 05:00:43 UTC 2015  <asciilifeform>   (pogo, heathen linux, pseudostatic, modified skull'n'crossbones)

Sat Apr 04 00:59:33 UTC 2015  <asciilifeform>   ^ for anyone who thought 'eh why do we need static anyway, at the very least on pogo'

Fri Apr 03 19:08:49 UTC 2015  <asciilifeform>   like i do on 'pogo' builds.

Fri Apr 03 19:07:04 UTC 2015  <asciilifeform>   (typically it contains a thing that can be booted from and ends up living in ram, like my pogo 'turdel')

Fri Apr 03 15:09:41 UTC 2015  <asciilifeform>   ;;later tell nubbins` can't felch it from the OS at runtime? << os does not know your external ip, if you are behind a nat. as, e.g., a pogo is overwhelmingly likely to be.

Fri Apr 03 03:25:55 UTC 2015  <asciilifeform>   but to cross-compile for normal machine (ibmpc, pogo, vax, whatever)

Wed Apr 01 20:31:06 UTC 2015  <pirateat40>   mircea_popescu: if exactly same, then will. this is kinda my notion with 'pogo'.

Wed Apr 01 20:27:21 UTC 2015  <JeredKenna>   ascii_field exactly. which is why i said, "when confronted with a bad software stack (pick a pogo, fix the os, run it there) is the correct solution not just for THAT one problem but for all the problems derived from the same source."

Wed Apr 01 20:20:13 UTC 2015  <gavinandersen>   and so what we're essentially doing when confronted with a bad software stack (pick a pogo, fix the os, run it there) is the correct solution not just for THAT one problem

Wed Apr 01 19:17:32 UTC 2015  <ukyo>   it's their pogo

Wed Apr 01 18:06:09 UTC 2015  <OgNasty>   ascii_field: pogo or...?

Wed Apr 01 01:54:07 UTC 2015  <pirateat40>   nubbins`, http://danielpbarron.com/pogo-build.sh.txt

Wed Apr 01 01:38:49 UTC 2015  <Shtylman>   iirc ascii mentioned it, said he'd maintain the pogo project. it's not a horrible idea.

Wed Apr 01 01:33:55 UTC 2015  <gavinandersen>   not sure if he's targeting the same, or the pogo via portatronic

Wed Apr 01 01:31:55 UTC 2015  <Inaba>   ironically enough, the same computer that successfully built bitcoind for pogo way back when the project first began

Sun Mar 29 18:52:37 UTC 2015  <asciilifeform>   nubbins`: speaking of 'pink pogo' here

Sun Mar 29 18:51:29 UTC 2015  <asciilifeform>   for instance, there was at one point a pogo entirely like this one but 256M.

Sun Mar 29 18:51:24 UTC 2015  <mircea_popescu>   nubbins` we can now just capture the packets and "activate" any pogo anywhere on the basis of another pogo can't we.

« Previous Page    Next Page »