Hey plugin authors! Where do you serve your plugins?

[Mat]

[Intentional double post from the TW group. Kindly answer in either.]

Where/how do plugin authors serve their plugins to the public?

As far as I can tell, it is:

Via a public wiki hosted on some server (tiddlyspot, private, github website)

Via github as "code" (visitors don't really "see" what the plugin does)

Do these to cover 99% of the cases or am I missing some common other option?

Yes, there is also the option to create your own plugin library that people can install to get access to your plugins but this is extremely uncommon. I believe only Jed and Tobias has done this, except for native TW of course.

Thank you.

<:-)

[PMario]

Hi Mat,

I did create an edition for every plugin, which can be reached from here:  https://wikilabs.github.io/

-m

[Mat]

OK thanks, so if I undestand, you publish via the first variant i.e

Via a public wiki hosted on some server (tiddlyspot, private, github website)

Do you know if there are any more alternatives than the ones I mention?

 

<:-)

[bimlas]

I think the first point covers most of the cases, but I can still imagine that you are storing JSON tiddlers in a shared Dropbox.

Otherwise, it would be best to have community plugins listed directly in the TW.com plugin library. If it had any categorization, it could completely replace the TiddlyWiki Toolmap.

[TonyM]

Bimlas

To replace TiddlyWiki tool map would require also curating tiddlywiki editions, learners documentation, hints and tips, macros and other paraphernalia.

Regards

Tony

[Mat]

TonyM wrote:

To replace TiddlyWiki tool map would require also curating tiddlywiki editions, learners documentation, hints and tips, macros and other paraphernalia.

So does keeping it.

Even if the gentleman running it does it very well, these types of projects should not be a one man job but a community effort. It inevitably decays otherwise because as new items are added it gets more difficult to maintain. And the mere progression of time makes things outdate automatically. This is a prime example of why we need a federated system.

<:-)