• a [[chapter]].
  • #push [[agora chapter]]
    • written for [[pkg book]].
    • #go https://docs.google.com/document/d/1DXJRDh9Ss5VCRBi3oirDw9d7yjn3H2hMqfN2ETTyjIc/edit?usp=sharing pull
    • #pull [[agora pkg chapter]] ~ [[agora chapter]] (these might converge, I use them in different contexts)
    • #pull https://docs.google.com/document/d/1DXJRDh9Ss5VCRBi3oirDw9d7yjn3H2hMqfN2ETTyjIc/edit#heading=h.lxyhsegwtr4m pull
    • the above should work, try iframes with [[google docs]]
      • it doesn’t work :( "Google Docs benötigt Zugriff"
        • oh, but you can click on "click here" to get through!
          • only on Firefox
          • it doesn’t work at all on Chrome :(
    • #comment https://docs.google.com/document/d/1DXJRDh9Ss5VCRBi3oirDw9d7yjn3H2hMqfN2ETTyjIc/edit?disco=AAAAhUbCJIQ pull
      • great top level comment by [[ivo]], see push here for summary (G1-G8).

• [[flancian]] https://social.coop/@flancian/108855071126533560 pull
• [[flancian]] https://social.coop/@flancian/108917814565371634 pull
• [[flancian]] https://social.coop/@flancian/108986085962318652 pull

• [[flancian]] https://twitter.com/flancian/status/1560958387243851776 pull
• [[flancian]] https://twitter.com/flancian/status/1564973746015936513 pull
• [[flancian]] https://twitter.com/flancian/status/1569342980338716672 pull

• [[2022-08-14 19:36:34]] [[@flancian:matrix.org]] (link):
  • 2. my default priorities for this month in the Agora are: 2a. to work on [[agora doc]], which now points to the format that I need to deliver [[agora pkg chapter]] on September 1 for [[pkg book]]. 2b. to node [[revolution]], the topic for August Node Club.
• [[2022-08-31 18:02:50]] [[@flancian:matrix.org]] (link):
  • prioritizing [[agora doc]] today as the deadline is tomorrow and tomorrow I also travel to Portugal :)
• [[2022-09-01 14:00:38]] [[@flancian:matrix.org]] (link):
  • From page 18 of [[agora doc]] ^ thank you all!
• [[2022-09-04 22:07:48]] [[@flancian:matrix.org]] (link):
  • Thank you all for reviewing [[agora doc]]! It’s been much informed and improved by the Agora Community.
• [[2022-09-08 15:27:47]] [[@flancian:matrix.org]] (link):
  • will be working on the Agora, focusing on [[agora doc]] in particular, until tomorrow evening
• [[2022-09-08 20:28:18]] [[@flancian:matrix.org]] (link):
  • extended work on [[agora doc]] until EOD tomorrow as agreed with editors to address comments from the community :)
• [[2022-09-29 20:52:52]] [[@flancian:matrix.org]] (link):
  • I’ve gotten back into [[agora development]] after a hiatus because of the day job + writing [[agora doc]]
• [[2022-10-08 19:59:59]] [[@flancian:matrix.org]] (link):
  • edsu: some time ago I believe you asked for a pointer to the text I’ve been working on about the Agora? [[agora doc]] is about it; the actual document can be seen at https://anagora.org/go/agora-doc pull. it’s currently under heavy scrutiny by editors, which will likely make it significantly more readable — regardless of whether it ends up published :)
• [[2022-10-27 13:56:44]] [[@flancian:matrix.org]] (link):
  • my main priority is to rewrite (yes, rewrite pretty much describes it :)) [[agora doc]] before the Sunday deadline.

• [[2022-10-01 20:45:12]] [[@flancian:matrix.org]] (link):
  • or in [[go/agora-doc]]

• [[youronlyone@c.im]] https://c.im/@youronlyone/110128906219705139 pull

