layout: post title: PHPWiki created: 1061253240 categories:

• Web 2.0
• PHP

Installation of PhpWiki is as simple as untarring the source distribution. PhpWiki works right out of the box. You will want to make configuration changes later for better performance and permanence, or to run PhpWiki off a relational database like MySQL, mSQL or Postgresql.

layout: post title: coWiki created: 1068654660 categories:

• Web 2.0
• PHP

From the front page:

coWiki is a free (GPL) tool written in PHP 5 which creates a collaborative website that gathers, organizes and extends knowledge. It can manage text documents and binaries, act like a weblog or organize knowledge bases such as FAQs.

coWiki provides an easy way to maintain and discuss its documents. It also provides a fast way for qualified contributors to create content online, using a simple and easy to apply markup language without needing HTML editing skills.

coWiki is template based, multilingual and modular.

layout: post title: What is a Wiki? created: 1084047646 categories:

• Personal Publishing

An excellent description of what a wiki is, and what it’s used for, all in non-technical terms. Todd asked about wikis in the forum here.

Ultimately, a wiki is a specific type of website. A wiki is special because it allows a group of people to build, edit and modify a website with no programming or HTML whatsoever. Because it doesn’t require technical expertise, all users of the wiki have equal ability to maintain and edit the site. Wikis are easy to learn and use, which makes them accessible to everyone. Common Craft: Wikis Described in Plain English

I also like this section:

Wikis are different from normal web sites:

Normal web sites are usually developed offline and then presented to users as a finished product. By comparison, wikis are first presented to users as a blank slate- an empty page. A new wiki is an empty wiki, no pages, no links. Instead of a team of designers developing a web site in private, a wiki is developed in public by the users of the wiki over the life of the wiki.

A Platform Designed for Collaboration: Federated Wiki§

URL : https://www.freefairandalive.org/read-it/#8

A section in the book [[Free, Fair and Alive]] on [[Federated wikis]] and the [[commons]].

Discusses [[FedWiki]] in particular but can apply to [[Federated wikis]] in general (e.g. [[Agora]], [[IndieWeb]]).

Page 255 [2021-05-16 Sun 08:27]: Participants in a Federated Wiki can decide to interconnect their wiki pages into a neutral, shared neighborhood of content, through which a consensus of viewpoints becomes visible.

Page 255 [2021-05-16 Sun 08:28]: This shift from the standard wiki to a form of writing based on “one person, one wiki, in a federated environment,” may sound like a step backward from the Wikipedia style of open collaboration. But in fact the effect is quite the opposite: giving online platforms to individual voices while bringing them together into a shared neighborhood of wikis results in a richer, more robust commons.

Imagine a huge continent of diverse residences. Some have only a few rooms. Others exist within skyscrapers and provide space for hundreds of rental homes with multiple rooms. Some are clustered together as neighborhoods. Others are smaller and more isolated from other flats and houses. These residences are dispersed all over the continent, but there are irregular corridors, pathways, and roads that can potentially interconnect them all.

To use another metaphor: people using Fedwiki sites are like gardeners or farmers. They can plant as many fields or gardens as they want, and reap the harvest from their own Fedwiki, but anyone else can also use someone’s harvest to enhance their own fields and gardens. Instead of toiling under a regime of private, competitive exclusion, the system encourages cooperative gains through commoning.

Page 257 [2021-05-16 Sun 08:41]: In other words, the Fedwiki software creates protected individual spaces for content generation while facilitating diverse permutations of collaborative authoring on a massive scale. It opens countless paths for individuals to organize their own knowledge while easily sharing it with others, and, what’s more, enabling a commons of knowledge to arise, without the intervention of an editor.

The Fedwiki platform blurs the supposed duality of the individual and the collective. By design, these two realms in Fedwiki world are integrated in a mutually enlivening way. Having my personal wiki does not contradict or interfere with my contributing to the commons — quite the opposite. This is [[Ubuntu Rationality]] at work and a vibrant example of the [[Nested-I]]!

Interestingly, the core idea enshrined in the design of Federated Wiki is similar to the design of many monasteries, as discussed in Chapter Five, in providing supportive environments for collective life while also protecting personal choice.

Fedwiki represents a new type of network platform that sidesteps the domination/subordination dynamics of conventional property

• [[2022-03-12 18:11:30]] [[@flancian:matrix.org]] (link):
  • [[agora tiddlywiki]] ^

Agora Wiki§

• How to best integrate wiki (community editable subnodes) into the [[agora]]?
  • [[etherpad]], perhaps with a wikilink extension
    • [[hackpad]], not maintained but potentially viable
  • [[gollum]]

Welcome§

Ahoy there, Steven!

• You can write Markdown here, multiuser.
• Eventually (shouldn’t take too long) the Agora will be able to just import notes from here, as produced by a user or a group.
• It doesn’t currently support [[wikilinks]] but we will likely add that :)

Welcome§

Ahoy there, Steven!

• You can write Markdown here, multiuser.
• Eventually (shouldn’t take too long) the Agora will be able to just import notes from here, as produced by a user or a group.
• It doesn’t currently support [[wikilinks]] but we will likely add that :)

Welcome§

Ahoy there, Steven!

• You can write Markdown here, multiuser.
• Eventually (shouldn’t take too long) the Agora will be able to just import notes from here, as produced by a user or a group.
• It doesn’t currently support [[wikilinks]] but we will likely add that :)

Welcome§

Ahoy there, Steven!

• You can write Markdown here, multiuser.
• Eventually (shouldn’t take too long) the Agora will be able to just import notes from here, as produced by a user or a group.
• It doesn’t currently support [[wikilinks]] but we will likely add that :)

Combining multiple personal wikis provisions a better commons than one central wiki§

This idea is embodied by the section in Free, Fair and Alive entitled [[A Platform Designed for Collaboration: Federated Wiki]].

Wikipedia tries to define an objective truth on the world’s knowledge. Is that possible? Maybe for some topics, but in many others, the phenomenon of edit wars would suggest not.

Wikipedia defines itself on the removal of voice and subjectivity.

If you can combine multiple personal wikis side-by-side in to one, you can retain voice and subjectivity.

Doesn’t it just become a mess? Isn’t some editorial overview important?

Norbert Wiener defined cybernetics in 1948 as "the scientific study of control and communication in the animal and the machine".

"Cybernetics is the study of automatic control systems, such as the nervous system and brain and mechanical-electrical communication systems." - [[Singularity vs. Daoist Robots]]

The word cybernetics comes from Greek κυβερνητική (kybernētikḗ), meaning "governance", i.e., all that are pertinent to κυβερνάω (kybernáō), the latter meaning "to steer, navigate or govern", hence κυβέρνησις (kybérnēsis), meaning "government", is the government while κυβερνήτης (kybernḗtēs) is the governor or "helmsperson" of the "ship".

Interesting that [[Cybernetics]] has the same Greek root as [[Kubernetes]].

Early theories of cybernetics often refer to [[John von Neumann]]‘s thought experiments: the [[von Neumann cellular automata]] and the [[von Neumann Universal Constructor]].

Cybernetics is closely related to [[Artifical Intelligence]], though the two split in the late 1960s and cybernetics became more interested in sociology and therapy.

