<story><title>Wikimedia is moving to Gitlab</title><url>https://www.mediawiki.org/wiki/GitLab_consultation#Outcome</url></story><parent_chain><item><author>encom</author><text>I immediately back out whenever encounter Recaptcha.&lt;p&gt;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 me.</text></item><item><author>rightbyte</author><text>Relying on Google&amp;#x27;s Spying-as-a-Service tooling is not very FOSS at all.&lt;p&gt;There need to be other ways to reach out to users who block Google.</text></item><item><author>phikai</author><text>Hi! I&amp;#x27;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&amp;#x2F;configured?&lt;p&gt;One item that is on the roadmap that is coming and may be of interest is `Optional Admin Approval for local user sign up` - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;groups&amp;#x2F;gitlab-org&amp;#x2F;-&amp;#x2F;epics&amp;#x2F;4491&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;groups&amp;#x2F;gitlab-org&amp;#x2F;-&amp;#x2F;epics&amp;#x2F;4491&lt;/a&gt;.&lt;p&gt;I&amp;#x27;m not in the group working on that, but it does appear to be coming soon and would limit the ability of newly created accounts from doing anything until they&amp;#x27;re approved.</text></item><item><author>jancsika</author><text>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&amp;#x27;s search results.&lt;p&gt;In other words-- if you want the common use case for a FOSS project:&lt;p&gt;1. publicly viewable main repository with publicly viewable issue tracker&lt;p&gt;2. requirement to log in to view all snippets, user profiles, perhaps even other repos as enforced by administrator settings (otherwise SEO bots will leverage these features to eat your search results)&lt;p&gt;3. anyone with an email can sign up to post issues to the main repo&amp;#x27;s issue tracker&lt;p&gt;There is no combination of settings in Gitlab CE to achieve this. Any sane approach has to leave out step #2. That means that your Gitlab instance gets hammered with user spam from bots which then get indexed in Google search results for your site.&lt;p&gt;Worse, Gitlab has no tools to make it easy to remove the user spam (and obviously no tools to prevent it from happening).&lt;p&gt;Just run a public-facing Gitlab CE instance for a few days. Search for one of the spam snippets you collect, and you&amp;#x27;ll find results for all the FOSS projects out there running their own Gitlab instances.&lt;p&gt;I&amp;#x27;ve never seen any solutions offered by Gitlab for this, nor frankly any interest in the myriad bug reports about them addressing this at all.&lt;p&gt;Edit: typo</text></item></parent_chain><comment><author>dalmo3</author><text>Yesterday I spent the longest ever with a recaptcha, about 2-3 minutes, at a frigging checkout page. I decided to endure it just because I really needed that ergonomic kb+mouse combo.&lt;p&gt;Hopefully they&amp;#x27;ll allow me to solve captchas for longer without getting a RSI.</text></comment>
<story><title>Wikimedia is moving to Gitlab</title><url>https://www.mediawiki.org/wiki/GitLab_consultation#Outcome</url></story><parent_chain><item><author>encom</author><text>I immediately back out whenever encounter Recaptcha.&lt;p&gt;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 me.</text></item><item><author>rightbyte</author><text>Relying on Google&amp;#x27;s Spying-as-a-Service tooling is not very FOSS at all.&lt;p&gt;There need to be other ways to reach out to users who block Google.</text></item><item><author>phikai</author><text>Hi! I&amp;#x27;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&amp;#x2F;configured?&lt;p&gt;One item that is on the roadmap that is coming and may be of interest is `Optional Admin Approval for local user sign up` - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;groups&amp;#x2F;gitlab-org&amp;#x2F;-&amp;#x2F;epics&amp;#x2F;4491&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;groups&amp;#x2F;gitlab-org&amp;#x2F;-&amp;#x2F;epics&amp;#x2F;4491&lt;/a&gt;.&lt;p&gt;I&amp;#x27;m not in the group working on that, but it does appear to be coming soon and would limit the ability of newly created accounts from doing anything until they&amp;#x27;re approved.</text></item><item><author>jancsika</author><text>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&amp;#x27;s search results.&lt;p&gt;In other words-- if you want the common use case for a FOSS project:&lt;p&gt;1. publicly viewable main repository with publicly viewable issue tracker&lt;p&gt;2. requirement to log in to view all snippets, user profiles, perhaps even other repos as enforced by administrator settings (otherwise SEO bots will leverage these features to eat your search results)&lt;p&gt;3. anyone with an email can sign up to post issues to the main repo&amp;#x27;s issue tracker&lt;p&gt;There is no combination of settings in Gitlab CE to achieve this. Any sane approach has to leave out step #2. That means that your Gitlab instance gets hammered with user spam from bots which then get indexed in Google search results for your site.&lt;p&gt;Worse, Gitlab has no tools to make it easy to remove the user spam (and obviously no tools to prevent it from happening).&lt;p&gt;Just run a public-facing Gitlab CE instance for a few days. Search for one of the spam snippets you collect, and you&amp;#x27;ll find results for all the FOSS projects out there running their own Gitlab instances.&lt;p&gt;I&amp;#x27;ve never seen any solutions offered by Gitlab for this, nor frankly any interest in the myriad bug reports about them addressing this at all.&lt;p&gt;Edit: typo</text></item></parent_chain><comment><author>wolco2</author><text>Are you sure you are human?</text></comment>