simpleblog VS instagram-web-api

There's another dimension that nobody seems to talk about, and that's what happens with access to content is restricted. There is basically no censorship and no abuse from "those who can't get away with stuff on other networks" in the realm of SMS (or WhatsApp/WeChat/whatever your country uses). You can have a very healthy network if the authors are responsible for access control to their content. That's the idea behind my side-project of an easy-to-use, easy-to-selfhost private blog.[1]

When people want to use the platform to "become a thought leader" or "expand their network" then you're in the realm of public publishing which is where all the problems you cite become issues. The web makes privacy possible, and I don't understand why so few people are interested in that angle. For me I want to be able to share photos of my daughter with family and friends. I don't care if someone else wants to privately rant about the government to their friends--privacy enables both of these.

[1] https://github.com/mawise/simpleblog

Simple, easy implementation of the Instagram private web API. Some API reference from jlobos/instagram-web-api Send DM using client from dilame/instagram-private-api

I am working on a website where I need to display a grid of the client's Instagram photos on the homepage. Managed to pull down the data using instagram-web-api, but the cdn domain of the returned images keeps changing, which makes it impossible to target them in the next.config.js file.

We'll use the instagram-web-api npm package to do the heavy lifting for the integration. which should be installed within a NextJS site with npm install instagram-web-api or yarn add instagram-web-api. Once the package is successfully installed it should be imported into index.js file (or whichever page you would like the Instagram feed to appear on) with:

instagram-web-api