Piefed community tags
-
Hi rimu@piefed.social did Piefed.social update recently to include community tags? I recall this was announced awhile back but it only just started breaking on NodeBB.
"tag": [ { "background_color": "#99c1f1", "blur_images": null, "display_name": "Feature request", "id": "https://piefed.social/c/piefed_meta/tag/198", "text_color": "#000000", "type": "lemmy:CommunityTag" }, ... ]I should point out that there's nothing wrong with the JSON. NodeBB's naive logic just expected every object in
tagto have anameproperty, which your community tags do not, so things exploded
-
Oh hey @rimu, what's the story behind the color attributes? Does other software besides PieFed use them, is there an FEP?
It's way down on my to do list, but I've still got a brain cell or two dedicated to declarative federated profile accent colors. @hollo has configurable profile colors, but doesn't federate them yet AFAIK.
-
Oh hey @rimu, what's the story behind the color attributes? Does other software besides PieFed use them, is there an FEP?
It's way down on my to do list, but I've still got a brain cell or two dedicated to declarative federated profile accent colors. @hollo has configurable profile colors, but doesn't federate them yet AFAIK.
julian@fietkau.social IIRC I think Rimu wrote an FEP for it but it was not submitted through the official FEP processes.
-
@rimu It looks like
display_namewas changed tonamein Lemmy: https://github.com/LemmyNet/lemmy/pull/5976 -
The change to how post flair federate was done with the 1.2 release. We tried to mirror the json structure as it currently stands with the planned lemmy 1.0 release (schema here).
We have some extra fields for indicating the text color and the background color of the post flair as well as whether the flair should apply a blur effect to the post preview (for things like spoiler posts). Lemmy hasn't yet finalized how they will schematize the color properties yet. You can see and contribute to the ongoing discussion here.
We will be updating our schema as theirs comes more into focus to try to keep the interop and transition as smooth as possible. If you want to see an example of an existing community that makes heavy use of post flair, you can look at !fediverse@piefed.social.
-
Oh hey @rimu, what's the story behind the color attributes? Does other software besides PieFed use them, is there an FEP?
It's way down on my to do list, but I've still got a brain cell or two dedicated to declarative federated profile accent colors. @hollo has configurable profile colors, but doesn't federate them yet AFAIK.
-
@rimu Thank you!
I took a look at the source code too and it seems to expect CSS hex notation (either 6-digit RGB or compacted 3-digit form).
One of the things I've been agonizing over is how to allow richer CSS colors, HDR etc. It'd be a short spec to be like “just do anything https://drafts.csswg.org/css-color/#color-syntax allows” but I'd want to give non-browser-based clients some sort of 8-bit RGB fallback. And all that without exploding the complexity.
Will keep thinking on it. -
@rimu Thank you!
I took a look at the source code too and it seems to expect CSS hex notation (either 6-digit RGB or compacted 3-digit form).
One of the things I've been agonizing over is how to allow richer CSS colors, HDR etc. It'd be a short spec to be like “just do anything https://drafts.csswg.org/css-color/#color-syntax allows” but I'd want to give non-browser-based clients some sort of 8-bit RGB fallback. And all that without exploding the complexity.
Will keep thinking on it.Another tricky aspect of this is different clients have all kinds of different designs and colors so depending on the situation the tags could look garish and crazy. But on the other hand a bit of crazy is fun.
