Covering Tree of Life paths

[volooptaz]

Hello,

First congrats for the app! Great resource.

Do you plan on adding also links for the paths in the Kabbalah section? It would require another json file with the paths, I suppose.

This is something I could collaborate on given that I'm interested in adapting this structure for a project I have for building "my" kabbalah.

Greetings from Rio, Brazil :-)

[gadicc]

Thanks, @volooptaz!

Yes this is definitely planned. Let me take a look at it over the next few days and update back.

Let me know what you're working on and if it's anything public I'll be happy to add a link to the README.

[gadicc]

Take a look. Feedback welcome :)

On PC you get a tooltip now on mouseover on the paths, showing letter, pathNo and tarotId.

Next step will be to show the letters programatically, might be a while till I get to that... but at least all the data is there now.

[volooptaz]

That's great :-) exactly what I was thinking about.

As soon as it's public in some form I'll ping you to put on README, but just to illustrate how I thought approaching this - let's call it "cyber kabbalah" for now, at first a "naming wrapping" on Kabbalah to express cybernetics and hacking values and techniques. I'm not sure if you're familiar with Thelema but I'm using Liber Ararita and the Heart of the Master as two basis texts, but studying a lot of different sources too.

So I was at the point of recreating something very similar to your data structure but with none of the frontend skills, when I went once again at Github and this time payed more attention to the enochian-osd and found out its deployment link :-)

So, it would make sense for the system as a whole if I forked it, and in a separate branch from master put my own symbols / attributes as a new key inside each .JSON item inside the main dictionaries, right? Like that:

  "1_2": {
    id: "1_2",
    hermetic: {
      hebrewLetterId: 'alef',
      pathNo: 11,
      tarotId: "0",
    },
    hebrew: {
      hebrewLetterId: 'he',
    }
    [...]
    cyber: {
        [...]    # my attributes
    }
  },

 keter: {
    index: 1,
    id: 'keter',
    name: {
      he: 'כתר',
      romanization: 'Keter',
      en: 'Crown',
    },
    color: {
      king: 'brillliance',
      kingWeb: 'white',
      queen: 'white',
      queenWeb: 'white',
    },
    [...]
    cyber: {
        [...]    # my attributes
    }
  },

For the paths this seems to be the best approach, but it clashes a bit with sephirot's annotations (e.g. its name would fit also for "name.cyber".

[gadicc]

Sounds intriguing and again, will be interested to see it once you have something public :) Are you developing in JS?

I think for long term maintainability, rather than forking the data, assuming you're working in JS, it would make more sense for me to separate the data into it's own npm package, with tools to augment the data, e.g.

import MagickData from 'magick-data'; 

MagickData.augment('tolPath', {

    "1_2": {
      cyber: { ... }
    },
    ...

});

MagickData.augment('sephirah', {

    "keter": {
      cyber: { ... }
    },
    ...

});

That way, as I and others continue to improve the data, you can just update the package, rather than rebasing the fork each time.

Initially the package would probably load all the data since it's so little, but moving forward there would presumably be better support to load only certain data sets.

I'd suggest to keep the cybernetic name in the cyber section, since name is tied to the sephirah's Hebrew name (in original Hebrew, romanization, and translations to English and eventually other languages). Presumably the cybernetic name might also be able to be translated to other languages? So maybe cyber.name.en? Or just cyber.name if you have no plans for i18n.

The cybernetics stuff is all your own, right? In case it's anything published from multiple sources, we can just put it straight in the main data files.

[volooptaz]

Hello,

Sorry for the radio silence, the holidays and the beginning of the year were a bit demanding here, and I also took some time to work on Liber Ada, a project that came up very recently and is both influenced and hopefully will help think the Kabbalah part. At the moment it's only in portuguese, but at least I have something to show you, I think DeepL or Google Translate will work well:

https://liber-ada.readthedocs.io

https://github.com/volooptaz/liber-ada

Yesterday I took some time to clone this repo and get used again to the structure; I'll work directly on the .JSON files for now because creating a npm package will take study and work and I'd like to have something online to show some people and also use already as a personal tool, but then when able I'll factor it out to a package, before contributing.

And yes, the source of this is basically me; the system does not exist but hopefully will incorporate concepts from specific sources (most proeminently Gödel Escher Bach, and other studies on information theory, cybernetics, and systems theory).

[gadicc]

Hey no worries at all, been pretty busy too my side. To that end, yes, I think it was a good idea for you to just clone the repo at this point... I'm also adding new fields here and there to the data so it's great not to need to worry about maintaining a separate repo quite yet. So glad this is working well for both of us :) (but to be clear, I did mean that I would be the one to factor out the data and maintain the magick-data package).

Everything looks great... I see you've put a lot of work into this already. Looking forward to see how it continues to develop. Keep it up and keep me posted :)