Make default outgoing-blocks setting off #454

Merged

floatingghost merged 1 commit from Seirdy/akkoma:outgoing-blocks-default-off into develop

2023-01-27 10:06:49 +00:00

Seirdy commented

2023-01-27 05:58:24 +00:00

Contributor

This should help mitigate negative impacts related to block-retaliation
and block-circumvention when blocks become visible to the blocked party.
Instances interested in broadcasting blocks can turn this on if they
wish. This should have always been the default.

See also: AkkomaGang/akkoma-fe#274

This should help mitigate negative impacts related to block-retaliation and block-circumvention when blocks become visible to the blocked party. Instances interested in broadcasting blocks can turn this on if they wish. This should have always been the default. See also: https://akkoma.dev/AkkomaGang/akkoma-fe/pulls/274

Seirdy force-pushed outgoing-blocks-default-off from 254781ee50 to 676cc0d0d7

2023-01-27 06:01:35 +00:00

Compare

floatingghost commented

2023-01-27 10:06:45 +00:00

Owner

yep, i agree with this

thanks!

yep, i agree with this thanks!

floatingghost merged commit d601ddeb91 into develop

2023-01-27 10:06:49 +00:00

floatingghost deleted branch outgoing-blocks-default-off

2023-01-27 10:06:49 +00:00

floatingghost referenced this pull request from a commit

2023-01-27 10:06:50 +00:00

Merge pull request 'Make default outgoing-blocks setting off' (#454) from Seirdy/akkoma:outgoing-blocks-default-off into develop

toast commented

2023-02-01 10:53:04 +00:00

First-time contributor

A bit of context from the foundkey side of things:

When a foundkey instance is aware of an account blocking you, we actually stop that account from seeing any of your posts (including public).
As such, when it comes to non-malicious entities, it's better to federate the blocks.

As for dealing with malicious entities, there are still ways to tell that a block has happened, so the appropriate way to deal with those is to defederate in the first place.

This is obviously not my project, but I would suggest at least telling people about the setting existing (many simply won't know!) and encouraging them to enable it (and mention why it isn't enabled by default) where applicable.

A bit of context from the foundkey side of things: When a foundkey instance is aware of an account blocking you, we actually stop that account from seeing any of your posts (including public). As such, when it comes to non-malicious entities, it's better to federate the blocks. As for dealing with malicious entities, there are still ways to tell that a block has happened, so the appropriate way to deal with those is to defederate in the first place. This is obviously not my project, but I would suggest at least telling people about the setting existing (many simply won't know!) and encouraging them to enable it (and mention why it isn't enabled by default) where applicable.