We're currently hotlinking to github. Instead, they should be stored in the static directory and served out of IPFS with the rest of the blog.
We're currently hotlinking to github. Instead, they should be stored in the `static` directory and served out of IPFS with the rest of the blog.
<!-- github-sync-id:828178860 -->
docs update to instruct authors to do it this way, and how
linter hook and/or CI for preventing non-local images from being posted
Fix ideally would include
* docs update to instruct authors to do it this way, and how
* linter hook and/or CI for preventing non-local images from being posted
<!-- github-comment-id:616786602 -->
content/post/003-registry-mirror.md
21:[](http://ipn.io) [](http://ipfs.io/) [](http://webchat.freenode.net/?channels=%23ipfs)
content/post/024-ipfs-companion-2.2.0.md
11:
60:| [](https://addons.mozilla.org/addon/ipfs-companion/) | [](https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch) |
content/post/035-go-ipfs-0-4-18.md
163:
167:|  |  |  |  |
content/post/039-london-hack-week-report.md
46:
content/post/050-ipfs-camp-recap.md
18:
25:
32:
38:
45:
52:
71:[](/img/060-ipfs-camp-recap/camp-gif.gif)
content/post/048-ipfs-dev-meetings-2018.md
9:
13:
content/post/weekly-001.md
24:
content/post/weekly-049.md
15:[](img/060-ipfs-camp-recap/camp-gif.gif)
content/post/052-operation-task-force.md
11:
content/post/073-073-go-ipfs-as-a-library.md
10:
content/post/071-ipfs-in-web-browsers.md
13:
29:
47:
59:
content/post/weekly-005.md
17:
content/post/weekly-006.md
19:
98:
118:
content/post/weekly-007.md
51:
55:
content/post/041-ann-ipfs-camp.md
27:
content/post/weekly-034.md
62:
content/post/weekly-036.md
67:
content/post/weekly-035.md
70:
content/post/weekly-038.md
76:
content/post/weekly-039.md
60:
content/post/051-new-ipfs-release-process.md
11:
content/post/019-js-ipfs-crdts.md
24:[](https://www.youtube.com/watch?v=-kdx8rJd8rQ)
content/post/020-js-ipfs-0.26.md
100:
content/post/034-js-ipfs-0.33.md
26:
30:|  |  |  |  |
content/post/060-ipfs-camp-keynotes-interviews.md
16:[](https://www.youtube.com/watch?v=zE_WSLbqqvo&feature=youtu.be)
21:[](https://www.youtube.com/watch?v=jpQnQbfhuBc&feature=youtu.be)
31:[](https://youtu.be/cQJXnJDbXv4)
40:[](https://youtu.be/wNfk05D887M)
45:[](https://youtu.be/3pSV6ai6QUI)
content/post/082-ethdenver-2020.md
9:
content/post/082-our-focus-for-2020.md
23:
content/post/083-improved-bitswap-with-netflix.md
23:
65:[](https://github.com/Netflix/p2plab)
content/post/085-announcing-rust-ipfs.md
45:
content/post/087-ipfs-mobile-design-research.md
13:
content/post/weekly-040.md
45:
Even the ones that point to the gateway/ipfs should move into the repo.
> `grep -r '!\[[^]]*\]\((https?:)?//' **/*.md`
```
content/post/003-registry-mirror.md
21:[](http://ipn.io) [](http://ipfs.io/) [](http://webchat.freenode.net/?channels=%23ipfs)
content/post/024-ipfs-companion-2.2.0.md
11:
60:| [](https://addons.mozilla.org/addon/ipfs-companion/) | [](https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch) |
content/post/035-go-ipfs-0-4-18.md
163:
167:|  |  |  |  |
content/post/039-london-hack-week-report.md
46:
content/post/050-ipfs-camp-recap.md
18:
25:
32:
38:
45:
52:
71:[](/img/060-ipfs-camp-recap/camp-gif.gif)
content/post/048-ipfs-dev-meetings-2018.md
9:
13:
content/post/weekly-001.md
24:
content/post/weekly-049.md
15:[](img/060-ipfs-camp-recap/camp-gif.gif)
content/post/052-operation-task-force.md
11:
content/post/073-073-go-ipfs-as-a-library.md
10:
content/post/071-ipfs-in-web-browsers.md
13:
29:
47:
59:
content/post/weekly-005.md
17:
content/post/weekly-006.md
19:
98:
118:
content/post/weekly-007.md
51:
55:
content/post/041-ann-ipfs-camp.md
27:
content/post/weekly-034.md
62:
content/post/weekly-036.md
67:
content/post/weekly-035.md
70:
content/post/weekly-038.md
76:
content/post/weekly-039.md
60:
content/post/051-new-ipfs-release-process.md
11:
content/post/019-js-ipfs-crdts.md
24:[](https://www.youtube.com/watch?v=-kdx8rJd8rQ)
content/post/020-js-ipfs-0.26.md
100:
content/post/034-js-ipfs-0.33.md
26:
30:|  |  |  |  |
content/post/060-ipfs-camp-keynotes-interviews.md
16:[](https://www.youtube.com/watch?v=zE_WSLbqqvo&feature=youtu.be)
21:[](https://www.youtube.com/watch?v=jpQnQbfhuBc&feature=youtu.be)
31:[](https://youtu.be/cQJXnJDbXv4)
40:[](https://youtu.be/wNfk05D887M)
45:[](https://youtu.be/3pSV6ai6QUI)
content/post/082-ethdenver-2020.md
9:
content/post/082-our-focus-for-2020.md
23:
content/post/083-improved-bitswap-with-netflix.md
23:
65:[](https://github.com/Netflix/p2plab)
content/post/085-announcing-rust-ipfs.md
45:
content/post/087-ipfs-mobile-design-research.md
13:
content/post/weekly-040.md
45:
```
Even the ones that point to the gateway/ipfs should move into the repo.
<!-- github-comment-id:616787293 -->
Closing, as Forestry author workflow in https://github.com/ipfs/ipfs-blog hard-encourages post authors to upload images to repo via the Forestry interface itself. If it continues to be a problem, we can look into linting for non-local images.
Closing, as Forestry author workflow in https://github.com/ipfs/ipfs-blog hard-encourages post authors to upload images to repo via the Forestry interface itself. If it continues to be a problem, we can look into linting for non-local images.
<!-- github-comment-id:795863210 -->
@jdiogopeixoto - how hard would this be for you to script to fix as a one-off for all old posts?
Find any images linked as Markdown that aren't linking to a local directory
Find any images linked as HTML that aren't linking to a local directory
Download all those images and move them to the public image directory
Re-point the links
@Stebalien Fair enough.
@jdiogopeixoto - how hard would this be for you to script to fix as a one-off for all old posts?
- Find any images linked **as Markdown** that aren't linking to a local directory
- Find any images linked **as HTML** that aren't linking to a local directory
- Download all those images and move them to the public image directory
- Re-point the links
<!-- github-comment-id:795931231 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We're currently hotlinking to github. Instead, they should be stored in the
staticdirectory and served out of IPFS with the rest of the blog.Fix ideally would include
Even the ones that point to the gateway/ipfs should move into the repo.
Closing, as Forestry author workflow in https://github.com/ipfs/ipfs-blog hard-encourages post authors to upload images to repo via the Forestry interface itself. If it continues to be a problem, we can look into linting for non-local images.
Reopening because we need to fix the existing images.
@Stebalien Fair enough.
@jdiogopeixoto - how hard would this be for you to script to fix as a one-off for all old posts?