Email or username:

Password:

Forgot your password?
dansup

I wanted to ship the ADR (Admin Dispute Resolution) mvp before announcing it, but in light of recent events, I figured now is more appropriate.

From my observations, when an instance gets #fediblock'd and notices it, half of the time the admin of that instance takes action to fix that, but that isn't easily determinable.

My goal with this is to provide @pixelfed admins a public service to dispute such events and make it easy for them to get unblocked when appropriate.

Shipping soon!

5 comments
dansup

@pixelfed In terms of the actual service, I was thinking of using HTTP sigs to validate admin actions and allow them to comment/provide context during the process, and this would be publicly viewable via the website.

Instance A: Blocks Instance B for federating with Instance C

Instance B: Blocks Instance C and requests validation

ADR service notifies Instance A that Instance B complied with their conditions

Radu

@dansup @pixelfed maybe this is a bad place to start this discussion. But isn’t blocking someone because they federate with someone else a bad reason? The risk is creating small bubbles everywhere instead of a sort of mesh which is bad for discussion

lars

@dansup I don't think it's any of Instance A's business who Instance B federates with. Such a tool encourages abuse of power.

dansup

@ls Well it may be none of A's biz, it's also their right to block B, this isn't an abuse of power, quite the opposite, this aims to resolve disputes and encourage federation between instances who may otherwise not

lars

@dansup But this would require a discussion between the instance admins to find a compromise. Not a platform to accept the unconditional surrender of the other entity.

Go Up