177100+ entries in 0.096s
mircea_popescu: good
thing jayz is so very "controversial", i
think ima go buy his album
BingoBoingo: AHA, he is being called out for "feed[ing] into preconceived notions about Jews and alleged Jewish ‘control’ of
the banks and finance." << Jews at Anti Defamation league
mircea_popescu: wait, he's
trying
to
turn
the horde of aging "trynna make it as a pimp" blacks into good consumers with credit cards ?
BingoBoingo: “You wanna know what’s more important
than
throwin away money at a strip club? Credit/ You ever wonder why Jewish people own all
the property in America?
This how
they did it.” << Line by noted White Supremacist Jay-Z
mircea_popescu: "looks like a python
that's
trying
to swallow a buncha smaller snakes"
sina: fair. possible rejiggings on
that
tomorrow
a111: Logged on 2017-07-08 10:54 sina: wasn't as bad as I
thought it'd be
sina: rather each privkey has an additional
top-of-file line which states either "-available", "-bogus" or
the peer name
sina: still needs a
tad work
to make
the code a bit easier
to read and finish model.delete_peer()
sina: wasn't as bad as I
thought it'd be
☟︎ sina: fair. In any case I
think I must retain for
the purpose of "chaff" feature
mircea_popescu: because absence of key is dispositive, whereas scribblings on
the key is at best indicative.
sina: if you're an enemy capable of capturing a gossiptron and knowing of
the
things, why wouldn't you?
sina: in
the model you proposed he would be able
to anyway right, just by seeing which symlinks are in keys/bogus
mircea_popescu: well suppose enemy finds a gossiptron. why should he be able
to
tell which keys were bogus ?
sina: damn.
that would've made my life easier :P
sina: so I guess I do need
to store
them
sina: oh. I might use
them for bogus data sendage
though or something
mircea_popescu: well yes,
the program needn't be able
to distinguish
them from keys generally. bogus is an operator designation.
sina: question: do bogus keys actually need
to be stored?
sina: mircea_popescu: I am guessing
tmsr is not fond of
things like JSON or YAML
☟︎ sina: so in lispland you get
this kind of native ability
to easily export/import primitive datastructures
to disk easily
sina: I dunno much about lisp, but I
think lisp handles
this better in
the sense you write state into
the "lisp machine" and can flush
that entire state out
to disk and read it
therefrom as well?
☟︎ sina: because I definitely remember in
the past
thinking
thoughts along
the lines of "filesystem is a ~btree, rdbms is a ~btree, why am I ~btree on
top of ~btree", and reading discussions about
this
topic on
the internet, and feel like I remember *someone* mentioning something about
this
sina: one interesting
thing is
that I
thought
there would be some databases implemented as flat files, but I can't seem
to find any
mircea_popescu: right. well, do you wish
to acquire some ? ~what
the whole discussion reduces
to.
sina: I just doubt I can impl, e.g.
transactions as well as sqlite guy
mircea_popescu: in which process you will have for
the first
time read and
tried
to understand it, and likely discovered some
things re greatness.
mircea_popescu: it's not directly obvious why it'd be shittier
though. if nothing else, can just cannibalize sqlite code, iuf you
think it's
that great.
mircea_popescu: i am not making you! and if it dun seem like something you wanna do best not
to do.
sina: agreed and understood, I am just subtly
trying
to make
the point of "making me implement a shittier sqlite"
mircea_popescu: sina
they do not protect against
this by design, but by implementation.
mircea_popescu: depending on how
the whole scheme is implemented, yes.
sina: sqlite
transaction for example protect against
this
sina: two assignment attempts might list
the same available key
sina: but
this introduces potential race condition now?
mircea_popescu: sina
to find out which keys aren't assigned you also keep a /keys/available
then
sina: what you said "wish
to find out what key you can assign" is what I meant
mircea_popescu: if you wish
to find out what key you can assign, you gotta enumerate
the db,
though ideally you keep
this in ram rather
than in
the db
sina: no, I want
to assign any available key
mircea_popescu: well, if you wish
to assign a SPECIFIC key,
then you must edit
the /keys/assigned/key.symlink reference
to point
to it.
sina: I dunno about
this suggestion. for example if I want
to assign an available key, I need
to list
the keys in /keys,
then subtract from
that list
the list of keys in /keys/assigned and /keys/bogus ?
mircea_popescu: sina you can just create/edit
the symlinks like any other files.
mircea_popescu: alternatively (and what everyone does) is make pagefiles and read
those.
though...
mircea_popescu: now, whether
this works irl or noit, we do not really know
sina: then I either need
to shell out
to mv/ln
sina: but what about bogus and available keys? keys/available/???.key and keys/bogus/???.key, so
the
two questions would be, 1. what are
they named, 2. how
to
transition states, e.g. from available
to assigned
sina: with
the privkey as
the contents of
the file
sina: for
the assigned keys, it seems fine
to have a directory like key/name_of_peer_assigned.key
sina: so
there are 3 "states" for a key, 1. available, 2. bogus, 3. assigned
sina: cool, appreciated. so I currently have 3
tables: keys, peers, messages. let's start with keys I guess.
sina: mircea_popescu: do you have 5-10m
to discuss
the filesystem
thing re gossipthing
sina: for now it's set
to clean up anything older
than a week every week
sina: not right
this second, hold pls
sina: alright, now back
to my /tmp dir
to
try and prototype a fs based
thing
sina: looks like
this now: 2017-07-08 05:54:50|delivered_by:*local|sender:sina|hello world
sina: fair. names are limited currently
to [a-zA-Z0-9_]+
mircea_popescu: prolly limit names
to alphanum and
then use eg "*self" or somesuch is
the approach.
sina: mircea_popescu: "self" just signifies
the message was published into
the local messages list by
the local client itself. suggestions are open for other ways
to signify same, e.g. if you
think
the entry should simply be blank
a111: Logged on 2017-07-08 01:11 mircea_popescu:
the amusing part not yet picked up (i was expecting alf
to jump) is
that... it has inband encoding. "self" is a special word!
a111: Logged on 2017-07-08 02:35 sina: and you contend
the actual final implementation of such a
thing will actually be less lines of a code
than
the existing
thing
a111: Logged on 2017-05-19 17:22 asciilifeform: in other news, a 4096-bit A**B
takes approx 14 seconds (3GHz) .
mircea_popescu: geting hard numbers on file system performance, something everyone involved in data storage for
the past 30 years has been vehehehery deliberately hiding, is certainly better use of
time
than, for instance, attempting
to reason with djb jzw & all.
mircea_popescu: there's no "best use of measurement" for exact same reason
there's no "wot best practices", or "ideal rng values"
mircea_popescu: it is fundamentally, and irrecoverably, flawed. measurements are
the only basis of
thought.
mircea_popescu: there's nothing wrong with measuring
the world around. an attempt
to explain why
this is a waste of
time isn't really going
to be entertained.