On Wednesday, 3 December 2014 at 20:42:28 UTC, Vladimir Panteleev wrote:
> On Wednesday, 3 December 2014 at 20:24:05 UTC, ketmar via Digitalmars-d-announce wrote:
>> On Wed, 03 Dec 2014 09:13:12 +0000
>> Dejan Lekic via Digitalmars-d-announce
>> <digitalmars-d-announce@puremagic.com> wrote:
>>
>>> I think DSource should not be shut down, but instead modernised
>>> and open for new D-based projects. We, old D programmers, just
>>> love DSource! :)
>> the problem with current dsource is that keeps poping up in first
>> google results. yesterday my mate asked me why we don't have gtk+
>> bindings for D. i answered "just google gtkD", he did it and the first
>> result was dsource link, which points just to svn repo, w/o docs and
>> such. this is disaster.
>
> Erm, that was due to a misconfiguration from a last-minute change. Sorry. Fixed now.

Added monitoring so this (at least this particular problem) won't happen again :)

On Wed, 03 Dec 2014 20:42:27 +0000
Vladimir Panteleev via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> On Wednesday, 3 December 2014 at 20:24:05 UTC, ketmar via Digitalmars-d-announce wrote:
> > On Wed, 03 Dec 2014 09:13:12 +0000
> > Dejan Lekic via Digitalmars-d-announce
> > <digitalmars-d-announce@puremagic.com> wrote:
> >
> >> I think DSource should not be shut down, but instead modernised and open for new D-based projects. We, old D programmers, just love DSource! :)
> > the problem with current dsource is that keeps poping up in
> > first
> > google results. yesterday my mate asked me why we don't have
> > gtk+
> > bindings for D. i answered "just google gtkD", he did it and
> > the first
> > result was dsource link, which points just to svn repo, w/o
> > docs and
> > such. this is disaster.
> 
> Erm, that was due to a misconfiguration from a last-minute change. Sorry. Fixed now.
thank you. but i mean that dsource.org is still poping up in results and it contains alot of obsolete projects. some projects was forked long time ago and their dsource pages weren't updated, some are just dead. people keep hitting dsource, trying projects and leaving with a great frustration: "ah, nothing is working, what a mess! besides, all that projects seems dead, so seems D."

i think that the whole dsource site must be shut down and replaced with a stub (except planetD) to stop this disease. that site was great, but now it does more harm than good.

On Wed, 03 Dec 2014 20:42:27 +0000
Vladimir Panteleev via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> On Wednesday, 3 December 2014 at 20:24:05 UTC, ketmar via Digitalmars-d-announce wrote:
> > On Wed, 03 Dec 2014 09:13:12 +0000
> > Dejan Lekic via Digitalmars-d-announce
> > <digitalmars-d-announce@puremagic.com> wrote:
> >
> >> I think DSource should not be shut down, but instead modernised and open for new D-based projects. We, old D programmers, just love DSource! :)
> > the problem with current dsource is that keeps poping up in
> > first
> > google results. yesterday my mate asked me why we don't have
> > gtk+
> > bindings for D. i answered "just google gtkD", he did it and
> > the first
> > result was dsource link, which points just to svn repo, w/o
> > docs and
> > such. this is disaster.
> 
> Erm, that was due to a misconfiguration from a last-minute change. Sorry. Fixed now.
ah, there is another post in D.learn, where guy tries to find python-d and hit dsource instead of bitbucket. kill that dsource monster, please! it hurts the whole community and it hurts newcomers alot!

On 12/3/2014 1:32 PM, ketmar via Digitalmars-d-announce wrote:
> thank you. but i mean that dsource.org is still poping up in results
> and it contains alot of obsolete projects. some projects was forked
> long time ago and their dsource pages weren't updated, some are just
> dead. people keep hitting dsource, trying projects and leaving with a
> great frustration: "ah, nothing is working, what a mess! besides, all
> that projects seems dead, so seems D."
>
> i think that the whole dsource site must be shut down and replaced with
> a stub (except planetD) to stop this disease. that site was great, but
> now it does more harm than good.

