Piefed community tags
Technical Discussion
8
Posts
5
Posters
56
Views
-
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 :cold_sweat: -
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.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@box464 Piefed's gallery view is the closest approximation I know of.
Pinetta was more directly focused trying to be a Pinboard alternative hasn't been updated in a couple of years.
-
@julian@fietkau.social that's a great idea! I should adopt that, there's no downside.
-
@julian@activitypub.space @paulgc I'm lucky none of my projects so far have needed to really deal with replies, so I haven't had to think about this. 😄
But it reminds me how I've been told that Misskey sends an account's likes to its followers in addition to the author of the liked post, which Mastodon does not. So on Misskey, if a post comes by your feed that someone you follow has previously liked, you see that information. That's cool in some ways and showcases implementation differences in activity delivery.
-
@julian@fietkau.social @paulgc@mastodon.social mm, I don't suppose there's any reason addressees and delivery recipients need align.
You can't enforce it 😁
NodeBB does this too, where we'll send a copy of a reply to everybody in the immediate chain, even if they're not mentioned.
-
@paulgc Glad it's working! Although now that I've tested it myself, I'm not quite as confident anymore. 🤔 A test reply I made at https://activitypub.academy/@begusla_laddaciul/115865414668779913 has the ActivityPub `to` set as the account's followers and `cc` to as.Public, but was sent to my server anyway. So I guess the behavior, at least on activitypub.academy, is to not individually address the parent poster, but send them a copy of the post anyway (presumably justified by W3C ActivityPub §7.1.3). Feels a bit funky.
-
@paulgc@mastodon.social yes, shared inbox is useful to reduce the number of requests sent.
NodeBB will always use a shared inbox if one can be found for the user.
-
@julian@fietkau.social @julian@activitypub.space @reiver Thanks - you're right, I am now seeing them. They turned up at the shared inbox, rather than the user's inbox, which is why I was missing them to start with. activitypub.academy looks useful!
-
In other words, @paulgc, you should be seeing those Create activities if the reply comes from Mastodon. I think if you reply to a post on your server from https://activitypub.academy you can inspect the payload that gets sent.
