Dead links

[Dr-Flay]

A huge amount of the resource links are no longer valid.
https://jackaudio.org/applications/
Likely some can be found again on new domains, but many links will require swapping to web archive backups, or removal.

[trebmuh]

You can indicate here which links are dead as you find them.

[riveravaldez]

Hi, in the page: https://jackaudio.org/applications/
Section: Audio File Editors
Broken link in Audacity: http://music.columbia.edu/pipermail/linux-audio-user/2005-July/024519.html , on "Please read this post for instructions on how to get Jackaudio and Audacity working together."
Let's keep adding the rest?
Regards!

[riveravaldez]

Hi, in the page: https://jackaudio.org/applications/
Section: Audio File Editors
Broken link in Audacity: http://music.columbia.edu/pipermail/linux-audio-user/2005-July/024519.html , on "Please read this post for instructions on how to get Jackaudio and Audacity working together."
Let's keep adding the rest?
Regards!

Broken links in Audio File Editors

https://music.columbia.edu/pipermail/linux-audio-user/2005-July/024519.html
http://www.roland.com/products/en/JUNO-Gi/
https://wiki.gnome.org/Marlin
https://gna.org/projects/mhwaveedit
http://dis-dot-dat.net/index.cgi?item=/code/sauditor
http://swami.sourceforge.net/ → redirects to → http://www.swamiproject.org/

Broken links in Mixers

http://home.gna.org/jackmixer
http://opensoundcontrol.org/

[falkTX]

Best way to see those fixed is to open a pull request, thanks

[kuutamo-666]

Hello, there is another dead link. This time in the Wiki guide: Section - Guides and walk-throughs / Demystifying JACK – A Beginners Guide to Getting Started with JACK - Libre Music Production.
Looks like this guide was interesting and helpful thing because I found a lots of references in other websites. However I cannot discover the article itself. If you have a copy, or somebody in the group just post it. Thanks.

[redtide]

This kind of giant pages link lists are something unmaintainable: over time some disappears, some change dependencies, others change name/url etc. Even automating you need to run something like linkchecker (which is the one I use), and then fix the changed links or remove when no more available. But in this case you should also ensure that that application still uses JACK as dependency.
That said if people would like to contribute, having a GitHub account it's easy to fix by click Fork button, create some fixed-urls branch, edit the file (which is a simple markdown text file) and then create a pull request. This shouldn't be that much harder than create an issue to report the problem.

[falkTX]

You do not even need to press fork, github provides easy implementation for editing single files.
Behind the scenes it will do a patch commit and PR. All the user needs to do is have a github account (which they need in order to comment anyway) and press the ✏️ plus submit changes

[redtide]

All the user needs to do is have a github account (which they need in order to comment anyway) and press the ✏️ plus submit changes

Which should be the same as clicking on "Improve this page" on the bottom right in the page footer.

[redtide]

If this can be useful I tested all 404 links with linkchecker of the entire website running Jekyll locally, mostly in applications pages, 1 on a post page.
404.txt
I guess there would need to remove no longer existing applications or those which has removed jack from their code, or find the new pages for those have changed url, not just delete them all 😃