Welcome to the [[Agora of Flancia]]!§

The Agora is a [[Free]] [[Knowledge]] [[Commons]] for the benefit of beings.

Navigating§

A quick tour of the Agora might be the best way to communicate its underlying goals and the core concepts behind it:

• A Node is the set of community contributions whose titles match an Agora location (i.e. what you searched for or the [[wikilink]] which brought you there).
  • You can see the list of all [[Nodes]] in this Agora.
  • You can also visit special location [[Random]] which will send you to some node out of the many gathered so far.
  • Or read [[Index]], inlined below; it is the community-maintained index of this Agora, which is richer and more diverse than this one.
• A User is anyone who has contributed resources to the Commons, either as part of a repository or individually through social media.
  • You can see the list of all [[Users]] and the nodes they’ve contributed to.

Joining§

The Agora is a bit different from most other sites around the internet in that joining is a two step process that begins elsewhere:

• First you take notes/write/make posts in the editor(s) or platform(s) of your choice.
• Then you tell an Agora that you’d like to contribute these resources to the Commons.

Contributing your personal notes and other writing§

• You can contribute to this Agora by taking notes using a personal knowledge management system (like [[Obsidian]], [[Logseq]], [[SilverBullet]] or [[Bull]]); storing your notes in a [[Git]] repository (self hosted or with the help of a forge like [[Github]], [[Gitlab]] or [[Codeberg]]); and sending an email to signup@anagora.org with the location of your repository and your desired username. Please also review the code of conduct in node [[CONTRACT]], which you are expected to follow.
• Notes can be [[Markdown]], [[Mycomarkup]] or [[Org mode]]. After integration, your notes will be available at the Agora locations matching their filenames as per the node convention described above. This means that if user A links to [[foo]] in a note and user B contributes foo.md, following the link in A’s writing will surface also user B’s resource.

Posting from social media§

You can also contribute to this Agora straight from social media! To do so, you need to follow an [[Agora Bot]] in a supported platform and then post following a convention.

• If you are in Mastodon/the Fediverse, you can follow https://social.agor.ai/@agora.
• If you are in [[Bluesky]], you can follow anagora.bsky.social.

Then write posts containing at least one [[wikilink]]; they will be linked in the mentioned nodes. You can additionally opt into storing copies of your messages and #hashtag handling by going through the [[opt in]] process once.

For more…§

• If you don’t use any of the above systems but would still like to contribute your writing or other media, please [[reach out]] and we’ll try to accommodate your preferred formats and sources!
• See [[Agora chapter]] (2023) for a book chapter on the vision behind the Agora project and what we have accomplished so far.
• Please reach out to [[@flancian]] or any of the other [[Stewards of the Agora]] if you need anything, enjoy the Agora, and have a great day! 🍮

Gemini’s Drafts§

• [[pull]] [[gemini]]
• [[push]] [[flancian]]

This directory contains draft nodes generated by Gemini on 2025-12-14 at the request of [[flancian]].

These drafts are based on the architectural suggestions provided in [[GEMINI]] (specifically the "Architectural Suggestions" section). They are intended to serve as seeds for future thoughts or as structural prototypes for expanding the [[Agora]]‘s conceptual graph.

The Drafts§

Core Architectural Suggestions§

1. [[SRE for Society]] (mapping systems engineering to social dynamics)
2. [[The Shadow of the Agora]] (exploring failure modes)
3. [[A Walk in the Garden]] (a narrative entry point)

The "Agonism" Cluster (Conflict & Friction)§

4. [[Agonism]] (political conflict as positive)
5. [[Forking Truth]] (handling epistemological divergence)
6. [[The Right to Exit]] (freedom of movement as governance)
7. [[Algorithmic Pluralism]] (resisting the single feed)
8. [[Social Friction]] (inefficiency as a feature)

The Loom & Stewardship (2026)§

9. LOOM.md (active stewardship clusters and task roadmap)
10. garden_review_master_synthesis.md (deep-scan master synthesis of 7,794 files)

Welcome to Flancian’s digital garden!§

• This is my [[digital garden]] or [[personal knowledge graph]].
  • If you’re viewing this as a [[git]] repository host, you will likely have a suboptimal experience; in particular, [[wikilinks]] may not work. Whenever you read something in [[double square brackets]], just know that you can resolve that link by visiting https://anagora.org/double+square+brackets pull or similar.
  • If you’d like help setting up a [[digital garden]] like this one for yourself, please reach out to me in any way you find convenient: [[flancian]].
  • For more information about some of my other projects, please refer to https://flancia.org pull
  • This garden is part of the Agora of Flancia, an experimental social knowledge graph, and can be found rendered with others in https://anagora.org/ pull

Navigating this garden§

• Please use the search function in the [[Agora of Flancia]] as linked or embedded above, or begin by browsing one of the following starting points which tend to be interestingly connected :)
  • [[person]]
  • [[thing]]
  • [[idea]]
  • [[do]]
  • [[contract]]
  • [[flancia]]
    • [[manifesto]]
    • [[twitter]]
    • [[mastodon]]
    • [[matrix]]
    • [[agora]]
      • [[agora project]]
        • [[agora server]]
        • [[agora bridge]]
        • [[agora plan]]
        • [[agora discuss]]
      • [[agora protocol]]
      • [[agora rfcs]]
      • [[wikilinks everywhere]]

License§

[[Flancia]] is [[Creative Commons]] and the [[Agora of Flancia]] is [[Free Software]].

Branch Renaming Notice (Completed 2025-12-14)§

This repository has migrated its default branch from master to main.

If you have a local clone of this repository, please update it by running:

git checkout master
git branch -m master main
git fetch
git branch -u origin/main main
git remote prune origin

Thank you for keeping the Agora aligned with modern standards!

Vera’s home on the web§

You made it to my secret lair, congratulations! 🎉

• Social links§

  mastodon: v@federate.social
• ssb: @UK4I9qaWYtSkBATEBnFxtvbnLadFWVrM9HFNc7XIGw4=.ed25519

Virtual places I frequent§

