Still maintained and still used. Glad to see new faces using the plugin.
--
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 tiddlywiki+unsubscr...@googlegroups.com.
T
I wanted to add that the Challenge Digest Authentication relies on Sessions
and cookies. I don't mention it in the readme, but if for some reason your
system had cookies disabled, it could cause an auth problem.
If that could be the case, the feature can be disabled in the wiki tab and
on line
t_max_size* must be at least larger
> than your wiki filesize
> - On NGINX client_max_body_size is another parameter worth looking at if
> uploads fail with *413 Request Entity Too Large*
>
> On Fri, Nov 16, 2018 at 8:16 AM sendwheel > wrote:
>
>> Great.
>>
ning into authentication errors when I try to save. Going to try again
> on a fresh empty wiki just to be sure I don't have anything hidden in there.
>
> On Fri, Nov 16, 2018 at 6:09 AM sendwheel > wrote:
>
>> Hey Scott, you're not wrong.
>> I just restored it, so yo
Hey Scott, you're not wrong.
I just restored it, so you should be able to find it on the github page now.
Let me know if you run into any troubles.
On Friday, November 16, 2018 at 1:16:19 AM UTC-5, Scott Kingery wrote:
>
> I was just checking this out. The Read Me makes reference to
> importing
n see about fixing it, maybe copying the content and
refreshing.
Not revolutionary, but something that's certainly needed in place of a file
lock.
On Sunday, September 30, 2018 at 1:04:35 AM UTC-4, TonyM wrote:
>
> Sendwheel,
>
> That sounds great but how does it handle conten
Added a new feature to the plugin:
*Stale Instance Overwrite Protection*
- This ensures the wiki you're working on isn't out of date with the server
before saving changes.
- It avoids a scenario where changes made earlier in another window were
not loaded into the current instance of the wiki an
Hi Tony, you should number your questions for easier reply
1. The plugin doesn't use plain passwords, and instead uses hashed one-time
use tokens that are based on the secret. So the secret is never passed out
in the open.
That said it should still use HTTPS, but the plugin has no control over
ng in transit.
The plugin and the backend are GPL license.
Project page here:
https://github.com/sendwheel/tw-receiver
On Sunday, December 18, 2016 at 10:01:33 PM UTC-5, Mark S. wrote:
>
> Any response back? It's one of the primary ways to run TW on the net. It
> would be nice if i
That's great. I'll look into that password saving w/ LastPass and others.
See if I can't straighten it out.
On Thursday, September 6, 2018 at 12:28:50 AM UTC-4, TonyM wrote:
>
> Sendwheel,
>
> Thanks that is working and working well. It is very exciting for me and I
n't have any bad edits.
and thank you for this feedback, I'll make some adjustments to the readme
and look at minimum php version requirements.
On Wednesday, September 5, 2018 at 10:49:05 PM UTC-4, TonyM wrote:
>
> Thanks Sendwheel,
>
> I possibly have enough knowledg
ly want to avoid letting the wiki push any kind of php code
payload.
On Wednesday, September 5, 2018 at 9:05:44 PM UTC-4, TonyM wrote:
>
> sendwheel,
>
> Thanks so much for this, I will test it in haste as I have a large online
> hosting environment based on PHP which has being
Super. Thanks. Hopefully this plugin will get some adoption.
On Wednesday, September 5, 2018 at 6:02:52 PM UTC-4, David Gifford wrote:
>
> I added this to the toolmap (
> https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM#z=3wGygvpg5j7GS-bK4HIkF_DT)
> under the section "Publishing and hosting TiddlyW
help squash environment/server problems
Project page here:
https://github.com/sendwheel/tw-receiver
Comments and contributions welcome.
Security wise offers:
- Challenge Digest Authentication (enhanced security)
-- This simple mechanism avoids passing the password in plain text.
Instead the
14 matches
Mail list logo