Later, the shift to the "new" cybernetics involved shifting focus from the system "being steered" to the system itself doing the steering. It also considered multiple systems "steering each other."

[[Project Cybersyn]] was a project in Allende’s Chile that tried constructing a "decision support system" that could manage the national economy. Project Cybersyn - Wikipedia It’s an example of economic cybernetics.

Filed in: [[Literature Notes]]

Related Links: [[The Computational Turn]]

Decentralised Wiki§

Seems a bit DAO-y.

• https://wiki.lobby.so/ pull
• appears to be centralised

Some of this content is from what I called the Duck Ramen Wiki, because I set it up right around the time we went on a trip to Victoria and I made duck ramen).

I put food, travel, and related type stuff on the [[AllTheBestRecipes]] site now.

Ecogwiki§

• [[go]] https://github.com/akngs/ecogwiki
• [[project]] by [[akngs]]
• [[recommended]] by [[type0]] on [[hn]]: "You might get some good ideas from there, it was a sort of similar python wiki like project that were made for App Engine, it has backlinks, it used json schema extensively (maybe too extensively)."

Emacs Wiki§

Fed Wiki§

Federated Wiki§

• a [[project]]
  • by [[ward cunningham]]
  • [[go]] http://about.fed.wiki/
  • Integration of [[c2]] with federated wiki: https://github.com/WardCunningham/remodeling/issues/3
  • [[pull]] [[fed.wiki]]
  • would love to integrate the Agora with fedwiki — or to just adopt fedwiki protocols/conventions

Federated Wiki§

I had known about Federated Wiki for a while, hearing about it through IndieWeb originally and Wikity. But I never really grokked or explored it.

I then started getting in to personal wikis in 2019.

And then in 2021 after reading the chapter on Federated Wiki in [[Free, Fair and Alive]] and [[Mike Hales]] posting on social.coop about how some of the neighbourhood features works has made me understand more about the exciting ideas it encapsulates.

I’m not yet using it because I’m happy with my wiki in org-roam but I’d like to explore Federate Wiki and its ideas more, one way or another.

