427300+ entries in 0.271s
BingoBoingo: CIA cuts coke with
talcum for private sector partners?
mircea_popescu: 2. Next Generation Cyber Initiative (Next Gen Cyber) received USD$ 400.6 mn in
Treasury funding in 2014 alone, which was used
to employ 1`333 full-time positions including 756 agents.
punkman: "Next Generation Cyber Initiative (Next Gen Cyber) received USD$ 400.6 mn in
Treasury funding in 2014 alone, which was used
to employ 1`333 full-time positions" << really?
they couldn't have hired 4 more?
trinque: BingoBoingo: "As if so often" <<
typo
decimation: as a long
time user of RPN calculators I do indeed find forth pleasing
BingoBoingo: I me probably not going
to intentionally acquire cat until possesses farm.
trinque: he challenged me
to a game of "lemme
try an' cut you" and I lost
BingoBoingo: mircea_popescu: Given
the duration seems like
they succeded closer
to 1 in 4 or 1 in 3
mircea_popescu: BingoBoingo "ddos" is you know, best effort kinda deal. just because you can't get
through in 5
tries doesn't mean every one of
the 50k or whatever many
tries also failks.
trinque: mircea_popescu: yep
that sounds fine
mod6: <+asciilifeform>
them &
the grapher. << i can live with
this.
trinque: that actually works fine for me as a separate
tool, and as you say, if
there's a wiki, great
assbot: Logged on 05-08-2015 21:50:41; mircea_popescu: but i guess
the consensus is pointing
towards, ml gets restated with antecedents,
trinque writes a grapher for it all ?
mircea_popescu: so wait, are we upon meditation now unaccepting
the previous consensus-y spot ?
trinque: need
to document process at a step? go for it, it's a damn wiki
BingoBoingo: And somehow 9 comment spammers made it
through DDoS
trinque: I actually grow
to like
the wiki suggestion best for
the patch
tree
trinque: you've got "who signed
this patch" and also "what is
the parent node patch of
this patch"
trinque: one
tangle is
the lack of clear separation of problems in
the conversation.
assbot: Logged on 06-08-2015 01:59:06; *: BingoBoingo
thinks whole problem is
that 'patch' demands line numbers instead of using nearby lines of code as landmarks
mod6: i just figured it was a neato way
to keep
the patches
that we sign separate from
the rest of
the heap of stuff.
mod6: no different
than what we're already doing.
mod6: <+mircea_popescu> moreover, it just puts you in harm's way mod6. << well. not all patches, just ones
that we've signed off on anyway.
assbot: Logged on 06-08-2015 01:51:35; mircea_popescu: asciilifeform
truth be
told : do you find
this interesting for any other reason
than
the vague whiff of a promise of perhaps allowing you
toi make btc chips /
mircea_popescu: what, now you're oBLIGEd
to sign shit so people can use it ?
trinque: just a hash of
the content aside from
the sig
trinque: this grouping
together of
things signed can be done with deeds as
they are
punkman: not
that I'd mind patch deeds, but can basically deed patch hashes already
mod6: well, nevermind
then.
mircea_popescu: "Bacteria have no junk in
their DNA. " << very false, actually. percent-wise,
the junk-in-dna is perhaps
the most stable parameter of life in general
punkman: I don't see how deeding patches helps with what started
this discussion
mod6: on
the other side of
the coin, if we do something like
this with deedbot, we need
to ensure a mirror is always available.
mod6: so i guess all in all,
the deedbot solution, if it can be created, seems better
than my initial proposal of 2 mailing lists; one for everything, one for patches accepted only. which seems simple as well, but now we have
to manage
two lists.
trinque: punkman: yup
that's precisely what's being discussed
mircea_popescu: asciilifeform ok. i both read
this before and i broadly agree with
the man.
trinque: neat
thought; I can see something useful
there for contracts generally
mod6: maybe something can be added? like
trinque is saying? i dunno.
mod6: i guess
this
thought was sort of a work in progress.
trinque: that calls for a second screen which would group by deed and list
the sigs
mod6: that way it sort of also solves
the problem of keeping
track of who signed which patch. since deedbot stores
these sigs in a horizontal fashion next
to
the address.
BingoBoingo thinks whole problem is
that 'patch' demands line numbers instead of using nearby lines of code as landmarks
☟︎ trinque: mircea_popescu: he's considering a case where
the
thing would be able
to accept new detached sigs for existing deeds
mod6: oh, i
think he was saying
that he would need
to implement accepting a second argument and making it so
that
the URL contains a hash of
the original plaintext patch.
mircea_popescu: "Good Forth programmers reportedly don't use much of
those. Good Forth programmers arrange
things so
that
they flow on
the stack. "
this is mel redivivus innit. most pessimum!
mod6: trinque
thinks
this might be able
to be implemented without moving heaven and earth
mod6: but what if we
then, say, at
the end of a
testing/release cycle were
to (instead of signing or as well as posting
to
the mailing list) post
the plaintext patch and a detach signature from
the originating author, myself & ben
to deedbot as a perm storage for
these patches?
mod6: ok so was kinda
thinking about something here... so we all love
to hate
the mailing list in a way - but it's a decent spot
to post new
things, experimental, SoBAs etc. But it's not good for keeping
track of patches
that /actually/ are accepted and a part of a given "release".
mircea_popescu: asciilifeform
truth be
told : do you find
this interesting for any other reason
than
the vague whiff of a promise of perhaps allowing you
toi make btc chips /
☟︎ Adlai: being able
to grow a beard should suffice
mircea_popescu: i have
to know
the ascii value of )
to code in forth ?
BingoBoingo: But I am in
the process of dancing with university
to set up job interview, so may have fiat stream
to start burning soon
BingoBoingo: mircea_popescu: It appears years in
the future. I imagine Adlai will prolly get an emacs client first. Or I'll get a sacrificial linux machine first (sacrificial linux machine is
tiered below box
to colo cheap for infrastructure BTC node).
mircea_popescu: "My VLSI
tools
take a chip from conception
through
testing. Perhaps 500 lines of source code. Cadence, Mentor Graphics do
the same, more or less. With how much source/object code?"
mircea_popescu: BingoBoingo chetty spent
two years for a result in parts no different.
BingoBoingo flipping
through Eulora source can make no sense of what files do what. It is nothing like Bitcoin which is
the only big cpp
turn I am kinda familiar with.
mircea_popescu: but it does seem
to me very much akin
to a "hey, if you salt a fresh frog leg you can electrocute it into moving". cool! but instead i order my slaves
to read and summarize for me!
BingoBoingo: Forth looks incredibly legible. More so
than cpp
BingoBoingo: asciilifeform: Probably only on PPC. PPC got a lot of cool stuff. Perhaps not across whole PPC run
though. Will have
to look into.
BingoBoingo: <asciilifeform> resistance of
the medium << Is
there any other reason
to ever do anything?
mircea_popescu: problem is sapper keeps
trying
to change profession into me
mircea_popescu: sit
there and debug off-by-one errors in a pile of asm ?
assbot: Logged on 20-06-2015 01:37:28; asciilifeform: phun phakt: 'scheme' programming language has its 'call-with-current-continuation', perhaps
the oddest and 'most generic' control structure known, which
takes
the current place in execution and
turns it into an assignable (yes) closure (i.e. callable function!) --
typically it is implemented using setjmp().
mircea_popescu: why would i make a "construct" in
the language
that does i+2
mircea_popescu: "If you can write 'if' in FORTH,
then why restrict 44 yourself
to
the usual if/while/for/switch constructs? You want a construct
that iterates 45 over every other element in a list of numbers? You can add it
to
the language."
BingoBoingo: I
think it makes sense for node operators
to come
to agreements
to make some of
their connections
through SSH
tunnels.