mss_cyclistGe0rG: top. I was not aware of this. It is a really good base.
May I use this or do I have to give credits for it?
Ge0rGmss_cyclist: we developed it back in the day as a template for xmpp service operators
Ge0rGmss_cyclist: TBH, I wrote it for https://yaxim.org/yax.im/privacy/ and the it got templated
mss_cyclistGe0rG: Nice. May I use your privacy and tos as a template as well?
Ge0rGmss_cyclist: feel free. just remove my name from it ;)
jonas’insert obligatory "IANAL" here, Ge0rG
mss_cyclistDo you need to provide a lust of data which you gather from users as well as a person responsible for processing that data in Germany?
Ge0rGmss_cyclist: it depends on how good your lawyers are
Ge0rGmss_cyclist: because GDPR is complicated and not easy to interpret
mss_cyclistYeah. In the Dutch version of it they do mention this responsible person and a list which must be at hand immediately for the authorities.
Wondering if this us part if the GDPR or if this is a Dutch speciality to make it even more difficult to offer a free XMPP service.
Ge0rGmss_cyclist: I'm pretty sure it's based on the GDPR.
Ge0rGmss_cyclist: depending on how critical the data is and how much of it you hoard, you might or might not have to create "Records of processing activities"
mss_cyclistGe0rG: So talking about plain standard xmpp server (ejabberd)
Ge0rGmss_cyclist: any standard xmpp server, yes
mss_cyclistThere should be no critical data logged. Except for what the user willingly shares with other users by messaging.
jonas’which could be quite critical :)
mss_cyclistGe0rG: So, you have such a list?
Ge0rGmss_cyclist: it's right there in the template
mss_cyclistGe0rG: I did not mean this.
More like this one (docx):
Ge0rGmss_cyclist: I'm not going to open random malware
I was searching for this link:
mss_cyclistThere are some pdf templates
mss_cyclistThis is another dimension than these standard disclaimers I come across
Ge0rGmss_cyclist: hmm... right. Not sure how large the overlap is, and I'm currently not in a position to work on GDPR. Sorry
mss_cyclistGe0rG: No problem. We are no lawyers. I thought this is not only an issue for me, but for all European operators.
So I was questioning myself wheater anyone else came across these additional documents which apparantly need to be kept track of.
tomMy prosody server keeps crashing
tomNo idea why. Nothing in logs
Ellenor MalikSwitch to another jabber server
tomI've changed logging level from info to debug
tomHopefully if it happens it something will say some info
tomI would like to find the cause before going though all the work of converting server
Nils (10rokita)has left
jonas’tom, check dmesg
tomlua5.2: segfault at 307be564 ip 00005649bbfa4652 sp 00007fff00a11760 error 4 in lua5.2[5649bbf92000+31000]
tomI didn;t know Lua could segfault
Nils (10rokita)has joined
jonas’tom, report that in xmpp:email@example.com?joinM
jonas’tom, report that in xmpp:firstname.lastname@example.org?join