Federated Wiki sites share pages circulating within a creative commons. A single-page browser application can read from many sites at once and save changes in that browser. Users who host their own sites can login there to have their edits shared back to the federation as they edit. [http://fed.wiki.org/view/welcome-visitors pull website]

FedWiki is the next wiki-generation. It is a [[software]] that allows everybody to create individual wiki pages while circulating its content in a global - federated - environment. It opens multiple paths for individual knowledge organization while demanding equal responsibility in creating a knowledge [[commons]] . This knowledge commons emerges out of thousands of wiki sites people freely contribute to.

In short: FedWiki provides an [[discrimination-free infrastructure]] that allows for co-creation in diversity.

“Just as the wiki changed how people write, FedWiki will change how people work.” (Ward Cunningham)

YOUTUBE 3nB8ml6UowE Keynote by Ward Cunningham, May 19th2015. [http://lanyrd.com/2015/writethedocs/sdmwxk/ html]

Catalog of federated wiki sites with domain names for page titles and brief descriptions tuned for search.

We publish federated wiki software as a Node.js package ready to run on a variety of platforms. This is usefully run on a personal laptop or an industrial server in the cloud. Most people get started by joining a community and launching sites and/or servers with their help. The server software supports a multi-tenant "farm" option useful for small groups or heavy users. [https://www.npmjs.com/package/wiki npm]

A community of open-source developers maintain both the client-side and server-side applications most frequently used to browse and edit pages. Pages themselves are composed of paragraph-sized items of various kinds. This same community provides a core set of plugins for rich content pages and a variety of experimental plugins that push boundaries of web computing. [https://github.com/fedwiki github]

Ward Cunningham started the federation in 2011 with a workshop project called Smallest Federated Wiki or simply SFW. The data visualization and sharing mechanisms were supported by Nike’s Sustainable Business and Innovation group. Early history has been documented in a series of video screencasts. Search for "video".

• [[flancian]] https://twitter.com/flancian/status/1471562801340727303 pull
• [[flanciavera]] https://twitter.com/flanciavera/status/1471585391031439360 pull
• [[ChrisAldrich]] https://twitter.com/ChrisAldrich/status/1471544698493755395 pull

Status Quo

Wikipedia

Pros:

• Single source of truth: it's a trustworthy source. People know to get their data from here.

• Tons of information. Crowdsourcing has done the

Cons:

• Because it's a single source of truth, there are constant fights over what belongs where that are often fruitless.

• There are also strong arguments that are made for information being 'out of scope' for wikipedia and belonging to a page or site that is more domain specific.

• The organization is bloated and inneficient. They really don't need your donations.

• The servers are centralized and controlled by a single private entity with the potenial to hold data (partially - sans clever parsers) captive.

Wikia

Pros:

• Tons of information with moderators who are experts on their domains.

• Dedicated contributors, existing communities, easy to edit.

Cons:

• Divided into lots of different wikis with no interoperability between them.

• Tons of overlap between wikis (i.e. multiple star wars and minecraft ones, among other franchises and tropes)

• Typically used for casual and hobby interests rather than professional writing and work - why?

Personal wiki implementation

Pros:

• Super flexible.

Cons:

• Not a consistent or reliable source of information, as it's typically controlled by one person.

• Can be disorganized and things can easily become unmaintained.

Version control managed files

Pros:

• Built-in consensus algorithm.

Cons:

• Concurrent modification hurts.

Goals

• Decentralized: share information from many sources without being controlled by any of them

• Open: should incorporate as many sources of knowledge as possible, and individual wikis should have tons of agency.

• Easy to use: it should be incredibly easy to contribute to and communicate with some sort of central wiki.

Information Sources

In order of priority:

1. Wikia sites (there are tons!)

2. Wikipedia

3. wiki.c2.org

4. Assorted third party wikis.

5. [perhaps] personal wikis

6. etc…

Fusing all of the Wikia sites into a single, cohesive wiki seems incredibly useful.

Feature Ideas

• shared & enhanced pages :: fuse pages that cover similar or related topics together into one view.

• consensus :: condense and share overlapping information, reducing the amount of duplication.

• interoperable :: shift from one wiki to another easily.

Wiki IR related decentralized wiki idea (what we were talking about in chat, but not really what is above)

• uses wiki IR standard to link together many peoples personal wikis

• there is an engine at the center (or several?) that crawl the wikiverse and attempt to bring together pages that are similar

  • when pages are similar (by AI?, NLP measure), suggest several types of merging

    • suggestion ways

      • as part of wiki IR cli tool display suggestions

      • make tiny website dashbaord backed by small webapp that phones to recomender engine

    • types of page merging (between peoples federated wiki)

      • link at the bottom of page to other pages with similar content (like webring)

      • transclude entire other page to bottom of your page (and vice versa, both pages in the link transclude eachother)

      • suggest that pages are merged using git-esque strategy (pull request, text diff/merge tools like mergely)

        • q: where does consenus page live? on neither page? (next to ai engines) on one page? (one of the merge requesters 'wins', one conceceds), or both (they share :))

    • goals of merging

      • reduce information duplication

      • instead of conflicts of information being resolved in backchannel of wikipedia, consensus arguments are disputed publicly through pull requests and accepted/rejected page links

      • epic and cool

Conversation linking

• make conversations first class primitive of wiki, so that concepts are linked to discussion in which they are conceived

• can be as simple as citations linking to specific conversations

• uses matrix? hard part is technical challenge of implementation

Backlink fixing

• move/rename pages and update backlinks

Automatically backup videos/external sites

• https://github.com/bibanon/tubeup

• like gwern, to prevent linkrot

Provide tools to make good public/private separation

• so that people can have shareable personal wiki concepts/reference pages, while also having extremely messy private brainstorming (brainstorming=unformed,errorfull,shameless,indulgently bad, creative, risky)/exobrain wiki pages.

Syntax that is not static/markup

• I want a markup syntax like (move [otherpage]: " this concept deserves to be in other page, but right now i am in [firstpage] and don't want to move all the way to otherpage in emacs so im gonna write this thought in a move block: this thought")

  • and that will append that thought to the bottom of other page once i save or run tool or something (linter?)

Smart todo aggregation system

• dokuwiki has decent one,

• zimwiki also has some good features (like hiding todo until certain date)

New types of syntax

• some syntax for assigning how sure you are of an idea, or how much you like it

  • font size???!

  • number of exclamation points vs question marks !!!

First class support for sorting lists

• idk how this would work but interactive sorting is underrated!!!

Visualizers

• like roam/logseq/etc.

• but if they want to use those interactively, just use them and use wiki IR to convert wiki to them

• maybe support something simple like

WIKI LSP

• breadcrumbs (https://i.stack.imgur.com/wu4kP.png)

• definition/lookup. like you can name concepts and hover for definitions?

• autocompletion of other page names

fedwiki§

• a [[project]]
  • [[pull]] [[federated wiki]]
  • [[ward cunningham]]
  • [[matrix]] #fedwiki:matrix.org
    • https://matrix.to/#/#fedwiki:matrix.org
  • [[go]] http://fed.wiki.org
    • [[http preferred]]
  • [[search]] http://search.fed.wiki.org:3030/

• [[federated wiki]]

FedWiki§

– about federated wiki

Smallest Federated Wiki Goals

• Demonstrate that wiki would have been better had it been effectively federated from the beginning.
• Explore federation policies necessary to sustain an open creative community.

I very much like FedWiki and [[federated wikis]] as a principle.

However, a downside of FedWiki (as far as I understand it) is that it is one platform, one tool, that facilitates the federation. A monoculture.

I would prefer a more distributed, protcol-based approach. [[Agora]] works in this sense as each individual can write their garden whichever way they see fit, and just needs to fit in to some accepted formatting protocols to be aggregated.

See also the [[IndieWeb]] approach, where the onus is less on aggregation and more on a certain protocol of communication.

See [[Interlinking wikis]].

FedWiki does seem to offer much simpler actions for copying content from one wiki to another. Agora doesn’t have this built in as such. IndieWeb maybe more so (retweets, quotes, likes, etc, are catered to through webmentions)

Functionality§

All content posted on Fedwiki sites is automatically licensed under a Creative Commons Attribution-ShareAlike 4.0 license upon publi- cation — meaning that it is “born shareable” the moment someone publishes it, making it available to the federation of sites.

– [[A Platform Designed for Collaboration: Federated Wiki]]

The Fedwiki recordkeeping “journal” tracks who has posted what, so authorship can be chronicled even if people make mashups of someone else’s content.

– [[A Platform Designed for Collaboration: Federated Wiki]]

The Fedwiki commons does have one vulnerability to outside control that it has not, as yet, been able to evade: the authentication of digital identity. Because of the complexities of providing a commons-friendly alternative, Cunningham and his colleagues have relied on the identity systems developed by Google and Facebook that function as a default for many sites on the internet.

– [[A Platform Designed for Collaboration: Federated Wiki]]

Criticism§

• http://thoughtstorms.info/view/LeavingTheSFW

[[federated wiki]]

[[go]] [[search]] http://search.fed.wiki.org:3030/ pull

• [[mathew@campaign.openworlds.info]] https://campaign.openworlds.info/@mathew/109420925478433660 pull
• [[flancian@social.coop]] https://social.coop/@flancian/110041076816472426 pull

• [[mathew@campaign.openworlds.info]] https://campaign.openworlds.info/@mathew/109670587454895492 pull

• [[flancian]] https://twitter.com/flancian/status/1473407386983571465 pull
• [[flancian]] https://twitter.com/flancian/status/1479382602985398274 pull
• [[flancian]] https://twitter.com/flancian/status/1499877317757259783 pull
• [[flancian]] https://twitter.com/flancian/status/1533894654118219777 pull
• [[flancian]] https://twitter.com/flancian/status/1552392330895695872 pull
• [[flancian]] https://twitter.com/flancian/status/1552396170953199618 pull
• [[flancian]] https://twitter.com/{‘id’: ‘773144670507499521’, ‘name’: ‘The Agora is a Federated Knowledge Commons’, ‘username’: ‘flancian’}/status/1552396170953199618
• [[flancian]] https://twitter.com/{‘id’: ‘773144670507499521’, ‘name’: ‘The Agora is a Federated Knowledge Commons’, ‘username’: ‘flancian’}/status/1552392330895695872

• [[2022-03-12 17:36:56]] [[@flancian:matrix.org]] (link):
  • moonlion.eth (vera) 🍄 wrote the [[fedwiki]] importer with similar logic, although it writes .md instead.

• [[flancian]] https://twitter.com/{‘id’: ‘773144670507499521’, ‘name’: ‘The Agora is a Federated Knowledge Commons’, ‘username’: ‘flancian’}/status/1552396170953199618
  • @BillSeitz @bmann @jessmartin @RobertHaisfield @csageland @balOShere @JoelChan86 @TiddlyWiki @an_agora @socialroots_io "Parallel play with forks" as a modality, like that IIUC implemented by [[fedwiki]] and [[agora]] in similar ways, I believe can lower friction significantly towards cooperation and enable bootstrap of a system which supports arbitrary modalities.- [[flancian]] https://twitter.com/{‘id’: ‘773144670507499521’, ‘name’: ‘The Agora is a Federated Knowledge Commons’, ‘username’: ‘flancian’}/status/1552392330895695872
  • @WardCunningham @csageland @BillSeitz @bmann @jessmartin @RobertHaisfield @balOShere @JoelChan86 @TiddlyWiki @an_agora @socialroots_io @Bortseb Ward, I’m a huge fan, this would be such an opportunity to advance on an interop standard for personal wikis — should [[personal knowledge graphs]] be talking [[fedwiki]] protocol to each other?

• [[2022-11-14 21:16:39]] [[@flancian:matrix.org]] (link):

  •                - report to Nathan on wiki consolidation with a yes :)
                - keep tech/operations as the One Repository to clone if you're a new member of the twg
                - fold [[sauce]] general scripts into [[tech operations]]
                - fold [[systemd unit]] files in [[sauce]] into [[ansible]]
                - fold [[tech operations]] wiki into [[general.wiki]]
                - [[redoak]] did the last mastodon upgrades, we could ask how long of a maintenance window we should call
                - Announce maintenance window for upgrades: **Let's shoot for Monday 21 at 18-20 UTC**
    

this

Currently has:

• the official [[markdown]] plugin, along with button visibility tweaks
• the krystal theme
• some settings tweaks
• my [[backlink footer]]
• some [[google fonts]]
• some basic tips

TiddlyWiki makes a great GuerillaWiki in situations where it is not practical to use a traditional wiki.

For instance, in a corporate setting, persuading an over-worked IT department to install a Wiki server for you is seldom going to be possible overnight. And if your PC is locked down you can’t install a conventional Wiki yourself. Equally, you can’t go and use one of the public hosted Wiki services because your Information Security department would not allow all that corporate data to flow into an outside server.

TiddlyWiki slices through those barriers by being usable on virtually all PCs.

Help Create This Wiki§

This page holds geeky info for how to edit Massive Wiki, the platform that Rel8 Wiki is built atop.

We value crispness, modularity and composability. Please follow the [[Writing Style for This Project]]

Massive Wiki is built atop GitHub (we may move to a different Git host, but Git is central), which means Rel8 Wiki pages obey GitHub’s Fork and Pull dynamics, which are an elegant (if geeky) way to collaborate.

So: To help edit and improve the Rel8 Wiki, create an account on GitHub, then fork the Rel8 repository into your own account. Then send pull requests with edits and additions.

More detailed info on Massive Wiki is over in its wiki. There’s also a Mattermost channel dedicated to it.

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

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

How personal is a personal wiki?§

At the beginning, I’m keeping it pretty academic. I’m not putting anything about my personal life, or more personal thoughts, in here. Mainly just as I’m hesitant to share that stuff. But it’s a personal wiki, should it have personal thoughts? I guess somewhere you have to make the distinction between personal thoughts and public and private thoughts.

Stuff that will never get published, but benefits from collecting and connecting the dots.

Ideally I’d like to have some parts of my wiki private/encrypted, so everything could be interlinked, but only what I choose to share is ever shared when I publish. I need [[gevulot]].

Private wiki§

The simplest solution is probably to just separate public/private thoughts out into different wikis. I am currently just using a separate [[org-roam]] private wiki.

[[Bill Seitz]] has lots to say about private wikis. Private Wiki - WebSeitz/wiki

How should you structure a personal wiki?§

Paths and threads§

How do you show someone around your garden? [[Connecting the dots]]. You can provide some paths to some degree in the wiki itself. But also turn it into articles from time to time, your own curated path for the here and now.

Wild or tended?§

h0p3 has a home page entry point that is carefully curated and groomed, but which is several layers up from a complete chaos of link dumps, raw drafts and random introspections […] These layers run a spectrum of accessibility—there is always a learning curve before you hit the bottom. You start with a doorway before entering a maze.

– Notes: We’ve Got Blog (2002), Kicks Condor

I think this relates to paths and threads. People can take any route around, but it’s good to provide some kind of path.

[[Page size]]§

hyper commonplace garden wiki§

I’m not sure what to call it. I think it’s

• a digital [[commonplace book]]
• a [[digital garden]]
• a [[personal wiki]]
• a [[hypertext]]
• an [[exobrain]]
• a [[personal homepage]]

some combo thereof.

Because everyone loves a colophon: some more info on how I make this place [[here]].

• [[bengo]] https://mastodon.social/@bengo/109354449070366913 pull

Inter Wiki§

• [[go]] https://wiki.c2.com/?InterWiki pull
• Similar to [[agora protocol]].

InterWiki§

URL : https://wiki.c2.com/?InterWiki pull

Over time, InterWiki has come to mean connecting existing wiki, of various WikiEngine types, together.

[[Interlinking wikis]]

• [[2022-05-14 12:10:45]] [[@charismatic_shell:matrix.org]] (link):
  • I have this older write-up on [[interwiki]]: https://mycorrhiza.lesarbr.es/hypha/idea/interwiki
• [[2022-05-28 20:41:23]] [[@flancian:matrix.org]] (link):
  • I want to implement [[interwiki]] in the Agora

Ipfs Backend for Tiddlywiki§

• [[ipfs]] [[backend]] for [[tiddlywiki]]
• [[go]] https://github.com/xmaysonnave/tiddlywiki-ipfs
• [[thank you]] [[stile65]] [[dietrich]] https://twitter.com/stile65/status/1352660883898421249 pull

In Search of a Nice Team Wiki§

Overview§

This page is collaboratively owned; please add / edit sections to improve.

Pete is joining a new startup team who are very engaged in the team’s business work, but who are not very technical.

What are some possible team wikis we might use? Key desired features: easy to use for non-technical folks, markdown support. Realtime collaborative editing a plus.

Pete started this page on 2024-10-26.

Outline§

https://www.getoutline.com/

Ask Pete kaminski@istori.com for an invite to his test instance (through 2024-11-24).

Looks pretty nice, actually. They don’t market themselves well, and their 30-day trial is difficult to set up (you need a business account on Google or Microsoft, or you can set up a Slack instance and sneak in that way). But that’s a one-time setup thing. After 30 days, workspaces go read-only but export still works.

Open source and self-hostable, which is nice. (The startup would probably use hosted, though.)

The organization and editor look easy enough for non-technical folks, and is mostly powerful enough for Pete. Looks like they have nice embedding support, including Grist and Diagrams.net among many others.

Has realtime collaborative editing.

The wiki linking is a little wonky. You can do it, but only with Command-K, not double square brackets. If a destination page gets renamed, link text to that page doesn’t change (and is not very easy to change by hand). I (Pete) am not crazy about how this works, but it might be fine for non-technical folks.

Affine§

https://affine.pro/

Looks neat, but it’s complicated.

Capacities§

https://capacities.io/

Very nice Notion alternative. Single player only, though.

Google Docs§

::rolls eyes::

Hedgedoc / HackMD§

Great for single pages, wiki features are not robust enough.

Massive Wiki§

https://massive.wiki/

Too free-form, no realtime collaborative editing, sync is either too technical (Git) or too brittle for multiple users (Obsidian Sync).

Otherwise, it’s perfect. :-)

(Engineering will have one or more Massive Wikis, of course.)

Notion§

https://notion.so/

The mainline alternative right now. Too complicated for Pete’s taste.

Confluence§

No thanks. Confluence is confusing and hard to use. (Not quite as bad as Jira, but don’t get me started.)

Other Disqualified Candidates§

• wiki.js - it’s cute, but too old school (despite the modernity of the implementation)
• https://decko.org/ (formerly Wagn) - neat vision, still under development
• TeamBrain - not beginner-friendly, too network-oriented, not page-oriented enough

In Search of a Nice Team Wiki§

Overview§

This page is collaboratively owned; please add / edit sections to improve.

Pete is joining a new startup team who are very engaged in the team’s business work, but who are not very technical.

What are some possible team wikis we might use? Key desired features: easy to use for non-technical folks, markdown support. Realtime collaborative editing a plus.

Pete started this page on 2024-10-26.

Outline§

https://www.getoutline.com/

Ask Pete kaminski@istori.com for an invite to his test instance (through 2024-11-24).

Looks pretty nice, actually. They don’t market themselves well, and their 30-day trial is difficult to set up (you need a business account on Google or Microsoft, or you can set up a Slack instance and sneak in that way). But that’s a one-time setup thing. After 30 days, workspaces go read-only but export still works.

Open source and self-hostable, which is nice. (The startup would probably use hosted, though.)

The organization and editor look easy enough for non-technical folks, and is mostly powerful enough for Pete. Looks like they have nice embedding support, including Grist and Diagrams.net among many others.

Has realtime collaborative editing.

The wiki linking is a little wonky. You can do it, but only with Command-K, not double square brackets. If a destination page gets renamed, link text to that page doesn’t change (and is not very easy to change by hand). I (Pete) am not crazy about how this works, but it might be fine for non-technical folks.

Affine§

https://affine.pro/

Looks neat, but it’s complicated.

Capacities§

https://capacities.io/

Very nice Notion alternative. Single player only, though.

Google Docs§

::rolls eyes::

Hedgedoc / HackMD§

Great for single pages, wiki features are not robust enough.

Massive Wiki§

https://massive.wiki/

Too free-form, no realtime collaborative editing, sync is either too technical (Git) or too brittle for multiple users (Obsidian Sync).

Otherwise, it’s perfect. :-)

(Engineering will have one or more Massive Wikis, of course.)

Notion§

https://notion.so/

The mainline alternative right now. Too complicated for Pete’s taste.

Confluence§

No thanks. Confluence is confusing and hard to use. (Not quite as bad as Jira, but don’t get me started.)

Other Disqualified Candidates§

• wiki.js - it’s cute, but too old school (despite the modernity of the implementation)
• https://decko.org/ (formerly Wagn) - neat vision, still under development
• TeamBrain - not beginner-friendly, too network-oriented, not page-oriented enough

In Search of a Nice Team Wiki§

Overview§

This page is collaboratively owned; please add / edit sections to improve.

Pete is joining a new startup team who are very engaged in the team’s business work, but who are not very technical.

What are some possible team wikis we might use? Key desired features: easy to use for non-technical folks, markdown support. Realtime collaborative editing a plus.

Pete started this page on 2024-10-26.

Outline§

https://www.getoutline.com/

Ask Pete kaminski@istori.com for an invite to his test instance (through 2024-11-24).

Looks pretty nice, actually. They don’t market themselves well, and their 30-day trial is difficult to set up (you need a business account on Google or Microsoft, or you can set up a Slack instance and sneak in that way). But that’s a one-time setup thing. After 30 days, workspaces go read-only but export still works.

Open source and self-hostable, which is nice. (The startup would probably use hosted, though.)

The organization and editor look easy enough for non-technical folks, and is mostly powerful enough for Pete. Looks like they have nice embedding support, including Grist and Diagrams.net among many others.

Has realtime collaborative editing.

The wiki linking is a little wonky. You can do it, but only with Command-K, not double square brackets. If a destination page gets renamed, link text to that page doesn’t change (and is not very easy to change by hand). I (Pete) am not crazy about how this works, but it might be fine for non-technical folks.

Affine§

https://affine.pro/

Looks neat, but it’s complicated.

Capacities§

https://capacities.io/

Very nice Notion alternative. Single player only, though.

Google Docs§

::rolls eyes::

Hedgedoc / HackMD§

Great for single pages, wiki features are not robust enough.

Massive Wiki§

https://massive.wiki/

Too free-form, no realtime collaborative editing, sync is either too technical (Git) or too brittle for multiple users (Obsidian Sync).

Otherwise, it’s perfect. :-)

