/indy0/🌐/1/gyuri/⭕/0/index 🔗

@links:

• @self
  • @view: /indy0/🌐/1/gyuri/⭕/0/index 
  • @sandbox: indy0pad.next
  • @web: indy0.peergos.me/1/gyuri/⭕/0
  • @parent:  indy0.peergos.me/1/gyuri
• @plex

@filename: indy0-🌐-1-gyuri-⭕-0

 

 refactor.practice-work/document

Abandon keeping a daily diary as a way to  track work by time

• Keeping a daily dary as a way to track worj=k
  • proved to be inadequate, and distractful.
  • That was not really practical
• Instead I started relying on the fact that 
  • anything that required real focus of attention 
  • resulted in annotation of worked on Web Hosted pages
  • when shared via hyperpost Peergos account
  • was also accessible to via.hypothes.is proxy

Use faceted search of annotations to get a slip stream of active Pages

• Using faceted search of annotations provided me with
  • dynamic listing in reverse chronological order
  • a list of all the recently annotated pages
  • much like the  slip stream in WikiNizer of old
  • did on a per browser basis.
• This new one is so much better. first of all it enables the listing of all pages
  • hosted on HyperPost in a recent period
  • and the faceted search can also allow filtering by annotators!
  • This brings the social aspect of hypothesis annotations
    • to give search capabilities that scale with hypothes.is
  • In any case hyperpost is built to be multiplayer and scalable
    • By design the IndraNet workspaces are shardeable by
    • named networks of networks
  • Eventually hyperpost will need to provide shared spaces for named
    • hlders of networks of networks of Peole or cascadeing down to
    • networks dedicated to some named common interest or pursuit
    •  
• filtered by path to hyperpost.peergos.me domain 
• gave a dynamic slip stream of significant document/work pages

That still left me without having a HyperMap of ongoing activities

This motivated me to setup indy0pad via IPFS infrastructure 

• so that we can be freed from 
  • the gotcha's of Peergos multi folder concurrent editing
  • work.how - avoid concurrent editing
    • collaboration on pages on the indyweb by multiple players
      • is setup such that each partiicipant in the collaboration
      • is assigned a unique nickname
      • and they all work on their own attributed to them copy of the document asynchronously
      • diffs can thus be computed and can be shown as suggestions both ways
    • when 1 works in their own space
      • before a Dot by indyWikiPad 
      • or a page is opened or a Page is opended by indy0pad the currently opened tabs are checked
      • and if the dot/Page is opened 

and rely on the fact that indy0pad actually saves pages by Trails folder path!

where folder path encodes intentionally named focus of attention orgamized by going from the more general to specific

 

---

share button on url bar

let's you designate a portin of the window/tab content

the image is copied to the clipboard after selection

ready to be pasted

👨‍👩‍👧‍👦

 

 

unstopable domains brave

TODO

Enable support of Unstoppable Domains in Brave?

Brave will be using Infura to resolve .altimist, .anime, .ask, .austin, .bald, .basenji, .bay, .benji, .binanceus, .bitcoin, .bitget, .bitscrunch, .blockchain, .boomer, .brave, .calicoin, .caw, .chomp, .clay, .crypto, .dao, .dfz, .doga, .donut, .dream, .emir, .ethermail, .farms, .grow, .her, .kingdom, .klever, .kresus, .kryptic, .lfg, .ltc, .manga, .metropolis, .miku, .ministry, .moon, .mumu, .nft, .nibi, .npc, .onchain, .pastor, .podcast, .pog, .polygon, .privacy, .propykeys, .pudgy, .quantum, .rad, .raiin, .secret, .smobler, .south, .stepn, .tball, .tea, .tribe, .u, .ubu, .unstoppable, .wallet, .wifi, .witg, .wrkx, .x, .xec, .xmr, .zil domain names that are on Unstoppable Domains. Brave hides your IP address. If you enable this, Infura will see that someone is trying to visit these domains but nothing else. See Infura's terms of use and privacy policy.