Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wikimedia is moving to Gitlab

mediawiki.org

Post reply on HN
Print view View original

271–280 of 408 posts

Re: Wikimedia is moving to Gitlab

#271

Post by mpol »

gramakri wrote: post #147
jancsika wrote: post #53

Anyone thinking of moving to their own Gitlab instance with Gitlab CE-- either stay on Github or prepare to waste your time dealing with user spam bots that pollute your site's search results. In other words-- if you want the common use case for a FOSS project: 1. publicly viewable main repository with publicly viewable issue tracker 2. requirement to log in to view all snippets, user profiles, perhaps even other rep…

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…

A service like Stop Forum Spam might be a solution to this. It checks for IP address and email address and gives it a value based on how likely it is assumed to be a spammer.

When they have to set up a new email account and maybe even a new IP address for every few accounts, it gets to be a lot of work soon.

https://www.stopforumspam.com/

Re: Wikimedia is moving to Gitlab

#274

Post by IggleSniggle »

rudedogg wrote: post #221
nerdponx wrote: post #200

Earlier quoted context omitted.

I don't get it. They post all this spam in the hopes that people click on the links therein, thereby boosting the ranking of those sites? Does that actually work at all?

It doesn’t actually require anyone clicking on the links. Google sees inbound links and uses that as a factor when calculating the ranking of the linked page.

I thought that was how it worked like a decade or more ago, but not today.

Re: Wikimedia is moving to Gitlab

#275

Post by mpol »

GLJHunt wrote: post #234
ran3824692 wrote: post #109

Earlier quoted context omitted.

There's been a gitlab bug for almost 3 years to stop relying on recaptcha, https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45684 Debian, KDE and Gnome have never wanted to make their users run Google's nonfree javascript blob to contribute on their gitlab instance. There's been interest, Gitlab has done very little about it. Edit: other bugs about this can be found here https://gitlab.com/gitlab-org/gitlab-foss/-/…

We have a team currently working on improving the detection and mitigation of spam. We continue to look for ways to improve the security and user experience of our product. Our product includes the Akismet Spam filter which you can read more about in our handbook: https://about.gitlab.com/handbook/support/workflows/managing... . Further, Gitlab.com includes the ability to report abuse directly to our trust & safety t…

(I already replied on a different thread but this might make more sense)

A service like Stop Forum Spam might be a solution to this. It checks for IP address and email address and gives it a value based on how likely it is assumed to be a spammer.

When they have to set up a new email account and maybe even a new IP address for every few accounts, it gets to be a lot of work soon.

https://www.stopforumspam.com/

It has a very simple API and is not that hard to implement (really, I have done it myself :) )

Re: Wikimedia is moving to Gitlab

#276

Post by leipert »

edflsafoiewq wrote: post #254
grey-area wrote: post #224

Earlier quoted context omitted.

This is a typical spam profile. Usually they contain links, which search engines follow. https://forum.cloudron.io/user/cardioaseg

The link contains rel=nofollow.

I don’t know for sure, but I think our Markdown implementation adds nofollow.

Re: Wikimedia is moving to Gitlab

#277

Post by reaperducer »

jychang wrote: post #263
eznzt wrote: post #217

Earlier quoted context omitted.

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.

That doesn't help narrow it down. I live in Seattle and the first think I thought of was a popular tiktok of teens finding a corpse in the river last month.

The word you missed was "common."

Re: Wikimedia is moving to Gitlab

#278

Post by brennen »

zdw wrote: post #253
brennen wrote: post #207

Earlier quoted context omitted.

We recently conducted an extensive evaluation of CI options[0], concluding at the time that GitLab could meet our needs but didn't make a whole lot of practical sense unless we also migrated to it for code review. Other considerations (Gerrit user experience and sustainability, onboarding costs, a de facto migration of many projects from our Gerrit instance to GitHub, etc.) led us to re-evaluate whether a migration f…

To clarify, is your GitLab-based job system done with configuration-as-code and does it share definitions of jobs across repos? The solution we come up with in using Gerrit/Jenkins was to have a common test invocation (in our case `make test`) that glossed over all the details of a projects build process, and was expected to output test and coverage in specific formats Jenkins could consume (junit/xunit and cobertura…

> To clarify, is your GitLab-based job system done with configuration-as-code and does it share definitions of jobs across repos?

We announced our decision to migrate to GitLab on Monday, so we don't so much have a GitLab-based job system.

Nevertheless, yes, GitLab CI jobs will be defined by files checked into version control, and we'll reuse things where appropriate.

Re: Wikimedia is moving to Gitlab

#279

Post by pcmaffey »

gramakri wrote: post #147
jancsika wrote: post #53

Anyone thinking of moving to their own Gitlab instance with Gitlab CE-- either stay on Github or prepare to waste your time dealing with user spam bots that pollute your site's search results. In other words-- if you want the common use case for a FOSS project: 1. publicly viewable main repository with publicly viewable issue tracker 2. requirement to log in to view all snippets, user profiles, perhaps even other rep…

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…

Could add nocrawl to your robots.txt and advertise the fact on signup page that search engines won’t find this content.

Re: Wikimedia is moving to Gitlab

#280

Post by remram »

protoduction wrote: post #133
phikai wrote: post #117

Earlier quoted context omitted.

Hi! I'm the PM at GitLab who works on Snippets, so thanks for providing this feedback. We do have Recaptcha support which can be configured - are you seeing these kinds of issues with that enabled/configured? One item that is on the roadmap that is coming and may be of interest is `Optional Admin Approval for local user sign up` - https://gitlab.com/groups/gitlab-org/-/epics/4491 . I'm not in the group working on tha…

Hi phikai, I built a privacy friendly alternative to ReCaptcha called FriendlyCaptcha [1], is there a possibility to see this integrated as a more user friendly alternative? Happy to chat (e-mail in profile) [1] https://friendlycaptcha.com/

> up to 20 seconds on old smartphones

That sounds like a very battery-unfriendly idea.

Post reply on HN