(Engineering will have one or more Massive Wikis, of course.)

Notion§

https://notion.so/

The mainline alternative right now. Too complicated for Pete’s taste.

Confluence§

No thanks. Confluence is confusing and hard to use. (Not quite as bad as Jira, but don’t get me started.)

Other Disqualified Candidates§

• wiki.js - it’s cute, but too old school (despite the modernity of the implementation)
• https://decko.org/ (formerly Wagn) - neat vision, still under development
• TeamBrain - not beginner-friendly, too network-oriented, not page-oriented enough

In Search of a Nice Team Wiki§

Overview§

This page is collaboratively owned; please add / edit sections to improve.

Pete is joining a new startup team who are very engaged in the team’s business work, but who are not very technical.

What are some possible team wikis we might use? Key desired features: easy to use for non-technical folks, markdown support. Realtime collaborative editing a plus.

Pete started this page on 2024-10-26.

Outline§

https://www.getoutline.com/

Ask Pete kaminski@istori.com for an invite to his test instance (through 2024-11-24).

Looks pretty nice, actually. They don’t market themselves well, and their 30-day trial is difficult to set up (you need a business account on Google or Microsoft, or you can set up a Slack instance and sneak in that way). But that’s a one-time setup thing. After 30 days, workspaces go read-only but export still works.

