Web form for submitting new sites about tiddlywikilinks HOT 5 OPEN

Thanks @saqimtiaz.

The problem here is how to remember between runs which rows have already been processed without checking temporary files into the repo.

The TiddlyWiki5 build scripts commit progressive changes to the jermolene.github.io repository (rather than as is normal completely overwriting the existing content). We may be able to use the same technique.

It's annoying that options are all so messy, particularly because I'd like to be able to make more of techniques like this. While we could write a little Lambda to do the necessary, I wonder if we might be better off using an off-the-shelf service that's tuned for this kind of thing:

https://zapier.com/apps/github/integrations/google-forms

from tiddlywikilinks.

It's annoying that options are all so messy, particularly because I'd like to be able to make more of techniques like this. While we could write a little Lambda to do the necessary, I wonder if we might be better off using an off-the-shelf service that's tuned for this kind of thing:

https://zapier.com/apps/github/integrations/google-forms

Yes that is worth considering. I saw the third party service options but was hoping to find a good alternative that avoided such a dependency. However none of the alternatives seem clean or robust enough as you have noted.

from tiddlywikilinks.

It occurred to me today that there is a way to resolve the security issue with option 3 above.

1. Create a new user account (machine account) and fork the TiddlyWikiLinks repository in that user account.
2. Have a Google Sheet script that has a PAT for the machine account, and does a POST request on every form submission to trigger a workflow for that fork creating a new branch with the submitted data incorporated. (The branch is created in the machine account's fork).
3. In the main TiddlyWiki links repository have a cron workflow that looks for new branches in the machine account fork that do not have corresponding PRs in the upstream repository, and creates PRs for them.

I tested the various parts briefly today and it seems the premise is sound.

from tiddlywikilinks.

Hi @saqimtiaz that sounds like it should work, very cunning.

from tiddlywikilinks.

Why not use a tiddlyhost with public access (I'm not sure if it can do this), and you can fetch the HTML and filter tiddlers from it...Just like how links site works.

The only requirement is a public editable tiddlyhost site.

from tiddlywikilinks.