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

81–90 of 408 posts

Re: Wikimedia is moving to Gitlab

#81

Post by marcinzm »

jefftk wrote: post #70
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…

Can you say more about how it's a problem if people can view things without logging in? Naively I would have seen that as a plus.

1. Create user account

2. Create spam content (snippets, profile, etc.)

3. Get spam content search indexed

4. Profit

Re: Wikimedia is moving to Gitlab

#82

Post by [deleted] »

mxskelly wrote: post #55
celeritascelery wrote: post #13

it was interesting to read their reasons for not using github, especially related to no control over bans or sanctions. Microsoft could pull the rug out from under them at any time if they got pressure from somebody like China.

Oh right yeah pressure from China, like what got youtube-dl entirely removed... Oh wait no that was the US government.

[deleted]

Re: Wikimedia is moving to Gitlab

#83

Post by tylersmith »

oconnor663 wrote: post #66
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…

Is it possible to configure a robots.txt file to accomplish #2?

robots.txt is nothing more than a request. It's essentially a "no dog on lawn" sign in the yard of a vacation home.

Re: Wikimedia is moving to Gitlab

#84

Post by frenchyatwork »

mxskelly wrote: post #55
celeritascelery wrote: post #13

it was interesting to read their reasons for not using github, especially related to no control over bans or sanctions. Microsoft could pull the rug out from under them at any time if they got pressure from somebody like China.

Oh right yeah pressure from China, like what got youtube-dl entirely removed... Oh wait no that was the US government.

It's naive to believe that Microsoft would stand up to the CPP and not the US government.

Re: Wikimedia is moving to Gitlab

#85

Post by spacechild1 »

krelian wrote: post #68

I never checked out gitlab but the name always made it seem like a github copycat. If you want to differentiate your product why not choose a name that rings different to your competitor? And now I finally went and browsed some repositories and it's clear as that they were very much "inspired" but Github's design, it's practically a github clone, at least in that regard (although something is a bit off in the smoothn…

The important difference is that GitLab is open source! That's a bit like critizing LibreOffice for "copying" MS Office and using the word "Office" in its name.

Re: Wikimedia is moving to Gitlab

#86

Post by marcinzm »

clscott wrote: post #72
oconnor663 wrote: post #66

Earlier quoted context omitted.

Is it possible to configure a robots.txt file to accomplish #2?

No, robots.txt is for well behaving bots like bing bot and google bot, not bots that will spam your forums (and Git repo apparently).

But if the issue is SEO bots then robots.txt would block the search engines thus meaning the spam content is of no importance (it's effectively private) and doesn't cause issues for the main sites SEO (nor help the spammers).

Re: Wikimedia is moving to Gitlab

#87

Post by parliament32 »

bastardoperator wrote: post #54
detaro wrote: post #32

Earlier quoted context omitted.

They're selfhosting.

You can self host GitHub too

It's not open source, at best they ship you a locked down VM image to run yourself.

Edit: Confirmed, "GitHub Enterprise is delivered as a virtual appliance that includes all software required to get up and running. The only additional software required is a compatible virtual machine environment." https://enterprise.github.com/faq

Re: Wikimedia is moving to Gitlab

#88

Post by bastardoperator »

BowBun wrote: post #59
bastardoperator wrote: post #54

Earlier quoted context omitted.

You can self host GitHub too

Source? I don't think that's true. Github has on-premises enterprise solutions but one should not confuse that with running free and open software on your own machines - https://enterprise.github.com/faq

I personally don't think anyone would confuse it, but the fact remains, you can host self GitHub. Maybe it costs, maybe it has string attached but ultimately the functionality is there... which makes it true.

Re: Wikimedia is moving to Gitlab

#89

Post by detaro »

clscott wrote: post #72
oconnor663 wrote: post #66

Earlier quoted context omitted.

Is it possible to configure a robots.txt file to accomplish #2?

No, robots.txt is for well behaving bots like bing bot and google bot, not bots that will spam your forums (and Git repo apparently).

It doesn't stop the spam from being created, but it does stop the spam from ruining your site reputation in search results was the suggestion I guess.

Re: Wikimedia is moving to Gitlab

#90

Post by ognarb »

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…

Strange I never saw this behaviour on our Gitlab instance invent.kde.org.
Post reply on HN