AT => any: Allow opt-in while hidden from logged-out users

[vyv03354]

Reported here (Japanese): https://bsky.app/profile/tukinet.info/post/3lb7e3a2gl22q

If "Discourage apps from showing my account to logged-out users" option is enabled, Bridgy Fed will not allow to start bridging. If the bridging is already started, however, posts will be bridged even if the option is checked. Is this an expected behavior? If it is not, please add a way to opt-in bridging even if the option is enabled, because the reported user desires the current behavior.

[Tamschi]

That's an interesting one. I think the behaviour is intentional, since hiding an account from logged-out users shouldn't just delete the fediverse bridge account (as that would sever all connections on ActivityPub).
However, it's not possible to translate the setting to ActivityPub, so for example Misskey instances can be used without login to view the account, if the handle is known.

Is it okay if I change the title to "AT => any: Allow opt-in while hidden from logged-out users", since this is a feature request?

@snarfed This could make sense with an --allow-logged-out-viewing flag added to the start command via DM. I don't think we should present that proactively in the help response, but we could surface it in #758 if this is why bridging fails.

[Tamschi]

Oh, I just saw #1549! That makes this easier, I think.

Edit: And I only now saw #1549 (comment).
It makes sense, we'd need to filter those posts out of the Bridgy Fed status pages too.

[vyv03354]

Is it okay if I change the title to "AT => any: Allow opt-in while hidden from logged-out users", since this is a feature request?

OK, I changed the title.

[snarfed]

That's an interesting one. I think the behaviour is intentional, since hiding an account from logged-out users shouldn't just delete the fediverse bridge account (as that would sever all connections on ActivityPub).

Yeah it's an interesting question. Once we detect the setting change, should we keep bridging? Or keep the bridged profile but pause bridging? Or delete the bridged profile entirely?

I think that question belongs in #1293 or nearby more than here. For this question, as you saw in #1549 (comment) , I'm likely to keep opt in/out as simple and black-and-white as possible, and just not allow bridging when "hide from logged-out users" is on. We can consider leaving this open to track the request though.

[snarfed]

#1293 now includes detecting when a Bluesky user changes their "hide from logged-out users" setting. Other than that, as discussed, I don't really plan to allow Bluesky users with that setting enabled to use the bridge. Sorry for the bad news.