Quaraman,
I would rarely upload content, just type it into a tiddlywiki.
On one hand
I really can not see any way for such regulations to apply to my personal
IP that no one can access (without hacking) has no information/copywrite
material about anyone else that is not publicly available.
On
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
The IP address for tiddlyspot.com is issued to Dreamhost.com. Dreamhost is
a California US based company. But they could have servers anywhere.
On Thursday, November 8, 2018 at 10:27:37 AM UTC-5, Mark S. wrote:
>
> Is the EU looking at small sites that narrowly?
>
> Where is tiddlyspot.com
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
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
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
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
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
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
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
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
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
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
13 matches
Mail list logo
