XSF Discussion - 2018-05-09

Travis seems to have choked on a PR I just issued. Does anyone have any ideas as to what is going on?

Steve Kille, on the xeps repository?

yup

I’ll take a look

ta

uh, something weird™

I’ll restart the build and hope for the best

cheers

jonasw did you tried to turn it of and on again™ ?

*off

edhelas, that’s exactly what I just did :D

It seems to be doing something this time, so fingers crossed.

doesn’t look better than the other one actually

but it also looks to me like this is, if anything, a travis issue

Yes, you're right. And I agree on the latter.

as a smoke test, I’ll re-run the test on Link Mauves PR and see if that also breaks

(for the curious: https://travis-ci.org/xsf/xeps/builds/376839878 that’s Steves build and this is Link Mauves build: <https://travis-ci.org/xsf/xeps/builds/374968366>)

yeah, looks similar

Steve Kille, seems to be some travis-CI issue. now that I know this won’t block the merge, I run the tests locally anyways.

thanks!

Question, it is normal when we accept a new contact "JID", we have several "Authorization accepted..." from Gajim or "[System Message] You are now authorized." from Psi+?

It is a server problem?

Neustradamus, I don't think there is a reason for there to be multiple notifications for the same JID

flow: thanks for your reply

yep the GDPR really stuck it to facebook didn't it? (or not) https://twitter.com/johnnyryan/status/993827965594202112

If that is true as written, that’s pretty sure invalid

> This appears to breach several important principles of the #GDPR, including the principle of purpose limitation, freely given, non-conditional consent, and of transparency. In other words, if Facebook attempts to collect consent in this manner, that consent will be unlawful.

exactly that