Open-Media-Network
/
openwebgovernancebody
7
4
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

Update ' 02a. Draft Funding Application for NLNET'

master
mj-saunders 2022-03-31 07:41:29 +00:00
parent 705a6d7803
commit 8bd27897f7
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
-02a.-Draft-Funding-Application-for-NLNET.md

@ -176,21 +176,21 @@ Link for more info https://unite.openworlds.info/Open-Media-Network/openwebgover
**What are significant technical challenges you expect to solve during the project, if any?
Fill a obvious hole in our set of openweb digital tools, not repuduce the mastakes of the past. I think this last one is the hardist thing to solve. take something that has worked for gennerations and turn it into #openweb code.
To fill an obvious hole in our set of openweb digital tools while not reproducing the mistakes of the past. We increase our chances of success by taking something that has worked for generations and turning it into #openweb code.
People challenges:
Mapping messy human processes to rigid code.
An API that is open and flexible - not too micro-focussed to do one thing only. ActPub is a good example.
We have to map messy human processes into code (which is better at representing more rigid structures). Our approach is therefore to map simpler behaviours and functions, while not imposing /how/ they may be utilised in the bigger picture. This allows for emergent behaviours to freely manifest, instead of trying (and failing) to define them.
[^ This needs work - particularly I think I'm not quite right in how I describe the "imposing"]
Integrating into complex live systems.
While ActPub is a standard, may implementations do not strictly follow.
An API that is open and modular, thus flexible - not too micro-focussed to do one overly specific thing only. ActivityPub is a good example.
Technological:
(D)DOS disruptions handled with standard techniques.
Access control managed by OAuth2.
Re-captchas to deal with account creation.
Integrating into complex live systems. While ActivityPub has a standard, many implementations do not strictly follow it. Our awareness of this coupled with #KISS should help us here - implement only what is necessary as we need it, i.e. solve the /actual/ problem in front of us while being conscious that this can be a moving target.
Bad actors cannot hold positions of power indefinitely. They may form or influence groups, but within a group they have no direct power enact change.
Technological challenges:
(D)DOS disruptions shall be handled with standard techniques.
Access control is to be managed by OAuth2, with re-captchas during account creation.
Bad actors are mediated by the system itself. This is one aspect of where sortition shines.
Mis- and dis-information is the responsibilty of a "Security Group" (part of all Templates) -
"Newbie's" are tagged as such to encourage others to be patient with them.