tobi
tobi
Oh that's annoying indeed. We'll have to investigate what's happening there. A workaround to this for now would be to suspend the instance from the admin panel if you know...
I think the issue is probably that trying to interact with an account/status that hasn't been dereffed in a while causes the instance to attempt refresh from remote. If that...
If they're accounts with separate host and account domain values, you may need to add both the host and the account domain for side effects to be fully processed. If...
This is confusing. Can you explain in more detail what you're trying to do, and why? What domain check are you referring to?
Mmmm I think so. For cases like this, would it not be sufficient to add an entry in your /etc/hosts file, or to mess around with docker dns for intra-container...
relates to #240
Mmm i'm also not sure... I wouldn't really like to try it tbh, it's probably just something we should fix in our fork.
Yup, makes sense! We've had this on the back burner for a while now as something to fix. It's been low priority because most other implementations don't really do anything...
> https://gotosocial.org/ns Indeed, the interactionPolicy feature is still in development so we didn't put anything up at the namespace yet. > can someone confirm whether this is correct? Thanks for...
Btw, no need to reverse a payload, current documentation for the feature is here: https://docs.gotosocial.org/en/latest/federation/posts/#interaction-policy