In your blog post, you assert that "far-right forces" attacked users. I'm just curious as to how you to came to that conclusion.
Thanks in advance!
That article doesn't answer my question. All it does is summarize what's in your blog post.
As such, I believe this issue should remain open.
It's not a conclusion, it's a fact evidenced by what kind of attacks we have observed on the platform, and which differs from "scriptkiddy" spam that we are used to.
We won't go into details, because we do not intend to expose the projects that reported the issues to us. And there is not much to be seen anyway, except for the stupid spam that was directed against specific kinds of projects.
I'd rather argue that the kind of reaction we have seen to the blog post, including network-level DDoS on Codeberg itself as well as a lot of hate to our inbox confirms that we were right with calling out the far-right.
@fnetX wrote in #1798 (comment):
It's not a conclusion, it's a fact evidenced by what kind of attacks we have observed on the platform, and which differs from "scriptkiddy" spam that we are used to.
The attacks being different than the "scriptkiddy" spam that you are used to is not evidence that "far-right forces" were behind the attacks.
We won't go into details, because we do not intend to expose the projects that reported the issues to us. And there is not much to be seen anyway, except for the stupid spam that was directed against specific kinds of projects.
Aside from the "NI**** B*LLS" spam incident, I can't find much info online regarding the attacks. More evidence would be useful, even if it's not much to see.
I'd rather argue that the kind of reaction we have seen to the blog post, including network-level DDoS on Codeberg itself as well as a lot of hate to our inbox confirms that we were right with calling out the far-right.
Alright, but what made you call out the far-right in the first place? What makes it a "fact" that the far-right were behind these attacks? What evidence is there to back this up?
@fnetX
I would appreciate any response, even if it's along the lines of: "I'm not able to answer those questions."
@fnetX wrote in #1798 (comment):
It's not a conclusion, it's a fact evidenced by what kind of attacks we have observed on the platform, and which differs from "scriptkiddy" spam that we are used to.
We won't go into details, because we do not intend to expose the projects that reported the issues to us. And there is not much to be seen anyway, except for the stupid spam that was directed against specific kinds of projects.
I'd rather argue that the kind of reaction we have seen to the blog post, including network-level DDoS on Codeberg itself as well as a lot of hate to our inbox confirms that we were right with calling out the far-right.
I must say, for an open-source free software platform, you're not being very open about this.
I've been recommending people to Codeberg ever since I found out about it, but I'm not sure what to think of this. 😕
Codeberg has been very transparent about the whole incident. The blog post shows that a lot of time was spent to explain what happened, what measures were taken and why.
This discussion was created by an account whose purpose is quite evidently exclusively for the purpose of trolling on this matter. It was not used for anything else. I propose the discussion is locked.
@earl-warren
With all due respect, this account was made prior to the incident, and for other reasons than trolling. Their blog post claims a lot of stuff, with little-to-no evidence to back it up. All we are asking for is some real evidence that the claims made in the blog post are true.
@moderation please lock this discussion to avoid necro posting.
I would be dishonest if I said this was unexpected. Sadly, as with any case where evidence isn't presented, a case-closed, no answers given response is what we've come to. I will pressure no further for any evidence, as it has become clear that any evidence that there may be will not be given to me, or shown to the public. Thank you for your time, although it seems to have been in vain.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?