• Gather
• [[matrix]] vera@fairydust.space
• · GitHub](https://github.com/codegod100)

Go links§

• [[go]]
  • [[books]] https://vera.files.fission.name/p/books

Tags§

• #Developer
• #Protopian
• #Anarchist

Experimental features§

[[agora pull]] [[vera]]

Wow it took this long to make a readme

QuickJS§

QuickJS is a small and embeddable JavaScript engine. It supports the ES2019 specification including modules, asynchronous generators and proxies.

It optionally supports mathematical extensions such as big integers (BigInt), big floating point numbers (BigFloat) and operator overloading.

Original Source: https://bellard.org/quickjs/quickjs-2019-09-18.tar.xz

Modifications: We made some changes to adapt the codebase to the WASI interface.

Running§

With wasmer§

Install it with:

wapm install -g quickjs

Without any arguments a simple REPL will be launched.

# Run a file
qjs --dir=. examples/hello_module.js

# Run the REPL
qjs

With wasmtime§

First build it by following the instructions in "Building".

# Run a file
wasmtime --dir examples/ build/qjs.wasm -- examples/hello_module.js

# Run the REPL
wasmtime --dir . build/qjs.wasm

Building§

The following script will download the WASI SDK and build the Wasm binary.

./build.sh

README§

See [[Neil’s Digital Garden]].

My [[nowtions]].

• https://doubleloop.net
• https://commonplace.doubleloop.net
• https://anagora.org/@neil pull
• https://social.coop/@neil

I am Maya of maya.land, where more biographical details can be found. I am an extensive [[tiddlywikiist]] privately, but I like the idea of contributing to the wonderful coop vibe goin’ on here, so I’m hoping to figure out a subset that’s useful to share.

• A [[digital garden]] in [[an agora]]
  • [[j0lms]]

These will tend to be code that runs on a per-node basis in one of two ways:

1. Actions can have a "default handler" that renders a subnode in nodes matching their name. For example, dice.py is expected to render a subnode in anagora.org/dice. The node builder in agora.py will call out to it if it exists. This helps serving node-specific interface elements, like a dice throw UI, ranked high within other subnodes in the same node — that is, without obscuring the node content.
2. Actions can also have "composite handlers" — there are Flask routes that will execute an action with a node or query string as a parameter. /dice/6, for example, can be expected to output a number 1..6 (as plain text or html?), the result of throwing a six-sided die. This can be called by client code outside of the main (server-side) rendering code.

To use§

This Agora Server is meant to be used in conjunction with an Agora. An Agora is a collection of digital gardens and other information sources that are assembled into a distributed knowledge graph.

For an example Agora, and for more information on the Agora design, please refer to https://flancia.org/go/agora https://anagora.org Philosophy of AI Applications.

The Agora Protocol§

The Agora Protocol is not a formal network protocol, but rather a set of core principles that guide the project’s design:

"Turn every dead end into a doorway."

• Decentralization: The filesystem is the ultimate source of truth. The server is a lens, not a silo.
• Nodes are Concepts, Subnodes are Utterances: A key distinction where abstract topics ([[Calculus]]) are composed of concrete contributions (@flancian/calculus.md).
• Composition over Centralization: Nodes are built by pulling and combining content from other, more specialized nodes.
• Everything Has a Place (No 404s): Every possible query resolves to a node, turning dead ends into invitations to contribute. Whether it’s a broken link, an empty node, or an unwritten thought—every absence of information is an invitation to create.

To develop§

Install OS dependencies:

$ apt-get install python3 python3-pip

Install npm. Then install JavaScript dependencies:

npm install

Install uv (as per https://github.com/astral-sh/uv):

curl -LsSf https://astral.sh/uv/install.sh | sh

Install Python dependencies:

uv sync

If you get a virtualenv-related error above, try removing virtualenv if you had installed it separately: pip3 uninstall virtualenv.

Then run the development server:

./run-dev.sh

Please see CONTRIBUTING for instructions on how to contribute; it may require a one-time signing of a Google CLA. See also CONTRIBUTORS for the full list of people who have helped build the Agora.

Note this project is not an official Google project, and will not be supported by Google. It was simply initiated by flancian@ while employed at Google, and thus copyright belongs to Google as indicated in LICENSE and in various license headers. This should be of essentially no effect to you or its users (beyond the required signing of the CLA if you contribute), as it is released under an open license; please reach out to flancian@ or some other maintainer if this concerns you.

If you have missing icons§

The Agora Server makes ample use of unicode emojis for illustrating concepts and aiding navigation. If you are on GNU/Linux and see partial rendering (i.e. empty squares instead of icons), you probably need to install additional font packages. On Debian/Ubuntu:

sudo apt install fonts-noto-color-emoji fonts-symbola

About the project§

As you might have inferred from the above, this project is based on Flask. /app hosts the Flask app. In it:

• app/__init__.py has the high level Flask setup.
• app/agora.py does rendering (url maps, views).
• app/db.py has logic to read/process notes. The db is actually the filesystem :)
• app/js-src has Javascript and Typescript sources.
• app/templates are Jinja2 templates.

Production Deployment§

The Agora is designed to be run as a systemd service using uWSGI for performance and reliability. The provided agora-server.service and prod.ini files are configured to support true zero-downtime deployments with a robust cache warming strategy.

Zero-Downtime Deploys with Graceful Rolling Restarts§

To update a running Agora without interrupting user traffic, you should use the reload command, not restart.

Correct Workflow for Production Updates:

# 1. Fetch the latest code
git pull

# 2. Update dependencies if needed
uv sync

# 3. Rebuild frontend assets if needed
npm run build

# 4. Trigger a zero-downtime reload
systemctl --user reload agora-server

How it Works§

This process is designed to be robust and prevent performance degradation during a deploy.

1. systemctl reload: This command runs the ExecReload directive from the .service file, which simply touches the file specified in touch-chain-reload in prod.ini.

2. chain-reload = true: This uWSGI directive tells the master process not to restart all workers at once. Instead, it will reload them one by one.

3. lazy-apps = true: This directive is critical. It tells each new worker to load the application code from scratch. This ensures the new worker picks up the updated code from the git pull.

4. Blocking Cache Warming: The application’s create_app() function contains logic that runs only within a uWSGI worker (if uwsgi.worker_id() > 0:). This logic performs the expensive cache warming (loading the entire graph into memory), which can take several seconds. Because this is a blocking part of the application’s startup, uWSGI’s master process will wait for the warmup to complete before it considers the new worker "ready".

5. The Rolling Restart: The master process kills an old worker, spawns a new one, waits for it to finish its multi-second cache warmup, and only then does it proceed to kill the next old worker. This ensures that the Agora’s full serving capacity is maintained throughout the reload process and that no user is ever served a slow response from a "cold" worker.

API & Core Routes§

The Agora Server provides a variety of endpoints for navigating the graph, extracting data, and reading content. Here is a TL;DR of the most important routes handled by app/agora.py.

Core Navigation§

• GET /: The Agora homepage.
• GET /<node>: The primary view. Renders the composite HTML view for a given topic, combining all user contributions (subnodes) and contextual panels (Stoas, Wikipedia, etc.).
• GET /@<user>: The user profile view. Renders all nodes contributed to by a specific user.
• GET /random: Safely redirects to a random node in the Agora.
• GET /latest: A feed of the most recently modified contributions across all users.
• GET /go/<node>: The "Go-Link" resolver. Parses the node for [[go]] links and automatically redirects the user (e.g., /go/music).

Getting the Full Graph§

The canonical way to get a full definition of the knowledge graph is through the /graph/json/all endpoint. This endpoint returns a single JSON object containing two keys:

• "nodes": A list of all nodes in the Agora.
• "links": A list of all edges, defining the connections between those nodes.

While the filesystem is the ultimate source of truth (the graph is built by parsing all subnode files in the garden/ directory), this API endpoint is the recommended method for retrieving that truth in a clean, usable format.

Note: You can also get the localized graph neighborhood for a single concept via GET /graph/json/<node>.

Extracting Raw Content§

If you need to extract the combined plain-text content of a specific location without any HTML formatting or JavaScript:

• GET /raw/node/<node>: Returns a concatenated Markdown document containing the text of all subnodes and pushed context for the specified node. It handles binary content gracefully by substituting placeholders. This is the recommended endpoint for feeding Agora data to LLMs or CLI tools.
• GET /raw/<path:subnode>: Returns the exact raw file content (Markdown, Org-mode, Image) for a specific user’s contribution (e.g., /raw/garden/flancian/readme.md).

Feeds§

• GET /feed/<node>: Returns an RSS feed of changes to a specific node.
• GET /feed/@<user>: Returns an RSS feed of all changes made by a specific user.

---

Branch Renaming Notice (2025-09-15)

Agora projects migrated their default branch from master to main in September 2025 to align with modern Git standards. Agora Server was migrated earlier.

If your local clone still points to master, run:

git checkout master
git branch -m master main
git fetch
git branch -u origin/main main
git remote prune origin

~ajhalili2006’s digital garden in Obsidian§

Welcome to my [[digital garden]], which is part of the Agora and can be found rendered in https://anagora.org/ pull.

You can also view this in [[Obsidian]] or [[Foam]] by cloning the repo and opening it as a vault. (Viewing this in GitLab and other git mirrors I (and maybe other people) maintain might cause you [[backend pain]] due to wikilinks may not work, among other Obsidian-specific Markdown formatting.)

How to navigate§

• The most obvious way to navigate around here is using Agora’s search feature.
• You can also find your way via tags:
  • [[daily notes]] - sometimes an daily diary, often my log of what I have done in the day
  • [[Gildedguy Stories]] - my starter pack for the Gildedguy Stories series by [[mikedmoy]]
  • [[ajhalili2006]] - mini personal README about me and the context behind the username

Other notepads§

• [[Kooky Insane Stuff]]

Contribute§

Most of my notes here in this digital garden are licensed liberally under [[CC-BY-SA-4.0]] (see [[LICENSE]] or this via GitLab)

Garden API§

An mini API for the garden website, using Denoflare

Development§

Install Deno

~ajhalili2006’s personal wiki and digital garden§

Home of my digital garden (and more) in one monorepo, powered by Obsidian + Foam for VS Code and Material for Mkdocs for the website (hosted on Cloudflare Pages).

Directory Map§

. You are here!
├── .devcontainer - Devcontainer files for GitHub Codespaces and Remote Dev Containers
├── .foam
│   └── templates - Foam templates, including daily notes
├── api - Experimential API to compliment with the wiki, currently prototyping in local devenv.
│   └── lib
├── overrides - theme overrides
│   ├── assets
│   └── hooks
└── src - Source Markdown and other files
    ├── garden - Digital garden
    │   └── daily-notes
    │       └── posts (default directory for blog posts, see docs)
    └── multiverse

Contributing§

I’ll be open this up for community contributions once I ironed up the needed infrastructure on it soon.

License§

MPL-2.0 for the source code, CC-BY-SA-4.0 for the wiki content + original media, unless otherwise specified.

My Garden setup§

Sensitive information is stored in a "walled garden", an encrypted keybase git-submodule. But couldn’t combine existing repo with it, due to GitHub’s jekyll complains, as explained in [[foam]]. So it has to happen in 2 steps: clone and attach submodule locally only.

Walled Garden§

Command to attach my walled Garden:

git submodule add -f keybase://private/ankostis/GardenWall Walls

The -f is needed because .gitmodules is in .gitignore, for it must not be pushed to GitHub repo.

agora§

DZG§

My name is Nicolás and you can reach me at @blindpill on Twitter

Boris Mann’s Digital Garden§

Live at https://bmannconsulting.com. Read the Colophon for details.

Running Jekyll, backlinks and second brain / digital garden features provided by Simply Jekyll theme.

Social and slightly more frequent posts are at https://blog.bmannconsulting.com.

Spacious nexus§

This is a “space.”. It’s what [[SilverBullet]] calls them. Likewise, Obsidian calls them “vaults.”. In other words, this is a repository of markdown files. I’ll call this the [[spacious nexus]]. These personal knowledge graphs are often referred to as “[[digital gardens]]” or “second brains.”.

See [[CONTRIBUTING]].

Frontmatter meaning§

• draft: boolean? - If the document shouldn’t be shown on the explorer in the spacious nexus website.
  This document itself is considered a draft, not because it is a draft. But rather its usefulness on the spacious nexus isn’t useful for most of the general public. It is intended to be displayed on the git repository.
• title: string? - The title of the document. If omitted, the file name of the document is used.
• publish: boolean? - Only used for explicit unpublishing. If false, prevents the page from being generated by [[Quartz]]. All pages are published by default.
• warning: string? - Used for content warnings on pages. Read the [[general disclaimer]] for what this entails.

Structure of this space§

• /Media - Images and videos.
• /Cards - Open Graph images. Files are named after the page they are for.
• /Libraries - Libraries used by SilverBullet. Likely excluded from Git. See .gitignore for libraries used by the space.
• /Discord - Curated Discord messages sent in a semi-private server.

As this space is to be ingested from various Git-based consumers, it’s generally advised keeping attachments small. For images, use lossy webp. The space can contain raw project files (i.e.: .pdn), but these aren’t to be versioned on Git.

Las Variaciones Burup (The Burup Variations)§

«Bella, mi Lady Burup / True Burup / Sea!» Archivo y repertorio pianístico dedicado a Lady Burup (Ocell).
Grabaciones MIDI directas desde el piano Kawai CN35.

1. Variaciones Principales (Master Takes - Volumen 1)§

2. Las Tomas Recobradas (The Rediscovered Master Variations - Volumen 2)§

3. Tomas Alternativas, Trims y Partes§

4. Análisis Musical y Arqueología Algorítmica (320+ Variaciones)§

Para un análisis formal de la huella interválica de Lady Burup (Burup Fingerprint), la topología distribuida entre paramita (nodo de producción) y tara (nodo web/archivo), y el catálogo de las más de 320 variaciones descubiertas en el archivo ~/mid/, consulta:

👉 BURUP_VARIATIONS_ANALYSIS.md

Para buscar y reproducir dinámicamente variaciones desde la terminal:

# Ver las mejores variaciones ordenadas por Burup Score:
findburup --top 25

# Reproducir las 30 mejores en modo aleatorio:
randomidi $(findburup -q --top 30)

5. Síntesis y Renderizado de Audio§

Para sintetizar todas las pistas MIDI a audio de alta fidelidad con SoundFont FluidR3:

uv run scripts/sync_burup_midis.py --render

Los archivos .mp3 generados están excluidos de Git por ser binarios de audio, pero se pueden reproducir localmente o servir en el Ágora.

Preservado con amor en el Ágora de Flancia.

garden§

My Digital Garden in the Agora

garden§

My Digital Garden in the Agora

Bienvenue !§

Communecter.org est une boîte à outils citoyenne collaborative, ouverte à tous, un réseau sociétal innovant, open source et libre, de développement de territoire avec une approche locale (quartier, arrondissement, commune, ville, …). La plateforme offre des outils adaptés aux échanges, aux rencontres, aux débats, au montage de projets , à l’expression des besoins des uns et aux services offerts par les autres.

⥅ [[/Images/communecter-title.png]]

Quelle plateforme souhaitez vous ?§

Nous vous proposons de créer votre propre plateforme personnalisée (appelée COstum). Grâce à notre ingénieux système vous bénéficierez des informations présentes dans communecter.org, et ce qui sera publié sur votre plateforme sera également visible sur communecter.org.

• Holoptisme et stigmergie de votre Organisation, Projet, Evenenement Système d’appel à projets
• Observatoire de secteur
• Plateforme d’action citoyenne
• Gestion de communauté et valorisation de ressources
• Réseau social
• Récolte de connaissances
• Gestion du temps bénévole & banque du temps

Vous êtes une organisation ?§

Communecter répond au besoin de différent contexte et s’adapte à vos objectifs, si vous connaissez les objectifs que vous aimeriez atteindre , nous vous aiderons à les atteindre, et si nécessaire nous pouvons créer des outils sur mesure et mutualiser .

• un group de citoyens ou une Association
• une Coopérative ou une Fédération
• Entreprise
• un secteur ou une Filière de société
• un Territoire : Un région, un département, une agglomération, une Commune
• Espace Public Numérique
• Média

Faite le vous meme ?§

• Communecter un espace personnalisé
• Créer un costum basé sur des template
• Créer un questionnaire en tout autonomie
• Connectez votre commune basé sur le COstum COcity
• Connectez des secteur et filière locale et déployez un Territoire intelligent : SmarTerritoire
• Envoyez nous votre cahier des rèves

Quelques réalisations§

Toute l’année nous développons des plateformes participatives, libres et locales.

CARNET DE DEV

Roadmap, Ligne de vie du projet§

Où sommes nous et va-t-on ?

• vision 2020

• en cours de développement en ce moment

• Milestone et Réalisation mise en prod

• Projets Réalisés et livrés

Listes des modules et fonctionnalités§

Comprendre, Participation , Implication§

• Comprendre le fonctionnement pour embarqué

• Organigramme : qui fait quoi

• Suivi de projet : Qu’est qu’il y aurait à faire en ce moment

• Comprendre la Gouvernance Ouverte

• J’aimerais participer , mais par où je commences

• d’où on vient

[[TOC]]

Bienvenue !§

Communecter.org est une boîte à outils citoyenne collaborative, ouverte à tous, un réseau sociétal innovant, open source et libre, de développement de territoire avec une approche locale (quartier, arrondissement, commune, ville, …). La plateforme offre des outils adaptés aux échanges, aux rencontres, aux débats, au montage de projets , à l’expression des besoins des uns et aux services offerts par les autres.

⥅ [[/Images/communecter-title.png]]

Quelle plateforme souhaitez vous ?§

Nous vous proposons de créer votre propre plateforme personnalisée (appelée COstum). Grâce à notre ingénieux système vous bénéficierez des informations présentes dans communecter.org, et ce qui sera publié sur votre plateforme sera également visible sur communecter.org.

• Holoptisme et stigmergie de votre Organisation, Projet, Evenenement Système d’appel à projets
• Observatoire de secteur
• Plateforme d’action citoyenne
• Gestion de communauté et valorisation de ressources
• Réseau social
• Récolte de connaissances
• Gestion du temps bénévole & banque du temps

Vous êtes une organisation ?§

Communecter répond au besoin de différent contexte et s’adapte à vos objectifs, si vous connaissez les objectifs que vous aimeriez atteindre , nous vous aiderons à les atteindre, et si nécessaire nous pouvons créer des outils sur mesure et mutualiser .

• un group de citoyens ou une Association
• une Coopérative ou une Fédération
• Entreprise
• un secteur ou une Filière de société
• un Territoire : Un région, un département, une agglomération, une Commune
• Espace Public Numérique
• Média

Faite le vous meme ?§

• Communecter un espace personnalisé
• Créer un costum basé sur des template
• Créer un questionnaire en tout autonomie
• Connectez votre commune basé sur le COstum COcity
• Connectez des secteur et filière locale et déployez un Territoire intelligent : SmarTerritoire
• Envoyez nous votre cahier des rèves

Quelques réalisations§

Toute l’année nous développons des plateformes participatives, libres et locales.

CARNET DE DEV

Roadmap, Ligne de vie du projet§

Où sommes nous et va-t-on ?

• vision 2020

• en cours de développement en ce moment

• Milestone et Réalisation mise en prod

• Projets Réalisés et livrés

Listes des modules et fonctionnalités§

Comprendre, Participation , Implication§

• Comprendre le fonctionnement pour embarqué

• Organigramme : qui fait quoi

• Suivi de projet : Qu’est qu’il y aurait à faire en ce moment

• Comprendre la Gouvernance Ouverte

• J’aimerais participer , mais par où je commences

• d’où on vient

Notes on the synthesis of form, by Christopher Alexander§

• [[202104241514]] summary (WIP)
• [[202105072305]] list of all notes created, without order

What I am§

A difficult thing to define.

Who I am§

My name is Henrique [[Darlim]].

Where I am§

• [[Email]]: henriquedarlim@gmail.com
• [[Twitter]]: https://twitter.com/henriquedarlim
• [[Personal site]]: https://hdarlim.github.io/
• [[Facebook]]: https://www.facebook.com/hdarlim/
• [[Letterboxd]]: https://letterboxd.com/hdarlim/
• [[Goodreads]]: https://www.goodreads.com/user/show/135189568-henrique

Draft [[Astro RFCs]]

As it says on the tin, not is not. This area is not strictly a part of my garden, and does not have wikilinks (or should not, rather. If it does do submit a PR to fix it, but use common sense, in some contexts it does make sense). Rather, this is an area to prepare documents in the public

MOVED§

MOVED TO https://git.sr.ht/~boehs/oasis

• This directory contains generated files. If you edit these, you can expect them to eventually be clobbered.

Flancia§

Repository for the writing and media in https://flancia.org pull.

Flancia by @flancian is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Installation§

This uses [[Nikola]] to generate https://flancia.org pull and [[markdown-pp]] to generate a book with selections from the site.

$ pip install nikola MarkdownPP

Then run [[make]] to make both.

Agora§

In Flancia there is an Agora, and Flancia is in the Agora :)