Open source and self-hostable, which is nice. (The startup would probably use hosted, though.)

The organization and editor look easy enough for non-technical folks, and is mostly powerful enough for Pete. Looks like they have nice embedding support, including Grist and Diagrams.net among many others.

Has realtime collaborative editing.

The wiki linking is a little wonky. You can do it, but only with Command-K, not double square brackets. If a destination page gets renamed, link text to that page doesn’t change (and is not very easy to change by hand). I (Pete) am not crazy about how this works, but it might be fine for non-technical folks.

Affine§

https://affine.pro/

Looks neat, but it’s complicated.

Capacities§

https://capacities.io/

Very nice Notion alternative. Single player only, though.

Google Docs§

::rolls eyes::

Hedgedoc / HackMD§

Great for single pages, wiki features are not robust enough.

Massive Wiki§

https://massive.wiki/

Too free-form, no realtime collaborative editing, sync is either too technical (Git) or too brittle for multiple users (Obsidian Sync).

Otherwise, it’s perfect. :-)

(Engineering will have one or more Massive Wikis, of course.)

Notion§

https://notion.so/

The mainline alternative right now. Too complicated for Pete’s taste.

Confluence§

No thanks. Confluence is confusing and hard to use. (Not quite as bad as Jira, but don’t get me started.)

Other Disqualified Candidates§

• wiki.js - it’s cute, but too old school (despite the modernity of the implementation)
• https://decko.org/ (formerly Wagn) - neat vision, still under development
• TeamBrain - not beginner-friendly, too network-oriented, not page-oriented enough

• [[jonny]] https://social.coop/@jonny/109135233389666304 pull

Jonny | Add to Wiki§

A place where [[jonny]] reminds themselves to add things to the [[autopilot]] [[wiki]], aka the [[autopilot wiki]] at https://wiki.auto-pi-lot.com pull .

Jonny | Add to Wiki§

A place where [[jonny]] reminds themselves to add things to the [[autopilot]] [[wiki]], aka the [[autopilot wiki]] at https://wiki.auto-pi-lot.com pull .

Jonny | Add to Wiki§

A place where [[jonny]] reminds themselves to add things to the [[autopilot]] [[wiki]], aka the [[autopilot wiki]] at https://wiki.auto-pi-lot.com pull .

Jonny | Add to Wiki§

A place where [[jonny]] reminds themselves to add things to the [[autopilot]] [[wiki]], aka the [[autopilot wiki]] at https://wiki.auto-pi-lot.com pull .

