Should the main (broadcast.websiteleague.org) instance federate with the Fediverse?

If that's how it works, and there's no risk of in-to-out content leak or out-to-in follow/interaction leak situations, I can support the idea of b.wl.o being a publicly federated feed, such that non-wlorg instances and their members can follow it and its posts. (I'm less concerned of in-to-out interactions leaking, or out-to-in content seepage, but it is something to take caution of and try to prevent unintentional/unconsented cases of.)

in-to-out is still a concern I think? we will likely have instances with no public frontend, and users expecting exposure only within league because of it. if someone can follow from Fedi and share their posts out to it, that could be a deal-breaker for users expecting a high trust guarantee.

and frankly, out to in is a vector for offsite bullshit to infect the vibe. cohost had a pretty strong culture of "don't share that tweet you're mad at" but if we're effectively open to the fedi populace, there's a plausible scenario where they become too big a faction to peer pressure out of that behavior.

@tanuki as far as I can tell, there's no way for either of those to happen. the only person seeing both would be whoever's operating an account on that instance.

@walking mirage hm. then yeah, as long as we can verify this I guess it's fine? and ultimately we'd still have the option of breaking outside federation if something unforseen arises.

edit: looks like viviridian has confirmed it below!

seems reasonable to me

so, on akkoma there's mrf policies that allow you to reject all activities from other instances, but they can still receive your instances. is it possible to do this on gts, so that broadcast can't see the rest of the WL? just to keep it all from leaking

edit: or, i mean, is this even necessary with the way activitypub works

i only have one concern: i don't know exactly how ActivityPub federation works, but there might be a problem if someone on a League node replies to a Broadcast post or Broadcast boosts a post from a League node. if this is not a problem, then it would be safe to do this

Personally I'd feel better about this if we tried it with some test instances, observing how gts actually handles this situation would help inform and ground this.

I have some ideas for how to mock that up *and* I have a fediverse instance so I'll tentatively pencil myself in for trying it, unless someone else wants to.

• ✔️

  @viviridian stand up a denylisted instance and try some scenarios where it acts as a bridge between a public fedi instance and a private fedi instance (not in the prod WL environment. i have a spare)

I'm having trouble understanding the benefits of connecting to the wider Fediverse at all. I thought the point was... not to? Is the stuff broadcast posts always going to be intended for a general audience, or like, will there ever be stuff that's primarily aimed at people in the league?

What is the purpose of broadcast? How does it differ from other ways we can communicate with everyone (here, main website, newsletter, etc.)? And how would that be affected by connecting to the outside - whether outgoing only or allowing some variety of incoming?

@isomorphism Generally agree with this, there's no specific reason I can think of for wanting the League connected to the broader fediverse other than as???marketing???. It's probably sufficient to just make it publicly visible. We could just maintain a GTS in fedi if we want to have an embassy account for this reason, rather than a link, which avoids having to deal with weird federation issues. If we're already agreeing not to have it boost Weague internal posts then it's identical.