Re: [tw5] PHP 5.6 EOL on December 31, what does this mean for the PHP saver?

2018-11-08 Thread Sven Wetzel 
Tony,

first: the draft of this copyright proposal speaks about websites that
offer user content upload.

And you are a user of your own site!

So you need an upload filter to monitor your own behavior!

But they can be exceptions for some sites/companies...

At this time nobody can exactly answer you this! Because first it need to
be made as law and then it need to be made as active law in the national
states.

After that - I read somewhere in the middle of 2019 - this can be answered
by a lawyer.

kind regards
quaraman

Am Do., 8. Nov. 2018, 16:10 hat TonyM 
geschrieben:

> Quaraman,
>
> Lets see if I can remove the riddle.
>
> If I build a website for me, online but behind a passphrase and on PHP and
> store personal information and media on it, the only user is me, I will not
> be taking me to task, and if my partner or trusted colleague also has
> access I would not be too worried. Once I have developed a good solution I
> may translate this into a secure website, build the code into a WordPress
> site. I understand the obligations and privacy issues but their are plenty
> of applications and cases where such simply do not exist. Personally I
> produce a lot of my own, original content that I produce myself for
> consumption only by me, it does not include copy write material, or
> collecting information from people but may hold a repository of Open source
> material for me.
>
> PHP services are now available from cloud providers so I can scale and
> prototype to my content.
>
> I understand where you are coming from but are surprised you cant imagine
> a genuine use for this that does not present unacceptable security risks.
> By the way, I appreciate you reminding me of these issues, but I am not so
> concerned at this time with these, even considering to only place anything
> online I cant loose.
>
> To be honest amongst my many roles in IT I also have a background in
> Security which I maintain an interest in.
>
> One example is a NoteSelf TiddlyWiki of my own from which I can export
> changes as a form of backup, or generate json files that exist in another
> folder with different security rights. I may even host a php server on
> local host.
>
> I hope that explains
>
> Now, I wonder if it is easy to get traditional html/php post to work
> within tiddlywiki. My original Question
>
> Thanks and Regards
> Tony
>
>
>
> On Friday, November 9, 2018 at 12:35:33 AM UTC+11, Sven Wetzel wrote:
>>
>> Hi Tony,
>>
>> without prooving against user failure it is very easy. But that is risky
>> as explained before.
>>
>> from tiddlywiki perspective it could be a html form that you present with
>> a submit button that trigger the php script.
>>
>> the php script then read the data it gets.
>>
>> That this function the tiddlywiki and the php script need to be served
>> from the same domain.
>>
>> But from your description it is a riddle for me how that you want.
>>
>> and when for example you are in the eu and the new eu copyright reform is
>> active this is illegal to use without a proove against copyright cases!
>>
>> kind regards
>> quaraman
>>
>> Am Do., 8. Nov. 2018, 07:24 hat TonyM  geschrieben:
>>
>>> Quaraman,
>>>
>>> Not withstanding your concerns, I still see value in being able to read
>>> and write using PHP independently of TiddlyWikis save steps. Remember such
>>> a website can be restricted to a single user with SSL and multiple levels
>>> of authentication, then all that would be permitted it to write to a
>>> particular filename, perhaps even one only the server can see. We could use
>>> the security method in https://github.com/sendwheel/tw-receiver which
>>> stops update access unless you have a long password/phrase set.
>>>
>>> I am not asking for a PHP lesson, only some insight as to how easy and
>>> or versatile this would be, and how you may invoke PHP from inside a
>>> TiddlyWiki. If accessible I will go to the effort of learning more about
>>> PHP.
>>>
>>> Thanks in advance
>>> Tony
>>>
>>>
>>>
>>> On Tuesday, 30 October 2018 23:27:02 UTC+11, Sven Wetzel wrote:
>>>>
>>>> Hi Tony,
>>>>
>>>> this is to unspecific to answer the questions.
>>>>
>>>> What is your concrete case?
>>>>
>>>> This type of extension is easy to program - only to save a file. But as
>>>> I described earlier : the difficult part is to decide how to handle the
>>>> rights and/or the security and/or your need to proove against such things
>&g

