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

161–170 of 408 posts

Re: Wikimedia is moving to Gitlab

#161

Post by Max70 »

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/

Wow! Thumbs up! I have just checked it out and FriendlyCaptcha seems to be a true game changer. I hope that it will replace every f*cking Google reCAPTCHA out there. Such a great idea!

Re: Wikimedia is moving to Gitlab

#162

Post by zdw »

I'd be interested in the CI aspects of this transition, which seem to be glossed over.

The combination of Gerrit with Jenkins and Jenkins Job Builder blows everything else I've seen out of the water with how easy it is to make both per-patchset and post-integration changes in an infrastructure-as-code manner across multiple repos, once you get over the learning curve.

Re: Wikimedia is moving to Gitlab

#163

Post by sytse »

ran3824692 wrote: post #149
sytse wrote: post #126

Earlier quoted context omitted.

I think the code of this problem is that it is hard to identify if a user is a bot or a human. I've not seen any elegant free solutions to this.

That is not the core of the problem. Spammers are humans, and sometimes they will solve recaptchas in large quantities to get their spam through. Its about having a multipronged approach for administrators to stay ahead of them. For some examples of free solutions see https://www.mediawiki.org/wiki/Manual:Combating_spam . It's even possible to connect spamassassin to forms. Gitlab needs tools and automation that dete…

I think the focus of our Trust and Safety team has been on GitLab.com and not on all GitLab instances. We'll discuss changing this.

Re: Wikimedia is moving to Gitlab

#164

Post by webphineas »

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/

Really nice! Finally someone is using the blockchain technology in a meaningful way!

Re: Wikimedia is moving to Gitlab

#165

Post by protoduction »

birdsbirdsbirds wrote: post #157
protoduction wrote: post #133

Earlier quoted context omitted.

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/

Hopefully you are successful, but how can you scale? If it takes 5 seconds on a desktop, then a server can solve 500.000 captchas per month. At $5 per month, a spammer can still send 1.000 messages for a cent.

It's not enabled yet in production - but the main mechanism is by increasing the difficulty as more requests are made from an IP in a certain timeframe (it's basically rate limiting at that point). Think: every 3rd request in a minute doubles the difficulty with some cooldown period.

With that the cost (and complexity) of an attack can hopefully be in the same ballpark (or higher) than ReCaptcha - without your end user having to label cars or send data to Google.

But in the end a determined spammer will get through any captcha cheaply (for reference: ReCaptcha solves are sold by the thousands for $1) - we just hope we can do better than ReCAPTCHA, especially UX-wise.

Re: Wikimedia is moving to Gitlab

#166

Post by ivank »

gkop wrote: post #158
riffic wrote: post #153

Earlier quoted context omitted.

getting that sweet sweet seo backlink juice

Isn’t that why we add rel=nofollow to low friction user submitted links on our platforms?

Google changed the interpretation of those a year ago. https://webmasters.googleblog.com/2019/09/evolving-nofollow-...

Re: Wikimedia is moving to Gitlab

#168

Post by 20after4 »

depressedpanda wrote: post #130
js2 wrote: post #12

Earlier quoted context omitted.

I much prefer the model of force-pushing your development branch to create change sets. It lets you more easily see how development evolves in response to feedback. And the final state of the branch which gets merged leaves all the in-progress work that no one cares about behind only in Gerrit. With Github/lab's model, if you force push your PR, you lose the ability to view its previous state and diff against that. A…

But you don't force push with Gerrit? Just update your change set, then push to refs/for/ again.

It's effectively similar to a force-push.

Re: Wikimedia is moving to Gitlab

#169

Post by 20after4 »

mikey_p wrote: post #142
Deukhoofd wrote: post #27

Earlier quoted context omitted.

They probably use the free Open Source option, which gives access to the top tiers for free. https://about.gitlab.com/solutions/open-source/

That means they are running non-free code, which seems to be one of their main points against Github.

It's community edition.

Re: Wikimedia is moving to Gitlab

#170

Post by 67868018 »

phikai wrote: post #117
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…

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…

None of your captcha settings work, not even the invisible captcha setting that requires enabling a feature flag.
Post reply on HN