Lmst

Ward comments on a recent #FedWiki issue, after the CoffeeScript conversion has been completed.

Removing the #jQuery dependency is the next target.

https://github.com/fedwiki/wiki-server/issues/205#issuecomment-3863523455

Ward Cunningham wrote 2 days ago:

I am in favor of simplifying our core javascript. I see no point in making lots of changes unless we have established a new direction. Since we have now completed a two year conversion away from CoffeeScript, I feel jQuery should be our next target. Simpler is our new direction.

Version 1.0.1 of wiki-plugin-wmap released thanks to valuable feedback from the fedwiki community!

https://www.npmjs.com/package/wiki-plugin-wmap

Fixes a race condition in the zoom action, an instance of malformed HTML, increases CSS compatibility with older browsers, and adjusts thumbnail rendering to be *slightly* more readable.

#fedwiki

Here’s one more plugin for #fedwiki before christmas!

wiki-security-oidc allows you to sign in and claim a wiki using Open ID Connect (eg. Pocket ID, Authelia, Keycloak)

https://www.npmjs.com/package/wiki-security-oidc

wiki-plugin-wmap is now available!

A plugin for federated wiki that allows you to render wardley maps from wmap syntax.

You can check it out here: https://www.npmjs.com/package/wiki-plugin-wmap

* example:: https://wiki.r.bdr.sh/view/welcome-visitors/view/about-wmap-plugin
* fedwiki: http://fed.wiki.org/view/welcome-visitors
* wmap syntax: https://map.tranquil.systems/wmap-language/

#wiki #fedwiki #wardleymapping #wardleymaps

A screenshot of a page from a federated wiki. The title reads “About Wmap Plugin”. The first paragraph reads: “This plugin renders wardley maps formatted in the wmap language using wmap-parser-js and wmap-renderer-canvas”.

Below that, an image shows a small rendered image of a wardley map, with the text not legible due to its size.

Pretty happy to reach this point for the wmap #fedwiki plugin.

It took a while to understand the plugin format, but I think wiki-plugin-markdown and wiki-plugin-graphviz werevery helpful.

I'll have to go through my code again and simplify, as I included a lot of things I didn't actually understand.

#wardleymapping #wardleymaps #wiki

A screenshot of a page from a fedwiki. The title reads “About Wmap Plugin”. The first paragraph reads: “This plugin renders wardley maps formatted in the wmap language using wmap-parser-js and wmap-renderer-canvas”.

Below that, an image shows a small rendered image of a wardley map, with the text not legible due to its size.

Change is coming.

https://github.com/fedwiki/wiki/pull/151#issuecomment-3611465255

#FedWiki

#FedWiki sitemap scrape statistics

http://ward.asia.wiki.org/assets/pages/sitemap-scrape-statistics/counts.html

Two graphs, one above the other.

First: scan pages.

The x axis shows the years from 2016 throughout now.

The y axis shows 50k and 100k markers.

The plotted graph begins around 37k and grows steadily until end of 2024 by a good 100k pages. A spike shows that scanning the federation was off for a while and only came back when another few tens of thousands of pages had been added within only a few months.

Second: index sites.

The x axis is the same.

The y axis begins around 850 and has ticks at 1000, 1500, 2000, 2500 and 3000.

The plotted graph grows steadily towards 3200 until now.

@feb Witzig. Wieder eine Geschichte föderierter Netzwerke, in welcher das Verbundwiki #FedWiki nicht auftaucht. Herrlich so über Jahre unter dem Radar zu fliegen …

Das förderierte Wiki ist ein bisschen anders.

ja hat so erstmal kein ssl-zertifikat. erstmal ignorieren.

http://fed.wiki.org/view/welcome-visitors/view/about-federated-wiki

#Förderation #Wiki #FedWiki

@sarahjamielewis Boosting your nodes and edges graph editing question for the #fedwiki crew who have a significant interest in graph presentation and transformation.

@rosano Why I meant that your idea of generalising lenses maps very well on the whole domain of data processing, and why I mentioned (serverless) functions, which can fulfill this task, is:

We once understood that #fedwiki transporters can be considered as functions, the basic Input-Process-Output pattern.

