Access - Revision history

TiberiusB at 16:04, 26 September 2024

2024-09-26T16:04:21Z

TiberiusB at 20:02, 13 October 2023

2023-10-13T20:02:41Z

TiberiusB at 19:58, 13 October 2023

2023-10-13T19:58:43Z

TiberiusB: Created page with "Access is understood in terms of permission and consent. Consent is at the human level, it is related to a purpose. Permission is related to the mechanics of access..."

2023-10-13T19:51:33Z

Created page with "Access is understood in terms of permission and consent. Consent is at the human level, it is related to a purpose. Permission is related to the mechanics of access..."

New page

Access is understood in terms of [[permission]] and [[consent]].

Consent is at the human level, it is related to a purpose.
Permission is related to the mechanics of access, [[credentials]].

An agent-centric system puts consent before, the purpose is supposed to drive access and even revoke permissions.

[[Permissionless]] systems are purely consent based.

← Older revision		Revision as of 16:04, 26 September 2024
Line 7:		Line 7:

	[[Permissionless]] systems are purely consent based. An interesting case was when the [https://en.wikipedia.org/wiki/The_DAO DAO was "hacked"] on [[Ethereum]] the community forked [[Ethereum]] and reverted back to erase the hackers damage. That action was possible because [[consent]] was broken, even if permissions were granted. The individual who did the damage was seen as a hacker, painted in a negative way, because he broke consent. The hacker tried to justify his actions saying that code is law and he used the code to exploit all its capabilities, therefore nothing wrong was done. In his argument he didn't make the distinction between consent and permission.		[[Permissionless]] systems are purely consent based. An interesting case was when the [https://en.wikipedia.org/wiki/The_DAO DAO was "hacked"] on [[Ethereum]] the community forked [[Ethereum]] and reverted back to erase the hackers damage. That action was possible because [[consent]] was broken, even if permissions were granted. The individual who did the damage was seen as a hacker, painted in a negative way, because he broke consent. The hacker tried to justify his actions saying that code is law and he used the code to exploit all its capabilities, therefore nothing wrong was done. In his argument he didn't make the distinction between consent and permission.
		+
		+
		+	See also [[openness]].

← Older revision		Revision as of 20:02, 13 October 2023
Line 6:		Line 6:
	An agent-centric system puts consent before, the purpose is supposed to drive access and even revoke permissions.		An agent-centric system puts consent before, the purpose is supposed to drive access and even revoke permissions.

−	[[Permissionless]] systems are purely consent based. ~~For example,~~ when the DAO was "hacked" on [[Ethereum]] the community forked [[Ethereum]] and reverted back to erase the hackers damage. That action was possible because [[consent]] was broken, even if permissions were granted. The individual who did the damage was seen as a hacker, painted in a negative way, because he broke consent. The hacker tried to justify his actions saying that code is law and he used the code to exploit all its capabilities, therefore nothing wrong was done. In his argument he didn't make the distinction between consent and permission.	+	[[Permissionless]] systems are purely consent based. An interesting case was when the [https://en.wikipedia.org/wiki/The_DAO DAO was "hacked"] on [[Ethereum]] the community forked [[Ethereum]] and reverted back to erase the hackers damage. That action was possible because [[consent]] was broken, even if permissions were granted. The individual who did the damage was seen as a hacker, painted in a negative way, because he broke consent. The hacker tried to justify his actions saying that code is law and he used the code to exploit all its capabilities, therefore nothing wrong was done. In his argument he didn't make the distinction between consent and permission.

← Older revision		Revision as of 19:58, 13 October 2023
Line 6:		Line 6:
	An agent-centric system puts consent before, the purpose is supposed to drive access and even revoke permissions.		An agent-centric system puts consent before, the purpose is supposed to drive access and even revoke permissions.

−	[[Permissionless]] systems are purely consent based.	+	[[Permissionless]] systems are purely consent based. For example, when the DAO was "hacked" on [[Ethereum]] the community forked [[Ethereum]] and reverted back to erase the hackers damage. That action was possible because [[consent]] was broken, even if permissions were granted. The individual who did the damage was seen as a hacker, painted in a negative way, because he broke consent. The hacker tried to justify his actions saying that code is law and he used the code to exploit all its capabilities, therefore nothing wrong was done. In his argument he didn't make the distinction between consent and permission.