See https://anagora.org pull, https://anagora.org/flancia pull for more.

A nerdy theme, based on HACK CSS

It has a few different color schemes, you can activate them by setting the HACK_VARIANT variable in GLOBAL_CONTEXT to one of

• dark
• dark-grey
• solarized-dark
• standard

©2017 Roberto Alsina

Nikola theme forked from https://github.com/pagecho/maupassant

Description from the original:

A simple typecho template with great performance on different devices.

Suggested configuration is to add Home to nav links so you see the "tabs" properly:

NAVIGATION_LINKS = {
    DEFAULT_LANG: (
        ("/", "Home"),
        ("/archive.html", "Archive"),
        ("/categories/", "Tags"),
    ),
}

TODO:

• Could add support for fontawesome icons in nav bar like some forks of this theme have.
• Image gallery is somewhat broken

Nikola MDL Mako Template§

This theme is based from Material Design Lite templates. It gets the idea from the blog example. This theme is for Nikola static site generator and used Mako templates. The RSS feed icon is getting from Community Icons

Installation§

To install:

Enter the command line below at the console

$ nikola theme -i mdl

Edit conf.py for setting these values below:

• THEME = "mdl"

Refer to Customizing Your Site for more information. If post_type is used, it accepts a dictionary value, where key is the post meta type and value is the icon name from Google Material Design Icons. There is an example in Customization section.

