interstar
commented
1 month ago Thanks Offray.
This is very interesting. Certainly a combination of TiddlyWiki front-end and Pharo back-end sounds awesome.
I'll create a page on ThoughtStorms about your stuff very soon, as I definitely want to record and track what you are doing.
As to the question of comments / feedback on ThoughtStorms, I agree, I seriously need to find a solution for it. Unfortunately that Hypothes.is comment doesn't seem to work. (Or at least the link looks broken to me here. Do you want to send me the comments you wrote there so I can add them to ThoughtStorms?)
The problem is that I decided that Cardigan Bay is a tool which publishes wikis (including ThoughtStorms) by exporting static pages. The ideal is that you don't need any server-side support for the published version. It's plain HTML/CSS/JS.
Unfortunately that precludes comments / discussion or other ways for readers to update what's on the server.
Having been thinking about this for a while, I'm currently inclined to use a third-party discussion server or social media forum for feedback. Probably Mastodon as it's both open-source and federated. Possibly this will look like a "comment on this page on Mastodon" link on every page. Or some kind of Mastodon embedding. Even some automated copying between Mastodon and Cardigan Bay. I've got to see what's possible with the API.
Further into the future I'm starting to wonder if I do need a third kind of thing : an optional server-side application that could handle feedback comments and some other housekeeping. In this scenario, you'd still be able to export static sites, but could also integrate with server-side functionality.
cheers
Phil
On Mon, 19 Aug 2024 at 01:59, Offray Vladimir Luna Cárdenas < @.***> wrote:
Hi,
As a previous reader, I'm happy to see this new iteration of your wiki that I stumble upon while revisiting SmalltalkNeedsANewUI https://thoughtstorms.info/view/SmalltalkNeedsANewUI. I was looking for a place to do comments on your Wiki/Bliki but found no want, so I will use this place to ask for them, as a feature request or a more explicit feature in case is already included. Also, I will make some comments here or via hypothesis, while we have the feature.
I have similar explorations to the ones present in ThoughtStorms, in what I call now "interpersonal wikis" which, in contrast with Small Federated Wikis are more related with the sociotechnical aspects of wikis, knowledge and communities and use TiddlyWiki as a front end, Pharo/GT Smalltalk as a middlewere and Fossil SCM as a backend. Well, they expand in both axes, in the sense that they provide UI, logic and storage, for different intended audiences, as shown here:
The software that bride everything together is TiddlyWikiPharo https://code.sustrato.red/Offray/TiddlyWikiPharo/ and I use the Lepiter/GT notebook interface to develop it.
[image: Documentation for the prototyping the Malleable Systems Wiki] https://camo.githubusercontent.com/05fdaea6a18be71d9473623b8002809ed1a26b664a2adc5fce7cc70de84c36f0/68747470733a2f2f692e696d6775722e636f6d2f4d474a7846437a2e706e67
My approach is to use "interstitial programming" trying to extend the sociotechnical systems from the frontiers connecting them, instead of from inside them. I think it has been an approach that has payoff at keeping incidental complexity at bay and Pharo/Lepiter have been important bridge building metatools in that sense, with TiddlyWikiPharo is one of the use cases among many projects https://offray.tiddlyhost.com/#Portfolio powered by such approach.
I made more specific comments on the notebook GUI for Smalltalk, using Hypothesis https://hyp.is/go?url=https%3A%2F%2Fthoughtstorms.info%2Fview%2FSmalltalkNeedsANewUI&group=__world__ .
Let me know which one works better to keep the conversation going and thanks for your wiki. It provided me of a thoughtful Sunday reading afternoon.
— Reply to this email directly, view it on GitHub https://github.com/interstar/cardigan-bay/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAWG5S6XK6V565FSKFCNW3ZSEYPXAVCNFSM6AAAAABMWZFKMOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TEMRQGU4DCNY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
offray
Hi,
As a previous reader, I'm happy to see this new iteration of your wiki, that I stumble upon while revisiting SmalltalkNeedsANewUI today. I was looking for a place to do comments on your Wiki/Bliki but found no way, so I will use this place to ask for them, as a feature request or a more explicit feature in case is already included. Also, I will make some comments here or via hypothesis, while we have the feature.
I have similar explorations to the ones present in ThoughtStorms, in what I call now "interpersonal wikis" which, in contrast with Small Federated Wikis are more related with the sociotechnical aspects of wikis, knowledge and communities and use TiddlyWiki as a front end, Pharo/GT Smalltalk as a middlewere and Fossil SCM as a backend. Well, they expand in both axes, in the sense that they provide UI, logic and storage, for different intended audiences, as shown here:
The software that bride everything together is TiddlyWikiPharo and I use the Lepiter/GT notebook interface to develop it.
My approach is to use "interstitial programming" trying to extend the sociotechnical systems from the frontiers connecting them, instead of from inside them. I think it has been an approach that has payoff at keeping incidental complexity at bay and Pharo/Lepiter have been important bridge building metatools in that sense, with TiddlyWikiPharo is one of the use cases among many projects powered by such approach.
I made more specific comments on the notebook GUI for Smalltalk, using Hypothesis.
Let me know which one works better to keep the conversation going and thanks for your wiki. It provided me of a thoughtful Sunday reading afternoon.