Re: [tw5] PHP 5.6 EOL on December 31, what does this mean for the PHP saver?

2018-11-08 Thread Sven Wetzel 
Hi Mark,

the Eu is looking after youtube and other big player.

But how that is affecting a small site is something we only see then the
law is out next year.

And who defines what a small site in the context of this law is?

Welcome in #neuland where politicians see that something like internet
exist!

Who is under this law? Everyone that want to have users living in the Eu!

kind regards
quaraman

Am Do., 8. Nov. 2018, 16:27 hat 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> geschrieben:

> Is the EU looking at small sites that narrowly?
>
> Where is tiddlyspot.com located? (All the whois info is redacted). Does
> tiddlyspot have to follow these rules?
>
> -- Mark
>
> On Thursday, November 8, 2018 at 5:35:33 AM UTC-8, Sven Wetzel wrote:
>>
>>
>> --
> 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.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/a9028e6c-3764-48fa-81af-f9f100757253%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/a9028e6c-3764-48fa-81af-f9f100757253%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CABLiyj%3DWc0yvYZK-fZXnzOaJM2h%3DXmWW3MTB6PA%2BwUQ-Eg3kFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] PHP 5.6 EOL on December 31, what does this mean for the PHP saver?

2018-11-08 Thread Sven Wetzel 
Hi Tony,

without prooving against user failure it is very easy. But that is risky as
explained before.

from tiddlywiki perspective it could be a html form that you present with a
submit button that trigger the php script.

the php script then read the data it gets.

That this function the tiddlywiki and the php script need to be served from
the same domain.

But from your description it is a riddle for me how that you want.

and when for example you are in the eu and the new eu copyright reform is
active this is illegal to use without a proove against copyright cases!

kind regards
quaraman

Am Do., 8. Nov. 2018, 07:24 hat TonyM 
geschrieben:

> Quaraman,
>
> Not withstanding your concerns, I still see value in being able to read
> and write using PHP independently of TiddlyWikis save steps. Remember such
> a website can be restricted to a single user with SSL and multiple levels
> of authentication, then all that would be permitted it to write to a
> particular filename, perhaps even one only the server can see. We could use
> the security method in https://github.com/sendwheel/tw-receiver which
> stops update access unless you have a long password/phrase set.
>
> I am not asking for a PHP lesson, only some insight as to how easy and or
> versatile this would be, and how you may invoke PHP from inside a
> TiddlyWiki. If accessible I will go to the effort of learning more about
> PHP.
>
> Thanks in advance
> Tony
>
>
>
> On Tuesday, 30 October 2018 23:27:02 UTC+11, Sven Wetzel wrote:
>>
>> Hi Tony,
>>
>> this is to unspecific to answer the questions.
>>
>> What is your concrete case?
>>
>> This type of extension is easy to program - only to save a file. But as I
>> described earlier : the difficult part is to decide how to handle the
>> rights and/or the security and/or your need to proove against such things
>> as illegal data (malware/copyrighted material/files that are only for
>> adults...)
>>
>> Regards,
>> quaraman
>>
>>
>> TonyM  schrieb am Di., 30. Okt. 2018, 10:15:
>>
>>> Sven,
>>>
>>> If the functions exposed were limited like can only save to a specific
>>> filename etc could we make it safer?
>>>
>>> If however this wiki would be behind a password and only trusted users
>>> had access, how far could we take this and would it be difficult?.
>>>
>>> I would appreciate your advice.
>>>
>>> Regards
>>> Tony
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To post to this group, send email to tiddl...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/tiddlywiki.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/fc7ac71f-df91-4096-b74b-bd42ec56727e%40googlegroups.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/51ea6c79-ea1a-48cb-9261-24d88dc9f77c%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/51ea6c79-ea1a-48cb-9261-24d88dc9f77c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CABLiyjm2k0ivJgPjnjXdfSGLAhj8GeKFdABJ%3D_r9HUg02GXTuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] PHP 5.6 EOL on December 31, what does this mean for the PHP saver?

2018-10-30 Thread Sven Wetzel 
Hi Tony,

this is to unspecific to answer the questions.

What is your concrete case?

