<aside> ⏩ For everyday users of Near Social, a significant change has been made to how the data you interact with is stored and delivered, making your experience faster and more reliable.

</aside>

<aside> 👨‍💻 Developer Walkthrough → Dev Guide to Cloudflare Caching for IPFS w/ Near Social Gateways

</aside>

This minor patch results in three main user-experience improvements:

  1. Faster Loading Times: Content will load quicker because more data is now stored in a way that's easier for your device to access.
  2. Lower Data Usage: You'll likely use less data accessing Near Social, which is especially good news if your internet plan isn't unlimited.
  3. Reliable Access: Your access to Near Social will be more consistent, with less waiting around for things to load, even if lots of people are online or the original place where the data is stored is having issues.

Not too bad. 😃

https://x.com/ekuzyakov/status/1780992304754409679

Developers should take the following actions:

<aside> 👨‍💻 Here's a comprehensive guide based on the latest documentation for developers looking to leverage Cloudflare's caching for IPFS on Near Social:

Dev Guide to Cloudflare Caching for IPFS w/ Near Social Gateways

</aside>

Brief Walkthrough of the Steps:

  1. Optimize File Serving: Make sure your files have proper extensions. This simple step lets Cloudflare know they should be cached, which can lead to improved performance.
  2. Implement Cache Rules: Define clear rules in Cloudflare for what gets cached. This can help manage how your app delivers content and ensure that users have the smoothest experience possible.
  3. Understand Throughput Limits: With caching, the 1Gbps limit on @fast-near for fetching recent data will be an almost non-existent bottleneck, allowing for more efficient data handling.
  4. Leverage Historical Data: Enabling indexed block caching for historical data means that applications relying on past data will benefit from quicker access, as this information is more likely to be served from the cache.

ELI5 Summary

Imagine the internet is a big delivery truck that brings you toys (data). Previously, Near Social's toys were kept in a warehouse far away by mistake, and it took a long time to deliver them.

Now, they've realized the mistake and asked the delivery truck to keep some toys right in your neighborhood (caching with Cloudflare), so you get them super fast every time you want to play.

For the toymakers (developers), this means you should pack your toys with clear labels (file extensions) and tell the delivery truck which toys are popular so it can keep them close by (implement cache rules).

Always double check the URL before you connect.

Always double check the URL before you connect.

Now, everyone can play without waiting, and there are enough toys for all your friends too!

Connect, Protect and Build Everywhere | Cloudflare