Why there is not a link in csound.com to

http://www.csounds.com/mikelson/     ?

Probably we are loosing great sites for being unconected to www.csound.com

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Yes, even the basic documentations are not available as links!

All I found is thru google search.

This helps, of course, to find the stuff in google search:
site:csounds.com/
site:csounds.com/resources/




--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

On Sat, Nov 02, 2019 at 11:09:28PM +0000, Csounder Csounder wrote:
> Why there is not a link in csound.com tohttp://www.csounds.com/mikelson/     ?
>
> Probably we are loosing great sites for being unconected to www.csound.com

It seems that csounds.com is largely dormant now. (:-()  There are no links
left on its own home page, except back to csound.com.   There must be a
whole hierarchy of stuff that's now inaccessible unless you have kept a
link.  I remember other Csounders had their work available there.

Maybe somebody can do a recovery job?

        -- Pete --

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

On Sun, Nov 03, 2019 at 07:46:46AM -0500, Steven Yi wrote:
> Older versions of csounds.com are already viewable on archive.org, i.e.:
>
> http://web.archive.org/web/20150426044952/http://www.csounds.com/
>
> You can go back through the various years and see how the site changed.
>
Oh, yes.  I always forget about that facility.  Interesting to browse.
But as the pages themselves still exist on the web, even if they aren't
accessible, why not provide some direct pointers?

For reference, I get a 'Forbidden' on http://csounds.com/resources,
but Hans Mikelson's stuff and everyone else's can still be found at

  http://csounds.com/resources/audio

        -- Pete --

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

On Sun, Nov 03, 2019 at 06:47:47PM -0500, Steven Yi wrote:
> As I mentioned on my other reply, I don't know of any particular reason any
> of these links are left out. It sounds like you want something to be done,
> but I can't guess what it is. So, what do you think should happen?

Hmm, sorry -- I wasn't  really intending to make any specific suggestion.
It's just that I remember csounds.com being a useful resource in days past.
I was also commenting on the original post asking why there were no links.
>
> Do you want csounds.com to change? You'll have to talk to Dr. B, he owns
> that domain and site.

Ah.  Well, perhaps he's willing to make its contents a bit more available.
As I remember 'csounds.com' predates 'csound.com' by a few years, and
the two names are rather confusable.  But there's quite a bit of historical
content there that would be a shame to lose, and curretly can't be reached
from the site itself.
>
> Do you want links to be added to csound.com?  Make a request here or file
> an issue at https://github.com/csound/csound.github.io/ and mention where
> you think would be a good place for them to be. I'm sure someone will take
> up the task.
>
It does seem a bit odd that 'csound.com' completely ignores 'csounds.com'.
I'd have thought that a link or two on the csound 'Community' page would be
appropriate.  Linking to the main page would be useless currently,
as there's nothing there, but the sub-pages, like 'csounds.com/resources/audio'
are reachable and have interesting content.  (I only found them through your
Wayback Machine reference, and extracting links. from there)

Hope that clears things up.  I guess it may be up to what Dr.B. wants to do.

        -- Pete --

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

hi,

well i will  throw in a topic in this discussion from another side:

it was very confusing for me as a new user of csound to realize the
difference from csounds.com to csound.com.

when i google e.g. the terms "csound ramdom" i will get only links to
the 3-4 years old documentation from csounds.com.

annoying, as i am used to quick type in google and get appropriate results.

and (even worse)  the docs on csounds.com don't tell me that this is an
very old version and

if i go up to  the opcode reference i wonder why there are lots of
opcodes missing.

isnt it possible to have a single source and make it clear?

i understand that there is some work to do e.g. get rid of the old docs
by redirecting etc. but i think it could have a value.

sure using site:http://csound.github.io/ would help but hard to
understand and realize as a new user ...

best, Christian

On 11/4/19 1:42 AM, pete.goodeve@COMPUTER.ORG wrote:
> On Sun, Nov 03, 2019 at 06:47:47PM -0500, Steven Yi wrote:
>> As I mentioned on my other reply, I don't know of any particular reason any
>> of these links are left out. It sounds like you want something to be done,
>> but I can't guess what it is. So, what do you think should happen?
> Hmm, sorry -- I wasn't  really intending to make any specific suggestion.
> It's just that I remember csounds.com being a useful resource in days past.
> I was also commenting on the original post asking why there were no links.
>> Do you want csounds.com to change? You'll have to talk to Dr. B, he owns
>> that domain and site.
> Ah.  Well, perhaps he's willing to make its contents a bit more available.
> As I remember 'csounds.com' predates 'csound.com' by a few years, and
> the two names are rather confusable.  But there's quite a bit of historical
> content there that would be a shame to lose, and curretly can't be reached
> from the site itself.
>> Do you want links to be added to csound.com?  Make a request here or file
>> an issue at https://github.com/csound/csound.github.io/ and mention where
>> you think would be a good place for them to be. I'm sure someone will take
>> up the task.
>>
> It does seem a bit odd that 'csound.com' completely ignores 'csounds.com'.
> I'd have thought that a link or two on the csound 'Community' page would be
> appropriate.  Linking to the main page would be useless currently,
> as there's nothing there, but the sub-pages, like 'csounds.com/resources/audio'
> are reachable and have interesting content.  (I only found them through your
> Wayback Machine reference, and extracting links. from there)
>
> Hope that clears things up.  I guess it may be up to what Dr.B. wants to do.
>
>       -- Pete --
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

yes it is confusing, and this confusion is also visible in the subject
of this thread: it is actually about csoundS.com, not csound.com.

as steven mentioned, this all has historical reasons.  the domain
csound.com could not be used by us until few years ago.

one simple solution would be that csounds.com redirects to csound.com.
there were suggestions to do so, but richard boulanger wanted to keep
csounds.com for boulanger labs.

what i find misleading when i go to csounds.com is:
- the inscription "The Csound Community"
- the copyright as "Csound.org" (which does not exist ...)
- no contact is provided

complaints and suggestions must go to richard, not to csound.com.

        joachim



On 04/11/19 02:17, Christian Bacher wrote:
> hi,
>
> well i will  throw in a topic in this discussion from another side:
>
> it was very confusing for me as a new user of csound to realize the
> difference from csounds.com to csound.com.
>
> when i google e.g. the terms "csound ramdom" i will get only links to
> the 3-4 years old documentation from csounds.com.
>
> annoying, as i am used to quick type in google and get appropriate results.
>
> and (even worse)  the docs on csounds.com don't tell me that this is an
> very old version and
>
> if i go up to  the opcode reference i wonder why there are lots of
> opcodes missing.
>
> isnt it possible to have a single source and make it clear?
>
> i understand that there is some work to do e.g. get rid of the old docs
> by redirecting etc. but i think it could have a value.
>
> sure using site:http://csound.github.io/ would help but hard to
> understand and realize as a new user ...
>
> best, Christian
>
> On 11/4/19 1:42 AM, pete.goodeve@COMPUTER.ORG wrote:
>> On Sun, Nov 03, 2019 at 06:47:47PM -0500, Steven Yi wrote:
>>> As I mentioned on my other reply, I don't know of any particular
>>> reason any
>>> of these links are left out. It sounds like you want something to be
>>> done,
>>> but I can't guess what it is. So, what do you think should happen?
>> Hmm, sorry -- I wasn't  really intending to make any specific suggestion.
>> It's just that I remember csounds.com being a useful resource in days
>> past.
>> I was also commenting on the original post asking why there were no
>> links.
>>> Do you want csounds.com to change? You'll have to talk to Dr. B, he owns
>>> that domain and site.
>> Ah.  Well, perhaps he's willing to make its contents a bit more
>> available.
>> As I remember 'csounds.com' predates 'csound.com' by a few years, and
>> the two names are rather confusable.  But there's quite a bit of
>> historical
>> content there that would be a shame to lose, and curretly can't be
>> reached
>> from the site itself.
>>> Do you want links to be added to csound.com?  Make a request here or
>>> file
>>> an issue at https://github.com/csound/csound.github.io/ and mention
>>> where
>>> you think would be a good place for them to be. I'm sure someone will
>>> take
>>> up the task.
>>>
>> It does seem a bit odd that 'csound.com' completely ignores
>> 'csounds.com'.
>> I'd have thought that a link or two on the csound 'Community' page
>> would be
>> appropriate.  Linking to the main page would be useless currently,
>> as there's nothing there, but the sub-pages, like
>> 'csounds.com/resources/audio'
>> are reachable and have interesting content.  (I only found them
>> through your
>> Wayback Machine reference, and extracting links. from there)
>>
>> Hope that clears things up.  I guess it may be up to what Dr.B. wants
>> to do.
>>
>>     -- Pete --
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here