[-] [email protected] 2 points 2 years ago

Pixelfed is great! But as much as I like the Fediverse, not everyone is here. :(

But I have a plan, to encourage people to use Pixelfed. Since I have to create error pages for the project, I have one in mind. When an instance gets rate limited/blocked, there will be a notice to use another instance (or create one) and a paragraph (or link) to encourage the use of Pixelfed.

It ain't much, but is honest work (View)

[-] [email protected] 2 points 2 years ago

Good news! Someone created a Dockerfile and docker-compose.yml is already merged in the repository.

[-] [email protected] 4 points 2 years ago

Me too, just give me the content! I don't want to login. But let's hope it can last long as much as it can.

[-] [email protected] 4 points 2 years ago

This is great! You don't know how happy this makes me! For things like this is why I wanted so much to have an API instead of just generating the HTML.

disclaimer I don’t really know what I’m doing, this is more of a yolo I wanna look into Android app development kinda thing.

Don't worry, I don't know what I'm doing either, the thing is learn while doing it. :D

[-] [email protected] 29 points 2 years ago* (last edited 2 years ago)

I witnessed the death of two great projects too: Bibliogram and Barinsta, I mentioned before that Bibliogram's death was the reason to create Proxigram. The way Proxigram works is that it scrapes the data off others Instagram viewers online, it has multiple providers and more will be added in the future.

@weirdo_[email protected] Asked the following:

Comment thread (view)

@[email protected]: So this’ll make use of other Instagram viewers instead of directly going to Instagram itself?

@[email protected]: 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.

183
submitted 2 years ago by [email protected] to c/[email protected]
0
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[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}
    • /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

ThePenguinDev

0 post score
0 comment score
joined 2 years ago