This type of extension is easy to program - only to save a file. But as I
described earlier : the difficult part is to decide how to handle the
rights and/or the security and/or your need to proove against such things
as illegal data (malware/copyrighted material/files that are only for
adults...)

Regards,
quaraman


TonyM  schrieb am Di., 30. Okt. 2018, 10:15:

> Sven,
>
> If the functions exposed were limited like can only save to a specific
> filename etc could we make it safer?
>
> If however this wiki would be behind a password and only trusted users had
> access, how far could we take this and would it be difficult?.
>
> I would appreciate your advice.
>
> Regards
> Tony
>
> --
> 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.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/fc7ac71f-df91-4096-b74b-bd42ec56727e%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CABLiyjktgvSKpQU%2BjB8B%2BYyUkw9kX2K9Y8saiarLYgMD%2BXY5Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] PHP 5.6 EOL on December 31, what does this mean for the PHP saver?

2018-10-30 Thread Sven Wetzel 
Hi TonyM,

it depends what you mean with writing files. The act to do this is easy.
But to make it save against attacks can be harder.

For example: If the php script has a failure in the checking who can upload
and what is allowed to be saved on the server, you allow attackers to
upload potential illegal/harmful files to your homepage space.

Kind regards
quaraman

TonyM  schrieb am Di., 30. Okt. 2018, 03:10:

