Rename federation fields for multi-community #6301
Draft
+147
−124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For community use
contentfor sidebar (markdown, long text) andsummaryfor short description (150 chars, plaintext).For multi-community use
preferred_username,namein the same way as community. Usesummaryfor the short description. Note that multi-community currently doesnt have a sidebar with markdown/long description and so nocontent.Tested this with Lemmy 0.19 and the sidebar gets set correctly. However it also uses the same sidebar text (from
summary) as short description, which is shown with HTML tags. So we should ignore summaries which contain<p>. With communities fetched from Piefed its the same. NodeBB doesnt havesource, so if we filter outsummarycontaining HTML we wouldnt get any description text. Peertube also usessummaryfor the long description (seems to be plaintext).To be consistent,
person.summaryshould also be calledcontent. But in fact Mastodon usessummarywith HTML content (and nosourcefield).Overall I'm unsure if this is the right direction. It results in incompatibility between different versions and platforms which cannot be resolved cleanly.
Requires #6295
TODO: