Yeah, it's still refusing to federate. Had some issues with it lately, I've noticed both shitposter instances and NCD since ~when we flipped the switch to let Darb and Dutch's FSE federate better. Can't federate anything we aren't tagged in from specific instances/users, it's weird.
@Sui@DutchBoomerMan@p This little setting fucks everything up. You'd assume it only applies to API (viewing posts in browser), but it cripples federation as well. It's documented nowhere, and to make matters worse people like @coyote used to spread misinfo in their "fedi privacy guides". Screenshot_20240112_212148.png
I think it was one that mentioned "verified" but I'm just a lowly 🧹 and haven't fucked around with anything myself yet. When instances have different settings for it, it seemingly nukes federation at random?
@Sui@DutchBoomerMan@p Yes, if it gets enabled, other servers regularly won't be able to fetch posts, so the only posts you'd see is from users on that instance that are followed by your own users. Recently goreslut.xyz had it enabled (I managed to convince them to disable it), apparently, SPC has it enabled as well, a couple moths before poast had it enabled too.
That's probably the main issue we're having then, we flipped it on before christmas. Is it likely to get patched so it works regardless, or do we have to try and get all the dark fedi admins to agree on what to set?
@mint@DutchBoomerMan@Sui@p What is happening here is I wanted the ability to make some users' posts always visible without authentication even if everything else is locked down.
@Moon@DutchBoomerMan@Sui@p Yes. It might, in fact, fail even if you have followers from server B, as long as the signed fetch actor's key aren't cached. The server doesn't even attempt to fetch them, instead immediately returning "Not found".
@Moon@DutchBoomerMan@Sui@p The bug here is the whole fact that the settings which should only apply to API access affect federation as well. Your solution is just to make this switch into a duplicate signed fetch option.
@mint@DutchBoomerMan@Sui@p I didn't get much sleep last night so I'm having a hard time following this for some reason. I'll take a look at it again tomorrow.
@mint@DutchBoomerMan@Sui@p I knew that would come up in this conversation, and I agree it doesn't actually work if someone expends just a small amount of intelligent effort.
@Moon@DutchBoomerMan@Sui@p (in a figurative sense; with how many years you wasted on this very network, you should know damn well signed fetches are a snake oil)
@Moon@Sui@p There are dozens of way of getting the posts that are as low effort as directly grabbing them from your instance's client API. I'm sure you heard about boardreader shenanigans.
@Moon@Sui@p P is in the thread, so he could tell you more. The gist is that there was as scraper that went on FSE's TWKN and attributed every federated post to FSE, which caused FBI to contact him because of fedpost on third-party server.