> Lost Admin,
>
> Sven's solution sounds great, I am currently using another php solution, I
> should add to your choices https://github.com/sendwheel/tw-receiver
>
>
> Sven,
>
> Thanks for sharing, I will have to check out your updated store php. You
> may like to review https://github.com/sendwheel/tw-receiver as no doubt
> has possible techniques for you.
>
> By the way given you skills in this area, how hard would it be for us to
> use http or php to to read or write files on a php host. Id love to allow
> json files to be exported to the host for others to import and other types
> of interaction..
>
> Regards
> Tony
>
>
> On Tuesday, October 30, 2018 at 1:48:39 AM UTC+11, Sven Wetzel wrote:
>>
>> Hi Lost Admin,
>>
>> you can use my version from : https://quaraman.de/tw/storephp.html .
>>
>> This version works under php 7 and can be used with https!
>>
>> So that should be no problem with the eol of php 5.6 .
>>
>> Kind regards
>> quaraman
>>
>> Lost Admin  schrieb am Mo., 29. Okt. 2018, 14:27:
>>
>>> Hi all,
>>>
>>> I saw this in the tech news today:
>>>
>>>
>>> https://www.zdnet.com/article/around-62-of-all-internet-sites-will-run-an-unsupported-php-version-in-10-weeks/
>>>
>>> When I first started with TiddlyWiki I used the store.php (Tobias Beer
>>> has a link http://tobibeer.github.io/tb5/#store.php). It wouldn't work
>>> with PHP 7 and required PHP 5. It appears at least one of us has updated it
>>> to run on PHP7 (
>>> https://groups.google.com/d/msg/tiddlywiki/72FpRZLyFMY/m_O6HQgNCAAJ).
>>>
>>> I wonder how many of us that still use it need to make updates or
>>> otherwise don't care about running unsupported PHP?
>>>
>>> I've moved everything to WebDAV (
>>> http://thelostadmin.tiddlyspot.com/#Apache%20HTTPD%20with%20WebDAV).
>>>
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To post to this group, send email to tiddl...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/tiddlywiki.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/85cd97e8-6f38-43c5-bd02-de337978a25e%40googlegroups.com
>>> <https://groups.google.com/d/msgid/tiddlywiki/85cd97e8-6f38-43c5-bd02-de337978a25e%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/c1da3bc4-ff03-423c-966b-5bbaae2e816d%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/c1da3bc4-ff03-423c-966b-5bbaae2e816d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CABLiyj%3DaLSZuhoRYRiSegkpAa1sxWa7XY4REBiQ2XUZ8PiwO0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] PHP 5.6 EOL on December 31, what does this mean for the PHP saver?

2018-10-29 Thread Sven Wetzel 
Hi Lost Admin,

you can use my version from : https://quaraman.de/tw/storephp.html .

This version works under php 7 and can be used with https!

So that should be no problem with the eol of php 5.6 .

Kind regards
quaraman

Lost Admin  schrieb am Mo., 29. Okt. 2018, 14:27:

> Hi all,
>
> I saw this in the tech news today:
>
>
> https://www.zdnet.com/article/around-62-of-all-internet-sites-will-run-an-unsupported-php-version-in-10-weeks/
>
> When I first started with TiddlyWiki I used the store.php (Tobias Beer has
> a link http://tobibeer.github.io/tb5/#store.php). It wouldn't work with
> PHP 7 and required PHP 5. It appears at least one of us has updated it to
> run on PHP7 (
> https://groups.google.com/d/msg/tiddlywiki/72FpRZLyFMY/m_O6HQgNCAAJ).
>
> I wonder how many of us that still use it need to make updates or
> otherwise don't care about running unsupported PHP?
>
> I've moved everything to WebDAV (
> http://thelostadmin.tiddlyspot.com/#Apache%20HTTPD%20with%20WebDAV).
>
>
> --
> 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.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/85cd97e8-6f38-43c5-bd02-de337978a25e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CABLiyjnr_m7nv3v6Yn2jyx4y99S7NHek3R%3DAgW4u-w_FnyTVjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Like TiddlySpot but using https.

2017-03-22 Thread Sven Wetzel 

Hi Lost Admin,

when I understood it right, the webdav protocol gives the control of 
user rights to the file system that is used to host the files.


Am 20.03.2017 um 16:59 schrieb Lost Admin:

*Status Update on my https project*

Hopefully I'm not wasting people's time with this post.

Instead of spending the weekend making modifications to store.php (to 
support a more secure password file) and some behind the scenes 
re-configuring of the web server, I decided to have another look at 
Jeremy's suggestion of using WebDAV for saving.


My initial plan with the VM was to set-up OwnCloud (and hosting my own 
tiddlywiki was incidental to that). I abandoned that plan because of 
the memory requirements of OwnCloud (I wasn't willing to pay for a VM 
with enough RAM). However, just implemeting the WebDAV module of 
Lighttpd is a different story.


So, I spent a chunk of the weekend re-building my set-up to do that. 
It works pretty well. Unfortunately it leads to some security issues 
I'm not ready to deal with in a multi-user environment. There is no 
built-in way (that I found) to limit the files that could be uploaded 
(I found some ways to limit per-file size but not per-user size, file 
names, or file types). This opens up a problem where it is far too 
easy for a malicious user to host nasty things if they find it. It 
also added a lot of complexity in setting-up individual repositories 
with the features I want. I may re-visit WebDAV in the future as I 
think these things are resolvable, just not in a weekend (at least not 
by me).


I did manage to swap out password management in store.php such that 
the back-end file now uses the same file format as Apache digest 
authentication (which is also used by Lighttpd). This doesn't involve 
changes to TiddlyWiki, so it is still transmitting the password in 
clear between the browser and the server. Only the back-end no longer 
stores passwords in clear text. Unfortunately, the WebDAV experiments 
left the web server all messed up and I didn't have time to clean 
things up to be usable.


I do think that long-term WebDAV is still the way I want to go. I just 
need to figure out how to introduce appropriate logic to better 
control and separate users.

--
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 
.
To post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ed536378-0f4f-4120-b0d9-a69898907e33%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2f4ef979-e2cc-5c45-41a0-e38353065e7f%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] how to use javascript in TW5

2017-03-21 Thread Sven Wetzel 

Hello Dave,

I think you must create a widget, that creates a button with the click 
event listener on it.


Or if you want it as macro you can try this with my SPilot4TW 
(https://www.quaraman.de/tw/pilot.html):


|\define myfunctionbutton(text:"hello world!")||

||LOOP:||
||PAUSE: Try it||
||CLS:||
||T: $text$||
||ENDLOOP:||

||\end|

|
Later in the tiddler: <>
|

This wait till the user presses the "Try it" button and then prints the 
text.


It is using another language as Javascript, but you can do this in a 
normal Tiddler without creating a plugin yourself.


Am 21.03.2017 um 22:51 schrieb Dave:
Is  a tutorial somewhere that would teach me how to take this 
javascript code


|




Click the button to convert the string to lowercase letters.

Re: [tw] Like TiddlySpot but using https.

2017-03-15 Thread Sven Wetzel 

Hi Lost Admin,

do you looked over to my plugin/storephp? 
https://quaraman.de/tw/storephp.html it can be used to have it run under 
ssl.


Am 15.03.2017 um 01:17 schrieb Lost Admin:

Hi all,

I'm working on a place to store tiddlywikis on the web similar to 
tiddlyspot.com except mine is going to use the https transport layer.


I've got a bare minimum setup (think early alpha or proof of concept).

Anyhow, I'm not really announcing it at this time, I've got a question.

The default when you save online is tiddlyspot.com (for obvious 
reasons). And for (hopefully equally obvious reasons), I would like to 
have the initial empty template I provide during setup to default to 
my site. I think I can modify the core enough to do that by editing 3 
system tiddlers:


$:/languate/ControlPanel/Saving/TiddlySpot/Hint
$:/language/ControlPanel/Saving/TiddlySpot/Description
$:/core/modules/savers/upload.js

Is there an easier way? Maybe a single tiddler that defines the default?


You won't have to use my template with my site. Just like tiddlyspot, 
you can use whatever starting point you want. I'm only planning on 
putting an initial empty wiki there for ease of use.


It will be https only. If you try http, it will redirect you to the 
https site (this already works).


For SSL certificate reasons it will be 
https://wiki../(/index.html)


I don't want to compete with TiddlySpot, I just want TLS and if I'm 
going to the trouble of making it for myself, I may as well let 
everyone play.

--
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 
.
To post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/cfbe4e4c-d487-40a8-9dbe-072436df3440%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b1aa246c-22ef-42b4-006b-50e6b7d05632%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Introducing SPilot4Tw a programming language developed for use in TW5

2017-03-14 Thread Sven Wetzel 

Hello all,

I have created a programming language for use in TiddlyWiki as plugin.

The plugin and its documentation can be found here: 
https://www.quaraman.de/tw/pilot.html .


Because I use it on a daily basis, I can say it is stable.

I have posted it on TiddlyWikiDev earlier - because I do not know which 
group is better to name new plugins.


It is hopefully easy to use.

The language is useful in many area:

* dynamically manipulate the wiki
* have dialogs that are easy to create
** the results of the dialogs are easy to be used for further work
* it can be used to have a basic leitner flashcard test (one box instead 
the traditional 5 box system)


Is it for anyone else interesting or only for me?

--
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2f1a822b-71e5-9c4f-9310-c2580c51f5fa%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: store.php for websites

2017-03-13 Thread Sven Wetzel 

Hello Lost Admin,

I have another changed version: https://quaraman.de/tw/storephp.html .
I made it because the original version does not function well with https 
websites.



Am 13.03.2017 um 20:24 schrieb Lost Admin:


On Monday, March 13, 2017 at 1:16:37 PM UTC-4, Lost Admin wrote:

A while back I ran across the store.php script (or a version of
it). I can't find where I dug it up now and don't know if I even
have the latest version.

Is there an official maintainer? Is there an official site or
repository?


Answering my own question, it looks to me like the official source is 
on github: https://github.com/makefu/tiddly_store


And hasn't been touched in 2 years. Guess I'll figure out how to use 
github. :)


I'm asking because I made a minor change that I thought might be
useful to some people. Specifically, I've added the ability to
have per-user directories sections the the ini file. Thus, you can
have...

|
[users]
user1=password_for_user_one
user2=password-for-user-two

[directories]
;thisdefines the defaults ifa user does nothave his/her own section
savedir=./default/wiki/save/dir
backupdir=./default/wiki/backup/dir
savefile=index.html

[user1.directories]
;specific to user 1only
savedir=./user1/wiki/save/dir
backupdir=./user2/wiki/backup/dir
savefile=index.html
|


I also added the savefile directive to override the name of the
file to be saved.

I am also planning on re-writing the password verification section
of the script so that it uses salted cryptographic hashes instead
of plain text passwords.

--
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 
.
To post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3a2b23eb-b303-46b7-a672-73f50d9c7509%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/398712db-b1c8-6fa4-645b-42f717c83aa2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.