• [[json_dirs]] https://twitter.com/json_dirs/status/1546692273643040769 pull
• [[json_dirs]] https://twitter.com/json_dirs/status/1560837797338001409 pull
• [[json_dirs]] https://twitter.com/{‘id’: ‘892306984610824192’, ‘name’: ‘𝚓𝚘𝚗𝚗𝚢﹏𝚜𝚊𝚞𝚗𝚍𝚎𝚛𝚜’, ‘username’: ‘json_dirs’}/status/1560837797338001409
• [[json_dirs]] https://twitter.com/{‘id’: ‘892306984610824192’, ‘name’: ‘𝚓𝚘𝚗𝚗𝚢﹏𝚜𝚊𝚞𝚗𝚍𝚎𝚛𝚜’, ‘username’: ‘json_dirs’}/status/1546692273643040769

• #pull [[klavawiki]]

Letter.wiki§

• [[go]] letter.wiki
• [[abstractfairy]] thought it was interesting

Making a recent changes page on my wiki§

I’ve changed my sitemap page to be a RecentChanges page - the pages that have changed recently, ordered anti-chronologically. [[Here it is]].

Why§

I’ve found that [[Phil]]‘s recent changes page is a nice [[entry point]] in to ThoughtStorms. It’s a very low-effort [[stream]] - it just falls out of the changes that you are already making.

I already have a kind of recent changes list, that was just the activity stream from the git repo of the source of my site. It worked OK, but I prefer this new list.

Interesting to compare ‘recent changes’ to my [[Recent noodlings]] - these are more curated and closer to the normal stream you would get on a Twitter-like microblog (and that I repost on my IndieWeb stream, in fact).

I guess I’ll have both, can’t hurt. Would be interesting to reflect on the difference between the two a bit more though.

How§

[[org-publish]] has a bunch of features for automatic sitemap generation. I was already using it to list all pages, but just sorted alphabetically. I changed it to sort ‘anti-chronologically’ (i.e. reverse date ordered). I also changed the sitemap-format-entry function to include the last modification date.

This post was helpful: Blogging with Org publishing.

Tweaks§

Updated date§

I think the date currently comes from mtime? Which sometimes gets changed when I do bulk changes and haven’t actually touched the content. Would be better to have something which is only changed when the content changes, perhaps pulling it out of git logs, or based on a property in the front matter of the notes themselves.

Everything?§

Currently it lists all pages in the garden. Doesn’t affect loading time, so not a big problem, but would it make more sense to just show the most recent X changes?

• a [[wiki]]
  • [[go]] https://massive.wiki/
    • [[quote]] "Massive Wiki is a movement to create a wiki ecosystem (rather than just one engine) that provides classic wiki utility, with a plurality of tools and processes that enable decentralization and federation of the pages."
      • sounds very [[agora]] like!
  • by [[peter kaminski]]
  • [[git]] https://github.com/Massive-Wiki/massive-wiki
  • [[manifesto]] https://massive.wiki/massive_wiki_manifesto pull
    • [[quote]] We use [[Markdown]] because it is a lingua franca.

• https://massive.wiki/

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

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

• [[flancian]] https://twitter.com/flancian/status/1471562801340727303 pull
• [[flanciavera]] https://twitter.com/flanciavera/status/1471585391031439360 pull
• [[ChrisAldrich]] https://twitter.com/ChrisAldrich/status/1471544698493755395 pull

• [[mathew@campaign.openworlds.info]] https://campaign.openworlds.info/@mathew/109857022655902893 pull

• [[mathew@campaign.openworlds.info]] https://campaign.openworlds.info/@mathew/109857031974557496 pull

Mediawiki & Communecter§

Introduction§

Cette partie du module interop, cherche en cas de mediawiki existant à le connecter avec communecter et de permettre via un bouton a créer des éléments du type de la page du wiki, ou en cas d’élément présent de fournir le lien, enfin mais nécessitant un réglage sur le wiki existant de marquer le wiki avec le liens de la page co.

Initialisation du mediawiki§

Dans le sub-menu-left d’un élément on clic sur @Mediawiki .

dans MediaWikiController.php beforeAction() instancie APIMediawiki (model de relations avec le wiki) qui est enfant de DB (model de relations avec la bdd)

interop/MediaWiki/index§

beforeAction() du controller instancie APIMediawiki (model de relations avec le wiki) qui est enfant de DB (model de relations avec la bdd)

le controlleur rend une vue partiel sauf pour edit qui renvoi une string.

L’action par default du controller actionIndex()§

un formulaire s’ouvre lors de la premiére connection ou l’url du wiki et son nom dans communecter son rentré par l’utilisateur. $this->renderPartial("interop.views.create.index"); a la validation du form direction actionChooseCat()

Si wiki deja connecté renvoi vers l’index via: $this->renderPartial("interop.views.default.indexMediaWiki");

L’action actionChooseCategory()§

Insére les données du formulaire (url et name) puis ouvre $this->renderPartial("interop.views.create.chooseCat");

un formulaire préremplie par les données de l’api du wiki sur les catégories filtrer par regex afin de coler aux catégorie du futur menu soit (acteurs, ressource, projet) (les regex son en dur dans le code faire un tableau de comparaison afin d’ajouter ou enlever des mots de trie peu étre une bonne contribution en cas de contributeur volontaire ;o) a la validation du form direction actionInsertCat()

L’action actionInsertCat()§

Insére les données du formulaire le wiki en db vaut désormais:

 "_id" : ObjectId("idmongo"),
    "name" : "name du wiki entré par l'user",
    "parent" : {
        "mongo id du parent" : {
            "type" : "type parent",
            "name" : "name parent"
        }
    },
    "url" : "url entré par l'utilisateur + '/api.php",
    "params" : {
        "actors" : [ 
            "categorie choisit par l'user",
            ...
        ],
        "classifieds" : [ 
            "categorie choisit par l'user",
            ...
        ],
        "projects" : [ 
            "categorie choisit par l'user",
            ...
        ]
    },
    "logo" : ""
}

renvoi vers la vue index return $this->renderPartial("interop.views.default.indexMediaWiki");

L’action actionMenuLeft()§

Vas chercher les données pour le menuleft des pages du wiki en fonction du button-catégorie(acteurs,ressources,projet) clicker ou du texte de la search bar. puis les rend dans la vue return $this->renderPartial("interop.views.menus.pages");

L’action actionPage()§

Vas chercher les données pour la page du wiki en fonction du nom de la page. puis les rend dans la vue return $this->renderPartial("interop.views.page.index");

L’action actionEdit()§

Ici via le modéle ApiMediawiki.php on marque la page du wiki avec un lien communecter (!! une propriétées est a créer sur le wiki distant |pageCo= voir avec l’administrateur du wiki.) renvoie une string message sur le status de l’edition.

L’action actionDoc()§

renvoi vers cette page

Relations wiki et Intégration dans communecter§

Dans A propos il ya trois boutons qui font les liens: Un bouton Page du Wiki qui redirige vers la page source du wiki. Un bouton Site web qui redirige vers le site de l’élement du wiki.

Le dernier bouton peu avoir deux valeurs : Créer dans communecter qui ouvre un formulaire préremplie et éditable afin de créer un élément communecter. Page Communecter qui redirige vers la page communecter en relation avec l’élément du wiki.

Mediawiki & Communecter§

Introduction§

Cette partie du module interop, cherche en cas de mediawiki existant à le connecter avec communecter et de permettre via un bouton a créer des éléments du type de la page du wiki, ou en cas d’élément présent de fournir le lien.

