Re: Re: EU and the GDPR
Reply #1 –
Hello feline,
but ElkArte looks prettier - unfortunately.
I need a new platform to replace a somewhat hacked SMF 1.1.6, and i would prefer to mangle an SMF database backup through a filter (or run some sed/awk/perl script on it) to obtain something that on be directly loaded into a juvenile database of th new forum. ideally on a different server or in a testing environment. Possible with Your code?
Re: Re: EU and the GDPR
Reply #2 –
Well .. our Forum Software is based on smf 2.1 ..
but we have changed many, many things in the code, and the tables we use are not compatible with any smf.
So you have to think what you need ...
Fel
Re: Re: EU and the GDPR
Reply #4 –
What do you expect in an ElkArte support board? Especially when posting such things as "we at our board offering another forum software are the kings and you here are not"?
Of course the users here love this software. That's why they are here.
Re: Re: EU and the GDPR
Reply #7 –
Did you also disable all the server logs?
Re: Re: EU and the GDPR
Reply #10 –
Back to Elkarte: is there any code available to do at least the most urgent stuff - signing the data protection policy and static hiding of embedded stuff (which is a severe topic independently of the DSGVO).
Re: Re: EU and the GDPR
Reply #12 –
Even worse:
embedding youtube videos is usually done by <iframe>-Tags. As these are loaded while the forum page builds up, personal data is sent to the Youtube servers, notably your IP address. And then a bunch of strange cookies and communication channel (IDs) will be placed on Your computer, not alone regarding Youtube alone, but gooogle in general and worst of all their advertizing network (doubleclick.net). Even if you embed in "enhanced"-privacy mode, one basic communication channel (ID) is set.
It is always up to YOU to inform Your users. But in case of 3rd party services this is usually not enough. to put a note into your policy or refer to the policy of the service!
It looks as if a conforming solution would require providing a static link, maybe with a local thumbnail image. But even then You must inform your users, and it is completely unclear to what degree and where You need to inform them.
easily forgotten are other objects loaded from external sources, notably images using the <img>-Tag. Also loaded during buildup of the page, and at least the IP address of the user will be send to the 3rd party server.