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 <[email protected] <javascript:>> > 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 <[email protected]> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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&utm_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 [email protected]. To post to this group, send email to [email protected]. 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/1b72bb21-53bc-41f4-afe7-f30d3553a75e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
