Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translate blocks #1162

Closed
snarfed opened this issue Jul 3, 2024 · 3 comments
Closed

Translate blocks #1162

snarfed opened this issue Jul 3, 2024 · 3 comments

Comments

@snarfed
Copy link
Owner

snarfed commented Jul 3, 2024

When we first looked at blocks in #713, we concluded that the main effect of a block, on either side of the bridge, was handled natively within that network. The blocker would no longer see the blockee, and the blockee's interactions wouldn't reach the blocker. So, we didn't necessarily need to translate blocks.

This is true, but the blockee still gets to interact with the blocker's content on the blockee's side of the bridge. We can prevent that by translating blocks. We should do that!

@qazmlp
Copy link

qazmlp commented Jul 3, 2024

Oh, that's surprising. I had (mis)interpreted the "just like with native users" in the docs to mean that the block would be visible to them too.

@snarfed
Copy link
Owner Author

snarfed commented Jul 6, 2024

Got this mostly working, fediverse => Bluesky block and unblock and Bluesky => fediverse block.

@snarfed
Copy link
Owner Author

snarfed commented Jul 8, 2024

Got Bluesky => fediverse undo block working!

@snarfed snarfed closed this as completed Jul 8, 2024
snarfed added a commit that referenced this issue Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants