Ryan Barrett

I was able to reproduce this. I revoked Bridgy Fed's access to a Mastodon account, then logged in with it again, confirmed that it only requested read-only account access, and...

related: #1008

Sadly yeah, I generally need to avoid command line and filesystem-based tools.

@Daft-Freak that looks exactly right! Minor: one other thing I tend to do when I implement external reqt's like this is to link to where they're defined or documented, in...

Another minor nit: we'd probably want to mention in the docstring's `Raises` section that it raises `ValidationError` for this even though technically it's not a lexicon schema validation error. Seems...

@Daft-Freak yes! Thanks for the nudge, and thank you again for the contributions. And it's working, congrats! https://indieweb.social/@snarfed/114049210341490927 => https://bsky.app/profile/fedi.test.snarfed.org (...despite Mastodon somehow converting or interpreting the video as a...

These generally aren't errors, they're valid activities that we just don't handle. For example, a non-bridged user replying to a bridged user, or a bridged user reposting a non-bridged user....

I'm also curious what you mean by backpressure. The inbox delivery part of the AP spec is very brief, https://www.w3.org/TR/activitypub/#delivery , and seems entirely deterministic. Nothing on flow control or...

Right. HTTP 429 is the closest we have to an actual application-level backpressure mechanism, and it's not in the AP spec or otherwise implemented to "slow down" inbox delivery on...

Regardless, again, I'm very much with you that the fediverse's async handling makes interop and debugging harder! I wrote about this somewhat at length a bit ago: http://web.archive.org/web/20240127153750/https://fed.brid.gy/docs#error-handling BF originally...