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.
Piefed's implementation is based off how Lemmy does it. Though, how Lemmy does it has changed.
Looking at the Lemmy implementation, I see it added a custom display_name field instead of the preferredUsername/name dynamic you'd normally use for Objects, ugh.
Piefed is written in python instead of rust and I can see how that's helping their dev speed but has anyone done any testing to see if the language/backend will perform well at scale?
18 replies
Piefed feature release speed is cracked.
Imagine if the team had full salaries to work full time😲
Is that good or bad?
"Cracked" means good lol. Like, if one were to be "cracked at Fortnite," it means that they are exceptionally skilled at the game Fortnite.
They are still refactoring post flairs in the API not fully perfect yet https://codeberg.org/rimu/pyfedi/issues/1274
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.
On the other hand
https://codeberg.org/rimu/pyfedi/pulls/1270
Is the flair implementation made in a way that Lemmy could add compatibility for it down the line?
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.
Piefed's implementation is based off how Lemmy does it. Though, how Lemmy does it has changed.
Looking at the Lemmy implementation, I see it added a custom
display_namefield instead of thepreferredUsername/namedynamic you'd normally use for Objects, ugh.I just don’t like the web interface on piefed. It visually blends the posts together, and that sets off some primal fear within me.
Try Blorp if it's available on your instance
https://blorpblorp.xyz/ works with any instance :)
Try the Card Shadow theme. It's the default theme of https://crust.piefed.social/ if you want a quick look.
That’s not bad. I can finally try piefed for more than 20 seconds at a time
I really gotta stop being a lazy shit and switch over to my piefed alt, don’t I?
https://piefed.world/ is waiting for you
Piefed is written in python instead of rust and I can see how that's helping their dev speed but has anyone done any testing to see if the language/backend will perform well at scale?