- https://github.com/fedwiki/wiki-plugin-transport
- https://github.com/dobbs/image-transporter
- https://github.com/WardCunningham/image-transporter

My deployment of an image transporter is currently down, but the idea sticks, here: always produce wiki JSON.

@mspro Es gibt andere Arten der Föderation und des Digitalen Föderalismus.

Im Verbundwiki #fedwiki finde ich Qualitäten die es an keinem anderen Ort im Internet gibt.

Ob es wohl daran liegt, dass es eine Gemeinschaft von stillen Schreiberlingen ist, die indirekt Inhalte teilen, und nicht eine Gemeinschaft aus Leuten im Speakers Corner, die alle um eine flüchtige, im Feed verschwindende Aufmerksamkeit ringen?

Immer den ganzen Feed abzuscrollen kostet ganz schön Zeit, um allen gleich zuzuhören.

@naturzukunft @evan When looking into #fedwiki:matrix.org, I find this post from last year by @k9ox

And there is:

* https://ibis.wiki/article/Announcing_Ibis,_the_federated_Wikipedia_Alternative
* https://github.com/Nutomic/ibis

Screenshot of https://matrix.to/#/!ORfrUEFeWFcHAMLFLr:matrix.org/$169103785953081MIWFo:matrix.org?via=matrix.org&via=matrix.allmende.io&via=tchncs.de :

In our call this morning some interest was expressed in feeding wiki content into Mastodon or other implementations federated with the ActivityPub protocol. I've now skimmed the specification which describes a client-server protocol, probably not of interest, and a server-to-server protocol which might have some utility. I can imagine an implementation as a server-side plugin supporting server-to-server requests similar to our existing Datalog and RSS plugins which make and answer requests respectively. I suspect we would find the "outbox" behavior most useful because it is consistent with our "pull only" discipline. I would imagine that a Mastodon user could follow a participating wiki site and would receive posts when pages were completed. I don't see how we could accept replies so any conversation that ensued would be between mastodon users. The spec does discuss a "ghost message" problem where a third party doesn't see replies so this might be a serious limitation to federated wiki's participation in the fediverse.

I encourage others to read through this specification. I would be happy to join a small group who do and would like to draft a document describing more carefully what value wiki's participation would bring and how this might be realized. https://www.w3.org/TR/activitypub/

@tk Ouuaiisss, ca existe encore et ca bouge. Suit le chez @k9ox et visite nous à #fedwiki:matrix.org

@bob As an addition, because @bhaugen's post below resurfaced in the #fedwiki chat:

Using Google identity was never a Valley assumption. It was useful and helped onboarding.

@k9ox regularly comments on how Google is making life worse for many, e.g. by imposing HTTPS on the web or making their identity ubiquitous.

Wiki also supports GitHub login, next to OAuth2 and the friends module.

* https://github.com/fedwiki/wiki-security-passportjs
* https://github.com/fedwiki/wiki-security-friends

I can show you examples, or help with setup if you like.

@trondhjort @marick @newcrafts @kentbeck I'm just wondering if we could use Ward's Federated Wiki for this: possibly writing this book together? #FedWiki #FederatedWiki @k9ox

We have some experience with supporting collective writing of books.

@marick @rgb There is also a Matrix chat channel with most of the FedWiki regulars. #fedwiki:matrix.org

@rgb @SReyCoyrehourcq @k9ox What #FedWiki would need (in my opinion!) to unfold its full potential is an educational platform that helps other communities to adopt it. But that would have to be an interactive process, rather than "dead" documentation. More like a Linux install party than like Linux documentation.

@rgb @SReyCoyrehourcq @k9ox When I started realizing this, it felt frustrating. It's not how we deal with software elsewhere. Software,is seen as a product with producers, consumers, documentation, etc.

#FedWiki feels more like "situated software", i.e. software built and evolved by its users following their needs. And that's how I think user-facing software *should* work. Tools adapt to communities, not the other way round.

@SReyCoyrehourcq @rgb @toxi As far as I can see, #fedwiki is not so much a piece of software as a community. The code is there in the open, but without the community it's not easy to figure out how to use it, in particular use if effectively.

#FedWiki

Client Info