x

helia

Interpersonal - reading - social annotating and conversations starting on the margins - threaded - intentional - interest based - mission bearing pursuances - conversational - co-authoring - co-evolutionary - personal first - offline first - long term - ambient - autonomous - private first - commons based - evergreen - open - FAIR - Findable, Accessible, Interoperable, Reusable, - with full provenance - recapitulable retraceble history of coevolution of ideas - intertwingled mutual learning symmathesy

suggest the term Actors

forming interpersunal networks of trust for trust

Everyone would have their own little localhost web server as part of the indynet kernel at sya indy.localhost to host their own interpersonal social networks connecting people they trust at progressive levels for mutual engagement. Once peope are invited to the indynet they can be a nod in its further reach

I annotate there fore I am

and weave with it the Interpersonsl Web, the IndyWeb with the right writing tools

[per an note](

ipns://k51qzi5uqu5dj5k3i25zo6bh2anhc587l7y6uc08fnc18nuiougazlvy7m5p98/viewer/web/viewer.html?file=https://bafybeidpugqajmaik7c5c4ewvwoybmw76zgqunob76kyndxo6glbqtqrgi.ipfs.w3s.link/yarrow%20-%20rays%20of%20encyclogenesis.pdf

perm an note

I annotate there fore I am

and weave with it the Interpersonsl Web, the IndyWeb with the right writing tools

https://opencollective.com/open-learning-commons/projects/indy-learning-commons

4 - yarrow

• identifies it as
  • something you always wish to keep available,
• exempting it from the routine garbage collection that
  • IPFS does on infrequently-used items
  • in order to efficiently manage storage space.

in addition to remote pinning services

be online once a day to renew ipns

CORS Header - allow cross-origin (CORS) requests from your dev server

no CLI

not ipns

Ther importancer of Distributed Hypertext networks were apprecited decade beofre the web

The Web was dumbed down enough to be made widely available. So when Ted nelson fam ously said to the Web conference referring to the Web

wthe future is in my past" actually the future of the web that we may be able to realize now was already running on Nuclear Submarin a decade berofre the Wb appeared

call that a privacy focused browser?

🖧

use this icon to designate localhost development environment

yarrow

from : https://hyp.is/XInHsD3nEe6tU79piYu0ug/adventofcomputing.libsyn.com/episode-79-zog-military-strength-hypertext

https://dweb.link/ipfs/bafybeigkkejifiutmpygurrhs5e43hwgk3eg5qxbc62cpnwt6qp5crbsxm?filename=PROMISHistory.pdf

We're getting back to my hypertext series with a big of an obscure tale. ZOG is a hypertext system what was first developed in 1972 at Carnegie-Melon University. It then stagnated until the latter half of the 1970s when it was picked back up. By 1983 it was cruising on a US Navy aircraft carrier. ZOG presents a hypertext system with some very modern notions. But here's the part that gets me excited: ZOG was developed after Doug Engelbart's Mother of All Demos. So, in theory, ZOG should take ques from this seminal event. Right? ... right?

x

from : https://hyp.is/0Qxxuj_uEe6Pfydmb3P2SA/www.google.com/search?q=declaration+independence+cyberspace+ipfs&oq=declaration+independence+cyberspace+ipfs&aqs=chrome..69i57j69i60l2.13663j0j1&sourceid=chrome&ie=UTF-8

x

search : declaration independence cyberspace ipfs

https://github.com/web3-storage/w3name 1/5

IPNS client and service for generating, updating, and tracking immutable names with signed updates View license 39 stars 10 forks 4 watching Activity Public repository Branches Tags View code

⁂

w3name

original : https://github.com/web3-storage/w3name

ipns://k51qzi5uqu5dj5k3i25zo6bh2anhc587l7y6uc08fnc18nuiougazlvy7m5p98/indy.web.hyp/pdf.viewer/viewer/web/viewer.html?file=https://bafybeiannkaihb7fqfsavdjpsin4kzrqgmkvwgtbzdm665jtziyzrh6hia.ipfs.w3s.link/web3-storage_w3name_%20IPNS%20client%20and%20service%20for%20generating%2C%20updating%2C%20and%20tracking%20immutable%20names%20with%20signed%20updates.pdf

copy paste it into a Brave browser

use this module

source

"self-issued" names

Just what we need to create "dynamic Named Everything Networks"

native to the Web

⁂

w3name

a dynamic web =

IPNS works by - using public key cryptography to - allow "self-issued" names

which don't require any - coodination or central authorities.

The caveat is that the definition of "name" is - somewhat constrained compared to - general-purpose key/value storage systems.

// problem

• • how ? can we assure
  • that everyone has the same view of the network

// solution

• empower each indyvidual to be an autonomous actor
• participant on their own(ed) networks
• connecting people, ideas, and autonomous capabilities
• unsing unenclosable carriers for sharing collaborationg
• on ling term info structures using tinkerable
• capabilities supported by long term emergent in the long tail infra sructure for
• storage, compute and communication
• where everything can be co-evolved with full provenance

• and recapitul-able history of their becomings.

4

• what's in a name?
• what's in a link

• Naming

s famously one of the few hard problems in computer science,

the exact number of which vary - depending on the computer scientist you're speaking with and - their predisposition to off-by-one errors.

civilization of the Mind

cyberspace

home of Mind

cyberspace the new home of Mind

which feeds hypernormalization

protocol for intertwingularity

<svg data-v-4cf932a9="" fill="none" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 116 135" alt="ProtoSchool" class="w3"><path data-v-4cf932a9="" d="M58.291 0L0 33.518v67.035l58 33.517 58-33.517V33.518L58.291 0zm53.92 44.593l-33.226-27.98 33.518 19.236v8.744h-.292zM13.407 63.246L25.94 28.563l8.16-1.457-20.693 36.14zm23.025-34.1h43.719l21.859 37.89-21.86 37.889H36.433l-21.86-37.89 21.86-37.89zM11.658 67.909l20.694 36.141L8.744 75.779l2.914-7.87zm65.578 39.93l-36.14 6.412-5.247-6.412h41.387zm25.94-37.015l-12.533 34.684-8.16 1.457 20.693-36.14zm1.749-4.663L83.94 30.02l23.608 28.27-2.623 7.87zm-65.87-39.93l36.141-6.412 5.246 6.412H39.055zm35.85-9.035l-44.01 7.87 37.014-13.408 6.995 5.538zM23.316 27.688L8.16 69.658l6.995-39.055 8.16-2.915zM6.704 77.528l28.562 34.392L4.955 86.271l1.749-8.743zm34.974 39.638l44.01-7.87-37.306 13.408-6.704-5.538zm51.588-10.784l15.156-41.97-6.995 39.055-8.16 2.915zm16.613-49.84l-28.854-34.1L111.337 47.8l-1.458 8.744zM65.869 9.036L24.774 23.9 58.29 4.663l7.578 4.372zM11.95 31.477L4.08 74.613V35.85l7.87-4.372zm-7.869 58l33.518 27.98L4.08 98.221v-8.744zm46.634 35.558l41.095-14.864-33.517 19.236-7.578-4.372zm53.919-22.442l7.578-43.136v38.764l-7.578 4.372z" fill="url(#paint0_linear)"></path><defs data-v-4cf932a9=""><linearGradient data-v-4cf932a9="" id="paint0_linear" x1=".136" y1="67.052" x2="116.42" y2="67.052" gradientUnits="userSpaceOnUse"><stop data-v-4cf932a9="" stop-color="#22F2AD"></stop><stop data-v-4cf932a9="" offset="1" stop-color="#AB21F4"></stop></linearGradient></defs></svg>

<svg data-v-4cf932a9="" fill="none" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 116 135" alt="ProtoSchool" class="w3"><path data-v-4cf932a9="" d="M58.291 0L0 33.518v67.035l58 33.517 58-33.517V33.518L58.291 0zm53.92 44.593l-33.226-27.98 33.518 19.236v8.744h-.292zM13.407 63.246L25.94 28.563l8.16-1.457-20.693 36.14zm23.025-34.1h43.719l21.859 37.89-21.86 37.889H36.433l-21.86-37.89 21.86-37.89zM11.658 67.909l20.694 36.141L8.744 75.779l2.914-7.87zm65.578 39.93l-36.14 6.412-5.247-6.412h41.387zm25.94-37.015l-12.533 34.684-8.16 1.457 20.693-36.14zm1.749-4.663L83.94 30.02l23.608 28.27-2.623 7.87zm-65.87-39.93l36.141-6.412 5.246 6.412H39.055zm35.85-9.035l-44.01 7.87 37.014-13.408 6.995 5.538zM23.316 27.688L8.16 69.658l6.995-39.055 8.16-2.915zM6.704 77.528l28.562 34.392L4.955 86.271l1.749-8.743zm34.974 39.638l44.01-7.87-37.306 13.408-6.704-5.538zm51.588-10.784l15.156-41.97-6.995 39.055-8.16 2.915zm16.613-49.84l-28.854-34.1L111.337 47.8l-1.458 8.744zM65.869 9.036L24.774 23.9 58.29 4.663l7.578 4.372zM11.95 31.477L4.08 74.613V35.85l7.87-4.372zm-7.869 58l33.518 27.98L4.08 98.221v-8.744zm46.634 35.558l41.095-14.864-33.517 19.236-7.578-4.372zm53.919-22.442l7.578-43.136v38.764l-7.578 4.372z" fill="url(#paint0_linear)"></path><defs data-v-4cf932a9=""><linearGradient data-v-4cf932a9="" id="paint0_linear" x1=".136" y1="67.052" x2="116.42" y2="67.052" gradientUnits="userSpaceOnUse"><stop data-v-4cf932a9="" stop-color="#22F2AD"></stop><stop data-v-4cf932a9="" offset="1" stop-color="#AB21F4"></stop></linearGradient></defs></svg>

There's now one universal domain: the domain of all possible values.

keys derived from content

guk

globally unique keys

x

content addressing - uniquely identify any piece of data using a cryptographic hash of the data itself.

• module-scoped function and classes

⁂ w3name

dynamic permanent using raw ipns

paste this to Brave browser that understands the ipns protocol

ipns://k51qzi5uqu5dj5k3i25zo6bh2anhc587l7y6uc08fnc18nuiougazlvy7m5p98/indy.web.hyp/pdf.viewer/viewer/web/viewer.html?file=https://bafybeiannkaihb7fqfsavdjpsin4kzrqgmkvwgtbzdm665jtziyzrh6hia.ipfs.w3s.link/web3-storage_w3name_%20IPNS%20client%20and%20service%20for%20generating%2C%20updating%2C%20and%20tracking%20immutable%20names%20with%20signed%20updates.pdf

IPNS works by - using public key cryptography to - allow "self-issued" names

which don't require any - coodination or central authorities.

The caveat is that the definition of "name" is - somewhat constrained compared to - general-purpose key/value storage systems.

// enquiry

• • how ? can we assure
  • that everyone has the same view of the network

4

• what's in a name?
• what's in a link

search - "symbolic unity" trailmarks

<svg id="mdn-docs-logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 361 104.2" style="enable-background:new 0 0 361 104.2" xml:space="preserve" role="img"><title>MDN Web Docs</title><path d="M197.6 73.2h-17.1v-5.5h3.8V51.9c0-3.7-.7-6.3-2.1-7.9-1.4-1.6-3.3-2.3-5.7-2.3-3.2 0-5.6 1.1-7.2 3.4s-2.4 4.6-2.5 6.9v15.6h6v5.5h-17.1v-5.5h3.8V51.9c0-3.8-.7-6.4-2.1-7.9-1.4-1.5-3.3-2.3-5.6-2.3-3.2 0-5.5 1.1-7.2 3.3-1.6 2.2-2.4 4.5-2.5 6.9v15.8h6.9v5.5h-20.2v-5.5h6V42.4h-6.1v-5.6h13.4v6.4c1.2-2.1 2.7-3.8 4.7-5.2 2-1.3 4.4-2 7.3-2s5.3.7 7.5 2.1c2.2 1.4 3.7 3.5 4.5 6.4 1.1-2.5 2.7-4.5 4.9-6.1s4.8-2.4 7.9-2.4c3.5 0 6.5 1.1 8.9 3.3s3.7 5.6 3.7 10.2v18.2h6.1v5.5zm42.5 0h-13.2V66c-1.2 2.2-2.8 4.1-4.9 5.6-2.1 1.6-4.8 2.4-8.3 2.4-4.8 0-8.7-1.6-11.6-4.9-2.9-3.2-4.3-7.7-4.3-13.3 0-5 1.3-9.6 4-13.7 2.6-4.1 6.9-6.2 12.8-6.2s9.8 2.2 12.3 6.5V22.7h-8.6v-5.6h15.8v50.6h6v5.5zm-13.3-16.8V52c-.1-3-1.2-5.5-3.2-7.3s-4.4-2.8-7.2-2.8c-3.6 0-6.3 1.3-8.2 3.9-1.9 2.6-2.8 5.8-2.8 9.6 0 4.1 1 7.3 3 9.5s4.5 3.3 7.4 3.3c3.2 0 5.8-1.3 7.8-3.8 2.1-2.6 3.1-5.3 3.2-8zm61.5 16.8H269v-5.5h6V51.9c0-3.7-.7-6.3-2.2-7.9-1.4-1.6-3.4-2.3-5.7-2.3-3.1 0-5.6 1-7.4 3s-2.8 4.4-2.9 7v15.9h6v5.5h-19.3v-5.5h6V42.4h-6.2v-5.6h13.6V43c2.6-4.6 6.8-6.9 12.7-6.9 3.6 0 6.7 1.1 9.2 3.3s3.7 5.6 3.7 10.2v18.2h6v5.4h-.2z" class="logo-text"></path><path d="M42 .2 13.4 92.3H1.7L30.2.2Zm10.4 0v92.1H42V.2Zm40.3 0L64.2 92.3H52.5L81 .2Zm10.4 0v92.1H92.7V.2Z" class="logo-m"></path><path d="M294 95h67v8.8h-67z" class="logo-_"></path></svg>

A name in IPNS is - the hash of a public key. - It is associated with an [IPNS record](https://hyp.is/8-qqdjxvEe6T8iddBKxUOQ/specs.ipfs.tech/ipns/ipns-record/} (/ipfs/CID) it links to and - other information such as - the expiration, - the version number, and - a cryptographic signature

signed by the corresponding private key.

New records can be signed and published at any time - by the holder of the private key.

https://hyp.is/qJx55PxNEe2WsvOtqF2XdQ/en.wikipedia.org/wiki/CAP_theorem

We Need to empower people to act as Autnonomouls HyperPlexMedia Actors

personal Agents

Human's as autonomous human actors in the the IndyVerse of Open HyperPlex Media

for - HCI - IndyWeb - Actor Model

HCI

HCI

ACM is for the Machines not for us

boostrapping a - Personal First - InterPersonal - Virtual - conversational - born collaborative - Autonomous - HyperPlexMedia Spaces - or Mutual Open Learning Commons

Indy Learning Commons

https://opencollective.com/open-learning-commons/projects/indy-learning-commons

boostrapping a - Personal First - InterPersonal - Virtual - conversational - born collaborative - Autonomous - HyperPlexMedia Spaces - or Mutual Open Learning Commons

Indy Learning Commons

https://opencollective.com/open-learning-commons/projects/indy-learning-commons

1280x720 resolution to create recordings of work

IPFS Desktop

just use that

for - DELL machine icon

needed to disambiguate indy space/device/browser combinations

user tracking platform right into the browser

overage fee

permanent deletion

private sensitive unencrypted

generate a CAR file

4 IPFS

export/html

for - htmx

youtube

bypass

how could we ensure that anyone do that?

Groot Search

GRoot Search

SSuite Progressive Web Apps

Cloudless Software

• no registration
• no account
• online or
• offline
• safety and privacy guaranteed

tml5 video player

docdrop

)

• from : https://twitter.com/TrailMarks/status/1278221135793000448

4 - software internet

)

one eye people run things the two eyed are in for a rough time

universal access to tools

mental

)

sanity and health immunological

typo

search - intertwingularity

collaboration at scale

• hierachical = categorizable
• sequential

online editor

WebNative

What if the only thing you need is a browser

No Cloud

for al people

not users

EDL

Edit Decision List

-

In the presentation, the document from which Nelson quotes from on the Xanadu translator is presented on the screen as a long series of characters that generally look like a long hyperlink. Within the link, the extracted string of text from the quote that ensures that the “address of the content never change” (Nelson says this is KEY). Such spans of content are non-breaking links and do not break with the EDL.

• any designated high resolution content fragment when annotatd, linked to or otherwise reference from with the IndyPlex, part can be shareable with full attribution and link to the source

flipp copy right any content that an individual engages with should be high resolution archive-able privately - offline first - private first

IndyPlex adds to Unbreakable Lints - Permanence of Content - Permanence of intertwingled Global Giant Associative comPLEXes - verifiable, permanent attribution to the Autnonomous Human Actors that created/contributed to any content throug interpersonal trustnetwored communication with full provenance and replayable verifiable history - on request - or openly available when shared in the commons

4 : HyperPlex

The XANADO model

Fix?

x

PWA Custom file Viewers

sandboxing system - isolates UI from in-memory content

wisdom is the Delta between - what measurement-based management Theory tells you to do and - what the right thing to do is - that's how I would define wisdom and

that's the thing if you want to optimize for anything on the return on - it's that is it's the only thing that and safely Steward the amount of technological power we have

so I don't want data driven anything - I want data informed but - there's so much sensible stuff that <br /> - we can sense at some level that we cannot quantify - that has to be factored when the Old Testament says in the top 10 things not to do - up there with murder and rape is

not have false idols - the measurement of reality and - the modeling of reality - is what it's talking about the false idol is our model of reality where we optimize for that rather than reality we're rather than be in direct sensory connection to reality we look at reality through our model

ipfs

x

template no longer works - organization by entity - CRUD centric thinking // to bad It's the connections that matter

'Tain't what you deal with that matter but why and how you do what you need to do to accomplish what intent flow process goal!

the way you connect the meaings of the connections and their emnergent composition Wholeness of intent and its implicate ordr if you just let it self-actualize thorugh articulation

reference architecture

prescriptive code templates

micro services have - controller - mediator - service - repository abstraction

// NB It is not abstraction we need but customization/transormation/adapter

The ultimate evolution from SQL to No SQL to anti database

it does not work

delegates to the next layer down

way too blury

problem invoice

crud centric

invoice server repository spread out in the system

lot more operations than CRUD

10 15 operations beyond

anything that touches an invoce

on big method here closure

method chain

abstracting methods out

unrelated operation

need to do instead is to

xxx

reasong not one layer at a time but one use case at a time accross layers and layyers

switching from sQL Server to Postgress

single entity at a time slow chatty

inversion of control tools unusually complex idesign

service boundaries

delineate responsibilities

prescriptive architecture

overcomplicated

onion architecure

the very things that promise better maintainability cause things to become unworkable over rtime

Mike Tyson

hibernate had its day

younger developers which means everybidy but me

Long Term info structure with long term evergreen easy to co-evolve infrastructure and sharding information about people by giving them custody and follow the intentional associative complexes connecting people information in desired consteallations of communication, storage and computation as required easy to change coevolve., deep cpupling with holistic holonic co-evolutionary self organising growth

what folks can now call vertical slice architecture just the idea that I am going to organize first by cohesive features within the system a bit of functionality and I'm trying to show this here I'm showing separate databases it doesn't necessarily mean you're automatically having a giant modular monolith that's targeting six eight totally different databases just that if a segment of the database whether it's a schema a set of collections if at least between features could be a little bit Loosely coupled from each other that even if you're a monolith if you could do upgrades this at a time one feature at a time that's practical you can convince product owners of hey we can do this upgrade in our case it's it's not necessarily an upgrade it's cheap right we kind of like to replace SQL server with postgres and some of our big systems just purely cost savings it would be nice if we could do that if we could tackle it more bit wise a Sprint by Sprint we could deliver in a Sprint we could deliver switching part of the app from SQL Server to postgres but there's no way in hell within one Sprint we could ever do the whole whole horizontal layer that's something to think about other weakness layered architecture they talk about well you can reason about one layer at a time you never reason about one layer at a time you reason about one use case at a time the full vertical stack hopefully you can concentrate on only the business logic or only the data access logic but likely when you have customer problems when you have integration tests failing you need to trace tightly related code from entry point to controller level to data access layer to service level to entity the tightly related code put it together keep it as close together in your code as you possibly can that means you're going to lose out on some of that that rigor that people try to do through project references people try to force this kind of loose coupling rule by setting all those kind of rules of you know this project can only access that project and can only have these Tack and all that that's great um it's extra overhead it's extra friction on you it's just better if developers can be disciplined instead okay I want to keep harping on keep harping on a little layered architecture just a little bit

not practica

real developer

not super great with PowerPoint

despise layered architecture

needs to go

write a little bit of code up here come and make a little bit of change way down here another change way down there when you're writing it you get the boiling frog problem you don't notice this at first when you're just dropping a few new classes in this adds up when you get really late 10 years later five to ten years later

separate jar

pur it here seemed a good idea at the time# location addressing instead of intentional addressing

named intent networks with composability and exchangeability guaranteed

separation of concerns bad too

we want integral design

where can have holonic components that are swappable, exchangeable

depending on need without effecting the intent of the software system

optionaility for all possible constellations of infrastuctural scaling concerns are themselves sqappable because the "Business Logic" the intent is formulated in uiversal terms independent of infrastructural concerns

so there is separation but not in some layers

but by design

Simonyi's law

Slay those layers

the future is layerless

question tech that needs layers

the problems incurred in large systems

and here what I mean is one of the early days of my current position I was asked hey Jeremy can you put together a reference architecture a reference template for what microservices or services are going to be and I partially out of laziness somewhat out of hey that's actually kind of dangerous when you set up a detailed reference architecture we'll get into this a little more the the key risk there is people will actually follow it

databse abstraction

least common denominator

we don't want to share our Rich domain model entities over a web service so we'll put some kind of mapping layer in there specifically to not share types go too far with that um that's why I design shows up go too far with that and what you do is you add a lot more mental overhead to understand the system how many jumps does any data element in the system go through mapping layer to service layer to mediator to a command over here

everything you do for the sake of loose coupling also comes with a little bit of cost of just **extra junk to try to keep track of **

Slay those Layers with Integral Intentional flipped Design

swap the databse layer later

least common denominator

very slow

the pan

everything works at first

googleable

a quality all by itself

https://jeremydmiller.com

going to complain about things that you're otherwise being told are the best practices in software architecture which they may actually be we're not going that badly

question tech that needs layers

the future is layerless

Social annotation is the best way to have meaningful discussions, without the disorganization of social media, message boards, and comment sections.

-# testing : sectionMark - one - two

-issue - experiment - make : plexMark MarkIn notation MarkDown compatible - the terminology for what we used to call TrailMarks is converging - have a new name for it PlexMark - experimenting with new matkdown compatible markin notation

search : windows 10 wifi status not showing

these connection are not connecting data points

but 'thought Vectors in Concept Space'