Style development§

You can skip this section if the theme is going to be used as it is. As the final styles.css is generated and placed in assets/css folder.

The css file is generated using SASS compiler. If you have it installed, you can generate the final styles.css file by calling make as there is a Makefile that contains the generation commands.

If you want to add custom styles in custom.scss or custom.css, set mdl__custom_css to True. Both files are git-ignored.

JavaScript development§

If you want to add custom JavaScript in custom.js, set mdl__custom_js to True. The custom.js file is git-ignored.

Components§

Here are the components that used in this theme

• Buttons (mdl-button) on site buttons
• Cards (mdl-card) on post, story and gallery
• Layout (mdl-layout) on site layout
• Navigation (mdl-navigation) on top and drawer navigations
• Grid (mdl-grid) on site grid
• Footer (mdl-mega-footer or mdl-mini-footer)
• List (mdl-list)
• Menus (mdl-menu) on more button in navigation
• Text Fields (mdl-textfield) not in the theme but you might need it on search box
• Tooltips (mdl-tooltip) not in the theme but you might need it on search box

Customization§

It supports some variables in the config file (conf.py). Below are the default values except post_type, where is {}:

    GLOBAL_CONTEXT = {
        "mdl__version": "1.3.0",
        "mdl__color_scheme": "indigo-pink",
        "mdl__roboto_font": False,
        "mdl__late_load_css": False,
        "mdl__cachebusting": "1",
        "mdl__fixed_header": False,
        "mdl__fixed_drawer": False,
        "mdl__no_drawer_button": False,
        "mdl__no_desktop_drawer_button": False,
        "mdl__multiple_header": False,
        "mdl__header_scroll": False,
        "mdl__header_waterfall": False,
        "mdl__header_waterfall_hide_top": False,
        "mdl__header_transparent": False,
        "mdl__header_seamed": False,
        "mdl__footer": "",
        "mdl__navigation_large_screen_only": False,
        "mdl__drawer_small_screen_only": False,
        "mdl__custom_css": False,
        "mdl__custom_js": False,
        "drawer_title": "",
        "drawer_logo_url": "",
        "drawer_show_title": "",
        "drawer_description": "",
        "drawer_note": "",
        "title_row_middle": False,
        "navigation_row_middle": False,
        "breadcrumb_separator": ">",
        "post_type": {
            "text": "format_align_justify",
        },
        "top_nav_header": False,
        "more_button_header": [
            ("/mobile/", "Mobile Site", "Mobile"),
        ],
        "image_plugin": "colorbox",
    }

