[Temp Check] Initiate a Dispute / Mediation Service

[garypalmerjr]

This is not the topic of this thread:

@accessor.eth

i.e, third party service and not funded by ens?

…And switching the topic (to change what I said is poor form).

__

What I said was:

@garypalmerjr

If this is done, then I prefer it to not be connected with ENS Domains.

…and that:

@garypalmerjr

I do not like the encroachment of arbitration into-or-near the protocol systems.

__

YOUR suggestion was to
attach this “Dispute Resolution” [vector attack]
to the official “ENS Domains” public-facing website:

@accessor.eth

maybe a dispute.ens.domains user facing page.

__

At this point I am just repeating myself:

Any “dispute resolution” or “Anti-abuse tools”
should remain separate-&-disconnected from, both,
1 . away from the ENS Protocol, and,
2 . away from official ENS Website(s).

__

Further, this idea is not new;
This is an extension & continuation of Encirca’s idea.
Encirca has a similar or same idea, years ago, of “anti-abuse mechanisms”,
which they had recently re-proposed (for ENS DAO streaming funds), here:

Service Provider Stream Nomination Thread

Name and website of Provider: encirca.eth Name of main point of contact: Tom Barrett (tom.encirca.eth) What do you want to build on ENS? Project Name: ENS Anti-Abuse Tools Four years ago, Brantly.eth published “Why ENS Doesn’t Create More TLDs: Responsible Citizenship in the Global Namespace | by brantly.eth | Medium.” This is worth a re-read. I am requesting an ENS Stream to kick-start a project to further the aspirations for responsible citizenship discussed in this article. Namely, the …

__

PS: Also, about these “dispute resolution” or “Anti-abuse tool” ideas,
[although I have reservations about adding our own vector attacks],
about these potentially dangerous systems-services, I had said:

@garypalmerjr

I like that users can be connecting and having conversations,
and sites are free to implement allow/disallow lists, (via EFP or whatever)

Nevertheless,
I do not support adding these systems-services to the ENS Protocol or website.
I prefer it to not be connected [directly or implicitly] with official ENS Domains systems-services.