You are reading content from Scuttlebutt
@mix.exe %FnrKq63GB7kRLEFtoj2bNBIlEwOIDwdnx28fXLA2lBQ=.sha256
Re: %EfEwGxRUS

Thinking in a less euro-centric way about data

NOTE the following aren't absolutes - every whanau is different, there is no one Maori perspective - so these are example of some differences I've seen.

  • where the data lives

    • European: data is just ones and zeros, ... maybe it's private, but if it's encrypted it's basically just ones and zeros that make no sense to outsiders
    • Maori: it's not really right if I'm holding data that's no my families, and the idea of people I don't know holding my data is uncomfortable
  • family trees

    • European: a family tree goes down and down and down
    • Maori: what about whangai - my father was raised by his grandparents, but we need to allow people to decide what the most important parental relationship is when drawing this graph. Oh also, non-blood relationships may or may not be relevant to a graph, it depends on the family
  • free access to info

    • European - information is power and should be free. maybe not free to everyone but if you're in the family you should be able to see everything
    • Maori - family members shouldn't be able to see everything, we have a practice of having kaitiaki who look after some sensitive knowledge (about culture, families), and they decide who learns somethings. (this is because information is power, which needs to be handled by people who have wisdom)
  • hierarchies

    • European - we have super admins who have access to everything
    • Maori - each level (whanau, hapu, papa-hapu, iwi) is self governing, and we coordinate across those levels. The iwi want the hapu to be in charge of defining who it's members are - they know best - and we also don't want the iwi to have access to all the data a hapu does - we the iwi shouldn't know everything.

Ways Ahau has build differently because of Maori perspectives about data

  • Ahau the company holds no whanau records
    • we run data relays/ patakas (storehouses) which are optional and allow no access to content
  • private groups are non-negotiable
  • application processes to join groups are needed, and allowing groups to define the questions they ask is important
  • allowing anyone to publish records, but having an approval / attestation process is needed
  • subgroups are implemented just as another group
    • they're not nested, rather just linked to on another
    • groups can become subgroups after they are created
    • there can be subgroups which not all members of the group know about - e.g. for all the wahine, as some cultural knowledge is specific to them
Join Scuttlebutt now