@charlie : that's exactly what i thought, when i first read Mark's comment 
(GMTA :-)

@mark : thanks for explaining the two problem cases, and how Bob solves 
#2.  In this site i'm now playing with <https://valedalama.github.io/> -not 
a Bob instance, but with tiddlers as separate .tid files- Github handles 
both 1 and 2 via Git's built-in version control affordances... But as i am 
editing this site via TiddlyDesktop (which *is* a node.js server, if i 
understand it correctly -yes?), i must take care to save the updated 
index.html file to my desktop when edit is finished, and then manage the 
Git workflow from my (Atom) text editor, such that i pull any updates from 
Github server before i push my update(s -any tiddlers edited, plus 
index.html) back thru Git.  Bit of a PITA for me, but worth doing, if i 
ever manage to engage any collaborators about this -at which time, we'll 
need to implement that "gentlemen's agreement" about some tagging 
convention TBD.

On Sunday, January 31, 2021 at 4:25:37 PM UTC [email protected] wrote:

> I have no experience with multi-user TiddlyWiki, so please take with a 
> huge heap of salt ...
>
> Mark S. wrote: "You can solve problem #1 by having a gentlewomen's 
> (gentlemen's) agreement for assigning tiddlers. Like "All my tiddlers will 
> start with LUD" Bob solves problem #2 by automatically showing you changed 
> tiddlers on the server."
>
> I'm thinking that would be a good occasion to use tags (instead of adorned 
> tiddler titles) for "tiddler ownership and tiddler assignment".  I.E. if 
> you aren't the owner of the tiddler and aren't assigned the tiddler, then 
> (as per gentlemen's agreement) do not be monkeying around with that tiddler.
>
> So the advantage here of using tags instead of tiddler naming 
> conventions:  the tags make it so easy to "query" (via filters) "your" 
> tiddlers.
>
> *And* then you can do some fancy aggregating of various tiddlers into 
> some nice consolidated personal and team views.
>
> For example:  When putting together an "aggregate notes tiddler" for some 
> app, each teammate can create tiddler notes with "ownership tag" and "app 
> name tag", and the related "app aggregate notes tiddler" can transclude all 
> related notes via filtering of the relevant tags.
>
> Just a thought.  Possibly over-caffeinated ...
>
> On Sunday, January 31, 2021 at 11:23:03 AM UTC-4 Mark S. wrote:
>
>> If you're making a collaborative wiki then one must assume that you are 
>> using some form node.js TiddlyWiki. You can't really do collaboration with 
>> single-file TW except via federation, which is more of a concept than an 
>> actual thing. With node.js you have multiple tiddler files. They can all be 
>> on a shared resource like dropbox. Each person then would have their own 
>> node.js instance running. Or in an office, there could be one server that 
>> everyone connects to. There are two problems.
>>
>> 1. Someone else can write over your tiddler while you're writing
>> 2. You can't see someone else's changes without restarting the node server
>>
>> You can solve problem #1 by having a gentlewomen's (gentlemen's) 
>> agreement for assigning tiddlers. Like "All my tiddlers will start with 
>> LUD" Bob solves problem #2 by automatically showing you changed tiddlers on 
>> the server.
>>
>> Security on the net is hard. Companies get hacked every day. Putting a 
>> node.js instance directly on a public-facing internet server would probably 
>> be dangerous, even though node.js does have a facility for ssl 
>> certificates. VPN provides a more secure way for non-experts in security to 
>> share files over the net.
>>
>> On Sunday, January 31, 2021 at 2:17:50 AM UTC-8 ludwa6 wrote:
>>
>>> @tones , can you explain: Why only in VPN-Intranet mode? Is it (a) To 
>>> maintain integrity of InfoArchitecture (i.e. controlled vocabulary, 
>>> taxonomy, naming conventions, etc.), or (b) Because of system security 
>>> (i.e. risk of malicious hacking)... Or is it A+B both?
>>>
>>> From my limited tech understanding, i would guess both, since "it's 
>>> tiddlers all the way down"... But i think it's important to distinguish 
>>> between these two forms of risk, because there could be different ways of 
>>> handling each.
>>>
>>> I've had a good browse around the Bob repo 
>>> <https://github.com/OokTech/TW5-Bob/>, b/t/w, but must say: i'm not 
>>> really understanding what UseCase(s) it is designed to enable, and i've yet 
>>> to find any working examples of it online.  Would be most interested to 
>>> see, if anyone can point me to any... And if you have any demo of your 
>>> solution-in-dev to show, Tones, that might also be instructive.
>>>
>>> On Saturday, January 30, 2021 at 11:30:51 PM UTC TW Tones wrote:
>>>
>>>> Cedric,
>>>>
>>>> My simple answer to " Do you think that it can be an suitable tool for 
>>>> me? " is yes, but it important to realise the following key points;
>>>>
>>>>    - TiddlyWiki is a platform on which a suitable tool can be built 
>>>>    and evolved
>>>>    - True collaboration is only possible on top of Bob which is a Node 
>>>>    solution and thus may be a safe Intranet or LAN solution, but only an 
>>>>    internet solution with a VPN by users into you LAN (my opinion)
>>>>    - Jed is building more of the security and Internet facing features 
>>>>    with Bob but he needs more funding support
>>>>    - I have being working toward a simple serial editor method (Check 
>>>>    in / Out) which would be another way to collaborate but I have not had 
>>>> much 
>>>>    support and would need some funding as well, as I need to make a living.
>>>>
>>>> Regards
>>>> Tones
>>>> On Friday, 29 January 2021 at 20:41:09 UTC+11 [email protected] 
>>>> wrote:
>>>>
>>>>> Hi everybody.
>>>>>
>>>>> I am Cedric, a French Software developer and I start working in a very 
>>>>> small (4 people) team o software developers in a very small company.
>>>>>
>>>>> Unfortunately the knowledge is neither organized either shared between 
>>>>> people who yet work in the same room and I want to start documenting 
>>>>> projects and applications while managing updates and versions. 
>>>>>
>>>>> Knowing that we already have a Jira to manage our project but we 
>>>>> cannot afford for a team plan I was looking for a free open source 
>>>>> wikimedia like or a home made blog using Wagtail when I discovered 
>>>>> Tiddly. 
>>>>>
>>>>> Do you think that it can be an suitable tool for me?
>>>>>
>>>>> Best regards.
>>>>> Cedric J. 
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ae8b575d-20f4-4351-ab43-0a134d858202n%40googlegroups.com.

Reply via email to