tmsr - Search: strings

500+ entries in 0.258s

mp_en_viaje: the ~reason~ they were there was that now and again i'd break out the red machine, which is an actual machine, and a slavegirl would sit in front of it, and type, by her pretty little hand, meaningless strings, from the black machinery connected to y'all and everything else.

lobbes: Then I realized that all that insanity was indeed because I was needlessly translating all kinds of strings across boundaries. I think the cleanest way to do this historical (May 28, 2016 to Now) log backfill is if I just provide you a text file in the same format as your "logstory.txt" you reference in this comment

billymg: ok, so trilema logs uses `word-wrap: break-all` on the entire content column. i used jfw's suggestion of `white-space: pre-wrap` on the code column because it wraps long lines without splitting individual strings

billymg: the latter was my thinking. even for experienced operator having the magic strings together at the top of the file might be useful / make the code easier to reason with

mircea_popescu: in any case, why do you want to maintain the "options" object ? too much hassle to take out entirely ? more elegant to have all the magic strings in one place ?

mp_en_viaje: for that matter, running strings over the output of one bringing up lots and lots of gggg pppp rrrrrrrr etc suggests monkley rather than man involvement.

spyked: http://logs.ossasepia.com/log/trilema/2019-11-02#1949277 <-- guids are currently arbitrary strings tho. mp-wp puts the link in ?p=postid style there iirc.

BingoBoingo: asciilifeform: From the local news stories I read in old country police usually took what they were given or bought what they were told with money similarly given with strings

snsabot: Logged on 2019-09-06 15:52:02 asciilifeform: tho possibly still isn't exactly what we traditionally want. e.g. this , possibly oughta match only space-bounded strings when quoted term ?

asciilifeform: tho possibly still isn't exactly what we traditionally want. e.g. this , possibly oughta match only space-bounded strings when quoted term ?

asciilifeform: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932202 << ada imho is uniquely unsuited to 'munge 9000 strings' type of proggy. so not sure whether would ever want pg glue in it. any attempt to use, will be tremendously ugly

asciilifeform: i.e. nulltermed strings & all.

diana_coman: given this, I seriously wonder if it can be much worse to make it in ada on top of all the gnat-mess including unbounded strings and gnat.sockets and everything else; at least the full gnat so far *is* more transferable

asciilifeform: mircea_popescu: quoted strings? indeed still gotta bake'em ( see in readme.txt, they're on the listof missing essentials , and errybody grumbles, i'ma do these next )

asciilifeform: ( for the curious : 'erlang' had 0 'shared memory' b/w threads. all inter-thread motion was in the form of messages (received in 'atomic' queues internally). these could consist of whatever -- symbols (a la lisp) , for simple 'a/b/c' cases ; strings of bits; etc. a message could be eaten, or forwarded to yet another thread, or even sent back to the sender. )

mp_en_viaje: and the other one is exactly the same situation : very good and clearly related, but not the exact item, which i am positive included the strings "you are male still" "abused your body"

asciilifeform: only ask that the 'begin' and 'end' strings match the given

lobbesbot: trinque: Sent 5 days, 6 hours, and 25 minutes ago: <BingoBoingo> http://logs.nosuchlabs.com/log/pizarro/2019-08-11#1000032 << Fellow from earlier indeed appears to have his private key. When you get a chance to, please swing by #pizarro to see if you can help him debug his issue decrypting deedbot strings to !!v.

a111: Logged on 2019-08-11 17:45 BingoBoingo: !Qlater tell trinque http://logs.nosuchlabs.com/log/pizarro/2019-08-11#1000032 << Fellow from earlier indeed appears to have his private key. When you get a chance to, please swing by #pizarro to see if you can help him debug his issue decrypting deedbot strings to !!v.

BingoBoingo: !Qlater tell trinque http://logs.nosuchlabs.com/log/pizarro/2019-08-11#1000032 << Fellow from earlier indeed appears to have his private key. When you get a chance to, please swing by #pizarro to see if you can help him debug his issue decrypting deedbot strings to !!v. ☟︎

asciilifeform: nao, a general-purpose strings-and-streams-munging script lang ~might~ be worth implementing in ada.

bvt: i would actually expect that pg protocol does not use 0terminated strings. re 80% of CL -- inside of it's implementation you'd find same shit. dunno how it would be different from using heathen libs

asciilifeform: but i strongly suspect that 'ada logtron' will consist mostly of non-humanreadable hex constants , and the pg glue will be eating null-termed c strings , and generally the result will not be a thing you 'would fly in it? i wouldn't walk under it!'(tm)(r)(h. hughes)

asciilifeform: bvt: i do not presently know what would have to be done to use utf8istic strings in gnat, either

bvt: well, for most of format strings you know the number of formatted elements, right. re memory allocator -- an arena allocator is typically used, and file data can be mmaped

snsabot: Logged on 2019-08-08 17:02:19 asciilifeform: you can't even concat 2 strings w/out 'secondary stack'ism

asciilifeform: you can't even concat 2 strings w/out 'secondary stack'ism

asciilifeform: PeterL: there's still coupla missing knobs in www logotron (quoted strings for search; pagination for same; backlinkage)

asciilifeform: possibly the source of confusion for the drosophila was the fact of ffa series being tagged, among other strings, 'bitcoin' , lol

mp_en_viaje: i got a trackback, first thoguht wtf is this spam (cuz you know, weird literal strings), then "holy shit wut is that url structure". had a 0.3 seconds of mental chaos.

BingoBoingo: asciilifeform: I notice when I drop the version number down enough I'll get a wider number of version strings in my peerslist

diana_coman: meanwhile I'm trying to disentangle here the cs/ps mess and I'm scratching my head at various bits: the CS engine works everywhere with names (strings) as ids (i.e. there are FindX functions only with string param, not with some numeric id despite the fact that internally it DOES HAVE them ffs) BUT then in some places it keeps various hashmaps with numeric ids for "common strings"

mircea_popescu: as i sit here now, there's things around me i've never read. serial numbers on smoke detectors, handling and caring labels on rugs, brand names on plaster and wall insulation facing inside, towards the wall. i am not about to tear the place apart to read all possible strings around me. i might, ~if need be~, of course. but not before.

mircea_popescu: you don't mean "pls try again" as in, issue command again ? as opposed to "put !!v strings in again" ? do you ?

mircea_popescu: now for yet another half hour episode of driving the-sorta-people-nobody-here-knows-how-to-replace blind on nonsense strings.

mp_en_viaje: no but listen : php chiefly exists for the task of "you know what? take every sentence in this text file and put <tag> around punctuation marks". that's what it was made for, substitute strings in strings, pretty much.

danielpbarron: it's my understanding that such a registration also comes with strings attached that we don't want attached

mircea_popescu: entirely no need of any actual events for globalwarmingourdemocracyblablabla word fountain to sprout strings.

phf: bvt: http://bvt-trace.net/2019/03/mes-part-1-stage0/ << "can to be implemented" "layouts textual strings"(?)

asciilifeform: http://btcbase.org/patches/ffa_ch18_subroutines.kv/tree/ffa/ffacalc/ffa_calc.adb#L553 << for thread-completeness, illustration of matching such 'strings'

asciilifeform: if all yer 'strings' come from the inside of a large, static string, can represent'em simply as tuples , as pictured in above

diana_coman: but yes, that uses also unbound strings

diana_coman: the code I saw so far is quite readable and self-contained so all surprisingly good there but it's true that he still uses all sorts including unbounded strings and pointers where I'm not sure it's really unavoidable

mp_en_viaje: it makes about as much sense to have os strings as it does to have os bitmaps.

mp_en_viaje: there's entirely no need of "utf/unicode/bs" ; the place where these go, as a mask atop bytes, is where "strings

a111: Logged on 2019-04-06 23:07 OriansJ: asciilifeform: no where did I say null terminated strings; it could be length prefixed strings but support for strings needs to exist in a human readable bootstrap.

mp_en_viaje: http://btcbase.org/log/2019-04-06#1907081 << i opted to let that pass in silence, too much work to open the can from that seam. but... yeah, no fucking strings, not ever again. ☝︎

mp_en_viaje: i reallly dislike noun strings, espcially as the count goes over 3.

OriansJ: asciilifeform: no where did I say null terminated strings; it could be length prefixed strings but support for strings needs to exist in a human readable bootstrap. ☟︎

a111: Logged on 2019-04-05 23:03 OriansJ: well the only extremely useful feature for bootstrapping hardware architectures have is clean encoding and a sane subset of operations that make working with strings and structs easy to do in assembly.

OriansJ: well the only extremely useful feature for bootstrapping hardware architectures have is clean encoding and a sane subset of operations that make working with strings and structs easy to do in assembly. ☟︎

diana_coman: ada doesn't have c-strings anyway

mircea_popescu: the ~problem~ with c-strings is that to know how loing it is you must look ~at the end~.

mircea_popescu: i really do not wish to see c strings, and i don't perceive char buffer to be different. "bitstream" does not exist. so my thinking is, to henceforth mandate datapassing as such a field.

mircea_popescu: i mean if the part of the brain that handles the mechanics of thought moves into adulthood, rendering the subject capable of articulating longer strings and remembering them,

a111: Logged on 2019-01-13 17:54 billymg: !Q later tell hanbot mp-wp patches have been updated: http://billymg.com/2019/01/minor-mp-wp-patch-updates/ -- the only "\ No newline at end of file" strings you should find in .svg refs patch are from before part of the diff (i.e. file diffed had no newline at the end)

