• 0 Posts
  • 9 Comments
Joined 10 months ago
cake
Cake day: November 20th, 2024

help-circle


  • 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!




  • It all works (I wrote it), but that issue is about consolidating some code for the future. We know there are going to need to be some changes made to the implementation of post flair once we start testing lemmy interoperability. So, that issue is essentially saying let’s write all the flair code in one place so that it’s easier to change in the future instead of having flair code duplicated between the api side and the web ui side of the piefed.


  • At the moment it would not be interoperable, but that is something we are planning to change once we can start testing it. Last time I checked, the lemmy test server wasn’t yet running a build that had post flair yet. As soon as it is, we would want to make sure that Activitypub messages we send have the same structure.