mirror of
https://activitypub.software/TransFem-org/Sharkey
synced 2024-11-21 21:45:11 +00:00
tweak wording
This commit is contained in:
parent
916509dd6a
commit
378408226b
5 changed files with 15 additions and 2 deletions
|
@ -201,6 +201,9 @@ proxyRemoteFiles: true
|
||||||
# Sign outgoing ActivityPub GET request (default: true)
|
# Sign outgoing ActivityPub GET request (default: true)
|
||||||
signToActivityPubGet: true
|
signToActivityPubGet: true
|
||||||
# Sign outgoing ActivityPub Activities (default: true)
|
# Sign outgoing ActivityPub Activities (default: true)
|
||||||
|
# Linked Data signatures are cryptographic signatures attached to each activity to provide proof of authenticity.
|
||||||
|
# When using authorized fetch, this is often undesired as any signed activity can be forwarded to a blocked instance by relays and other instances.
|
||||||
|
# This setting allows admins to disable LD signatures for increased privacy, at the expense of fewer relayed activities and additional inbound fetch (GET) requests.
|
||||||
attachLdSignatureForRelays: true
|
attachLdSignatureForRelays: true
|
||||||
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
||||||
checkActivityPubGetSignature: false
|
checkActivityPubGetSignature: false
|
||||||
|
|
|
@ -273,6 +273,9 @@ proxyRemoteFiles: true
|
||||||
# Sign outgoing ActivityPub GET request (default: true)
|
# Sign outgoing ActivityPub GET request (default: true)
|
||||||
signToActivityPubGet: true
|
signToActivityPubGet: true
|
||||||
# Sign outgoing ActivityPub Activities (default: true)
|
# Sign outgoing ActivityPub Activities (default: true)
|
||||||
|
# Linked Data signatures are cryptographic signatures attached to each activity to provide proof of authenticity.
|
||||||
|
# When using authorized fetch, this is often undesired as any signed activity can be forwarded to a blocked instance by relays and other instances.
|
||||||
|
# This setting allows admins to disable LD signatures for increased privacy, at the expense of fewer relayed activities and additional inbound fetch (GET) requests.
|
||||||
attachLdSignatureForRelays: true
|
attachLdSignatureForRelays: true
|
||||||
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
||||||
checkActivityPubGetSignature: false
|
checkActivityPubGetSignature: false
|
||||||
|
|
|
@ -288,6 +288,9 @@ proxyRemoteFiles: true
|
||||||
# Sign outgoing ActivityPub GET request (default: true)
|
# Sign outgoing ActivityPub GET request (default: true)
|
||||||
signToActivityPubGet: true
|
signToActivityPubGet: true
|
||||||
# Sign outgoing ActivityPub Activities (default: true)
|
# Sign outgoing ActivityPub Activities (default: true)
|
||||||
|
# Linked Data signatures are cryptographic signatures attached to each activity to provide proof of authenticity.
|
||||||
|
# When using authorized fetch, this is often undesired as any signed activity can be forwarded to a blocked instance by relays and other instances.
|
||||||
|
# This setting allows admins to disable LD signatures for increased privacy, at the expense of fewer relayed activities and additional inbound fetch (GET) requests.
|
||||||
attachLdSignatureForRelays: true
|
attachLdSignatureForRelays: true
|
||||||
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
||||||
checkActivityPubGetSignature: false
|
checkActivityPubGetSignature: false
|
||||||
|
|
|
@ -211,6 +211,9 @@ id: "aidx"
|
||||||
# Sign outgoing ActivityPub GET request (default: true)
|
# Sign outgoing ActivityPub GET request (default: true)
|
||||||
signToActivityPubGet: true
|
signToActivityPubGet: true
|
||||||
# Sign outgoing ActivityPub Activities (default: true)
|
# Sign outgoing ActivityPub Activities (default: true)
|
||||||
|
# Linked Data signatures are cryptographic signatures attached to each activity to provide proof of authenticity.
|
||||||
|
# When using authorized fetch, this is often undesired as any signed activity can be forwarded to a blocked instance by relays and other instances.
|
||||||
|
# This setting allows admins to disable LD signatures for increased privacy, at the expense of fewer relayed activities and additional inbound fetch (GET) requests.
|
||||||
attachLdSignatureForRelays: true
|
attachLdSignatureForRelays: true
|
||||||
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
# check that inbound ActivityPub GET requests are signed ("authorized fetch")
|
||||||
checkActivityPubGetSignature: false
|
checkActivityPubGetSignature: false
|
||||||
|
|
|
@ -793,8 +793,9 @@ export class ApRendererService {
|
||||||
|
|
||||||
@bindThis
|
@bindThis
|
||||||
public async attachLdSignature(activity: any, user: { id: MiUser['id']; host: null; }): Promise<IActivity> {
|
public async attachLdSignature(activity: any, user: { id: MiUser['id']; host: null; }): Promise<IActivity> {
|
||||||
// When using authorized fetch, Linked Data signatures are often undesired (as it can allow blocked instances to bypass the check).
|
// Linked Data signatures are cryptographic signatures attached to each activity to provide proof of authenticity.
|
||||||
// We allow admins to disable LD signatures for increased privacy, at the expense of increased incoming fetch (GET) requests.
|
// When using authorized fetch, this is often undesired as any signed activity can be forwarded to a blocked instance by relays and other instances.
|
||||||
|
// This setting allows admins to disable LD signatures for increased privacy, at the expense of fewer relayed activities and additional inbound fetch (GET) requests.
|
||||||
if (!this.config.attachLdSignatureForRelays) {
|
if (!this.config.attachLdSignatureForRelays) {
|
||||||
return activity;
|
return activity;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue