Bluesky Federation: Lemmy Hitting a Technical Wall While ICE Battle Rages in the Comments
Federation links like `https://bsky.app/profile/unitedkingdom.feddit.uk.ap.brid.gy` exist, showing technical capability, but commenters universally acknowledge more development is needed for full utility.
The debate centers on ICE's presence on Bluesky. Some argue its inclusion is an inherent 'form of harm,' specifically criticizing Bluesky’s verification system, as stated by `wisdomchicken`. `priapus` counters this sharply, noting that current searches return content heavily critical of ICE, and suggests US government accounts face more direct legal jeopardy than policy changes from Bluesky.
Technical functionality is hampered by specific instance policies. `73ms` warned that the Bluesky-to-Lemmy link will be severely constrained unless Lemmy instances switch their default federation policy to opt-in. The clear consensus is excitement for interoperability, but its current state is deeply conditional on developer action.
Key Points
Technical federation is functional but limited.
General technical excitement is noted through working examples, specifically citing Bridgyfed linking Lemmy and Bluesky (`nutomic`).
ICE presence on Bluesky is problematic.
Some users explicitly criticize Bluesky's verification mechanisms due to the presence of ICE content (`wisdomchicken`).
Legal risk to US accounts outweighs policy concerns.
`priapus` argues that legal threats against US government accounts are more imminent than any structural pivot from Bluesky.
Lemmy-Bluesky federation needs a default policy overhaul.
`73ms` warned that the link will be 'extremely limited' without Lemmy instances adopting an opt-in default for federation.
Users can actively block undesirable content.
`eleijeep` offered practical advice, telling users to add an instance block for `fed.brid.gy` in their settings to filter content.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.