a111: Logged on 2019-01-15 22:10 mircea_popescu: (ie, you can construct an infinity of rng strings which'll make a given sct "falsely" converge)

mircea_popescu: (ie, you can construct an infinity of rng strings which'll make a given sct "falsely" converge) ☟︎

lobbesbot: hanbot: Sent 1 day, 10 hours, and 22 minutes ago: <billymg> mp-wp patches have been updated: http://billymg.com/2019/01/minor-mp-wp-patch-updates/ -- the only \ No newline at end of file strings you should find in .svg refs patch are from before part of the diff (i.e. file diffed had no newline at the end)

billymg: !Q later tell hanbot mp-wp patches have been updated: http://billymg.com/2019/01/minor-mp-wp-patch-updates/ -- the only "\ No newline at end of file" strings you should find in .svg refs patch are from before part of the diff (i.e. file diffed had no newline at the end) ☟︎

billymg: well, not used as image references, but other instances of those strings. used in, e.g. matchers in a conditional in some script

mircea_popescu: i utterly don't need a scriptable wrapper to do string manipulation, what the holy shit is this, onyl someone who grew up on c strings can imagine such nonsense.

asciilifeform: in earlier days there were also folx stuffing strings into block hdrs, but dunno if this is still in fashion, and at any rate no longer doable if you aint chinese, to 1st approx

asciilifeform: hey BingoBoingo what do you call in english those strings ?

mircea_popescu: anyway. there's differences i'm sure, if nothing else the tag strings differ. but i fail to see any comparably important to the similarities, and so it goes.

diana_coman: mircea_popescu, fixed-length strings get rid of all sorts of ugh pretty much everywhere; this being said, I can't quite tell what we need as filenames and recall that they include the path - I think that's the main reason why it will still be variable

BingoBoingo: asciilifeform: I just plucked 12 character strings outta the soup

a111: Logged on 2018-11-11 16:04 BingoBoingo: asciilifeform: When you return let me know if you have a preferred manner for hashing salted customer strings

BingoBoingo: asciilifeform: When you return let me know if you have a preferred manner for hashing salted customer strings ☟︎

Mocky: I don't know where else to go with this, mircea_popescu. I don't see anymore strings to pull on

a111: Logged on 2018-11-04 18:32 diana_coman: it still seems at best silly to manually split strings that one would than have to merge if they want to use as such somewhere else

diana_coman: it still seems at best silly to manually split strings that one would than have to merge if they want to use as such somewhere else ☟︎

diana_coman: onth I suppose that the 80cols rule either is or isn't, so it should apply even to strings that make no sense split, a bit of cutting to fit the bed style

diana_coman: the fact that I have to manually and arbitrarily split strings that in fact are of any use only un-splitted

mircea_popescu: who the everloving fuck reads "profiles" ? same people who exec user strings i suppose ?

asciilifeform: you're xoring Kbits distinct (if lowest kbit is 0, and there are no symmetries in the message) strings into a Kbits-sized hole.

a111: Logged on 2018-10-29 18:29 asciilifeform: it's about xor, in the specific style used in winblowz shitware to hide strings from av.

asciilifeform: it's about xor, in the specific style used in winblowz shitware to hide strings from av. ☟︎

asciilifeform: so apparently i gotta reimplement bounded strings nao..

asciilifeform: bvt: linux kernel is fundamentally retarded, it expects null-termed rubbish, at times, at other times, char * and length, not to mention a pile of untyped ptrs inside structs, really oughta eat ada structs , ada fixed strings, properly typed arrays, etc instead

asciilifeform: bvt: maptron is actually done aside from the strings horror raised last night

asciilifeform: tldr : the shitcoin people are in fact pretending to compatibility with ordinary btc protocol; even going as far as using unchanged version strings, and backdated block timestamps ( of course trb rejects the liquishit in O(1) , but it is entertaining )

bvt: thanks, i see what you mean. the Interfaces.C.Strings.New_String() comments explicitly say that the heap allocation is necessary for the large strings, which is not the case for vpatch temporary file names.

bvt: it seems that 'c strings' in ada are still controlled by ada mechanisms, i.e. they are ada strings (with bounds checking), just with null byte in the end

mircea_popescu: bvt you asking for a primer on the longstanding hatred of c strings here, or found on own ?

a111: Logged on 2018-10-15 19:11 bvt: btw, now vpatch.adb does not require Interfaces.C/Int.C.Strings for anything, they will go away in the revised vpatch.

bvt: btw, now vpatch.adb does not require Interfaces.C/Int.C.Strings for anything, they will go away in the revised vpatch. ☟︎

mircea_popescu: http://btcbase.org/log/2018-10-15#1862793 << i'd rather never have to import c strings anywhere either, i'd say a major goal of the whole effort is to get rid of them. so paranthesis-yes! ☝︎

ave1: and in that code, another way to send strings from Ada to C; http://p.bvulpes.com/pastes/GZtAH/?raw=true

mircea_popescu: how do you mean "works just as well" ? The pg_trgm module provides functions and operators for determining the similarity of ASCII alphanumeric text based on trigram matching, as well as index operator classes that support fast searching for similar strings. << seems eminently based on birthday problem, "how many different permutations of 60 characters can there be"

asciilifeform uses searchtrons perhaps 98% for eggog strings, 1% for electronic parts purchase, and 1% remain

bvt: i will give it a try. i'm still learning ada, will have to take a look at how strings and interfacing with C are done properly.

asciilifeform: mircea_popescu: observe that i was able to index 9.3 mil pgp comment strings somehao, on 1 iron, and with <1s lookup

diana_coman: and no, certainly not variable-length strings

asciilifeform: the one variant that is not an option is returning variably-long strings ( this'd pull in secondarystackism . )

asciilifeform: it also shows how to output strings in a civilized way, for n00bz.

asciilifeform: ( tho will add, ada Strings actually work with arbitrary garbage, given as they do not use the idiot c 'null termination' paradigm )

asciilifeform: 'you concated two strings, of course this uses unbounded heap space and frags'

mircea_popescu: THESE IDIOTS REIMPLEMENTED C STRINGS you understand me. also wrongly, of course. fucking pancake.

asciilifeform: mircea_popescu: one of the things that never ceases to fascinate me re physics crackpots, is how rarely they grasp the sheer 'unreasonable effectiveness' of making ~political~ , rather than simply technical, cuts . ( observe, i dun need to read , much less attempt to individually refute, errything the strings people shit out -- for the same reason i dun need to read gavin's code . )