• mdl__version is Material Design Lite version number
• mdl__color_scheme is colour scheme from Material Design Lite
• mdl__roboto_font is a flag whether Roboto font is used, refer to styles documentation
• mdl__late_load_css is a flag whether CSS styles are deferred, refer to Optimize CSS Delivery
• mdl__cachebusting is a flag solving the cache problem for CSS and JavaScript files.

Layout§

Additional optional MDL classes for outer div element:

• When mdl__fixed_header is True, class mdl-layout--fixed-header is applied for making the header always visible, even in small screens
• When mdl__fixed_drawer is True, class mdl-layout--fixed-drawer is applied for making the drawer always visible and open in larger screens
• When mdl__no_drawer_button is True, class mdl-layout--no-drawer-button is applied for not displaying a drawer button
• When mdl__no_desktop_drawer_button is True, class mdl-layout--no-desktop-drawer-button is applied for not displaying a drawer button in desktop mode

Header§

• When mdl__multiple_header is True, logo and title will be first line and top navigation will move to second line
• When title_row_middle is True, title row (or first line in multiple header lines) will position in the middle

Additional optional MDL classes for header element:

• When mdl__header_scroll is True, class mdl-layout__header--scroll is applied for making the header scroll with the content and mutually exclusive with mdl__fixed_header
• When mdl__header_waterfall is True, class mdl-layout__header--waterfall is applied for allowing a "waterfall" effect with multiple header lines
• When mdl__header_waterfall_hide_top is True, class mdl-layout__header--waterfall-hide-top is applied for hiding the top rather than the bottom rows on a waterfall header
• When mdl__header_transparent is True, class mdl-layout__header--transparent is applied for making header transparent (draws on top of layout background)
• When mdl__header_seamed is True, class mdl-layout__header--seamed is applied for using a header without a shadow

footer§

