242500+ entries in 0.148s
mircea_popescu: Framedragger i've not yet got
through
the log because parsing
threw exception on
that line i quoted :D
a111: Logged on 2016-11-19 16:52 Framedragger: asciilifeform: at least with public-static and phuctor boxes being separate, you'd have access
to
the latter if it were private. (but i guess you could object with "private/undisclosed box on
the internet, what is
this oxymoron!")
mircea_popescu: they really couldn't, and didn't, give a shit about phuctor working
throughout
the years it worked.
mircea_popescu: and
the ONLY
thing
that interests
the shitgnomes is display.
Framedragger: to
the point of having a ready-made system image (no, does not imply need
to use docker), deployable at vps center in a matter of minutes.
mircea_popescu: yes, but
there are
two concerns
that are separable : a) flood stops processing and b) flood stops display.
Framedragger: (by other people's sites i mean sites
that i'm responsible for.)
Framedragger: because 1) other sites' experience may be impacted, and 2) phuctor db would place some load on
things. why = because i'd create a few indices,
those would hog some memory, and assuming users want
to do quite a bit of sorting etc, would
take some cpu
time as well. just sayin'. nothing scientific.
mircea_popescu: asciilifeform
the wisdom of having
the data in a cheap vps is becomingf ever more apparent.
a111: Logged on 2016-11-19 17:18 ben_vulpes: Framedragger: i am also curious
to know what kind of requirements you have for a vps
that your current loggotron doesn't serve.
Framedragger:
http://btcbase.org/log/2016-11-19#1570793 << current loggotron also runs on vps, and in itself it requires very few resources. no db use, even. at
this point
there's a bunch of stuff and other people's sites running on
that vps, i don't feel comfortable adding additional load.
☝︎ Framedragger: mircea_popescu: (syn flood suspicion because sockets don't respond with anything, even when possible
to establish
tcp connection. and yes ping does seem
to work.)
a111: Logged on 2016-11-19 17:30 mod6: <+Framedragger>
trinque: fine with me << settled
then?
mircea_popescu: i can
tell you what wtf right now : learn not
to overload box.
mircea_popescu: 31 packets
transmitted, 31 received, 0% packet loss,
time 30040ms < you actually can't ping it ?
mod6: <+Framedragger>
trinque: fine with me << settled
then?
☟︎ mod6: <+trinque> Framedragger: ben_vulpes: it probably makes
the most sense for me
to do
the WoT browser << perhaps. i'd be up for anything really at
this point.
mod6: This would be a really great project
to work on, we're long overdue
to get
this working with deedbot, etc.
mod6: I
think
the idea would be
to get back
to some sort of analog of what mike_c had in place. And
then add improvments as necessary.
ben_vulpes: Framedragger: i am also curious
to know what kind of requirements you have for a vps
that your current loggotron doesn't serve.
☟︎ Framedragger: ben_vulpes: i'll
think about
this next week. it may be
that it's not really needed, yeah - i agree. and integration of
things such as ssh server banners with phuctor keys is something
that asciilifeform said he'd be up
to do on phuctor's db itself..
ben_vulpes: just don't connect it
to
the internet, what
ben_vulpes: replication works on
the wal, not on
the committed db, and so i don't
think it would have
the load impact you do.
ben_vulpes: 'read only sql users
to a replica of
the phuctor db' is, while an interesting project, not wanted by
the people doing most of
the analysis afaict
trinque: ^ right way
to analyze data
ben_vulpes: i
too would like more detail in re 'shall provide a platform for
those interested in analysing RSA keys'
Framedragger: i mentioned js in relation
to WoT as it's more applicable
there (lots of ready-made libraries for discrete graph visualizations and so on)
Framedragger: asciilifeform: well, less so visualizations
than easy ways
to query and analyse data. but, i agree with mircea_popescu and yourself
that concrete merits are
to be discussed. maybe it's not needed.
ben_vulpes: even mike_c-'s
thing only used js
to populate
the
typeahead iirc
trinque: alright I'll
take
that and you can focus on phuctor viz
mats: i imagine
this'd have a lot of applications in, ie, mosul, raqqa, and more modern battlefields of
the future
Framedragger: regarding visualization, a more condensed question: if a javascript-using
thing were delivered, would
this be hated upon (and berated by asciilifeform) and accepted if otherwise good and properly maintained, or hated upon and dismissed (and berated by asciilifeform)? :)
☟︎ trinque: anyone else is going
to have stale data
☟︎ trinque: Framedragger: ben_vulpes: it probably makes
the most sense for me
to do
the WoT browser
a111: Logged on 2016-11-19 16:52 Framedragger: asciilifeform: at least with public-static and phuctor boxes being separate, you'd have access
to
the latter if it were private. (but i guess you could object with "private/undisclosed box on
the internet, what is
this oxymoron!")
mats: i wonder what a limited remote steering package on a
toyota camry is worth
mats: many affordable non-luxury cars
today ship with front and rear-view wide multi-angle cameras
ben_vulpes: wot browser somewhat higher priority
though
Framedragger: ben_vulpes: oh hmm, i've never used it, very interesting and
thanks for
the pointer
ben_vulpes: phf: may be able
to chime in on how much load
that'd add
to
the db process but i don't
think much
ben_vulpes: Framedragger: if you go down
the 'phuctor visualizer/dash' route, you might consider leaning on pg streaming replication
☟︎ Framedragger: re. visualization, i like stuff like
this (mouse over on labels around
the circle), but it's a hella lot of JS, and i share
the hate
towards
the latter:
http://bl.ocks.org/mbostock/7607999 - what's nice about btcalpha visualization is
that it uses by-now standard html5 canvas directives (<path>) with no need for JS.
☟︎ Framedragger: asciilifeform: at least with public-static and phuctor boxes being separate, you'd have access
to
the latter if it were private. (but i guess you could object with "private/undisclosed box on
the internet, what is
this oxymoron!")
☟︎☟︎ Framedragger: i suppose
the idea could be
to re-implement
that, but using deedbot's view of WoT, and add additional
things as desired.
☟︎ mod6: So I wanted
to avoid
that. But going forward, I
think
that'll just some sort of optional field or whatnot. I'm excited
to put some work into
that as soon as I can here.
Framedragger: fair 'nuff. guess it depends on agreed-upon processes and overall mindsets of
team, and so on...
mod6: Framedragger: aha. yeah, in my experience with
ticketing systems ala scrum, it's my observation
that if a
ticket is "assigned or owned by Jeff, I don't even
think
twice about it."
Framedragger: mod6: sure! maybe "assignee" would have
the desired (lesser) connotation, i don't know. coming from some
trac feature/bug
tracking in distributed
teams experience, 'owner' is
there interpreted as simply 'person who is ultimately responsible for implementing/fixing
this', with other collaborators invited and acknowledged
mod6: Anyway, now
that it seems
that private a more rich
ticketing system is wanted,
these
things can be considered for sure. Salud!
☟︎ mod6: Framedragger: point
taken about 'owner' on
tickets. I considered adding a 'assignee' or 'owner' for a given
ticket(s), but with
the narrow view of
the first project (trb), i didn't want
to discourage people from
thinking about solutions for a given problem just because it had my name on it or something.
mod6: <+mircea_popescu> Framedragger if you wanna do data visualisations,
the
thing
to do is
the wot explorer.
that i actually miss. << me
too.
Framedragger: i hear you, examining
them ourselves (in some automated fashion or w/e) would have been prudent. "trust
the public
to do it", uh :/
Framedragger: asciilifeform: by links break you mean
that
they are unreachable for extended periods of
time? but boxes with cached static content can be armoured against ddos more, no? i guess unless you maintain
that
this is indeed syn flood or equivalent, which is agnostic
to whether content up
the stack is dynamic or sttaic...
mod6: Framedragger: black mirror is pretty good -- im halfway
through
the latest series.
pete_dushenski: of lines of code and
that many chinese sensors ~will~ fail at some point. and it will be unexpectedly. and catastrophically.
☟︎ pete_dushenski: mats: do you see
the appeal in
the whole autonomous driving
thing ? it strikes me as appealing
to
the same neophilic and inconsiderate mind
that wanted
to vote shillary in simply because she's a woman and WOULDN'T
THAT BE GREAT, not because
the consequences had any bearing on
the decision making process. frankly
the idea
that sv-shitware was in
total control of my vehicle is frightening.
that many millions
Framedragger: still,
the permalink-able key pages can be cached and/or served from somewhere else, no?
Framedragger: 'providing public services' does not necessarily imply 'provide
them on
the very box which does
the important stuff'.. (though i hear you re. your 'ability
to provide caching
to live feed' concerns..)