Fix broken Facebook and Instagram social icons

[4tala]

Problem

The Facebook and Instagram icons in the footer were broken/not displaying correctly.

Solution

Replaced unreliable image URLs with stable CDN sources from flaticon:

• Facebook icon: https://cdn-icons-png.flaticon.com/512/124/124010.png
• Instagram icon: https://cdn-icons-png.flaticon.com/512/174/174855.png

Updated both socialLinks (used in footer) and ICONS object (general use) for consistency.

Testing

• Lint passes
• Build passes

[netlify]

✅ Deploy Preview for linksforisrael ready!

Name	Link
🔨 Latest commit	0f77030
🔍 Latest deploy log	https://app.netlify.com/projects/linksforisrael/deploys/6988a0ac5976410008e8c673
😎 Deploy Preview	https://deploy-preview-734--linksforisrael.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[qodo-code-review]

Review Summary by Qodo

Fix broken Facebook and Instagram social icons

🐞 Bug fix

Walkthroughs

Description

• Replace unreliable Facebook icon URL with stable Flaticon CDN source
• Replace broken Instagram icon with Flaticon CDN URL
• Update both socialLinks footer and ICONS object for consistency

Diagram

flowchart LR
  A["Old URLs<br/>Wikipedia/Local Files"] -- "Replace with" --> B["Flaticon CDN<br/>Stable Sources"]
  B --> C["socialLinks<br/>Footer Icons"]
  B --> D["ICONS Object<br/>General Use"]

Loading

File Changes

1. app/utils/consts.ts 🐞 Bug fix +4/-5

Replace social icons with Flaticon CDN URLs

• Updated Instagram icon URL from local file /images/instagram_icon.png to Flaticon CDN
• Updated Facebook icon URL from Wikipedia to Flaticon CDN in socialLinks object
• Updated Facebook icon URL in ICONS object from Wikipedia to Flaticon CDN
• Updated Instagram icon URL in ICONS object from local file to Flaticon CDN

app/utils/consts.ts

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Oversized remote footer icons 🐞 Bug ➹ Performance

Description

• socialLinks now points Instagram/Facebook icons to cdn-icons-png.flaticon.com/512/... while
  the footer renders them at ~18–20px.
• This is likely to download much larger PNGs than necessary (wasted bandwidth/latency) and adds a
  new third-party availability dependency for critical UI chrome.
• No explicit fallback is configured in the rendering path, so failures degrade the UI (missing
  icons).

Code

app/utils/consts.ts[R4-10]

+		imgSrc: "https://cdn-icons-png.flaticon.com/512/174/174855.png",
		alt: "Instagram",
	},
	{
		href: "https://www.facebook.com/LinksForIsrael/",
-		imgSrc:
-			"https://upload.wikimedia.org/wikipedia/commons/thumb/b/b8/2021_Facebook_icon.svg/1024px-2021_Facebook_icon.svg.png",
+		imgSrc: "https://cdn-icons-png.flaticon.com/512/124/124010.png",
		alt: "Facebook",

Evidence

The constants now reference 512px flaticon PNGs, and the footer renders them as tiny icons using
Chakra <Image> (i.e., a direct browser <img> request). That combination implies potentially
oversized downloads and introduces dependency on the flaticon host for every page view that includes
the footer.

app/utils/consts.ts[1-11]
app/components/Footer/Footer.tsx[29-33]
app/components/Footer/Footer.tsx[78-95]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
Footer social icons now load 512px PNGs from a third-party CDN (`cdn-icons-png.flaticon.com`) but are rendered at ~18–20px. This can increase page weight/latency and makes footer UI dependent on that external host. The current rendering path doesn’t configure an explicit fallback.

### Issue Context
These icons are rendered via Chakra `Image` (browser `<img>`), so the client will fetch these URLs directly.

### Fix Focus Areas
- app/utils/consts.ts[1-11]
- app/components/Footer/Footer.tsx[29-33]
- app/components/Footer/Footer.tsx[78-95]

### Suggested fix
- Prefer self-hosted icons in `public/images/...` (or inline SVG) and reference them via relative paths.
- If remote hosting is required, switch to a smaller asset (e.g., a 24/32px version or SVG), and configure Chakra `Image` with a `fallbackSrc` pointing to a local icon.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more