Makes sense.

On Wednesday, 3 December 2014 at 21:37:33 UTC, ketmar via Digitalmars-d-announce wrote:
> On Wed, 03 Dec 2014 20:42:27 +0000
> Vladimir Panteleev via Digitalmars-d-announce
> <digitalmars-d-announce@puremagic.com> wrote:
>
>> On Wednesday, 3 December 2014 at 20:24:05 UTC, ketmar via Digitalmars-d-announce wrote:
>> > On Wed, 03 Dec 2014 09:13:12 +0000
>> > Dejan Lekic via Digitalmars-d-announce
>> > <digitalmars-d-announce@puremagic.com> wrote:
>> >
>> >> I think DSource should not be shut down, but instead modernised
>> >> and open for new D-based projects. We, old D programmers, just
>> >> love DSource! :)
>> > the problem with current dsource is that keeps poping up in first
>> > google results. yesterday my mate asked me why we don't have gtk+
>> > bindings for D. i answered "just google gtkD", he did it and the first
>> > result was dsource link, which points just to svn repo, w/o docs and
>> > such. this is disaster.
>> 
>> Erm, that was due to a misconfiguration from a last-minute change. Sorry. Fixed now.
> ah, there is another post in D.learn, where guy tries to find python-d
> and hit dsource instead of bitbucket. kill that dsource monster,
> please! it hurts the whole community and it hurts newcomers alot!

Violence is not the answer.

I'll look into adding a warning banner to the site template.

On Wednesday, 3 December 2014 at 21:32:27 UTC, ketmar via Digitalmars-d-announce wrote:
>
> i think that the whole dsource site must be shut down and replaced with
> a stub (except planetD) to stop this disease. that site was great, but
> now it does more harm than good.

Alternatively: use robots.txt and don't let Google index that.

On Wednesday, 3 December 2014 at 22:48:50 UTC, ponce wrote:
> On Wednesday, 3 December 2014 at 21:32:27 UTC, ketmar via Digitalmars-d-announce wrote:
>>
>> i think that the whole dsource site must be shut down and replaced with
>> a stub (except planetD) to stop this disease. that site was great, but
>> now it does more harm than good.
>
> Alternatively: use robots.txt and don't let Google index that.

This will not help: clawling != indexing, and robots.txt only stops crawling. robots.txt will not prevent a site from appearing in Google search results, and it will not help in lowering a site's search popularity. All it'll do is prevent Google from showing snippets of Dsource pages, and indexing links from DSource.

The existing search result ratings for DSource are because of all the existing links to it, and not so much because of the content on DSource.

On 12/3/2014 2:42 PM, Vladimir Panteleev wrote:
> Violence is not the answer.
>
> I'll look into adding a warning banner to the site template.

Alternatively, replace the pages in dsource with forwarding pages. The page forwarded to can have two links - one to the original page, the other to the modern one.

On Wed, 03 Dec 2014 23:26:41 +0000
Vladimir Panteleev via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> The existing search result ratings for DSource are because of all the existing links to it, and not so much because of the content on DSource.
that's why it should be replaced with stub. google ranking algos knows about sites without content and will lower such sites even if they are linked from alot of other sites.

btw, stub can contain email which authors of the hosted projects can use to get their sources if necessary. but i doubt that anyone will use it.

On Wednesday, 3 December 2014 at 23:26:42 UTC, Vladimir Panteleev wrote:
> This will not help: clawling != indexing, and robots.txt only stops crawling. robots.txt will not prevent a site from appearing in Google search results, and it will not help in lowering a site's search popularity. All it'll do is prevent Google from showing snippets of Dsource pages, and indexing links from DSource.
>
> The existing search result ratings for DSource are because of all the existing links to it, and not so much because of the content on DSource.

What about using the noindex meta tag (https://support.google.com/webmasters/answer/93710)?