News
Instagram’s Chronological Feed Is Now Available For All Users
In addition to the chronological feed, there’s now also a new favorites feed option, which shows the latest posts from a list of chosen accounts.
In 2016, Instagram turned off the ability to display new posts in chronological order, claiming that users were missing many posts, even those posted by their close connections.
The algorithmic home feed took over, and it has been dictating what Instagram users see until now. After more than five years and many heated discussions about how the algorithmic home feed works, the ability to display new posts in chronological order is finally back.
“We want you to be able to shape Instagram into the best possible experience, and giving you ways to quickly see what you’re most interested in is an important step in that direction,” writes Adam Mosseri, Head of Instagram, in a blog post.
The decision to bring back the chronological feed comes after last year’s Senate hearing, during which Mosseri was asked if he believed users should be able to use the app without being manipulated by algorithms. The hearing prompted Instagram to say that it would give its users more freedom, and the social network has finally delivered on that promise.
Also Read: How To Find & Cancel Pending Instagram Requests
In addition to the chronological feed, there’s now also a new favorites feed option, which shows the latest posts from a list of chosen accounts.

To activate the chronological and favorites feeds:
- Launch the Instagram app on your smartphone.
- Tap the Instagram logo in the top left corner.
- Choose Following to see posts in chronological order or Favorites to see the latest posts from chosen accounts.
Unfortunately, the change doesn’t stick, which means that Instagram’s algorithmic feed will be back every time you reopen the Instagram app.
Another limitation is that it’s not possible to see Stories from the chronological and favorites feeds, making them feel somewhat inferior to the algorithmic feed, and that’s probably exactly how Instagram wants it to feel in order to steer its users toward the default experience.
News
Nano Banana 2 Arrives In MENA For Google Gemini Users
Google brings its latest image model to Gemini and Search, adding 4K output and tighter text control for regional users.
Google has opened access to Nano Banana 2 across the Middle East and North Africa, pushing its newest image model into everyday tools rather than keeping it inside the exclusive (and expensive) Pro tier.
The rollout spans the Google Gemini desktop and mobile apps, and extends to Google Search through Lens and AI Mode. Developers can also test it in preview via AI Studio and the Gemini API.
Nano Banana 2 runs on Gemini Flash, Google’s fast inference layer. The focus is speed, but also control. Users can export visuals from 512px up to 4K, adjusting aspect ratios for everything from vertical social posts to widescreen displays.
The model maintains character likeness across up to five figures and preserves fidelity for as many as 14 objects within a single workflow. This enables visual continuity across scenes, iterations, or edits — supporting projects like short films, storyboards, and multi-scene narratives. Text rendering has also been improved, delivering legible typography in mockups and greeting cards, with built-in translation and localization directly within images.
Also Read: RØDE Adds Direct iPhone Pairing To Wireless GO And Pro Mics
Under the hood, the system taps Gemini’s broader knowledge base and pulls in real-time information and imagery from web search to render specific subjects more accurately. Lighting and fine detail have been upgraded, without slowing output.
By embedding the model inside Gemini and Search, Google is normalizing advanced image generation for a mass audience. In MENA, where startups and marketing teams are leaning heavily on AI to scale content across languages and borders, that shift lands at a practical moment.
The move also folds creative tooling deeper into search itself, so that image generation is no longer a separate workflow. It now sits right next to the query box.
