I think the limited part of this is that there are still lots of things that you can only do in the web ui that aren’t exposed to the api yet. It isn’t rate limited.
There are some api rate limits (look for RateLimitExceeded in routes), but the settings are generous enough that a normal user (and not a bot) isn’t going to get caught by them.
Off the top of my head, some of the cross post aggregation that piefed does in the web frontend was only very recently (like literally yesterday) added to the api. Post flair is another that was only just added to the api within the past week or so, so I don’t expect it has seen a lot of use yet in apps. Lots of the features around feeds and topics aren’t included yet. And, most annoyingly for me, is that most of the notification types are not returned in the api yet. So, you can end up in a scenario where the api will tell you that you have X unread notifications, but since some of those notification types might not be defined yet in the api, you can only interact with a subset of them.
Okay, yeah. I mean that’s not relevant but you’re right sure. However using piefed via voyager only shows you comments from the post in the community you click. Not all the cross posts. It also doesn’t show you flares and the color tagging etc. Only the web version currently does that.
However using piefed via voyager only shows you comments from the post in the community you click. Not all the cross posts.
Interesting, I thought that Voyager did that for Lemmy, and assumed it was the case for Piefed. Based on the other comment, seems like that was added to the API yesterday.
There is an api by which things like mobile apps can be used with piefed.
But I abuse piefed on mobile and have never got any rate limit warnings?
I think the limited part of this is that there are still lots of things that you can only do in the web ui that aren’t exposed to the api yet. It isn’t rate limited.
There are some api rate limits (look for
RateLimitExceededin routes), but the settings are generous enough that a normal user (and not a bot) isn’t going to get caught by them.Huh, I’m using Voyager on Android, am I missing anything useful?
Off the top of my head, some of the cross post aggregation that piefed does in the web frontend was only very recently (like literally yesterday) added to the api. Post flair is another that was only just added to the api within the past week or so, so I don’t expect it has seen a lot of use yet in apps. Lots of the features around feeds and topics aren’t included yet. And, most annoyingly for me, is that most of the notification types are not returned in the api yet. So, you can end up in a scenario where the api will tell you that you have X unread notifications, but since some of those notification types might not be defined yet in the api, you can only interact with a subset of them.
We are working on it!
Repost aggregation for one
The person above is a PieFed.ca user
Okay, yeah. I mean that’s not relevant but you’re right sure. However using piefed via voyager only shows you comments from the post in the community you click. Not all the cross posts. It also doesn’t show you flares and the color tagging etc. Only the web version currently does that.
Interesting, I thought that Voyager did that for Lemmy, and assumed it was the case for Piefed. Based on the other comment, seems like that was added to the API yesterday.
No not yet. But that’s great news if it has! That’s why I hadn’t been using voyager as much lately. That’s a killer feature.
An API is what an app uses to talk to the server and show you things.
If you are using the web browser front-end (either mobile or desktop), then you are not using the API back-end.
API = Application Programming Interface, an alternative to the web browser.