Why would it be blocked? I can use http sites just fine, and even then you could setup a self-signed certificate.

I googled it, and it seems like you can just enable cors.

How so? Lua (with luajit) is very performant, and since it’s embedded in nginx, you have all the features of nginx in your app

Due to ratelimits, I don’t think any instance has atom feeds enabled yet. If one does, it would be at /:username/atom.xml.

If you can get openresty and lapis running, it should work. I didn’t get it running last time I tried in termux.

I did some poking, and it’s due to ratelimits. I’m working on a fix now

How is what? Keeping up with changes? It’s not too hard, it doesn’t happen too often, and I can usually get stuff fixed quick enough.

Atom (which is supported by basically every rss reader) is now supported, but disabled by default. If you self host you could get it working.

It’s not too bad, but yeah, stuff does break. Instagram’s code is dogshit though, so there’s a lot of workarounds for most stuff.

Feel free to fork it and give it a different name

Judging from the stack trace, its definitely a problem that occurred on the server

That’s weird, because it works for me. Maybe it happens when a user is loaded for the first time?

I’ve been keeping up with changes for the last ~9 months.

I just tried a random user and it worked, that was probably temporary. That issue has popped up before.

Huh. That was working yesterday. I’ll take a look soon

I was able to delete my Twitter account because of nitter, because I could view posts without logging in.

I made this because I hate Instagram, but there’s still lots of valid reasons to use it.

Its social because you’re interacting with other people

Lemmy is social media

I’ve already read that article, the situation on Instagram has changed a bit, which makes scraping easier.

Ratelimits are still a problem if you don’t have a residential IP, but I have a workaround for that (which I’m hesitant to share publicly).