Initialisation du mediawiki§

Dans le menu d’un élément on clic sur @Mediawiki en dessous de "Points d’intérêt".

Arrivé dans interop/MediaWiki/ beforeAction() instancie APIMediawiki (model de relations avec le wiki) qui est enfant de DB (model de relations avec la bdd) cherche en base de données l’existence ou non de ce wiki, si non cela crée dans collection "mediawiki" un wiki vide de la forme:

public function newIn($id, $name, $type)
{
$baseDataDB = [
"name" => $name,
"parent" => [
"id" => $id,
"type" => $type
],
"url" => "",
"params" => "none",
"logo" => ""
];
PHDB::insert("mediawiki", $baseDataDB);
}

L’action par default du controller ActionIndex() elle récupère les infos en base de données via le model et envoie les bonnes données dans la vue

{
    "_id" : ObjectId(""),
    "name" : nomduwiki,
    "parent" : {
        "id" : ,
        "type" : 
    },
    "url" : "<urlEnregistré>/api.php",
    "params" : {
        "ressources" : {
            "get" : [ 
                "[[Cat%C3%A9gorie:<catTrouvé>]]", 
...
            ]
        },
        "acteurs" : {
            "get" : [ 
                 "[[Cat%C3%A9gorie:<catTrouvé>]]", 
...
            ]
        },
        "projets" : {
            "get" : [ 
               "[[Cat%C3%A9gorie:<catTrouvé>]]", 
...
        }
    },
    "logo" : ""
}

Utilisation navigation§

Sur interop.views.default.indexMediaWiki les boutons Acteurs, Projets, Emplois s’affiche en cas d’existence. Clic direction interop/mediawiki/menuleft qui appel la méthode **menu(**catégorieChoisie) de l’instance APIMediaWiki. Qui va chercher la listes des pages liées créer la data pour la vue appelé par le controller qui affiche les résultats dans un menu déroulant trié par ordre alphabétique en accordéon si résultat est supérieur à 30 unités: interop.views.menus.pages.

Au clic sur le nom du page direction interop/mediawiki/page qui appel la méthode page(nomPage) de l’instance APIMediaWiki qui scan les propriétés disponibles de la page puis récupère les données. Ces données sont trié et converties afin de standardiser pour la vue et les inputs préremplies de formulaires de création d’élément via convertWikiMediaToPh(['data' => $dataRécupérer, $nomCatégorie, $nomDuWiki) dans le module citizenToolKit/model/Convert.php

Ces données sont envoyées dans la vue interop.views.page.index qui affiche par défault un A propos de la page du wiki et le menu left contient en fonction des données des boutons proposant de lister Communautées(sous divisé en communauté et utilisateur), Défis, Ressources en rapport avec la page du wiki.

Tout clic sur une entités réprésentant une autre page du wiki fait le méme chemin a partir de interop/mediawiki/page du controlleur interop/MediaWiki.

Relations wiki et Intégration dans communecter§

Dans A propos il ya trois boutons qui font les liens: Un bouton Page du Wiki qui redirige vers la page source du wiki. Un bouton Site web qui redirige vers le site de l’élement du wiki.

Le dernier bouton peu avoir deux valeurs : Créer dans communecter qui ouvre un formulaire préremplie et éditable afin de créer un élément communecter. Page Communecter qui redirige vers la page communecter en relation avec l’élément du wiki.

• [[jonny]] https://social.coop/@jonny/109327688014029017 pull
• [[jonny@neuromatch.social]] https://neuromatch.social/@jonny/109677892115717208 pull

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

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

• [[2023-03-11 18:59:44]] [[@flancian:matrix.org]] (link):
  • then I intend to set up [[mediawiki]] and maybe [[bonfire]], but let’s see how far I get ;)
• [[2023-03-15 21:46:31]] [[@flancian:matrix.org]] (link):
  • I plan to migrate to wiki.social.coop to [[mediawiki]] some time from now into weekend :D

Muscle Wiki§

• [[pull]] [[musclewiki]] [[musclewiki.com]]
• [[go]] musclewiki.com
  • Nice site that maps [[muscle]] groups to focused [[exercises]].
  • [[stretches]] [[bodyweight]] [[barbell]] [[dumbbell]] [[kettlebell]]

P2P Foundation Wiki§

URL : https://wiki.p2pfoundation.net/ pull

Shame that [[Michel Bauwens]] went off the rails, but I think/assume that the P2PF wiki is still a solid source of info, as it is a wiki of many voices.

patternlanguage.commoning.wiki§

http://patternlanguage.commoning.wiki/view/welcome-visitors pull

interop Mediawiki§

ouvrir le dynfom config§

$("#central-container").load(baseUrl+"/interop/mediawiki/index", {id: contextData.id, name: contextData.name, type: contextData.type});

connecter au MW§

https://www.communecter.org/interop/mediawiki/choosecategory actionChooseCategory this->api->insertFirstStep url : https://movilab.org/wiki/Api.php?action=query&list=allcategories&aclimit=max&format=json faut etre loggué

• [[jonny]] https://social.coop/@jonny/109327688014029017 pull

Sequential Wiki§

• Not a formal term, but I use it often. A sequential wiki is like a wiki page, but people contribute blocks of [[content]] instead of arbitrary fragments; and they maintain clear ownership and control over their blocks.
• I call the [[agora]] a distributed sequential wiki. [[nodes]] are akin to sequential wiki pages. [[subnodes]] are user contributed blocks.
• [[pull]] [[everything2]]

…Sequential Wiki Not a formal term, but I use it often. A sequential wiki is like a wiki page, but people contribute blocks of [[content]] instead of arbitrary fragments; and they maintain clear ownership and control over their blocks. I call the [[agora]] a distribu…

This is an excellent concept but I’m not sold on the name, simply because part of what’s so powerful about this kind of thing is that the possibilities for sequencing are wide open. Like with the experimental upranking in settings — maybe what I want to see first are my social contacts’ blocks, people I "follow". Or maybe I want to pull in a ranking service that has experts vet medical info and be able to uprank based on that. Or maybe I want to most of the time see something like one of the above, but sometimes surf the recent content just for fun. You know? "Sequential" makes me think the order is important, I guess, but that might be overly programmer-brained, and probably I’m coming at this with different metaphors than you had in mind. Curious to hear your thoughts!

• #go https://wiki.sgmk-ssam.ch/wiki/Workshops#AI@SGMK pull

• a [[project]].
  • To move wiki.social.coop to [[mediawiki]].
  • Started by [[jonny]].

• Welcome!
• This is a knowledge graph about [[SPARQL]]. It contains a summary page of a [[SPARQL training course]], links to tutorials, specifications, [endpoints]([[SPARQL Endpoints]]), explanations of SPARQL keywords and functions, syntax, query examples, [tools]([[SPARQL Tools]]) and many other resources. The graph will grow based on the knowledge captured from training sessions, support chats, and feedback.
• This wiki has special features for content use and exploration not available in traditional wikis. You can use it intuitively, or you may check these [tips]([[How to use this graph?]]) first.
• [[How to use this graph?]]
• [[SPARQL training course]]
• [[SPARQL Syntax]]
• [[SPARQL Endpoints]]
• [[Exploratory queries]]
• [[SPARQL Tools]]
• [[Prefixes]]
• Tutorials
• Created by [[Ivo Velitchkov]].
• Last update: October 11, 2024
• If you want to report an error or suggest an improvement, please create an issue on GitHub.
• Related wikis on semantic technologies: SHACL Wiki

• [[fROYndlich]] https://twitter.com/fROYndlich/status/1426068830506344455 pull

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

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

tiddlywiki§

• a [[wiki]]
  • [[single file]]
  • one of the OGs in the [[tools for thought]] space.
  • by [[jeremy ruston]]
  • [[go]] https://tiddlywiki.com pull
  • [[git]] https://github.com/Jermolene/TiddlyWiki5

    • Welcome to TiddlyWiki, a non-linear personal web notebook that anyone can use and keep forever, independently of any corporation.

    • [[gitter]] https://gitter.im/TiddlyWiki/public
    • [[discord]] https://discord.gg/HFFZVQ8
  • https://twitter.com/flancian/status/1454464250555023368 pull
  • [[node server]]
  • [[tiddlywiki markdown]]
  • [[pipe alises]] == [[pipe links]]
    • [[bar]]
      • https://twitter.com/TiddlyWiki/status/1483764445063139328 pull

TiddlyWiki§

• [[maya@occult.institute]] https://occult.institute/@maya/109354462938087192 pull
• [[schmidt_fu@mstdn.social]] https://mstdn.social/@schmidt_fu/110677044498483081 pull

• [[flancian]] https://social.coop/@flancian/108369075968512603 pull
• [[flancian]] https://social.coop/@flancian/108435415096641688 pull
• [[flancian@social.coop]] https://social.coop/@flancian/109956569673071202 pull
• [[nicksiv@octodon.social]] https://octodon.social/@nicksiv/110088967145350810 pull
• [[nicksiv@octodon.social]] https://octodon.social/@nicksiv/110111809856897871 pull
• [[nicksiv@octodon.social]] https://octodon.social/@nicksiv/110235156011003440 pull
• [[nicksiv@octodon.social]] https://octodon.social/@nicksiv/110603854003880838 pull
• [[nicksiv@octodon.social]] https://octodon.social/@nicksiv/110614511808198969 pull

• [[gavcloud]] https://twitter.com/gavcloud/status/1518337332293758976 pull

• [[gavcloud]] https://twitter.com/gavcloud/status/1482156651087990786 pull

• [[flancian]] https://twitter.com/flancian/status/1483746620927795201 pull
• [[gavcloud]] https://twitter.com/gavcloud/status/1514112636253716486 pull
• [[OnePlaybookHQ]] https://twitter.com/OnePlaybookHQ/status/1514172616667537409 pull
• [[flancian]] https://twitter.com/flancian/status/1529855422865317888 pull
• [[flancian]] https://twitter.com/flancian/status/1532084341643296768 pull
• [[flancian]] https://twitter.com/flancian/status/1534100049499721728 pull
• [[gavcloud]] https://twitter.com/gavcloud/status/1535387701142241281 pull
• [[fractal_person]] https://twitter.com/fractal_person/status/1535402106571595776 pull
• [[gavcloud]] https://twitter.com/gavcloud/status/1538347941034967040 pull
• [[flancian]] https://twitter.com/flancian/status/1576234838725521410 pull

• [[2022-03-12 17:30:32]] [[@flancian:matrix.org]] (link):
  • [[pesho]] uses [[tiddlywiki]] as well — the question I have open is how to integrate gardens which aren’t based on .md files

• [[flancian]] https://twitter.com/flancian/status/1576234838725521410 pull
  • @kvistgaard @TfTHacker @jessmartin @logseq @an_agora There’s some more tools in the legacy-named [[roam likes]] ~ https://t.co/bc5i2RFYqy, but not all Markdown based or Markdown friendly.

Most notably though: [[tiddlywiki]] by @Jermolene has a Markdown backed mode which I’ve been meaning to try.

@an_agora

Tweets From TiddlyWiki§

Metadata§

• Author: [[@TiddlyWiki on Twitter]]
• Full Title: Tweets From TiddlyWiki
• Category: #tweets
• URL: https://twitter.com/TiddlyWiki

Highlights§

• Interesting discussion on the epistemology and ethics of TiddlyWiki https://t.co/iTiAuS8mbv https://t.co/kEz3A2yeRR

  ⥅ [[https://pbs.twimg.com/media/FCIsIylXsAAjtwY.jpg]]

  ([View Tweet](https://twitter.com/TiddlyWiki/status/1450770564193390593 pull))

#go https://github.com/vimwiki/vimwiki

• [[flancian]] https://social.coop/@flancian/107785983377123406 pull
• [[flancian]] https://social.coop/@flancian/108041638417581984 pull
• [[flaneur@merveilles.town]] https://merveilles.town/@flaneur/112911636893657801 pull

• [[flaneur@merveilles.town]] https://merveilles.town/@flaneur/112911636893657801 pull

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

• [[2024-08-05 21:54:10+00:00]] @[[flaneur@merveilles.town]] (link):

  • @aynish ahoy there! I checked your digital garden (nice) and your git repos. Turns out that you use [[vimwiki]], I use [[wikivim]] - ha!

What are the similarities and differences between Agora and FedWiki?§

Moved to [[Comparing FedWiki and Agora]]. (because that’s a better name, and is the same name vera has used for her comparisons.)

Differences between agora and stoa ok o

Differences between agora and stoa ok o

Differences between agora and stoa ok o

Differences between agora and stoa ok o

Why have a personal wiki?§

I find writing too hard to want to spend it on things that disappear

– Martin Fowler (What is a Bliki)

At first my reasons were very similar to Nick’s reasons:

• writing my thoughts publically makes me write them a bit more carefully
• my thoughts are fuzzy and vague in my head, they become more real outside it (and may self desctruct in a cloud of stupidity)
• it provokes debate, which helps me refine the arguments: 1+n minds are better than 1
• I think I have something to say (we’ll find out right?)
• I get sad at the state of debate in the world
  • news and media normally tell gossipy stories about anything but the underlying topic
  • in-person debate usually veers dramatically off-course and debates a well-worn set of less interesting topics instead
  • blogs or "point-in-time" publishing systems don’t produce an always-up-to-date sof thoughts

I think my reasons have changed slightly over time - my wiki has become perhaps more a way for personal notetaking, for shaping my thoughts, with less emphasis on the debate straight away.

The social part is definitely important though because I want to learn through discussion. Don’t just want to be typing into the void, in dialectic only with myself. The [[stream]] is perhaps more for that - [[networked learning]], [[connectivism]].

But is that its own thing? I guess so. You could technically have an entirely private stream and garden, if you wanted. So making it public is more for the networked learning aspect?

Combined, the [[blog/wiki combo]] helps me think more about what I learn (through wiki-ing it) and learn more about what I think (through conversations on the stream), I’m really digging it.

I think we need to better foster that though in our [[social software]] - currently it feels optimised for aggro. If you say a wrong thing, make a mistake, you’re more likely to be piled on rather than helpfully educated.

I have found it has aided massively in helping me form ideas. I’ve built up enough mass to have gravitational pull for other ideas now. New articles I encounter, things people post, I feel like I’m in a good place to relate it to what I already have thought about.