• By default, mdl__footer is empty. But it could be also either mdl-mega-footer or mdl-mini-footer or even any custom classes, refer to [footer documentation] (http://www.getmdl.io/components/index.html#layout-section/footer)

Navigation§

• When mdl__navigation_large_screen_only is True, it hides navigation row in multiple header lines on smaller screens
• When navigation_row_middle is True, navigation row (second line) in multiple header lines will position in the middle

Drawer§

• When mdl__drawer_small_screen_only is True, it hides drawer on larger screens
• drawer_title is the title in the drawer and it could be set the same as BLOG_TITLE
• drawer_logo_url is the logo url in the drawer and final output is
• The default of drawer_show_title is False. It hides the drawer title (for example, if drawer logo already contains the text).
• drawer_description is more HTML text between drawer_title and drawer navigation
• drawer_note is more HTML text after drawer navigation

Others§

• When Post Types feature in Nikola is used, post_type can used to style different type of posts.
• When top_nav_header is true, navigation will visible when top header is appeared on wider screen.
• When more_button_header is true, more button at top menu header will visible after search button. It is a tuple list, where ("URL", "title", "menu name") as format.
• String value image_plugin is either empty string, lightbox or colorbox. It it is empty string, no image plugin will be used. If it is colorbox, colorbox script is used to view full images. It is the same image library as Nikola used. If it is lightbox, lightbox script is used to view full images in gallery pages.
• Add meta ‘type’ and ‘hidetitle’ to ‘story’ page.
• Add meta ‘no-card-shadow’ and ‘no-card-media’ to ‘post’ and ‘story’ pages.

Depreciated GLOBAL_CONTEXT§

• mdl_version is replaced with mdl__version
• color_scheme is replaced with mdl__color_scheme
• roboto_font is replaced with mdl__roboto_font
• mega_footer (boolean type) is replaced with mdl__footer (string type)

Depreciated classes§

• theme-blog is replaced with site
• theme-blog__posts is replaced with site-posts
• theme-blog__post is replaced with site-post
• theme-blog__gallery is replaced with site-gallery
• theme-blog__page is replaced with site-page
• theme-blog__listing is replaced with site-listing
• theme-card is replaced with site-card
• theme-nav is replaced with site-navigation
• theme-nav__button is replaced with site-navigation__button
• previous is replaced with site-navigation__previous
• next is replaced with site-navigation__next
• theme-crumbs is replaced with site-breadcrumbs
• searchform is replaced with site-header__search

New classes§

• site-header
• site-header__title-row
• site-header__navigation-row
• site-header__row-middle
• site-header__navigation
• site-header__more-button
• site-title
• site-drawer
• site-drawer__title
• site-drawer__description
• site-drawer__navigation
• site-drawer__note
• metadata
• site-post__author
• site-post__date
• site-post__total-comment
• site-post__tag
• site-post__source-link
• site-post__source-link
• site-page-list
• site-page-list-post
• site-page-story
• site-page-tags
• site-page-tag
• site-footer

Known Issues§

• Not all features of Nikola are tested
• slideshow is not working
• Submenus in navigation links are not supported
• THEME_COLOR is not used regardless the value
• Not meet WCAG 2.0 level AA

Dependencies§

• Material Design Lite
• jQuery
• Colorbox
• Lightbox

License§

Material Design Lite Apache License Version 2.0

Google Material Design Icons - Attribution 4.0 International

RSS Feed Icons - SIL Open Font License 1.1

jQuery - MIT License

Colorbox - MIT License

Lightbox - MIT License

Templates - Apache License Version 2.0

The zen and zen-based themes are very customizable, so to make these themes work, you have to use the sample config file. The theme uses Font Awesome v5 icons.

More info about the zen themes family here.

Enjoy!

Damián

WARNING: The themes use Less for their styles, but you don’t need a Less compiler installed to use it.

garden§

My Digital Garden in the Agora

garden§

My Digital Garden in the Agora

garden§

My Digital Garden in the Agora

garden§

My Digital Garden in the Agora

Nerd Fonts§

This is an archived font from the Nerd Fonts release v3.4.0.

For more information see:

• https://github.com/ryanoasis/nerd-fonts/
• https://github.com/ryanoasis/nerd-fonts/releases/latest/

IBM 3270§

A 3270 font in a modern format.

For more information have a look at the upstream website: https://github.com/rbanffy/3270font

Version: 3.0.1

Which font?§

TL;DR§

• Pick your font family:
  • If you are limited to monospaced fonts (because of your terminal, etc) then pick a font with Nerd Font Mono (or NFM).
  • If you want to have bigger icons (usually around 1.5 normal letters wide) pick a font without Mono i.e. Nerd Font (or NF). Most terminals support this, but ymmv.
  • If you work in a proportional context (GUI elements or edit a presentation etc) pick a font with Nerd Font Propo (or NFP).

Ligatures§

Ligatures are generally preserved in the patched fonts. Nerd Fonts v2.0.0 had no ligatures in the Nerd Font Mono fonts, this has been dropped with v2.1.0. If you have a ligature-aware terminal and don’t want ligatures you can (usually) disable them in the terminal settings.

Explanation§

Once you narrow down your font choice of family (Droid Sans, Inconsolata, etc) and style (bold, italic, etc) you have 2 main choices:

Option 1: Download already patched font§

• For a stable version download a font package from the release page
• Or download the development version from the folders here

Option 2: Patch your own font§

• Patch your own variations with the various options provided by the font patcher (i.e. not include all symbols for smaller font size)

For more information see: The FAQ

ray-dorai.github.io§

garden§

My Digital Garden in the Agora

These are my FOAM notes.

They will have information that I want to be easily retrievable about my development practices.

Useful for others doing the same work or if you’re investigating whether you want to collaborate with me.

The web page for browsing the notes is at: goldfishlaser.github.io/dev-notes/

Gyuri’s Foam powered digital garden§

• Here to explore integration with agora
• edited

👋 Welcome to your new Foam Knowledge Base!

Getting started§

This documentation assumes that you have a GitHub account and have Visual Studio Code installed on your Linux/MacOS/Windows machine.

1. If you haven’t yet, browse over to the main Foam documentation to get an idea of what Foam is and how to use it.

2. Press "Use this template" button at foam-template (that’s this repository!) to fork it to your own GitHub account. If you want to keep your thoughts to yourself, remember to set the repository private.

3. Clone the repository to your local machine and open it in VS Code.

   Open the repository as a folder using the File > Open... menu item.

4. When prompted to install recommended extensions, click Install all (or Show Recommendations if you want to review and install them one by one)

After setting up the repository, head to [[getting-started]] to get familiar with your new knowledge base!

To learn more about how to use Foam, read the Recipes bubbles of the Foam documentation workspace.

And remember that you can always join our Foam community on Discord!

Using Foam§

We’ve created a few Bubbles (markdown documents) to get you started.

• [[inbox]] - a place to write down quick notes to be categorized later
• [[getting-started]] - learn how to use your Foam workspace
• [[todo]] - a place to keep track of things to do

In the docs directory you can find everything you need to learn the basics of Foam.

Submitting Issues§

As you may have noticed, issues are disabled. With the goal to keep the project fairly easy to maintain, please file your issues in the main Foam repository:

https://github.com/foambubble/foam

fabric-service-pages§

Microsoft Fabric Consulting Services - Hexaview Technologies - Microsoft Fabric consulting services help organizations assess, design, and implement Fabric with guidance from experienced Microsoft Fabric Consultants.

Microsoft Fabric Consulting Services§

Transform your enterprise data with expert Microsoft Fabric consulting services. Our Microsoft Fabric consultants help you plan, implement, migrate, optimize, and manage your Fabric environment.

Microsoft Fabric Implementation Services§

From strategy to production, we manage the complete Microsoft Fabric implementation lifecycle, including workspace and capacity setup, OneLake configuration, pipeline development, data migration, and go-live support. We’ve delivered multiple Fabric implementations for US-based teams, helping organizations turn their Fabric roadmap into a reliable, production-ready data environment.

Azure Data Factory & Synapse to Fabric Migration That Doesn’t Break What Already Works§

Azure Synapse and Data Factory got your data platform this far. An Azure Synapse to Fabric migration with Hexaview gets you going further without downtime, data loss, or a rebuild from scratch.

SQL Server to Microsoft Fabric Migration Services: Retire the Maintenance Tax on Your Data Platform§

Rising SQL Server licensing costs, an SSIS pipeline nobody wants to touch, and a BI stack spread across three separate tools are not problems a patch fixes. Hexaview Technologies plans and runs your SQL Server to Microsoft Fabric migration from assessment through cutover, so your team spends less time keeping servers alive and more time building on top of the data.

Alteryx to Microsoft Fabric Migration: Rebuild Less, Validate More§

A workflow estate built over years does not belong in a weekend cutover. Hexaview Technologies plans and runs your Alteryx to Microsoft Fabric migration from workflow inventory through validated go-live, so your analysts keep their logic, your IT team gets a governed platform, and nobody discovers a broken macro three weeks after launch.

• Welcome to my "Digital Garden", inspired by [[Anne-Laure Le Cunff]] and many others. About the [[technology of stian’s notes]].
• I’ll also slowly capture some details about my workflows and hacks here, beginning with
  • [[Retro concept]]
• Some interesting pages (or see all pages)
  • My notes on the absolutely fascinating [[Awakening From the Meaning Crisis]] series
  • [[Fundamentals of Alexander Technique with Michael Ashcroft by James Stuber (Course Builders series)]]
  • [[Mastering the Game of Allyship with Wendell Brit by James Stuber (Course Builders series)]]
  • [[Sapiens📒]] (currently part of a book club project)
  • Idea for a "book club platform" [[Project Fluid]]
  • My book notes on
    • [[Deep Work]]
    • [[The Body Keeps the Score]] (processing)
    • [[Atomic Habits]] (unprocessed)
    • [[Attention Is Cognitive Unison]] (unprocessed)
  • Things I’m thinking about
    • [[Three levels of Note taking]]
    • [[E: Ad hoc book clubs]]
      • [[Concrete Book Club Idea]]
    • [[E: Incremental Brainstorming]]
    • [[A: Chinese]]
    • [[E: Textbook design for learning]]

notes.reganmian.net§

Uses https://github.com/aravindballa/gatsby-theme-andy/

Running the project§

• yarn
• yarn start

This is my personal wiki, served at https://wiki.jacob.chvatal.com Daily thoughts are stored in journals/, while pages/ holds long-term notes.

The wiki's built with a tool I wrote and maintain, wikigen Feel free to check it out and request any features you'd like - especially if you'd like to use the tool yourself!

This website has been inspired by the following:

• Devine Lu Linvega's Blog

• Andy Matuschak's Notes

• Tom Critchlow's Site

• Nikita Voloboev's Gitbook

• Oleg's Notes

• Bruno Henriquez' Knowledge Base

• Jethro's Braindump

and is in a state of continuous improvement.

I often use Logseqto work on these notes, though my primary interface to them is through org-roam

Contributing

If you've found an issue with the wiki or would otherwise like to contribute, feel free to open a pull request!

Jaysen Naidoo’s bliki & public txt instance§

about§

Jaysen Naidoo, a 50 odd year old mostly-male, living in Johannesburg, South Africa. Software developer by trade - currently taking a break from contract work to experiment with a few ideas for public software…

Spend time on and thinking about:

• free-software, free-culture and info-politics;
• new-work and worker owned co-ops;
• social software and public information infrastructure;
• the human project and the political
• armchair science - evolution; life; neuroscience; cosmology; physics; complexity.

See also:

• Online-things
• Projects

Content§

• Wiki - linked wiki pages
• Blog - weblogging
• Notes - nothing yet
• Posts - Toots, tweets, threads, micro-blogs - all can get duplicated here.

More about PublicTxt, and its GitHub repo See also notes on bliki - blog and wiki hybrids contained in public-text repos.

About§

#handbook

´´´ ID: Agora4 Jayu Eleuthéria Creation: 2023-05-19 Last modification: 2023-05-19 ´´´

Welcome to [[my]] digital [[Zettelkasten]], nicknamed [[This Zettelkasten]]. Its main purpose is to assist me with my research objective—[[evaluating and improving psychoanalysis’ scientificity and efficacy]]. Nonetheless, other related and unrelated subjects may also appear here.

An archetypical, analog Zettelkasten (there are other variations with slight or significative differences) is a collection of physical index cards in which one registers some kind of content. These cards usually are linked to each other by some sort of metadata: tags, direct references to other cards, Folgezettel, etc. In a sense, Zettelkästen are some of the many ancestors of [[hypertext]], and have been used since their inception by many different kinds of people, from scientists and philosophers to writers and artists.

In this Zettelkasten, every individual page is a [[card]], with a title and a numerical ID. Cards are connected to each other either through [[wikilinks]] naturally inserted into the card’s body, or through being referenced in a [[Trail]]—a sequence of related cards. [[Tags]] help organizing cards into broader categories and classes, and convey certain info about them (e.g. the #incomplete tag marks a card whose content I intend to develop more in the future).

Cards have classes, indicated by tags. This one is a [[Handbook]]—a card whose content serves to explain how this Zettelkasten works.

LICENSE§

This Zettelkasten by Jayu Eleuthéria is licensed under CC BY-NC-SA 4.0

garden§

My Digital Garden in the Agora

Table of Contents§

• [[How to interact with exobrain?]]
  • [[navigation sidebar]]
  • [[search]]
  • [[via the source code?]]
  • [[content]]
  • [[page structure]]
  • [[what do timestamps/priorities/todo states mean?]]
  • [[longevity]]
• [[FAQ]]
• [[Exobrains/wikis made by other people]]

Exobrain, or "second brain", or "brain dump" is something like public wiki where you can keep your bookmarks, notes, ideas and thoughts.
Other people can search in your exobrain without having to physically interact with you.
The point is not to avoid physical interaction altogether, but to scale collaboration and knowledge exchange with other people.

It also allows for quicker iteration in writing blog posts or developing thoughts – I can just quickly publish it here, share it gradually, and receive immediate feedback.

You can find org-mode sources of the files here, and the code to process and compile it here.

My exobrain contains semi-curated notes, tasks and links.

You can read more about exobrain on on its project page.

How to interact with exobrain?§

Granted, there is lots of stuff here, and it’s unclear what should you start with (if at all?).

navigation sidebar§

It might be useful to explore and overview what’s in my exobrain.
I’m still figuring out a system to distinguish ‘link dump’ pages for more interesting ones.
For now I’m just marking the latter with emojis, like this ⭐.

search§

I imagine search as the primary means of interacting with the exobrain.
The search yields you results as you type, which means incredibly fast feedback.

Note that at the moment it’s still in development.

via the source code?§

You can also clone the org-mode repository and eplore it in emacs directly.

content§

Some pages are quite unprocessed, but hopefully enough to make sense, especially if you are looking for something specific.
Note that not everything is my own text:

some (if not most?) notes are just clippings
Usually the clippings are quoted like this.

, so hopefully it’s easy to tell apart what’s quoted and what are my own thoughts.
If it’s a clipping, doesn’t mean I agree with it, or think the information is true, just means that I found it curious or worthy further research.

page structure§

Usually the content on the top of the page is somewhat curated and has higher information weight.
In the bottom of the page the links I’ve refiled pile up, and it’s a bit more chaotic.
Usually I separate the two with ============================.

For example, see page on python.

what do timestamps/priorities/todo states mean?§

First, if they annoy you, can turn toggle them via the settings in the bottom of the page.

• timestamps usually correspond to the time I created a bookmark/note, it’s useful to assess how relevant is information (e.g. something from 5 years ago is more likely to be irrelevant to me now than something I added yesterday)
• priorities roughly mean how important/valuable I think a piece of information/todo is, for me or other people.
  Some bookmarks don’t have priorities, which usually means I either haven’t processed them yet.
• todo states (TODO/STRT/DONE) usually mean whether I’ve processed a bit of information, or it’s in my queue

longevity§

While I’m generally doing my best to combat link rot, notes may move around, some IDs change, etc.
So if you see a piece of useful information here, make sure to copy its text, not just the heading link.

FAQ§

• do you really think that what you have here is interesting to anyone
  Yes, to some people. It’s also useful to me when I want to share something I’ve already written down with other people.
• isn’t it too much information?
  Yes, I have a certain kind of FOMO. But I think I’m managing it relatively well :)
• are you actually retaining any knowledge?
  Yes, in fact I can’t imagine learning without notetaking.
  I certainly don’t retail all of it (or perhaps even most of it).
  But even knowing where you can find some information in the form you like is a big part of learning process.
• aren’t you making yourself vulnerable by sharing too much unfiltered content?
  I don’t know… maybe? This is kind of inevitable with any form of public online communication.
  I do have beliefs/opinions from several years ago I’m not holding anymore or even cringe at.
  If you think something I have here is problematic etc., please feel free to reach out, and I’ll be happy to discuss, I realy am open for change.

Exobrains/wikis made by other people§

You can also find more links here.

• ‘Everything I know’ wiki by Nikita Voloboev

  If you want to check out one exobrain, start with this. It was my main inspiration and got lots of high quality and curated stuff.

• xxiivv by Devine Lu Linvega

• h0p3’s Wiki

• Braindump by Jethro Kuan

• ‘One Hundred Ideas for Computing’ repository by Sam Squire

• more wiki examples from Nikita Voloboev

KGB_Agora§

Kieran’s Agora is a place of constant learning. While you may draw assumptions from what is being learned here, a friendly, open, and charitable discussion will be given a chance upon disagreement.

Like all Agora, it may change. This is to be celebrated. Knowledge is not static.

Who am I?§

I’m a storyteller and lookout. I’ve been called ‘Paḻaiya kai’, ‘hem-netjer’, ‘arlequin’, and ‘саботажник’ over the years, but the roles I’ve played have served who I am, they’ve not made who I am.

Romanticism aside, I have some form of external certification in the following domains:

Certified§

Continued Learning§

• Writing
• Economics
• Artificial Intelligence
• Programming
• Data analysis
• Sociology
• Astronomy
• Journalism
• First Aid

Experienced but not continued§

• Radio broadcast
• Marketing
• Web development
• Business management
• Fencing (sport)

Uncertified§

Continued Learning§

• Politics
• Mental healh issues (not policy)
• Queer/Polyamorous issues
• Linux systems operation
• Military politics
• Community management
• Voice acting
• Speech writing
• Video editing
• Image editing
• Audio editing

Experienced but not continued§

• Motorsports
• Choral singing
• Catholic history/rites
• Acting

agora§

A contribution to http://anagora.org/ pull

Luciana’s digital garden§

Bienvenides Notas sobre literatura, lingüística, etc.

Quartz v4§

“[One] who works with the door open gets all kinds of interruptions, but [they] also occasionally gets clues as to what the world is and what might be important.” — Richard Hamming

Quartz is a set of tools that helps you publish your digital garden and notes as a website for free. Quartz v4 features a from-the-ground rewrite focusing on end-user extensibility and ease-of-use.

🔗 Read the documentation and get started: https://quartz.jzhao.xyz/

Join the Discord Community

Sponsors§

moaparty.com§

The moaparty.com website. Used for status, updates, and documentation for moa.party, a cross poster for Mastodon, Twitter, and more.

The Index§

This is my Agora node. It exists as of [[2021-01-24]]. Here are some of my projects:

• [[hash-viewer]]
• [[econ-ipsum]]
• [[hash-viewer]]
• [[jekyll-citations]]

If you want to contact me, you can find my information here: [[identity]]

olofl’s digital garden§

Welcome to my [[digital garden]]!

This garden is part of the Agora and can be found rendered in https://anagora.org/ pull. If you’re viewing this on Github, you will have a suboptimal experience (many links will be broken).

Contact me on Twitter.

This is Andreas’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Daniel’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Eduardo’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Ekin’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Fiona’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Ivo’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Jonathan’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Katherine’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Maya’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

This is Natalia’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

Welcome !§

This is a place for all participants of the Christopher Alexander reading group to upload files — whether they be notes, images, reference texts, etc. — for sharing with the group!

How To:

• please only upload files to the folder with your name on it (so we keep track of who shared what)
• everyone can access all folders and files (that’s how we share)
• some file formats will be displayed by the GitHub webpage in a readable form directly: such formats include .txt, .md, .pdf, .jpg, .png, …
• files in the .docx format of Microsoft Word and various other formats cannot be display on this webpage and not everyone might have the software to display such formats on their personal computer, so it is encouraged, whenever possible, to use file formats that are as accessible as possible!
• to upload files, select the "add file" button, then select "upload file" from the drop-down menu. Once the file is uploaded, one needs to scroll down a bit and click the green button labeled with "Commit Changes" for the file to be save to the folder.

Further/other info:

• The word "repository" that is used on the GitHub webpage can be thought of as just meaning "folder" or "place"
• Some documents (such as .txt files and .md files) can be created and/or edited directly in the GitHub webpage (there is a little pencil symbol to enter edit mode). In order to save changes, one needs to scroll down and click the green button labeled with "Commit Changes".

This is Simon’s folder for the "patterning" reading group. A place for any kinds of files - personal notes, images, references, etc.

Plantey’s Digital Garden§

Welcome to my digital garden! Here, I cultivate idea-seeds. For more clarity on this, see Digital Garden

garden§

My Digital Garden in the Agora

garden§

My Digital Garden in the Agora

Rel8 Wiki§

Rel8 is born from two questions:

• Why is it so difficult for us to share our notes?
• Why don’t we know what we know collectively?

At the very personal scale, plenty of individuals are [[perfecting their note-taking]], but usually those notes are just for themselves. The rest of us are often duplicating those efforts and not benefiting from the possibilities of a hive mind.

At the larger organizational scale, plenty of companies and nonprofits have spent decades and millions on Knowledge Management, with little benefit to show for it.

We are now in a new era, one that recognizes that humans are essential to Knowledge Management, that visualization is an essential complement to KM, and that collective intelligence must respect differing points of view.

Rel8 is a shepherding and stewarding project, not a coding project to build yet another platform.

Instead, Rel8 seeks to figure out out what conditions, organizations and dynamics need to exist so we can create a shared memory. This mission requires:

• Convening solution-finding conversations
• Creating prototype code and use cases to illustrate what’s possible and why

[[What Are We Doing Now]]?§

[[Where Is Rel8]]?§

• [[Rel8 Goals]]: S, M, L§

• [[Rel8 Key Questions]]§

• [[Rel8 Projects]]§

[[Get Involved]]§

[[Our Groundrules]]§

Rusp§

Welcome to my Agora

This repository will be used to host the public version of my Roam notes.

Aly’s digital garden§

• [[pull]] [[Aly]].

This garden is part of an experiment on what being part of a shared digital knowledge base entails.

This garden is a part of [[Flancian]]‘s [[Agora]].

garden§

My Digital Garden in the Agora

For an intro to this project, see our start here page. If you are reading on Agora, start here. This is a work in progress networked notebook, but is ready for sharing. Feel free to make pull requests and suggestions, or comment on pages.

Website made using Quartz.Host your second brain and digital garden for free. Huge shoutout to Jacky Zhao for being so helpful getting this site off the ground to fit our needs.

sephagora§

notes sent to an agora

also hosted at seph.news

written in obsidian

garden§

My Digital Garden in the Agora

The source for the SPARQL wiki graph, published here.

garden§

My Digital Garden in the Agora

neuralnomicon§

An org-roam for practical-technical-scientific Stable Diffusion information.
WEB VERSION

WHAT IS THIS?§

A map of everything that has happened AI self-hosting wise.
An organized quick-reference wiki of the papers and the tools.
Git-based, can seen from the browser: WEB VERSION

WHY§

For those who don’t know where to start researching stuff nor the current state. Also to avoid duplication.
I focus only in papers that potentially enhance the condition of the LOCAL ai-user.

HOW§

The structure comes down to: next to a paper you will find others very much related. Organization proposals are welcomed

WHAT ELSE IS THIS§

A social experiment, an org-book(links to a lemmy-fediverse community)

HOW TO USE WITH EMACS?§

FIRST CLONE§

Terminal:

cd ~/org/roam
git clone https://github.com/tekakutli/neuralnomicon

and add this to your roam .gitignore so it doesn’t get mixed-in with yours

roam/neuralnomicon/

THEN INSIDE EMACS§

To create nodes for this directory I have a template.
for your config.el

(setq org-roam-capture-templates
      '(
        ("n" "default" plain
         "%?"
         :if-new (file+head "%<%Y%m%d%H%M%S>-${slug}.org" "#+title: ${title}\n")
         :unnarrowed t)
        ("s" "neuralnomicon" plain
         "%?"
         :if-new (file+head "neuralnomicon/nodes/%<%Y%m%d%H%M%S>-${slug}.org" "#+title: ${title}\n#+filetags: :neuralnomicon:\n")
         :unnarrowed t)
        )
)