• [[rmdes@mstdn.social]] https://mstdn.social/@rmdes/110514528168602804 pull

• a [[document]].
  • …or several :)
    • you find in the [[Agora of Flancia]].
  • #2019 https://docs.google.com/document/d/1hKYrcScFTqggWhtlc-Ot3XQoWQmBFKXF/edit pull
  • #2022 https://docs.google.com/document/d/1MxO0l9wDDWQdrutOVgdS6YO_TK9FH8C9/edit pull
  • #go https://docs.google.com/document/d/1MxO0l9wDDWQdrutOVgdS6YO_TK9FH8C9/edit pull
  • #stoa https://doc.anagora.org/flancia-doc pull

• I have a [[Google Docs]] version of https://flancia.org pull. I thought several times of moving writing there, but I haven’t solved the question of how to ‘sync back’ text to the site, if at all.

• a [[book]], maybe.

Always feel free to fail. Free yourself from suffering if you can and free others: this is the whole of [[Flancia]] as a practice maybe.

But I’m getting ahead of myself; please allow me to introduce myself. I’m a [[Flancian]]. In practice, you can think of this as meaning that I try to be open about my thoughts by default, follow the [[Principle of Charity]] in discussion and attempt to increase overall [[loving-kindness]].

To learn how to communicate with you better I started writing this.

How are you today?

• [[very well]]
• [[well]]
• [[not so well]]

(Some Flancians identify as Buddhists like me, but these labels are optional.)

If you need help, please [[reach out]] at 0@flancia.org.

Next: https://anagora.org/go/flancia-doc pull

• a [[book]], maybe.

Always feel free to fail. Free yourself from suffering if you can and free others: this is the whole of [[Flancia]] as a practice maybe.

But I’m getting ahead of myself; please allow me to introduce myself. I’m a [[Flancian]]. In practice, you can think of this as meaning that I try to be open about my thoughts by default, follow the [[Principle of Charity]] in discussion and attempt to increase overall [[loving-kindness]].

To learn how to communicate with you better I started writing this.

How are you today?

• [[very well]]
• [[well]]
• [[not so well]]

(Some Flancians identify as Buddhists like me, but these labels are optional.)

If you need help, please [[reach out]] at 0@flancia.org.

Next: https://anagora.org/go/flancia-doc pull

• a [[book]], maybe.

Always feel free to fail. Free yourself from suffering if you can and free others: this is the whole of [[Flancia]] as a practice maybe.

But I’m getting ahead of myself; please allow me to introduce myself. I’m a [[Flancian]]. In practice, you can think of this as meaning that I try to be open about my thoughts by default, follow the [[Principle of Charity]] in discussion and attempt to increase overall [[loving-kindness]].

To learn how to communicate with you better I started writing this.

How are you today?

• [[very well]]
• [[well]]
• [[not so well]]

(Some Flancians identify as Buddhists like me, but these labels are optional.)

If you need help, please [[reach out]] at 0@flancia.org.

Next: https://anagora.org/go/flancia-doc pull

• a [[book]], maybe.

Always feel free to fail. Free yourself from suffering if you can and free others: this is the whole of [[Flancia]] as a practice maybe.

But I’m getting ahead of myself; please allow me to introduce myself. I’m a [[Flancian]]. In practice, you can think of this as meaning that I try to be open about my thoughts by default, follow the [[Principle of Charity]] in discussion and attempt to increase overall [[loving-kindness]].

To learn how to communicate with you better I started writing this.

How are you today?

• [[very well]]
• [[well]]
• [[not so well]]

(Some Flancians identify as Buddhists like me, but these labels are optional.)

If you need help, please [[reach out]] at 0@flancia.org.

Next: https://anagora.org/go/flancia-doc pull

Automatically push git repo

