Hi Mirko,
Calling Daniel's behavior a symptom is a gross understatement.
Happy hacking!
Florian
___
Discussion mailing list
Discussion@lists.fsfe.org
https://lists.fsfe.org/mailman/listinfo/discussion
This mailing list is covered by the FSFE's Code of
Please stop immediatly!
I've certainly not elected you, I'm not even a member of the FSFE or
your abusive fellowship of data robbers, and I certainly haven't
participated on any election.
You have "sequestered" my personal data for the good of your personal
agenda, and hosted it on systems o
On 03/05/2019 19:00, Paul Boddie wrote:
> So, in the case of the Copyright Directive, where much fuss was made about
> keeping code sharing platforms free of copyright filters, it seemed that the
> FSFE was acting to defend GitHub and various proprietary services on the
> basis
> that they help
Hi Paul,
Thank you for asking this question. Let me try to give you a summary to the
best of my knowledge. I am sorry this mail is going to be pretty long, but I
need to provide some background here for this to make sense.
As far as I can tell the root cause of the issue with Daniel consists
Hello,
> On 4. May 2019, at 02:51, Carmen Bianca Bakker wrote:
>
> Je ven, 2019-05-03 je 23:30 +0200, Paul Schaub skribis:
>> For a start, are the allegations of "censorship" regarding the blog and
>> newsletters written by Daniel Pocock true? I dislike the word
>> censorship, as I can see valid
On Saturday 4. May 2019 02.51.44 Carmen Bianca Bakker wrote:
>
> The gist of it is:
>
> - Elections pit contributors against each other, which is not in the
> spirit of collaboration.
>
> - There are already other ways to become a GA member.
>
> - And, if you ask me, the idea of a "fellowship r
Hello,
I see that some people are still having fun with the Mailman interface trying
to unsubscribe people from this list, specifically 91.64.208.89 or
ip5b40d059.dynamic.kabel-deutschland.de as they are also known.
Perhaps some actual, reasoned discussion about the challenges raised by recent