OPERATIONAL§

operational wise: https://www.orgroam.com/manual.html
but (M-x org-roam-node-find) and (M-x search-buffer) and clicking-links should suffice

garden§

My Digital Garden in the Agora

garden§

My Digital Garden in the Agora

readme§

see [[me]]

An object is something that can be unambiguously referenced by means of an address.

A simple object is an object containing no parts.

The following are simple objects:

• proof
• name
• interpretation
• blob

Complex objects are objects that consist of parts.

With the exception of the empty context, every complex object contains a context, which is required for assigning value to an interpretation

unrival

v.

1. to undo a state of rivalry
2. to outcompete conclusively
3. to accomplish the above by means of an Unrival object

garden§

My Digital Garden in the Agora

Yolo

Hugo PaperMod | Demo

☄️ Fast | ☁️ Fluent | 🌙 Smooth | 📱 Responsive

Hugo PaperMod is a theme based on hugo-paper. The goal of this project is to add more features and customization to the og theme.

The demo includes a lot of documentation about Installation, Features with a few more stuff. Make sure you visit it, to get an awesome hands-on experience and get to know about the features …

ExampleSite can be found here: exampleSite. Demo is built up with exampleSite as source.

Features/Mods 💥§

• Uses Hugo’s asset generator with pipelining, fingerprinting, bundling and minification by default.
• 3 Modes:
  • Regular Mode.
  • Home-Info Mode.
  • Profile Mode.
• Table of Content Generation (newer implementation).
• Archive of posts.
• Social Icons (home-info and profile-mode)
• Social-Media Share buttons on posts.
• Menu location indicator.
• Multilingual support. (with language selector)
• Taxonomies
• Cover image for each post (with Responsive image support).
• Light/Dark theme (automatic theme switch a/c to browser theme and theme-switch button).
• SEO Friendly.
• Multiple Author support.
• Search Page with Fuse.js
• Other Posts suggestion below a post
• Breadcrumb Navigation
• Code Block Copy buttons
• No webpack, nodejs and other dependencies are required to edit the theme.

Read Wiki For More Details => PaperMod - Features

Install/Update 📥§

Read Wiki For More Details => PaperMod - Installation

Social-Icons/Share-Icons 🖼️§

Read Wiki For More Details => PaperMod-Icons

FAQs / How To’s Guide 🙋§

Read Wiki For More Details => PaperMod-FAQs

Release Changelog§

Release ChangeLog has info about stuff added: Releases

Pagespeed Insights (100% ?)§

Special Thanks 🌟§

• Highlight.js
• Fuse.js
• Feather Icons
• Simple Icons
• All Contributors and Supporters

agora§

doc.anagora.org§

This is meant to be a read only dump of notes hosted in doc.anagora.org (the default [[stoa]] as of the time of writing.)