Show Idle (>14 d.) Chans

← 2022-05-04 | 2022-05-06 →
dulapbot: Logged on 2022-05-04 21:06:29 thehorrors: I suppose I am still too new here not to be percieved as the guy who is trying to fuck with you and not simply someone who is trying to engage in productive discussion
dulapbot: Logged on 2022-03-20 20:09:10 signpost: believes in the time-honored tradition of men giving each other shit as much as possible.
signpost: it's a delight to spar, and paying someone respect when you bother to.
signpost: literally, returning their gaze.
signpost: and not only, but telling them what you see, even if you don't like it.
signpost: *if they don't like it
signpost has meanwhile been putting together the init process for pentacle
signpost: I'll throw another WIP copy of it up on my blog tomorrow sometime for folks that want to test it in a chroot.
signpost built bitcoind with it the other day, having ported it and the deps (bdb, boost, openssl, etc) to pbuilds, worked nicely.
signpost: given the importance of bitcoind I see no reason to remove its own build process, but for the bitcoind pbuild I just make -f makefile.unix
signpost: pentacle can be thought of as a spiritual successor to rotor, tbh. I wanted sane and easily reproducible build environments for everything I use.
thehorrors: << Sure. There is also sometimes a fine line between sparring and trolling. I've never been interested in either much. There are plenty of opportunities to give each other shit while intelligently discussing ideas, in a much more interesting and subtle way. I suppose it's a matter of preference.
bitbot: Logged on 2022-05-05 04:04:00 signpost: it's a delight to spar, and paying someone respect when you bother to.
thehorrors: keyboard MMA on the other hand does not strike me as a particularly masculine, delightful or respectable activity. Maybe I am just a snob
verisimilitude: I'm not trolling.
signpost: thehorrors: I was telling you to hit him back.
signpost: instead of politely discussing the rules, say.
signpost: everyone's atomized into their own pocket of "interesting" enough to halt culture.
signpost: << example of a recent thread where I didn't politely whine that the mods wouldn't remove someone I didn't find "interesting".
dulapbot: Logged on 2022-03-03 19:27:13 signpost: verisimilitude is signaling his status as a middle-caste slave with his nazi racial theory fantasies, lest he be lowered further.
dulapbot: Logged on 2022-05-05 01:09:31 signpost: everyone's atomized into their own pocket of "interesting" enough to halt culture.
signpost: as broadly as the word means.
verisimilitude: I agree, then.
signpost will grant that the amish probably still know how to talk to one another, but halted by other means.
signpost: collectively, I suppose.
verisimilitude: Each one of us is in his own world, but with enough tangents to stay.
thehorrors: verisimilitude, I never said you were, wasn't really saing anything about you specifically. It's just I was not sure what to tell you when I say something about sqlite unit testing and you respond with "oh you think I don't know how to use a computer? Huh? Yeah?"
verisimilitude: It's simple misprediction.
verisimilitude: Read what I write here in a monotone, and it will have the intended effect.
signpost: neither of you were communicating well. you quoted a bit from your hidden belief systems, said nothing substantial of the models informing the output.
verisimilitude: It would be a hard sell to tell thehorrors ``Read the entirety of my website.'' now wouldn't it?
verisimilitude: No, I'm not communicating well at all, right now.
verisimilitude: That was a non sequitur, wasn't it?
thehorrors: I am reading more than you might think perhaps. But I am taking it one step at a time.
thehorrors: I've read the entirety of loper-os and about half way through trilema
verisimilitude: That's a lot of reading.
thehorrors: Still trying to answer the question of "what exactly is the project?" I am getting conflicting messages from different sources
thehorrors: yes, I took a deep dive - just the way I like it
thehorrors: It unfolds to me unevenly, with a lot of discontinuities
signpost: this reminded me of a thread where phf and I had a mad.
dulapbot: (trilema) 2017-04-10 phf: you clearly have some twisted issues related to me. ~that was not my intent~. ~i genuinely think that you were speaking of pulling levers~ ~because there's nowhere in the thread where you attempted to dissuade me of my notion~
signpost: complete failure to discuss the unstated parts of our disjunct models of the world.
signpost: kinda funny to read now.
thehorrors: signpost, taking the throughput of the channel into account - how can you hope for efficient model sync?
signpost: there's actually quite a lot of me in the logs at this point, so I imagine it's easier to assemble a me-simulation as time goes on, not harder.
signpost: of the assembled, I was probably the most tech-bro adjacent of the bunch, so phf's nose wasn't even wrong, if allergic.
thehorrors: It seems reductionist. Even though I read all those blog posts - I am nowhere near understanding who Stan or MP are. There was a poet who said something like "a though spoken is a lie"
signpost: I brought my "fuck you, I will discuss any topic I choose to discuss" and I can only imagine was his "casuals are mauling what was a high pursuit", and these had the expected result.
signpost: thehorrors: I'd expect the logs to be more illuminating there, and even that might be hard given the years of context.
thehorrors: well, yeah, that's another thing - the sheer amount of information that keeps accumulating over the years, with context. Good grief. I don't think anyone can read through it all.
signpost: << a republic is a machine which evaluates this question for as long as it can.
dulapbot: Logged on 2022-05-05 01:54:54 thehorrors: Still trying to answer the question of "what exactly is the project?" I am getting conflicting messages from different sources
thehorrors: that contradicts MP however
signpost: say how?
thehorrors: he was all about "measurable outcome". Struggling to find that post in bookmarks
thehorrors: it was the post about utopias
signpost: mp's notion that everyone not sucking on his toes was an NPC had a lot to do with limiting his impact on the world.
thehorrors: "concrete reference" he called it
signpost: but I don't see a contradiction in valuing measurable outcomes.
thehorrors: I tend to distill concrete ideas, I am not particularly fond of his (public) character
signpost: doesn't building one product inform the next one you build?
signpost: iterating on "what's the project" is what a business is.
verisimilitude: Has anyone seen a functional business, then?
verisimilitude: This seems more like the myth of a business.
signpost: depending on where you put the goalposts, I ran one for a decade.
signpost: might even fart out another, who knows
thehorrors: I got disconnected for a second. Anyways, the closest I've found is
verisimilitude: Fine, signpost.
signpost: thehorrors: << this thread might have some useful context
dulapbot: Logged on 2021-08-30 20:49:40 pete_rizzo_: thanks for the invite
thehorrors: He had a business, other people in tmsr had businesses. I think tmsr was something else for him, something he abandoned in 2020; I've found his rationale unsatisfactory.
thehorrors: I'll read it
signpost: try to stop using hand-waving like "something else"
signpost: what else?
dulapbot: Logged on 2021-08-31 06:46:41 punkman: even by end of 2014 some called it a "cult"
signpost: I think the vision was as grand as reality would allow, and it didn't.
thehorrors: I'd tell you if I understood. Some sort of movement is my current understanding.
thehorrors: (clearly flirting with cryptoanarchy)
signpost: I'm not an anarchist, but a republican.
thehorrors: but also a sort of a mix between "bronze age", Plato, "might is right" and early Peterson-esque type of initiatives.
thehorrors: Oh I am not talking about you, signpost
thehorrors: I am talking about my attempt to understand what MP was about
signpost: afaik we preceded peterson's public life by years.
signpost: << at some point mp turned from republicanism to this kind of monarchial thinking, continued to call it republicanism.
signpost: but also feudalism, because "eat shit, I will force you to embody contradiction"
signpost: that said I don't even dislike peterson.
signpost: he could stop crying so much while he's preaching traditionalism, but I've never quit benzos, so what do I know.
thehorrors: yeah, I've seen that. I didn't realize it all went to feudalism at some point though. The declaration itself didn't not hint at that
thehorrors: so where did you come in, signpost?
dulapbot: (trilema) 2014-10-16 mircea_popescu: !up undata
thehorrors: eight years, huh
thehorrors: you seem to be critical of MP. And you implemented WoT, didn't you?
dulapbot: (trilema) 2014-06-16 trinque: I can take it
signpost: thehorrors: I implemented maybe the 3rd or 4th iteration
thehorrors: who did the first one?
signpost: first one would've been the old bitcoin-otc WoT, I believe.
dulapbot: Logged on 2021-08-31 12:27:39 punkman: <punkman> at some point there was an incident with bitcoin-otc bot, and then the WoT split, and a new separate WoT was created, administered by kakobrekla/assbot
signpost: that whole punkman thread has a bunch of major events
thehorrors: But WoT is centralized, isn't it?
signpost: << I agree that decentralizing it is important.
dulapbot: Logged on 2021-07-18 17:06:32 signpost: wants the decentralized wot, decentralized comms network, cryptographic control of what information leaks from my relationships
thehorrors: Is anyone building it? I want to build it
signpost: would be a mighty fine thing to build atop pest.
signpost: say as an extension of thimbronion's blatta
thehorrors: I didn't read the spec yet, but isn't pest a p2p communication protocol? How would it support decentralized WoT persistence? In my view it should be something like a blockchain
thehorrors: I don't understand blatta yet either - didn't look at it
thehorrors: is asciilifeform building pest? Is it in Ada?
signpost: it would support decentralized wot gossip. what the messages for wot updates look like, how they are stored, is not defined.
signpost: I'm skeptical you need an entire blockchain for this, since there's not much of a double-spend problem with statements about reputation.
signpost: (but it may entertain you to know that I wrote the wot for ethereum)
signpost: haven't released or anything.
thehorrors: it does entertain me, thank you
thehorrors: the decentralized WoT will need more deliberation. It all depends on how people view it and want to use it. In my view a "global", visible wot would be best
signpost: I figure all pest-wot needs is a rule like "I believe the worst rating I receive with the most recent bitcoin block hash"
thehorrors: therefore, a "public ledger of trust"
signpost: and if I routinely had somebody in my wot emitting spam ratings with the same hash, I'd just negrate them.
signpost: eh, trust is not global.
signpost: that's entirely the wrong way to think about it, and leads directly to chinese social credit.
thehorrors: well then there is not much value in decentralizing it - everyone will just have their own little wot
signpost: one can only have trust along the specific paths across the social graph from me to you.
signpost: you're misunderstanding. global state yes, but what that state means *to you* is necessarily different than to me.
thehorrors: oh, sure
signpost: there's no such thing as "my score in the wot"
thehorrors: no, I agree
signpost: there's just "across these relationships I have these paths of transitive trust to thehorrors"
thehorrors: I mean more like "publicly visible"
signpost: yeah 100% agree with that
signpost: "res publica"
thehorrors: right, because I want to see if you trust that guy and that guy trusts the guy I trust etc
signpost: yup yup
thehorrors: yeah, the scores are individual, just the way it is now
thehorrors: it's the decentralized storage I think is all that is needed pretty much
signpost: << worthwhile thread too, if I got the right one
dulapbot: (trilema) 2017-01-26 mircea_popescu: the fundamental problem here is that there's no way to reason in the manner you expect to reason. IF anything about the wot process is opposable to anyone involved ; then the wot process becomes by that measure less useful. no change whatsoever appears in the swamp it's made to confront.
signpost: mp raised the objection to signing ratings that the ratings become sworn statements opposable to the rater.
signpost: meaning legally, traditionally, and practically today before the megastate.
signpost: I think it's still worth discussing, because how the fuck do I trust that the relationship described by the rating actually exists without the signature in a decentralized setting with no elected trusted observer (e.g. deedbot, which verified the rater without sharing that verification with others)
thehorrors: I had a blasphemous idea about that
dulapbot: Logged on 2022-05-05 03:01:52 thehorrors: is asciilifeform building pest? Is it in Ada?
thehorrors: Still not sure if it is any good.
thehorrors: you can assign public keys (and therefore trust) to systems, they don't have to be people.
signpost: how do you prevent your trusted system from becoming a dumping ground for people who aren't themselves held to account for what they did to it?
thehorrors: that's one of the questions, yes
signpost: imho this is why asciilifeform introduced V, to solve that problem
thehorrors: verisimilitude, I'll check your blog, you got patches?
verisimilitude: No, but I've source code.
verisimilitude: I'm building all components first.
verisimilitude: Nothing specific to Pest is yet present.
thehorrors: signpost, how do you see V solving that problem?
thehorrors: verisimilitude, what are you writing it in?
verisimilitude: I'll be writing it in Ada.
signpost: because there is no centralized authority on what authors I accept in my local V.
thehorrors: signpost, not sure I understand you. Suppose I want to rate you as X
signpost: I have a wot directory containing some public keys, and the tool assembles a source code state using that and the patches/sigs I have
signpost: I am addressing the idea of having systems hold a key, but perhaps you should explain what you hoped to solve with that idea.
thehorrors: I tell everyone "I am rating signpost as X" and I sign it. Everyone can verify that I signed it, so the relationship does exist, no?
thehorrors: so what's the problem?
thehorrors: Noone can do this for me (fake my rating)
signpost: the problem is the gpg-contracts interpretation of signing
signpost: you're swearing to the veracity of the rating, such that it can hypothetically stand on its own legally, rather than act as a pointer which causes me to ask you personally if I should go do business with the person you rated.
signpost: the idea was to augment the human relationship, not replace it.
signpost: this might be a pointless religious notion standing in the way of something useful. I'm just saying what the past context was.
signpost: I've loosened up on my own interpretation of signing, having signed entire linux kernels/gccs/etc for pentacle
signpost: and holy shit, I never realized the lovecraftian terror of c standard headers before this project, not like this.
thehorrors: ok, well but then we can do without wot altogether to be honest. As long as everyone knows each other's keys, we can ask each other questions about the keys and be done with it.
signpost: asciilifeform once took a crack at enumerated meaning of signatures.
signpost: nah, I think computable trust is entirely valuable. think what it means at the level of packet routing, say.
signpost: suppose I lose my connection to asciilifeform, but I need to tell him something direly. it'd be nice if my machine had some sense of where to send that message, such that it will eventually reach him.
thehorrors: what is pentacle? is that a distro I am getting a sense?
thehorrors: For that you would have a server you trust, maybe?
signpost: yes, pentacle's a distro I'm working on; nope, it won't have anything but signed vpatches, and nobody's system will be identical, nor will it rely on somebody's "repo" of packages
thehorrors: how is it different from billymg's gentoo?
signpost: lifted a lot of inspiration from gentoo; I used it for many years, am on a gentoo machine right now.
signpost: where it differs is in beingg built to use V for src.
signpost: *being
signpost: gentoo has also succumbed to significant complexity and interdependency creep. asciilifeform's frozen gentoo is great, but still requires a lot of work to cut back the dependency hell.
signpost: ends up being a littany of USE="-oh -no -you -fucking -dont"
signpost built pentacle outwards from what'd build the compiler itself, then "ok, now I need a kernel/init/text-editor"
thehorrors: have you looked into bsds?
signpost: sure, I ran openbsd for a long time
signpost: deedbot's server is openbsd
verisimilitude: I checked recently, and ``litany'' has but one letter t, signpost.
signpost: hm, ty
verisimilitude: It's no issue.
verisimilitude: I'd also thought it had two.
thehorrors: why not make a bsd distro instead of linux?
signpost: familiarity, probably. I don't think anybody'd object to someone making a set of BSD vpatches.
thehorrors: That's another project I will be thinking about.
signpost: I have a few state-management ideas I'm working on atop pentacle which involve squashfs and overlayfs, descendent of the way I used to do embedded linux for another project.
signpost: working on a formalized notion of a "job" which I can huck easily at a server running this system, and have it fire up and receive command/control via pest.
signpost: "job" here is basically a special signed-and-encrypted filesystem image.
thehorrors: well, here is where I disagree with heterogeneous systems. If you have identical systems, would you need such jobs?
thehorrors: it's a cool idea, don't get me wrong
signpost: you just buzz-worded at me, unpack the macros
thehorrors: well you said that no one's system will be identical, right?
signpost: my servers will certainly be identical.
signpost: yours will not be identical to mine, necessarily.
thehorrors: ok. Your concept of a job seems like a container, no?
thehorrors: why else would you need to exchange file systems instead of just saying "do this on this data"?
signpost: wtf does "do this on this data" mean aside "here's a binary, run and give it this input" ?
thehorrors: right
signpost: restate your question?
thehorrors: so why do you want jobs that entail exchanging file systems?
signpost: restate it again lol
signpost: at some point, you have a wad of program and data you want on some box
signpost: I am not spending the rest of my life polishing bespoke boxes by hand.
signpost: the things are getting a kernel installed on them and becoming part of a compute fabric I own.
bitbot: Logged on 2022-05-05 07:52:55 signpost: "job" here is basically a special signed-and-encrypted filesystem image.
signpost: and I'm not using fucking kubernetes to do that.
thehorrors: all I am trying to figure out is why do you want such "jobs" as you define them
signpost: explain what "heterogeneous systems" are to you, and why you disagree with them
thehorrors: "I have a different version of everything", practically meaning "you cannot assume what version of binaries etc I have (or a server has)"
signpost: you're misunderstanding.
signpost: when I say pentacle uses V as a fundamental principle, I mean that it's a machine into which *you* can load different vpatches than *me*.
thehorrors: right
signpost: thus we might mean very different things when we say we both run "pentacle"
signpost: when I'm discussing what I want to do with my servers, that assumes a uniform node substrate I build (and probably call a distinct piece of software from pentacle) which allows me to declaratively load jobs on any of the machines in my fleet.
thehorrors: okay. And all the servers you control will have the same vpatches.
thehorrors: the only detail here I want to clarify is the jobs themselves
signpost: the bitcoind job might have a statically linked bitcoind in it, and a script that fires it up.
signpost: maybe a ML job has a python and pytorch in it.
thehorrors: so my question was "why do you want to package jobs as filesystems"
signpost: programs are files in *nix
signpost: what's the alternative?
thehorrors: send a server a binary and data, an arhive, basically
thehorrors: why bother with a filesystem?
signpost: you're just giving an alternative without the merits of the alternative, but I'm happy to explain why I like this approach better.
signpost: but I'm running out of steam, so after this gonna hit the hay
thehorrors: that's all I was asking for. That's okay, we both might be getting a bit tired. GN, signpost, good talking to you
signpost: an archive is just a shitty filesystem image which you have to unpack somewhere, take up even more disk space with that.
signpost: then when you read it, it'll end up in the linux fs cache anyway in RAM
signpost: seems like mounting a squashfs is less duplicative.
thehorrors: I see, it has merit
signpost: then the use of overlayfs is for composition. two jobs might both want busybox's utils around for shell.
signpost: can have one busybox.squashfs, and union-mount w/e's different atop.
thehorrors: that explains it, thank you
signpost quite open to better ways, so long as same-or-better management of the linux system-state shitwad.
signpost: alrighty, gnite.
thehorrors: gnit, signpost, thanks!
dulapbot: Logged on 2022-05-05 03:26:06 signpost: because there is no centralized authority on what authors I accept in my local V.
dulapbot: Logged on 2022-01-21 20:44:32 asciilifeform: if a hero arises who comes up with an algo for forcing handles on a multi-level pestnet to actually stay unique -- let's all take off hats & use it
crtdaydreams: I've been thinking about this. What signpost mentions is a very similar problem regarding a decentralized WoT without an agent to say "this key belongs to xyz" and verify that.
crtdaydreams: 2 Solutions, one more novel than the other.
crtdaydreams: Firstly, it's important to make a distinction between a username and nick. Think in terms of IRC usernames e.g. cdd@, but my nick is crtdaydreams
crtdaydreams: username is a network identifier, a nick is just a handle
crtdaydreams: 1) Arguably less sophisticated solution, but werks. All peers are identified by their fingerprint and the entire notion of handles is purely client-side. When peering the peer will submit a handle, if the handle is already taken within your network the peers handle will default to "handle_fingerprint", from the client side you can then change the client-side handle of that
crtdaydreams: peer. If the /nick command is used by a peer in a chan, the same principle applies.
crtdaydreams: 2) Employs the use of a wot in which several peers can sign to say that "x key belongs to y handle" which can be automated. A simple "majority rules" would determine whether or not that peer can lay claim to that nick.
crtdaydreams: ^ would revert to above to resolve a name conflict wherein all partys hold the same trust for that nick
crtdaydreams: Now that I mention it, it feels too trivial, like I'm missing something. If tis' been thought of and rejected would like a link in logz.
asciilifeform: << think about it for a minute. it doesn't matter what kind of string is used 'in place of handle', a l2 or more distant station can still collide (deliberately or otherwise) and you have precisely same problem as when using handles strictly
dulapbot: Logged on 2022-05-05 05:45:14 crtdaydreams: 1) Arguably less sophisticated solution, but werks. All peers are identified by their fingerprint and the entire notion of handles is purely client-side. When peering the peer will submit a handle, if the handle is already taken within your network the peers handle will default to "handle_fingerprint", from the client side you can then change the client-side handle of that
asciilifeform: << there is no public key crypto in pest. pest keys are secret keys (i.e. known strictly to a given pair of peers), your statement makes 0 sense in context of pest
dulapbot: Logged on 2022-05-05 05:51:21 crtdaydreams: 2) Employs the use of a wot in which several peers can sign to say that "x key belongs to y handle" which can be automated. A simple "majority rules" would determine whether or not that peer can lay claim to that nick.
asciilifeform: crtdaydreams: ... and the various threads re why no rsa in pest.
dulapbot: Logged on 2022-01-24 11:58:52 asciilifeform: thimbronion: recall the orig. reason why pest is using symmetric crypto, btw
asciilifeform: << that's what even ~means~ to decentralize -- yes, 'everyone will have own little wot', which is exactly as it should be. there is no actual reason why wot needs 'universally agreed global state' at all.
dulapbot: Logged on 2022-05-05 03:07:30 thehorrors: well then there is not much value in decentralizing it - everyone will just have their own little wot
asciilifeform: observe that nuffin stops you from propagating the particular ratings you can see from your l1 to l2+ on request.
dulapbot: Logged on 2022-03-25 20:03:40 asciilifeform: (nuffin stops a peer from later adding the warez to his own share and then pass to ~his~ l1. is the logical way to propagate it.)
asciilifeform: << and what happens when someone walks off with (or via other means lifts the key from) the box ? or finds a way to get it to sign $arbitrary turd.
dulapbot: Logged on 2022-05-05 03:20:45 thehorrors: you can assign public keys (and therefore trust) to systems, they don't have to be people.
asciilifeform: mechanically-firing pubkey signers are a braindamaged concept.
asciilifeform: ( and walks straight into 'dao'-style lulz )
asciilifeform: << a decentralized wot is precisely a means for 'asking questions about keys' in such a way that one can post, for one's l1, the answers at a given time.
dulapbot: Logged on 2022-05-05 03:31:26 thehorrors: ok, well but then we can do without wot altogether to be honest. As long as everyone knows each other's keys, we can ask each other questions about the keys and be done with it.
asciilifeform: this is the correct way to implement a wot, such that it doesn't reduce to 'some d00d's www' which lives & dies with him; or to the ancient meatspace snail grind where you gotta write to yer l1, and ask'em to write to ~theirs~, and wait months/years for a complete picture
asciilifeform: it requires, yes, a usable secure p2p comms protocol, to implement. which at last exists.
asciilifeform: ( and in which, observe, the 'root of trust' is still manually-operated rsa signatures . as it oughta be. )
asciilifeform: crtdaydreams: see also e.g. this thrd re the essence of the problem of unique handles
dulapbot: Logged on 2022-01-19 22:02:03 asciilifeform: chains to begin with were asciilifeform's notion of how to give ~some~ measure of authenticity for l2+ hearsays
dulapbot: Logged on 2022-01-26 18:48:29 asciilifeform: thimbronion: current notion, summarized: we bite off 64byte from payload, and get 2 new fields, call'em 'unlock' and 'lock'. lock == h256(errything else in msg, incl. 'unlock', and unrevealed 32byte turd 'S'.); unlock = 'S' from yer previous msg.
asciilifeform: ^ ugly but asciilifeform suspects it is closest thing physically possible to a solution
verisimilitude: I suppose that would make the linked-list a doubly-linked-list, yes.
asciilifeform: verisimilitude: not precisely (in principle someone can forge a forward linkage once he has an old 'S'; however the forged chain is then ~distinguishable~, which is the point
dulapbot: Logged on 2022-01-26 12:23:03 asciilifeform: and of course dr.evil can still forge msgs in transit, so long as 1) he remembers, for all time, to withhold all further upstream ones 2) he is willing to be that his upstream victim has no other paths to the downstream dupes
verisimilitude: Yes, but forgery is already trivial, right?
asciilifeform: verisimilitude: aha
asciilifeform: aim there is to make all l2+ speakers ~distinguishable~
verisimilitude: If a packet drops correctly, someone can already impersonate others.
asciilifeform: verisimilitude: nobody can impersonate an l1 station (unless its key compromised)
asciilifeform: the issue is w/ l2+
verisimilitude: The L1 refers to those stations with registered keys, right?
asciilifeform: verisimilitude: refers to a given station's direct peers
verisimilitude: Okay; a packet gets dropped, but I get the copies; impersonation can happen here.
asciilifeform: aint clear what dropped packets have to do with it. atm anyone can emit anyffin at all marked as 'rebroadcast'
verisimilitude: I'll write more about Pest when I'll be closer to finishing my client.
asciilifeform: verisimilitude: didja read the spec ?
phf: was going to opine on wot, but actually gtg
verisimilitude: wtf wgl lol brb
asciilifeform: eh it aint as if there's some kinda hurry. let fella fix his tractor, feed horse, etc lol
verisimilitude: idk wym ymmv
signpost holds power button on verisimilitude down for 5sec.
asciilifeform installed an old-fashioned 'knife switch' mains switch yest., makes very satisfying 'thunk'
verisimilitude: Abbreviations being used so much is bothersome.
verisimilitude: Anyway, I repeatedly fail my self-imposed deadlines; my new goal for finishing a tiny little language service is within this month.
verisimilitude: I don't even like toki pona, but I'm nowhere near being able to write a Whitaker's Words program for Latin yet.
verisimilitude: I don't know how to write a CGI program, but there's a solution to that: I'm just going to expand the table to its passive form and add some URL rewriting rules to the Apache configuration. Even for Latin, it shouldn't be larger than one hundred mebibytes.
shinohai: jfc killfiles can't happen soon enough.
shinohai: $vwap
busybot: The 24-Hour VWAP for BTC is $ 39137.50 USD
verisimilitude: I'm that bad, am I?
mats: yes
asciilifeform: wb mats
verisimilitude: I just wanted to nudge the topic back to programming.
verisimilitude: Does anyone care to discuss tries, then, or something else?
dulapbot: Logged on 2022-05-05 13:05:32 asciilifeform: eh it aint as if there's some kinda hurry. let fella fix his tractor, feed horse, etc lol
signpost: dang, my mother just died of a heart attack.
signpost: pretty surprising, not much led up to it.
phf: signpost: please accept my condolences
signpost: thank you phf.
shinohai: Damn signpost my condolences as well. :/
signpost: shinohai: thanks bud
thimbronion: I am so sorry signpost.
billymg: very sorry to hear that signpost, my condolences
verisimilitude: That's unfortunate to read, signpost.
scoopbot: New article on A Syndication of Verisimilitudes: A Trivial Trie in Ada
asciilifeform takes off hat.
signpost: thanks all; fact of life.
bonechewer: Very sorry for your loss, signpost.
← 2022-05-04 | 2022-05-06 →