At least it’s pointing at Digi-Key’s KiCad library.
I had high hopes for Digi-Key’s KiCad library when it first came out, but it seems like development on it has pretty much stopped. (And it represents only a minuscule fraction of the parts that Digi-Key sells.) I’d been hoping the library would grow over time.
With bazillion lines they’re stocking it’s quite understandable… I’d rather expect component manufacturers to recognize Kicad and provide proper library models.
It’s understandable that it’s a small fraction and probably always will be, but I wish they were continuing to add to the library at a steady if slow pace.
Hi!
Thanks for notifying SparkFun! Links pointing to the old domain have been updated in the tutorials and blog. I also added a warning in the “Beginner’s Guide to KiCad” tutorial before downloading the software.
Hmm, I tried posting a comment on the YouTube Videos for the " Getting To Blinky KiCad Tutorial Series" but I think it might have gotten deleted/marked as spam? I do not see my comment anymore. 
Some of these descriptions have links to the old domain as well. @ChrisGammell , I’m not sure if you have started on those links yet but it looks like you are already aware after reading through this forum thread. =) I’m not sure how many other videos in the channel link to the old domain.
Uh, I’m not sure if the KiCAD development team is updating archived GitHub repo links as well but I noticed this ‘KiCad Website’ link in the README.md points to the old domain as well => https://github.com/KiCad/kicad-library#readme .
The old KiCad library GitHub repo has been fixed.
I thought they had only 793 milli-bazillion.
There are still a few files that point to the old URL:
Symbols:
kicad-symbols/LICENSE.md:You can read more about KiCad library licensing [here](http://■■■■■■■■■■■■■/libraries/license).
kicad-symbols/CONTRIBUTING.md:Before contributing to the KiCad symbol libraries, it is recommended to read the [contribution guidelines](http://■■■■■■■■■■■■■/libraries/contribute).
kicad-symbols/CONTRIBUTING.md:Contributions to the KiCad libraries must meet the [KiCad Library Convetions (KLC)](http://■■■■■■■■■■■■■/libraries/klc)
kicad-symbols/.github/PULL_REQUEST_TEMPLATE.md:All contributions to the kicad library must follow the [KiCad library convention](http://■■■■■■■■■■■■■/libraries/klc/)
Footprints:
kicad-footprints/LICENSE.md:You can read more about KiCad library licensing [here](http://■■■■■■■■■■■■■/libraries/license).
kicad-footprints/CONTRIBUTING.md:Before contributing to the KiCad footprint libraries, it is recommended to read the [contribution guidelines](http://■■■■■■■■■■■■■/libraries/contribute).
kicad-footprints/CONTRIBUTING.md:Contributions to the KiCad libraries must meet the [KiCad Library Convetions (KLC)](http://■■■■■■■■■■■■■/libraries/klc)
kicad-footprints/.github/PULL_REQUEST_TEMPLATE.md:All contributions to the kicad library must follow the [KiCad library convention](http://■■■■■■■■■■■■■/libraries/klc/)
And too many to list in the 3d packages.
Those are definitely updated in gitlab a week ago.
These are on github.
Going through today, thanks for the pointer. Will also check on the main site.
Unfortunately, the cheatsheet svgs on GitHub also has links to the wrong domain.
I’ve gone through the whole list now and either raised an issue with the maintainer or made a pull request. A lot of these repos have been forked though - is there any way of cascading issues to forks on GitHub?
These repos have been locked so I don’t think they are mirrored from GitLab so we may have to manually fix them.
Yea, all the content on Gitlab were fixed already, including things like cheatsheets.
GitHub is kind of abandoned and archived
I’m attaching a list of sites referencing kicad - pcb . org as indexed by Google (got it from Mark Roszko).
I’m not sure if it’s a good idea to chase them all, but there’s clearly some places where it may be a good idea to get in touch with the administrators. For example, I’ve submitted bug reports about this to Debian and GNU Guix.
I made a very simple script with which someone can monitor the changes made to that site.
#/bin/bash
rm -r ■■■■■■■■■■■■■
wget -o wgetlog.txt -m -R png,jpeg,jpg,svg -X fonts,fontawesome,img https://■■■■■■■■■■■■■/
# expects the original in a renamed dir, so this must be run once first and ■■■■■■■■■■■■■ renamed
diff -r original_kicad-pcb.org/ ■■■■■■■■■■■■■/
# diff output should be for one line only which includes data-cfemail obfuscation which changes every time
diff -r original_kicad-pcb.org/ ■■■■■■■■■■■■■/ > latest_diff.txt
(Let’s see how it looks like here, the forum editor blackens the domain name immediately…)
(EDIT: cencorship doesn’t cover everything, but it shouldn’t matter because if this post is indexed by search engines, the name points to this discussion and isn’t a link.)
Prerequisites: bash, wget, diff. This was written on Windows using Windows Subsystem for Linux / Ubuntu.
It takes about a minute for me, the downloaded data is 4.6M. Run once and rename the downloaded directory to which is expected in the script. Run again. It outputs the diff and also saves it. If there’s anything more in the diff than one line (which is always different and irrelevant), “they” have changed something and you can see what it is.
This of course compares the latest state with the first one you downloaded and renamed, so you should confirm first that the initial state is clean if you want to know there’s nothing suspicious there.
The way back machine has been tracking -pcb for years so it should be possible to spot a change via this. It slowed down trawling it due to lack of change but it does pick up