500+ entries in 0.656s
lobbesbot: trinque: Sent 2 minutes ago: <asciilifeform> lemme know if this needs additional knobs (
jsonism ?) to work with deedbot
lobbes: !~later tell mircea_popescu ^^ 'help sexpr' and 'help
json' also working. lobbesbot has been brought up to spec
a111: Logged on 2017-10-05 18:20 mircea_popescu: ok so results of audit : Framedragger, shinohai, phf : your bot has no help implemented whatsoever, in spite of spec. trinque Framedragger you don't follow the
json/sexpr portion, bot simply puts out the same help.
a111: Logged on 2017-10-05 18:20 mircea_popescu: ok so results of audit : Framedragger, shinohai, phf : your bot has no help implemented whatsoever, in spite of spec. trinque Framedragger you don't follow the
json/sexpr portion, bot simply puts out the same help.
mircea_popescu: the part what's under discussion is the ~why~ nobody implemented the
json/sexpr part of the spec./
mircea_popescu: ok so results of audit : Framedragger, shinohai, phf : your bot has no help implemented whatsoever, in spite of spec. trinque Framedragger you don't follow the
json/sexpr portion, bot simply puts out the same help.
☟︎☟︎ phf: there's ISLISP standard, which was supposed to create a subset of multiple different lisps (like common lisp and scheme, but also eulisp, since designed by europeans). i don't think anyone (particularly sexp library authors for other languages) ever tried to conform to it. typical solution is to have a
JSON-like subset of sexps, so that you can express (FOO "abc" 2), i.e. symbol, string, number and list and nothing else
a111: Logged on 2017-07-08 07:23 sina: mircea_popescu: I am guessing tmsr is not fond of things like
JSON or YAML
sina: mircea_popescu: I am guessing tmsr is not fond of things like
JSON or YAML
☟︎ trinque: looks like trb was not pleased with python's
json.dumps() taking upon itself to use scientific notation after I changed fee and deed amounts.
mircea_popescu: whereas "copy this code snippet to do
json bro" is EVERYWHERE.,
gabriel_laddel_p: shapefiles are heathen nonsense, but it turns out they can be easily converted to
json, which CL has plenty of parsers for.
trinque: ben_vulpes: www-wot package farts out a bunch of
json index files for the search
mircea_popescu: no more of this should it be
json or sexpr and pass via urls bs
Framedragger: (as in, if it's requested by a non-browser it'll return
json - e.g. `curl ipinfo.io/8.8.8.8`)
shinohai: Forgive the
json brackets, will try to sort that crud out
trinque: and don't worry; there's probably a migration to
JSON underway
a111: Logged on 2016-09-13 08:11 mircea_popescu: trinque asciilifeform & everyone : without detracting from the more important gossipd spec work, im thinking of making a bot spec. it'd require bots to answer in pm to help, help
json and help sexpr. comments/ideas ?
mircea_popescu: trinque asciilifeform & everyone : without detracting from the more important gossipd spec work, im thinking of making a bot spec. it'd require bots to answer in pm to help, help
json and help sexpr. comments/ideas ?
☟︎ mircea_popescu: znort987 deedbot has a
json for that, lemme find it for it
phf: ben_vulpes: well,
json integer is number without fractional part, but from my reading of "standard" it's not mandatory to treat number as such. as far as numerics it has type "number", which is up to client to interpret. here on rum island we do not believe in rum
phf: ben_vulpes:
json also doesn't have integers
ben_vulpes: 'jq' is this mostly-c-thinger that parses
json.
ben_vulpes: in
json you mean? or are you talking about the jslib 'jquery'?
ben_vulpes: whatever it is that returns the
JSON that sends mircea_popescu scrambling and screaming for the "programmer's view"
mike_c: <ben_vulpes> ;;later tell mike_c does your wot thinger spit out
json anywhere?
jurov:
JsonParserExceptionTooTesty
phf: ben_vulpes: i dunno, i've seen some pathological cases in
json readers, "too nesty" at 10kb could be one of them
ben_vulpes: holmes i can read 10mb of
json into memory naively and not even begin to sweat the phone.
nubbins`: he sends a special packet and the node dumps its mempool,
json format
assbot: Logged on 28-02-2016 04:08:36; mircea_popescu: phf> i think ascii short term plan is specifically rewrite of rpc, because it's an easily achievable low hanging fruit, which when done completely will let us get rid of
json/
http << quite.
mircea_popescu: phf> i think ascii short term plan is specifically rewrite of rpc, because it's an easily achievable low hanging fruit, which when done completely will let us get rid of
json/
http << quite.
☟︎ phf: i think ascii short term plan is specifically rewrite of rpc, because it's an easily achievable low hanging fruit, which when done completely will let us get rid of
json/
http jurov: in stat
json output
ben_vulpes: who is john w. wilkinson and is there any reason to keep his
json spirit license around?
mircea_popescu: trinque i dunno, jurov was saying something about email, but that seems silly. just allow the import of files and piss them out as a
json i guess ?
polarbeard: aha I see, but maybe ascii can trash the
jsonrpc part and keep the functionality itself?
copypaste: kakobrekla: I'd like to make a request if you have a moment. When I get my OTP from assbot, it sends the header `Content-Type: application/
json; charset=utf-8` ... This causes my browser to incorrectly interpret GnuPG documents as
JSON, so it spews annoying errors which prevent me from just doing Ctrl-A Ctrl-C...to wit, "There was an error parsing the
JSON document. The document may not be
adlai: asciilifeform: isn't shiva supposed to be an optimal point BETWEEN sentient-AGI-bitcoinOS and
jsonrpc on port 8332?
assbot: Logged on 27-01-2016 15:13:14; mircea_popescu: the idea is to replace
json with sexpr which means you'll have to have some sort of scheme in there. and once you do, it'll replace the retarded format of coin scripts too, eventually.
mircea_popescu: the idea is to replace
json with sexpr which means you'll have to have some sort of scheme in there. and once you do, it'll replace the retarded format of coin scripts too, eventually.
☟︎ mircea_popescu: asciilifeform so you added tinyscheme to have sexpr rather than
json, and now you telnet into scheme ?
punkman: well, something for the foundation to decide, whether
json is to be kept or replaced with something else
punkman: there are some tiny
json libraries
mircea_popescu: yes but fuck that, we have a protocol that then imports
json ?
mircea_popescu: incidentally, why the fuck does bitcoin have
json support ? do we actually want this ?
mircea_popescu: after all... we have fucking
json in there for reasons!
jurov: Stratum protocol is based on
JSON-RPC 2.0 (although it doesn’t include “
jsonrpc” information in every message).
ben_vulpes: ;;later tell mike_c does your wot thinger spit out
json anywhere?
mircea_popescu: just pipe it from
json to iptables -A INPUT -s x -j DROP through your favourite perl ?
ben_vulpes: BingoBoingo: note the giant blob of
json in the middle
adlai: tl;dr: "DAE STAT
JSON?"
davout: re jurov's comments suggesting an mpex-style API, there's a slot for signed receipts in the returned
JSON mircea_popescu: this can be readily verified for the entire list visible there, not so much for
json because well,
json doesn't have the links baked in, being
json assbot: Logged on 19-09-2015 14:41:47; mircea_popescu: it looks exactly like someone gutted lisp and replaced it with "easier to use" javascript.
json mircea_popescu: it looks exactly like someone gutted lisp and replaced it with "easier to use" javascript.
json ☟︎ punkman: kakobrekla: I think that means XML instead of
json