- cross-posted to:
- selfhosted
- [email protected]
- cross-posted to:
- selfhosted
- [email protected]
We all know the record of bad practices that Meta has done against user’s privacy. Regardless of that, Instagram still is one of the largest social media in the world. This makes it imposible to not have to check Instagram sometimes, but it can be hard to use Instagram when the website is filled with sign-up banners everywhere, is tracking all your activity and wants you to install the official app. This is where Proxigram comes in.
There are other Instagram viewers out there, but some of them can be a little tricky to use since most of them have ads, need JavaScript or are full of captchas and trackers. Proxigram does the job for you and goes to these services, parses the data, and gives it back to you.
Using an instance of Proxigram, you can browse Instagram without JavaScript while retaining your privacy with all the requests going through the server. The client never talks to Instagram or other service providers (unless it is specified).
Screenshot
Features
- See user profile and feed
- See individual post by shortcode
- See tags
- RSS feed
/{username}/rss
-> Posts
- API
/api/{username}
-> profile info/api/{username}/posts
-> profile feed- query:
- cursor: {postId}_{userId}
- query:
/api/p/{shortcode}
-> post/api/p/{shortcode}/comments
-> post’s comments/api/tag/{tag}
-> tag posts
We plan to add more features like RSS, stories and more, stay tune! At the moment, there is not a official instance, but you can follow the README.md in the repository to run one or use one in the wiki page of public instances.
CHANGELOG:
- RSS feed has been added as new feature
- Fix misspelings
- Add wiki page of instances
oh nice! I was hoping something like this would come back after Bibliograms death
Yeah, Bibliogram was really cool! Bibliogran’s death was the reason to make proxigram.
So this’ll make use of other Instagram viewers instead of directly going to Instagram itself?
Basically, but maybe in the future Instagram support is added, just I didn’t want it to make it dependable on scraping Instagram since they are more likely to block the instance. If Instagram support is added in the future, since a random provider is selected every time, is less likely to get blocked by Instagram.
Nice. Hope to see some public instances and eventually integration with those redirect extensions.
I really hope to see it too! That would improve a lot of people privacy journey.
I just created a wiki page of public instances! Thanks to @[email protected] for hosting the first one!