log
94 entries in 0.704s
mp_en_viaje: asciilifeform, word. the whole thing dovetails into another angle of whole gns thing indeed.
asciilifeform: atm we're doing quite a bit of hand-cranked mirrorism for this. but ultimately would make moar sense to have mechanism where gns(....hash....) spits out ~always~ e.g. diana_coman's log tape, or logotron.vpatch, or whatnot, for so long as can reach ~any~ tmsr machine
trinque: Mocky: can I encourage you to produce an ebuild for your gns item when done?
a111: Logged on 2019-06-22 15:18 Mocky: my work on gns is at the stage where I'm loading v fully into my head and making sure I know the questions I need to ask before I start implementing. I'll blog about it
Mocky: my work on gns is at the stage where I'm loading v fully into my head and making sure I know the questions I need to ask before I start implementing. I'll blog about it ☟︎
mircea_popescu: in other lulz : you may build and even install a proper wine (ie, configured without the derp-ass gcc "stack protection", that evidently doesn't work) ; and it'll even work, system-wide. however that doesn't mean playonlinux won't stick to its sadder, older version. and of course you can't just force-copy symlinks over in its holy directory, because they're all brokenly relative, and gns resolution works as shown in that p
mp_en_viaje: (gns is gns, a's can be domain names as they can be dictionary words. i can see the argument for "global warming" or w/e tv "celebrity" not resolving to anything.)
mp_en_viaje: at t4, another fellow named F looks to change gns so that a0 -> b8. this fellow goes through all the keys, loads up all possible tips (which are t1#t1, t2#t1, t3#t3, the last one ~in itself ambiguous at this point in our tale) and produces : on the first chain a t4#t2 ; on the 2nd chain a t4#t2 ; on the third chain a t4#t4, and signs all of these.
mp_en_viaje: suppose instead the fellow only knew K. he'd have pressed t1#t1, resulting in a gns a0->b0 ; a1 -> b2 ; a2 -> b5 and a manifest #t3.
mp_en_viaje: At t3, a fellow looks to add a2 -> b5 to the gns. suppose this fellow whose name is R knows only Q. Thus therefore he presses t2#t1, and so gns becomes a1->b1, a2->b5 while manifest becomes #t3.
mp_en_viaje: At t2, there is a patch upon t0#t0, transforming gns to a1->b1 ; manifest becomes #t1. this is signed by A, Q, G, B, N, I.
mp_en_viaje: At t1, there is a patch upon t0#t0, transforming gns to a0 -> b0 ; a1 -> b2 ; manifest becomes #t1. this is signed by A, W, F, G, U, K.
mp_en_viaje: At t0, there is a genesis, consisting of a gns file, containing a0 -> b0 ; and a manifest file, containing #t0.
Mocky: and i can also expand later on what's with the 'connecting', tcp? and what's with the directories, protocol on top of tcp? I'm hoping that its figurative and you don't literally want to build gns on tcp and http
asciilifeform: e.g. http://trilema.com/gns/mp etc
asciilifeform: http://btcbase.org/log/2019-05-03#1911006 << imho the correct use, given working gns, for errybody's stockpile of heathen dns names, is to park gateways ☝︎
mp_en_viaje: Mocky, so, what about dat gns ?
mp_en_viaje: obviously in time you'll discover that it's eminently not WORTH it to pay 10 bux or w/e to random empire of idiots pretend-authority. and obviously you'll discover it's fun to declare google.com or w/e whitehouse.gov == pronhub. but these future discovery is neither here nor there ; and the fact that my email currently addressed to mp@whitehouse.gov will start even being delivered once gns is live also doesn' tmatter that much
a111: Logged on 2019-05-03 04:27 Mocky: I see embrace and extinguish as more appropriate for dns destruction (ala a dnsmasq-esque approach) than isolated bunkers. I mean, i could have joined up with republic prime instead, but they already completed work on gns prime, and maybe they passed out ip based links for a while, but eventually pulled up the ladders to their tree forts and now they can't even be found. So who knows if republic prime or double prime even exists.
mp_en_viaje: how would fetlife slut know about gns anyway ?
mp_en_viaje: http://btcbase.org/log/2019-05-03#1910987 > i haven't used civillian dns for what, two years now. i dont' care to, either. this usecase is massively more important than "fetlife slut". for one thing, fetlife slut ain't reading anything anyway ; for the other thing, nothing forces you to limit yourself to gns if you don't want to. ☝︎
a111: Logged on 2019-05-03 03:18 Mocky: http://btcbase.org/log/2018-11-24#1874402 << this suggests that each key holder can only host $key/gns at one ip address. And what about vpatch ordering and the v manifest file? If i have an entry for archive.is and want to change that entry, I can't just make and sign a patch of my own, i have to patch on top of the 'consensus' press, otherwise manifest won't match and can't press multiple heads. Am I wrong about how that works?
Mocky: I see embrace and extinguish as more appropriate for dns destruction (ala a dnsmasq-esque approach) than isolated bunkers. I mean, i could have joined up with republic prime instead, but they already completed work on gns prime, and maybe they passed out ip based links for a while, but eventually pulled up the ladders to their tree forts and now they can't even be found. So who knows if republic prime or double prime even exists. ☟︎
Mocky: http://btcbase.org/log/2019-05-01#1910435 << using gns as proposed, I don't see any other way than passing out ip based links. I can't send a blog link to a slut on fetlife who doesn't have cuntoo, nor can i send a link to cuntoo guide. The whole thing seems like tree forts connected with tin cans and string. For gossipd I have no objection, for name resolution of published material? How is it even published if 'must be this tall to ☝︎
a111: Logged on 2018-11-24 19:51 mircea_popescu: i ~suppose~ one manner of handling this is the followingf convention : patches to be acquired from $key/gns/ dir, for all keys in the seals ring. so it'd look for "6160E1CAC8A3C52966FD76998A736F0E2FB7B452/gns" which is not a "valid" domain per usg.verisign "rules" however it DOES resolve in our own system. because we can put ips on anything we want.
Mocky: http://btcbase.org/log/2018-11-24#1874402 << this suggests that each key holder can only host $key/gns at one ip address. And what about vpatch ordering and the v manifest file? If i have an entry for archive.is and want to change that entry, I can't just make and sign a patch of my own, i have to patch on top of the 'consensus' press, otherwise manifest won't match and can't press multiple heads. Am I wrong about how that works? ☝︎☟︎
Mocky: http://btcbase.org/log/2019-05-01#1910400 << I want to do the dns. I was reading recently: http://btcbase.org/log-search?q=gns ☝︎
mircea_popescu: asciilifeform so basically it all comes down to a gns absence issue ?
trinque: once off that, I might see about ebuilding trb (with perhaps phf's v+portage work if it surfaces), and then mircea_popescu's gns v-tree, unless gpg replacement surfaces soon, in which case deedbot->peh work
spyked: http://btcbase.org/log/2018-11-27#1875439 <-- this has been on my mind after seeing http://trilema.com/2018/this-gns-thing/#selection-317.47-317.193 . the next immediate step in my queue after publishing rss bot vpatches will be to look at automating communication with deedbot. ☝︎
mircea_popescu: trinque incidentally, you ever read http://trilema.com/2018/this-gns-thing/ ?
mircea_popescu: incidentally, re http://btcbase.org/log/2018-11-25#1874601 it occurs to me i should probably also share the echo "FC66C0C5D98C42A1D4A98B6B42Fv9985AFAB953C4/17215D118B7239507FAFED98B98228A001ABFFC7/gns" | sed 's%.\{1\}%&<wbr />%g' that produced it. ☝︎
mircea_popescu: http://trilema.com/2018/this-gns-thing/ << fixed, finally.
deedbot: http://trilema.com/2018/this-gns-thing/ << Trilema - This GNS thing...
mircea_popescu: billymg it should look like this : http://trilema.com/2018/this-gns-thing/#selection-141.91-153.102
asciilifeform: y'mean gns ? or renamed
mircea_popescu: cracking dns, replacing with gns, makes the world fucking work already.
mircea_popescu: and so therefore, how about this convention : re-dld gets ~all~ keys from seals dir ; looks in $key/gns for patches. dumps all the found ones in a dir, then proceeds to build and press tree, that's the hosts and that;'s it.
mircea_popescu: i ~suppose~ one manner of handling this is the followingf convention : patches to be acquired from $key/gns/ dir, for all keys in the seals ring. so it'd look for "6160E1CAC8A3C52966FD76998A736F0E2FB7B452/gns" which is not a "valid" domain per usg.verisign "rules" however it DOES resolve in our own system. because we can put ips on anything we want. ☟︎
a111: Logged on 2018-10-15 19:34 asciilifeform: for instance 1 possible answer is 'no files, errything is an s-expression, and names live in gns'
asciilifeform: for instance 1 possible answer is 'no files, errything is an s-expression, and names live in gns' ☟︎
mircea_popescu: thinking about this, it's fucking evident what difference the online made for the thinking mind. yes i was a child, but child or no child, it didn't occur to me that i must have a gns link to the item that i like. "this" and pointing was an acceptable manner of reference in the 90s, because why the hell wouldn't it be and what's a global namespace anyway.
mod6: I can delcare the v054 release with a manifest of my own ala: To declare a "release", an author's GNS pointer for a project would point to his selected manifest.
mircea_popescu: yes. his intuition is correct, eventually will grow into gns.
trinque: esthlos: ^ gns updated
mircea_popescu: are we specifiing a gns standard for these ?
mircea_popescu: gns:mircea/writings/trilema/categories/ is just about the only way to corectly refer to the item.
mircea_popescu: myeah. the only problem is that i suspect the unix notion of filenames (if ~properly~ regarded, ie, full paths) is actually entirely correct, and how gns will have to work anyway.
mircea_popescu: gns, when.
mircea_popescu: http://btcbase.org/log/2018-02-02#1779464 << this is an iffy point, currently mostly used to serve imperial nonsense/crapola, but we might end up wishing to overload it. see whole http://btcbase.org/log-search?q=gns thing ☝︎
mircea_popescu: item eminently doesn't deal with "programs" or "applications" or anything ; it's a proper url system, it locates resources. can put in the gns that you're a dentist in kennebunkport, maine, and if i need a dentist...
mircea_popescu: so announcement of a new partch would be author changing his gns entry for X from press-to-q to press-to-k ; if user is disinterested he jkust gets dragged along, otherwise if user requires he sign local copy he stays put.
mircea_popescu: there's no requirement that the gns even be properly global ; it's your job to make it global-locally and that's that.
mircea_popescu: 4. in all cases, a container consists of a tag and binary data ; the tag section of the gns tells it what v trees are acceptable applications upon that data.
mircea_popescu: 2. the client queries whichever gns it is configured to, and inquires as to contacting machines which hold data related to this item. it receives a list of them, on the basis of what signatures mircea_popescu told it to trust signed.
mircea_popescu: as for the gns above, no obligation.
mircea_popescu: so gns is basically just a lengthy registrar of assignments, a=b sorta thing, signed by keys.
mircea_popescu: asciilifeform in ~principle~ a container could tell you what class of procedure it wants to be eaten by ; and gns could tell you which v-trees implement it.
mircea_popescu: so tell me how is pstp going to work without a gns to reference container content names ?
mircea_popescu: http://btcbase.org/log/2018-01-05#1765100 << this is a gensym in the sense girl you met at butcher's is your true love. why not call gns like sane people. ☝︎
mircea_popescu: yes we don't have a gns yet, but this doesn't excuse us from... doing the same computations by hand as if we had it! it's not suddenly allowable to go "well since i have no running water i therefore do not wash". no bitch -- since you have no running water, you walk fifty miles uphil each way to GET water in a bucket. still wash.
mircea_popescu: the oither problem is of course that this lays right into gns
a111: Logged on 2016-11-23 16:07 mircea_popescu: think - currently deedbot administers a very narrow implementation of the gns, whereby if you claim to own X domain, it challenges you and if you pass it gives it to you.
ben_vulpes: "gns"? http://btcbase.org/log/2016-11-23#1572653 ☝︎
a111: Logged on 2017-07-09 04:11 trinque: concretely, I would like to connect to your lisp instance from mine and be able to interrogate it for classes of objects it contains, for particular instances (i.e. there is a global notion of identity, global addressing, see threads on GNS), get instances which match some predicate...
trinque: concretely, I would like to connect to your lisp instance from mine and be able to interrogate it for classes of objects it contains, for particular instances (i.e. there is a global notion of identity, global addressing, see threads on GNS), get instances which match some predicate... ☟︎
Framedragger: http://btcbase.org/log/2016-12-27#1590857 << i guess so. i also guess that gns/gossipd are competing paradigms in terms of namespace / choosing how to name things. but they can also be orthogonal, i'd think.. ☝︎
Framedragger: i guess one may have a database of keys, as well as a table of signed-with-key nicknames which establish someone claiming a nickname for key? sort of gns. alternative scheme is to have any kind of aliasing be local, as per gossipd. less convenient for things like looking up nickname in wot.deedbot.org of course.
mircea_popescu looks up meaning in gns, is unaffected.
mircea_popescu: in principle can index by any of the three for new software / maintain current association for extant software, and be ready to migrate when we finally have a proper gns
a111: Logged on 2016-11-23 16:15 mircea_popescu: and it'd be gns://trilema.com/
mircea_popescu: asciilifeform you realise, deedbot searched me in its own copy of the gns. by fp.
mircea_popescu: all our uses, in deedbot, in voicing model, in wot, in v, all rely on the concept of fp as gns namespace.
mircea_popescu: and it'd be gns://trilema.com/ ☟︎
mircea_popescu: gns:// plox
Framedragger: so deedbot or gns would decide on the allowed fingerprinting schemes.
mircea_popescu: think - currently deedbot administers a very narrow implementation of the gns, whereby if you claim to own X domain, it challenges you and if you pass it gives it to you. ☟︎
mircea_popescu: gns is not dns ; it will hold any symbols you realise.
Framedragger: the N-to-1 relation (many possible ratings for one name) needs to be stored somehow, i suppose it may be multiple gns fields, but then it is the case that not *all* fields of a specific name are controlled by the name's owner; or, there's a separate service / storage thing.
mircea_popescu: in principle it would be very gns-based. if i sign btcbase/logs mkj.lt/log trilema.com etc, you can do "signed:mp" in your search box and get results from THESE
Framedragger: i suppose the system could then also integrate with gns, in the sense that gns-listed content could in principle be searched, too..
mircea_popescu: we're even contemplating making a proper gns to be fed through dns pipe, much to alf's chagrin.
mircea_popescu: currently, you can not register a gns item. at some point X, you will become able to. thenceforth, you will be able to. that's the whole timeline.
a111: Logged on 2016-11-16 00:34 Framedragger: because it would be great if WoT-gns worked like other WoT things, i.e., via the enforcement of WoT itself.
Framedragger: because it would be great if WoT-gns worked like other WoT things, i.e., via the enforcement of WoT itself. ☟︎
trinque: ben_vulpes: there's one important distinction here. the gns has a WoT identity running it.
Framedragger: mircea_popescu: i guess in your view, perhaps no viable conflicts would arise in gns? say, two owners of two distinct pgp keys claiming ownership of "apple.com". some kind of due process is to take place, presumably
Framedragger: right. how would the process of resolving conflicts in gns look like, though? (i'm just curious, i.e. question is well-intentioned, not troll-y)
mircea_popescu: up SOMEWHERE. that's the gns.
Framedragger: so the notion of a local symbol frame/context will be retained inevitably, is that what you're saying mircea_popescu? (in which case i'd add that gns-the-implementation could even probably be used - on each interested user's machine - as a local name system. etc.)
mircea_popescu: asciilifeform i would say the gns as discussed on trilema drastically reduces it.
Framedragger: personally i don't see why there could not be a GNS which would be separate from commitments to specific transport standards. have a table, have a transport layer, swap the layer later. i may be naive in regards to the "swap" step, i guess... :/
decimation: "Aircraft conducting WAAS approaches must possess certified GPS receivers, which are much more expensive than non-certified units. In 2006, Garmin's least expensive certified receiver, the GNS 430W, had a suggested retail price of US$10,750.[27]"
herbijudlestoids: personally i prefer implementations like the GNUnet Name System (GNS)