Actually federate license #259
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#259
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We currently fallback to the default license for remote articles, but it should be federated. I think Peertube federates it, we should see how it is done there.
Plume version (and/or commit): 0.2.0
I checked a bit Peertube's code (oh god typescript is better than js), and here are a few thing that we might replicate from them (all of the below vars goes into the
objectpart of an activity):license is federated via a
licencetag, which is aI assume identifier is an id and name the actual license name, however I haven't time to check yet
Edit: Peertube support a limited number of licenses, with id from 1 to 7 :
comments are disabled via a
commentsEnabled: bool(see #270)there is an
updated: Datefield, which we might want to use too as we support post updateicon are federated via a
icontag (see #236), which is a