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)

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

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.

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

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_from_space@sh.itjust.works Asked the following:

Comment thread (view)

@weirdo_from_space@sh.itjust.works: So this’ll make use of other Instagram viewers instead of directly going to Instagram itself?

@ThePenguinDev@lemmy.world: 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.