• a [[thing]].
  • #pull [[google docs]]
  • I love docs, but unfortunately you can’t embed them using [[iframes]] as of [[2022-08]] :(
  • figure out how to easily import one in the Agora?

• [[flancian]] https://social.coop/@flancian/108425134406449471 pull

• [[flancian]] https://twitter.com/flancian/status/1533442728368939008 pull

• an [[editor]]
  • [[concurrent]]
    • like [[etherpad]] for [[markdown]]
  • [[go]] https://hedgedoc.org pull
  • [[example]] https://demo.hedgedoc.org/p5-fOIzSS26BbR5AAN7XDw?both pull
• a [[stoa]]
  • https://docs.hedgedoc.org/setup/manual-setup/ pull
  • defaults to using UUIDs as urls for docs, but allowFreeURL replicates [[etherpad]] behaviour (entering a non-existent doc URL creates a doc with that alias)
    • https://docs.hedgedoc.org/configuration/#users-and-privileges pull
  • had to yarn add babel-runtime separately to make an error go away while installing
  • now embedded as the default stoa in anagora.org.
  • [[nginx]] https://docs.hedgedoc.org/guides/reverse-proxy/#nginx pull

Here is an example configuration for Nginx.

map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
}
server {
        server_name hedgedoc.example.com;

        location / {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
        }

        location /socket.io/ {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
        }

    listen [::]:443 ssl http2;
    listen 443 ssl http2;
    ssl_certificate fullchain.pem;
    ssl_certificate_key privkey.pem;
    include options-ssl-nginx.conf;
    ssl_dhparam ssl-dhparams.pem;
}

• Here is an example configuration for Nginx.

Backlinks§

• • [[hedgedoc]]

• • [[hedgedoc]]

Backlinks last generated 2022-01-28 07:55:20

• Here is an example configuration for Nginx.

Here is an example configuration for Nginx.

map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
}
server {
        server_name hedgedoc.example.com;

        location / {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
        }

        location /socket.io/ {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
        }

    listen [::]:443 ssl http2;
    listen 443 ssl http2;
    ssl_certificate fullchain.pem;
    ssl_certificate_key privkey.pem;
    include options-ssl-nginx.conf;
    ssl_dhparam ssl-dhparams.pem;
}

Here is an example configuration for Nginx.

map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
}
server {
        server_name hedgedoc.example.com;

        location / {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
        }

        location /socket.io/ {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
        }

    listen [::]:443 ssl http2;
    listen 443 ssl http2;
    ssl_certificate fullchain.pem;
    ssl_certificate_key privkey.pem;
    include options-ssl-nginx.conf;
    ssl_dhparam ssl-dhparams.pem;
}

Here is an example configuration for Nginx.

map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
}
server {
        server_name hedgedoc.example.com;

        location / {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
        }

        location /socket.io/ {
                proxy_pass http://127.0.0.1:3000;
                proxy_set_header Host $host; 
                proxy_set_header X-Real-IP $remote_addr; 
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
        }

    listen [::]:443 ssl http2;
    listen 443 ssl http2;
    ssl_certificate fullchain.pem;
    ssl_certificate_key privkey.pem;
    include options-ssl-nginx.conf;
    ssl_dhparam ssl-dhparams.pem;
}

• [[flancian]] https://social.coop/@flancian/107446102378527179 pull
• [[flancian]] https://social.coop/@flancian/107446462858160893 pull
• [[flancian]] https://social.coop/@flancian/108102784626286844 pull
• [[flancian@social.coop]] https://social.coop/@flancian/111568741250365015 pull

• [[smallcircles@social.coop]] https://social.coop/@smallcircles/109777930327614829 pull

• [[flancian]] https://twitter.com/flancian/status/1470785067333136384 pull
• [[flancian]] https://twitter.com/flancian/status/1470807439264161795 pull

• [[2023-07-28 01:52:48]] [[@flancian:matrix.org]] (link):
  • w.r.t. to wysiwyg editing, I don’t know of a great option currently. [[hedgedoc]] is pretty good and what we run as a default stoa in anagora.org; that install just syncs to the agora every 30s with a cronjob which dumps documents to markdown on disk.

