103500+ entries in 0.063s
trinque: aha, deedbot also will not eat more
than 20 entries from a feed at a
time
trinque: the bot's "seen" is based upon
that
trinque: asciilifeform: what's
the value in
the <id>
tag on your end? RSS decrees
those don't repeat
mircea_popescu: doesn't have
to overflow ; have it wait 1s between reports.
mircea_popescu: and yes now it feels like it's an actual republican item rather
than ductape-and-windoze press a key and go draw a bath.
mod6: The Exalted Great Lord Me etcetera You're
too old for me, sorry. << lmao
mircea_popescu: tbh i'm very happy
to have
this item back, i can now search for keys again!
trinque: I'll digest more and probably have more proposals for ya, but will get my hands into
the code myself
too, and we'll get a genesis of
this put
together.
esthlos: cool,
that's agenda item 1
trinque: not detracting from your having put in
the work so far, glad
to see a lisp V.
trinque: moving from printing
to returning objects (recall, you can inform lisp ~how
to print your objects at
the repl) would be a huge improvement
esthlos: if you do so before friday, I can likely get a prototype by monday. otherwise it will be sometime
the week after
esthlos: so
trinque, can you provide me with a list of changes (or write your own and diff, if you prefer)?
trinque: I agree
that
this
thing can get smaller, just not by pretending lisp is scheme. write it like scheme and we're all damend
to learn your particular idiosyncracies.
trinque: the idea is
to produce an item
that implements
the (sorely needed!) functionality correctly, and not as entertainment for one developer
esthlos: I was
thinking of replacing
the CLOS with records, or possibly just sexprs
trinque: make something
that eats, processes, and returns sane datastructures first
trinque: you
then
take
that item and make it read console args, print
to screen, whatever
trinque: thing needs
to be refactored with
that in mind
trinque: considering
that
there may be other lisp programs
that want
to use
this as a dependency, it'd be really nice if instead of returning nils, printing strings, you returned a list of vpatch objects.
trinque: don't get
too excited; I've got plenty of feedback for you on how
this is written
mircea_popescu: and yes, you've got clear way here
to producing a standard item, so burn rubber baby.
esthlos: esthlos-v doesn't
touch on (a); I was indeed waiting for standardized philosophy file format. (b) I will
test
mircea_popescu: i vaguely recall us discussing
the matter of graphing and my saying "hang on, phf is about
to write one
then you can import it", but not worth spelunking for it right now.
a111: Logged on 2018-04-09 04:25 hanbot: phf et al: attempted
to press latest vtools
to
the keccak head. v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command). v will press
to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
a111: Logged on 2018-01-23 14:28 mircea_popescu: esthlos it is not standard procedure ;
the emerging consensus is
to have a dedicated philosophy file which a) all patches must
touch (by protocol) ; b) contains comments as
to
the patcher's state of mind and c) contains one line per patch uniquely identifying it, machine generated.
the format's not fixed yet, but as phf is working on a new proper vdiff it's probably going
to coalesce around a variant of whatever he uses.
esthlos: I'm fairly beginner, don't know many of
the useful functions
trinque: but
that can be cleaned up
trinque: yeah,
the lisp is a little green
a111: Logged on 2018-05-01 16:29 mircea_popescu: but we have esthlos waited on a fix, and
then
there's whatever you were waiting
to publish. so i'm guessing it'd have
to be one of you.
mircea_popescu: just in case you're still belabouring under
the misapprehension
that
the usg puppet show is a "field" with "experts" and whatnot,
that is.
mircea_popescu: unless you bother
to actually find and edit
the magic numbers and recompile, which is about on par with rewriting
the damned
thing.
mircea_popescu: asciilifeform, i'm certain
this is not something postgres can do.
mircea_popescu: "determination is orthogonal
to correctness, elementarily" << fortunately, determination is not an elementary item, but can be further broken down and classified.
there's
the sort of determination resulting from narcissism, where it is simply fueled by
the [perceived] cost of changing
the other side, "what do you mean my model of sexuality and society is wrong,
this'd mean i'd have
to have a long
talk with
the woman in my hou
a111: Logged on 2018-05-02 05:26 mircea_popescu: !Qlater
tell bingoboingo is
this right, 3035+3058 ?
a111: Logged on 2014-08-25 03:08 asciilifeform: busy as a bee << funny
that
they show an idiot sow scrubbing, and not, e.g, paul erdos crapping out
theorems
lobbesbot: BingoBoingo: Sent 11 hours and 20 minutes ago: <mircea_popescu> also were
there errors
to be rectified from b4 or anything ?
lobbesbot: BingoBoingo: Sent 11 hours and 21 minutes ago: <mircea_popescu> is
this right, 3035+3058 ?
a111: Logged on 2018-05-02 05:27 mircea_popescu: !Qlater
tell bingoboingo also were
there errors
to be rectified from b4 or anything ?
trinque: nah not in
touch.
told him he was among
the worst leaders I'd ever labored under, and
that was
that.
trinque: sure, and
this was a guy
that was spending his own money because "eventually we'll figure out what
to do with UX"
trinque: postgres can serve up "materialized views" pretty damned fast;
that's what would've been
the caching solution, similar
to what's done with webshits currently
trinque: made no attempt
to solve many unavoidable problems, in pursuit of desired "UX"
trinque: whole project started at far
too high a stack of chairs, atop postgres, browser, etc
trinque: nodes can also describe
transformations from one schema
to another, so your "post"
table's cols map
to mine via a given function
trinque: taking
the simple case of a blog, node serves up a metadata endpoint
that says "posts, comments, etc" and
their structure. client can
take suggestion from
the server on how
to display
these, or can use whatever it likes on its end instead.
trinque: it's amazing how much gabriel_laddel reminds me of an old boss. nearly drank himself
to death, grand mission
to
turn
the www into a distributed db.
the obsessive ones like
this only get un-stuck by
the
threat of death, which is why
they
try as
they might
to impose it upon
themselves.
spyked agrees. and also wonders why
the whole "cloaks are a privilege handed by fleanode staff" etc. still, uses
the bit above for
the
time being and would have been odd
to keep
to himself.
mircea_popescu: spyked,
there's about 0 interest in importing nickserv behaviours as some kind of perpetual legacy.
spyked: from what I understood, he measured all of
them by filming
the keypress-to-screen latency with a high fps camera.
though
this begs
the question of what even means "keypress registered" in case of software kbds. at least he put
the
touchscreens in another
table.
spyked is of course curious
to hear if
this is considered an anti-feature by republican standards. but has used it for a while now.
spyked: lobbes, in general nicks grouped under a user might inherit other properties (e.g. op privileges), but I'm not sure whether
this has any utility for bots. I only used it as a very cheap way
to get cloak for bots,
though probably
the correct approach would be
to register a user per nick.
lobbes: I'll probably be splitting lobbesbot into several seperate bots over
the coming months/year, so now I am curious
lobbes: Neato spyked.
Though, I'll be honest, I don't
think I've ever grouped nicks under a user via NickServ. Besides
the cloaking, what other utility is
there
to grouping in
this way?
spyked: given
the growing number of args, I'd rather personally have
them all be keyword args.
spyked: I've added
the "user" slot as a keyword argument
to highlight optionality, but not sure whether
this is
the right way
to go about it.