Earlier quoted context omitted.
That means they are running non-free code, which seems to be one of their main points against Github.
It's community edition.
Wikimedia is moving to Gitlab
261–270 of 408 posts
Re: Wikimedia is moving to Gitlab
#262Earlier quoted context omitted.
They're selfhosting.
I was able to see Wikipedia uses something called openstack, but not the details of what infrastructure they host on. Anyone know what facilities these repos will ultimately be served from?
Re: Wikimedia is moving to Gitlab
#263Earlier quoted context omitted.
I know this because in our forum we have LOTS of "spam" users - https://forum.cloudron.io/users . These users will go into posts and actually make "helpful" comments. Like, "Oh I tried this solution but I found that my disk my full. Deleting data fixed my problem". It almost seems genuine but they build reputation and once they have some votes, they go back and edit all the comments to have links.
Banning entire countries helps a lot. I don't want to name certain countries, but let's assume it's one where it's common to see human corpses floating on a big river.
Re: Wikimedia is moving to Gitlab
#264Earlier quoted context omitted.
Is this mainly a concern for the Gitlab issue tracker? Wikimedia will continue to use Phabricator for issue tracking, Gitlab CE will only be used for CI and code review/hosting...
No. Spammers will create repos and user profiles and snippets and anything they can with spam in them.
Re: Wikimedia is moving to Gitlab
#265Earlier quoted context omitted.
There doesn't appear to be any discussion on your website or on GitHub about why, to be blunt, this is even a good idea in the first place. A classic 2004 paper, "Proof-of-Work" Proves Not to Work [0], explained that the fundamental problem with proof-of-work bot filters is that attackers will always be able to solve the cryptographic puzzle faster than legitimate users. A touch of security-through-obscurity can help…
I'm not associated with the project in any way, but your well researched comment did miss at least one important factoid. This comment: > The closest to any discussion of these numbers that I saw was a mention that it may take up to 20s on mobile; for comparison, the much-hated image CAPTCHA takes about 6-12s on average for native English speakers, and 7-14s for non-native speakers. Missed this quote from the website…
Re: Wikimedia is moving to Gitlab
#266Earlier quoted context omitted.
>the same way I could create an operating system called YeahOS and everyone would understand that OS is a suffix that blends into the branding Yet if you named it myOS and copied the look and feel from iOS everyone could see that you created an iOS clone. That's the only point I was making but seems that many feelings were hurt in the process.
It's all fair. Looking back at my comment I sounded a little bit harsh and I apologize for that. What I was trying to establish is that there's really no solid ground to claim that any Git platform is a copy of another one since they are all essentially productivity and team-work wrappers around Git. If you're talking about the general information architecture that's how SourceForge was even before Git existed, so ha…
I think that's fairly obvious. I guess I didn't explain clear enough the point I was trying to make in the original post. I kind of regret writing it now.
Re: Wikimedia is moving to Gitlab
#267Earlier quoted context omitted.
The spam is infuriating (not GitLab's fault, of course). Atleast, on our instance at https://git.cloudron.io , we got massive snippet spam. After we disabled snippets, we got massive spam on the issue tracker (!). The way we "fixed" is by turning on mandatory 2FA for all users. As a general lesson, what we learnt is these are not bots. These are real humans working in some poor country manually creating accounts (alw…
We had one of the "real humans" write to us (in issues) asking us to leave his spam up for "just a few hours". We implemented a filter anyway. (This was not Gitlab, but a specific form on our unique website.)
What... why? What is their goal???
Re: Wikimedia is moving to Gitlab
#268Earlier quoted context omitted.
Relying on Google's Spying-as-a-Service tooling is not very FOSS at all. There need to be other ways to reach out to users who block Google.
I immediately back out whenever encounter Recaptcha. The other day I was forced to endure it, because I wanted to delete my ancient Minecraft account, since Microsoft pulled a Facebook and are going to require a Microsoft account to play going forwards. Without exaggeration, it took me 15 minutes of training Google surveillance AI (had to solve it three times), for Recaptcha to let me in. I guess Google really hates…
Re: Wikimedia is moving to Gitlab
#269Earlier quoted context omitted.
We had one of the "real humans" write to us (in issues) asking us to leave his spam up for "just a few hours". We implemented a filter anyway. (This was not Gitlab, but a specific form on our unique website.)
> asking us to leave his spam up for "just a few hours" What... why? What is their goal???
Re: Wikimedia is moving to Gitlab
#270Earlier quoted context omitted.
We had one of the "real humans" write to us (in issues) asking us to leave his spam up for "just a few hours". We implemented a filter anyway. (This was not Gitlab, but a specific form on our unique website.)
> asking us to leave his spam up for "just a few hours" What... why? What is their goal???