• Una [[escritora]].
  • De [[Argentina]].

• #go https://docs.google.com/document/d/1i0vkN5x7fQFEZGowCygdrtNPbv59uwHO5rjx1iBn-Y8/edit# pull
  • [[lowry]]

• #go https://docs.new pull

Original CTZN design document§

Technical architecture

Data mesh§

CTZN requires a "data mesh" to provide globally-accessible databases. It currently uses the Hypercore Protocol but other data networks such as IPFS could satisfy this requirement. The Hyperbee Key-Value Database is the most frequently-used structure at present.

The mesh uses public-key cryptography to address databases. The pubkeys represent agency in the mesh, much like server origins represent agency in the Web.

All users have first-class identities in the mesh because any device can generate pubkeys and their databases — not just publicly-reachable servers.

The mesh is extremely cache-friendly. All information is signed and can be redistributed trustlessly by peers. This ensures the network can scale while maintaining agency; users sign their data, retain key ownership, and then sync the dataset to caching peers which can handle heavier traffic.

The mesh uses "pull-based" transmission. Software identifies which databases to sync and then will watch the databases for updates to their records. As a result, aggregated indexes act as the basis of communication.

To give a trivial example, 3 user databases which post shortform blogs could be aggregated into a "feed database" which represents their 3-person community’s posts; the 3 users would reference the feed db to see their community activity. The production of shared indexes therefore determines participation in a shared space.

Identity and re-homing§

All databases possess a public-key ID and may optionally declare a DNS-based ID. DNS-IDs take the form of "username@domain" and can be resolved by contacting the server at "domain."

All records are identified by public-key URLs. This means that links are not changed by DNS-ID changes.

Databases can "rehome" (change their DNS-ID) by declaring a new ID in their dataset and updating the server records which map the DNS-ID to their database. Pubkey-rotation is solved by a similar process; a new database (and new pubkey) are minted and the DNS-ID records are mapped to the new database. The new database declares itself as a "resumption" of the old database, thereby maintaining old records at their previous URLs while producing new records under the new pubkey URL.

Rehoming is easily detected by followers of a database and can be validated by ensuring the database and DNS records agree. Once they are found to agree, followers can update their local records to the new identifiers.

Data schemas§

CTZN relies on machine-readable database schemas which are addressed by URLs. These schemas are automatically enforced by the software in order to maintain compatibility across the network.

Within Hyperbees, the schema URLs act as the identifiers for datasets. Therefore a given user’s comment (id=1) might be addressed by the following pseudo-code:

userDb.getTable('ctzn.network/comment').get(1)

Which maps to the following hyper-url:

hyper://1234..af/ctzn.network/comment/1

Schemas can be seen as major determinants of applications; support of a specific schema determines the nature of an application. The strict schema model ensures clarity in the dataset while also providing extensibility by creating new schemas with new URLs.

Applications model§

Applications interact with the data-mesh to provide new UIs and new PXs.

CTZN’s use of the data mesh means that access to the network can be provided by Web, desktop, or mobile applications. The only requirement is that the application can access the data mesh (Hypercore Protocol).

Database signing keys may be held by user devices or by "hosting servers." Since servers can be accessed remotely via the Web, they provide a convenient solution to key-hosting. The user can migrate to a new key-host by using the key-rotation process.

CTZN uses JSON-RPC over WebSockets for RPC.

Whenever possible, applications are encouraged to access datasets using Hypercore rather than via RPC requests to other nodes. This ensures the network will take advantage of the scaling properties of the Hypercore Protocol. An exception to this rule is the API for write-access, which is required when the user’s keys are held in a hosting server.

Core schema

CTZN’s core schema is still under development but will include table-definitions and flows for:

• User accounts
• Social following
• Short-form posts and comments
• Content voting
• Notifications
• Community aggregation

Political architecture

