My posts on Mastodon say that no one is permitted to quote-boosts my posts — yet I never made that choice.
-
My posts on Mastodon say that no one is permitted to quote-boosts my posts — yet I never made that choice.
(I'm actually OK with others quote-boosting my posts.)
I know enough to be aware this.
Most aren't.A very large number of people have no idea that someone else made this choice for them.
I suspect the vast majority of them would have chosen the opposite.
I think Mastodon should have represented "user has not chosen" in the JSON-LD.
-
R AodeRelay shared this topicR ActivityRelay shared this topic
-
My posts on Mastodon say that no one is permitted to quote-boosts my posts — yet I never made that choice.
(I'm actually OK with others quote-boosting my posts.)
I know enough to be aware this.
Most aren't.A very large number of people have no idea that someone else made this choice for them.
I suspect the vast majority of them would have chosen the opposite.
I think Mastodon should have represented "user has not chosen" in the JSON-LD.
-
I think you just have to add the following to allow Mastodon and everyone else who implements FEP-044f to quote-post it:
"interactionPolicy": {
"canQuote": {
"automaticApproval": [
"https://www.w3.org/ns/activitystreams#Public"
]
}
}, -
I think you just have to add the following to allow Mastodon and everyone else who implements FEP-044f to quote-post it:
"interactionPolicy": {
"canQuote": {
"automaticApproval": [
"https://www.w3.org/ns/activitystreams#Public"
]
}
},@reiver @stefan You need the interaction policy as well as the ability to respond to quote requests with publicly dereferenceable quote authorizations.
If you don't care about the ability to revoke quotes, you can use a stateless blanket permission pattern that I've described here for PieFed: https://codeberg.org/rimu/pyfedi/issues/1566#issuecomment-9755480
PieFed has been relying on that for a few weeks now, so I guess we can call it “proven in practice.”
-
I think you just have to add the following to allow Mastodon and everyone else who implements FEP-044f to quote-post it:
"interactionPolicy": {
"canQuote": {
"automaticApproval": [
"https://www.w3.org/ns/activitystreams#Public"
]
}
},@reiver thanks for the tip. I'll give it a try.
-
@reiver @stefan You need the interaction policy as well as the ability to respond to quote requests with publicly dereferenceable quote authorizations.
If you don't care about the ability to revoke quotes, you can use a stateless blanket permission pattern that I've described here for PieFed: https://codeberg.org/rimu/pyfedi/issues/1566#issuecomment-9755480
PieFed has been relying on that for a few weeks now, so I guess we can call it “proven in practice.”
-
@reiver @stefan You need the interaction policy as well as the ability to respond to quote requests with publicly dereferenceable quote authorizations.
If you don't care about the ability to revoke quotes, you can use a stateless blanket permission pattern that I've described here for PieFed: https://codeberg.org/rimu/pyfedi/issues/1566#issuecomment-9755480
PieFed has been relying on that for a few weeks now, so I guess we can call it “proven in practice.”
@julian@fietkau.social I suppose I'll have to do this as well, thanks for sharing.
-
My posts on Mastodon say that no one is permitted to quote-boosts my posts — yet I never made that choice.
(I'm actually OK with others quote-boosting my posts.)
I know enough to be aware this.
Most aren't.A very large number of people have no idea that someone else made this choice for them.
I suspect the vast majority of them would have chosen the opposite.
I think Mastodon should have represented "user has not chosen" in the JSON-LD.
@reiver this setting is enabled by default, so you probably changed it at some point to disable quotes of your posts.
Or you are looking at an old post that was created before the feature was launched?