Our goal is to establish trust in authority when it must be given. Our tools for gaining that trust is distributed & contingent authority ("Authority model") and constrained powers of authority ("Constitutional networks").

Authority model§

CTZN’s authority model has two primitives:

1. DNS ownership - provides the ability to map domains and DNS-IDs to pubkeys.
2. Pubkey ownership - provides the ability to modify a given database.

These primitives are used to create PX spaces. Consider the following example:

Element

Impact

example.com maps to the example database’s pubkey

Establishes the example.com community’s database.

example declares the usage of ctzn.network schemas

Establishes the example.com community’s core application.

example declares 3 user records — alice@example.com, bob@example.com, and carla@example.com — and their database pubkeys.

Establishes the example.com community’s membership.

alice, bob, and carla databases declare profile and post records.

Establishes the content of the example.com network.

example database declares a secondary index of the latest posts.

Establishes the timeline of the example.com community activity.

We can infer a few things from this example:

• There is a hierarchy of identity, from DNS -> server database -> user databases
• User databases maintain their own profile/post records and can be accessed independently of the example.com community.
• The example.com database maintains community information only, including secondary indexes which represent a current "view" of the activity.
• As records are linked by their pubkey-URL, there is no hard binding to the example server.

Because of this separation of authority, the members of example.com maintain the freedom to migrate their content away from the example community without any disruption to the network. This migration would be similar to "forking" a codebase — the content would remain but the community authority would be modified.

This interplay between community authority and individual authority is a repeatable PX pattern. By maintaining individual rights to migrate away from a community, the community maintainers’ authority is contingent on the members’ satisfaction with their leadership.

Constitutional networks§

A future goal for the Hypercore Protocol is a toolset for "smart contracts" - code which has externally-auditable execution. Once CTZN’s data-mesh supports smart contracts, it will integrate the contracts in the PX patterns to create community "constitutions."

Using constitutions, communities can define a strict ruleset by which community-members can exercise authority. These constitutions will establish rules for:

• Identity registries
• Content and user moderation
• Discovery and content-ranking

And so on.

Smart-contract constitutions create both transparency and constraints. Moderators will not be able to modify the community datasets without following the contract rules, and every action will be placed in an auditable log.

Constitutions will provide members of large-scale communities an assurance over how their community will be governed. Rather than trusting the moderators to follow a declared process, the community can legislate the constitution to establish how moderators will govern.

• [[flancian]] https://twitter.com/flancian/status/1425864809204027401 pull
• [[flancian]] https://twitter.com/flancian/status/1532111136212013056 pull

• [[2022-03-07 09:15:44]] [[@flancian:matrix.org]] (link):
  • it seems I’m using [[orgpython]] to render these nodes, or so I wrote at some point. I may just try piping org through [[pandoc]] instead and see what happens

• [[flancian]] https://social.coop/@flancian/108438253529627602 pull
• [[mmlvx@mastodon.world]] https://mastodon.world/@mmlvx/109711596746267437 pull

• [[flancian]] https://twitter.com/flancian/status/1534282416180838402 pull

costum en BDD§

les costums utilisent du json pour fonctionner pour les maps des costums ya 3 endroits possible à regarder 1 - l’entrée en base de données dans la collection costum 2 - le fichier json car en local , on travail en direct 3 - l’attribut costum de l’element (orga dans votre cas) car il surcharge les 2 premiers

costum en BDD§

les costums utilisent du json pour fonctionner pour les maps des costums ya 3 endroits possible à regarder 1 - l’entrée en base de données dans la collection costum 2 - le fichier json car en local , on travail en direct 3 - l’attribut costum de l’element (orga dans votre cas) car il surcharge les 2 premiers

treedoc§

• an [[abstraction]] for [[tree-structured file formats]]
  • [[go]] [[git]]
  • [[git]] https://github.com/tommyod/treedoc
    • [[json]]
    • [[yaml]]
    • [[xml]]
• distinct from [[tree notation]]