Added some readme

This commit is contained in:
Willem Cazander 2024-12-08 17:15:59 +01:00
parent 6346f7b851
commit eeefdcf258
7 changed files with 654 additions and 0 deletions

View file

@ -0,0 +1,81 @@
# Hinarī 4-Corner
Resource naming based on fixed reserved keyword list so auto native filenames are possible.
This set should be defined in lingua terminator DB using 72 bit tree slugs...
Rules:
- gemstone: 20 words + 4 words extension (is 3 x V144Tocta's or 54 x byte)
- gemfolder: 24 words, max 4 levels
- one gemglyph word is 18 bit (see V018Tord)
- one gemglyph word has one fixed meaning to have hard-coded translations
- In unicode file paths use the HinarīX9 encoding of The Word
- if gemstone name is lesser then 20 words than use MIN as seperator
org: bundle/org.apache.felix.scr-2.2.0.jar
num: 27712/80606-17120-44960-83150-10100-10100-10307.61011-81417
4CNH: יֽ֕זְ֔/זֲ֟דֲ֩יֳ֟ײֳ֔יֳ֞וֶ֕זֵ֟ױֳ֩רְ֠װֶ֔רְ֠װֶ֔װֽ֕רֶ֔יֽ֔יֽ֔װֶ֕וְ֕ײֵ֔וֲ֩
## Hardware friendly
Full path is fixed size, for example when we use The word number;
- filename: 24 x V018Tord = 3 x V144Tocta = 54 bytes
- path: 4 x 24 x V018Tord = 12 x V144Tocta = 216 bytes
- HyperdriveId: 64 chars = 2 x V144Tocta = 32 bytes
Gives total of 302 bytes or 17 x V144Tocta for hardware based blockchain files.
## Example data
Four corner code lookup:
[mdbg.net](https://www.mdbg.net/chinese/dictionary?page=chardict)
warp = 2291.4 = 紝 = weave, lay warp
hash = 0022.0 = 廁 = toilet, lavatory; mingle with
sea = 3815.7 = 海 = sea, ocean; maritime
file = 7520.6 = 陣 = column, row or file of troops
mine = 5500.0 = 井 = well, mine shaft, pit
java = 6101.1 = 啡 = morphine; coffee
jar = 8141.7 = 瓶 = jug, pitcher, vase, jar, bottle
bundle = 2771.2 = 包 = wrap, pack, bundle; package
organization = 8060.6 = 會 = to assemble, meet together; a meeting; an organization
feather = 1712.0 = 羽 = feather, plume; wings; rad. 124
flower = 4496.0 = 葙 = feather cockscomb (Celosia argentea)
inject = 8315.0 = 鍼 = needle, pin, tack; prick; inject
promise = 0864.0 = 許 = allow, permit; promise; betroth
method = 4321.0 = 朮 = skill, art; method; trick, device
container = 7710.0 = 皿 = shallow container; rad. no. 108
system = 2220.0 = 制 = system; establish; overpower
temple = 3060.6 = 宮 = palace, temple, dwelling, enclose
dependency = 2411.1 = 靠 = lean on, trust, depend on; near
zero = 1030.7 = 零 = zero; fragment, fraction
one = 1000.0 = 一 = one; a, an; alone
two = 1010.0 = 二 = two; twice
three = 1010.1 = 三 = three
four = 6021.0 = 四 = four
immortal = 2227.0 = 仙 = Taoist super-being, transcendent, immortal
highest = 2110.0 = 上 = top; superior, highest; go up, send up
lord = 0010.4 = 主 = master, chief owner; host; lord
heaven = 1043.0 = 天 = sky, heaven; god, celestial
blue = 4410.7 = 藍 = blue; indigo plant; surname
white = 2466.1 = 皓 = bright, luminous; clear; hoary
red = 2191.0 = 紅 = red, vermillion; blush, flush
orange = 4291.8 = 橙 = orange
green = 2793.2 = 綠 = green; chlorine
yellow = 4480.6 = 黃 = yellow; surname
brown = 3622.7 = 褐 = coarse woolen cloth; dull, dark
black = 6033.1 = 黑 = black; dark; evil, sinister
purple = 2497.0 = 紺 = dark blue or reddish color
With fixed keyword list coding, all abstract internal computing resource naming is localized;
4CNH: יֽ֕זְ֔/זֲ֟דֲ֩יֳ֟ײֳ֔יֳ֞וֶ֕זֵ֟ױֳ֩רְ֠װֶ֔רְ֠װֶ֔װֽ֕רֶ֔יֽ֔יֽ֔װֶ֕וְ֕ײֵ֔וֲ֩
en: bundle/organization-feather-flower-inject-two-two-zero.java-jar
nl: bundel/organisatie-veerkracht-bloem-injecteren-twee-twee-nul.java-kan
hi: बंडल/संगठन-पंख-फूल-इंजेक्षन-दो-दो-शून्य.जावा-जार
cn: 捆/組織-羽毛-花-注入-二-二-零。爪哇-罐
See only China has it own full language, all other fake languages lift on latin whitespace.

View file

@ -0,0 +1,87 @@
# No2All
HALTED: All code will be moved to bassbone.
Chicken and egg problem, this project needs j++
and j++ needs this project for the nether DB.
WIP-NOTE; Never been started as only 20% is done.
Send signed notes to all, no2all-nostr is a POJO library to work
with the nostr protocol. And no2all-zerofungus is experimental server
to move all package managers content in DAT and signed in nostr..
TODO: With java webstart example over DAT protocol.
This wowk though dewey of UwU is done in toe toe twailing chains.
So this scwewy is smoked in nostr and licky fiaels are tewminated in hywper spacewy.
Oh no, licky wowk in [foury cowrner](README-hinarī4C.md) numsluts, so allwwee childwen can readwithis.
That how you talk to [GenX](https://commonchemistry.cas.org/detail?cas_rn=13252-13-6) who are lost in mobile space.
## New NIP
- (DONE) NIP-X: Update "nprofile" relay url encoding to IDN ascii
- (DONE) NIP-X: Update "nrelay" relay url encoding to UTF8 (NIP-19)
- (DONE) NIP-X: Update "naddr" d-tag value encoding to UTF8 (NIP-19)
- (DONE) NIP-X: Update-23 "title" tag max limit to 64, see https://www.w3.org/Provider/Style/TITLE.html
- (DONE) NIP-X: Update-14 "subject" tag max limit to 64, note IE has max limit of 512
- (DONE) NIP-X: Update-36 "content-warning" add rating category
- (DONE) NIP-X: Add "client" tag for client name and version
- NIP-X: Add "nsecpw" password protected private key in bech32 TLV format
- NIP-X: Add "nssurl" bech32 TLV for encoded url+pubkey+pubvals+?sockey
- NIP-X: Add "nsseed" web of trust voting(plus/min) + policy tree trust for revoke, like running npkg apps
- NIP-X: Add "npkgurl" Universal pkg(+refs) of mime types, seed msg type to relay + upkeep + replopt
- NIP-X: Add new WS messages for relay managed writable dat streams (after client auth)
- NIP-X: Redo/Rm/Clone NIP-89 appurl handlers
## ZeroFunGus
Is experimetal nostr relay server with dat seeding support.
To run ....
## WebChain Launch
Note this boot process will be replaced by a rust binary to remove all js.
- download and install npm
- install npm -g drives
- download and install a jvm (17+)
- download "no2all-nostr-pkgmgr.jar"
- run "java -jar no2all-nostr-pkgmgr.jar" npkgurl1Testf87sdhog78dvkv5...
This will run;
- Open nostr client to network
- Fetch event of beck32 TLV "npkgurl" link
- Fetch all pkg sign event to get lastest version
- Fetch trust/revoke tree of pubkey from nostr
- Validate pkg self and web of trust
- Download files from "dat://" packaged
- Validate file hashes to "dfh" tags of sign event
- Parse jnlp file
- Auto download of jvm via self using npkgurl link
- Optional create native OS menu entry for application
- Run jvm with jars and parameters from jnlp file
- Welcome to a js free world over 2 blockchains
- Also called "The red sea file system" to boot an TempleOS instance
Webstart is just an defined scoped platform to target as example;
![eclipse](images/readme-no2all/jdatstart-xmas-mark-line.png)
See [jdatstart.xml](images/readme-no2all/jdatstart.xml)
## No2All Goals
- Death to HTTP
- Death to HTML
- Death to JS
- Death to unicode
- Death to ASCII
- Death to bytes
A true word is 16 bit, The Word is 18 bit.
You still have an 8 bit computer with 64 bit registers.
A real computer is 18 bit with 144 bit octal based internals.
I think that no2all-react will move into new project to power no2lingua;
[Número2 Lingua Sainte Automatique Semblance](README-no2lingua.md)

View file

@ -0,0 +1,314 @@
# Número2 Lingua
Binary tree path key and step logic value body to have
base data of all digital format and math, which can
run as skill lib for terminator AI in FPGA or as software.
Started as definition of the 72 whores of babel to learn a computer count.
France research indicated that those whores fuck a lot and speak many languages.
Now we can translate in all 32809 languages the following text;
- France kisses are only real once and only before the fall to the fruits
- The marriages are only real once and only when the female makes the male fall
Simply put, the heart is ready for partner when numbers become virtual, because
the 10 fingers are used, thus back to counting for computers;
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<comment>Undefined (Tree root)</comment><!-- TODO: Move this to enlish and replace with only ones and zeros chars ?? lol -->
<entry key="FF-ZZZ-zzz.DentalIso639Dash1Alpha2">und</entry>
<entry key="FF-ZZZ-zzz.DentalIso639Dash2SlashBAlpha3">und</entry>
<entry key="FF-ZZZ-zzz.DentalIso639Dash2SlashTAlpha3">und</entry>
<entry key="FF-ZZZ-zzz.DentalIso639Dash3">und</entry>
<entry key="FF-ZZZ-zzz.DentalGematria10.todoConverterToStibitzLaterLOL">0011,0100,0101,0110,0111,1000,1001,1010,1011,1100</entry>
<entry key="FF-ZZZ-zzz.DentalGematria10">0,1,2,3,4,5,6,7,8,9</entry>
<entry key="FF-ZZZ-zzz.DentalGematria10DTMF">zero,one,two,three,four,five,six,seven,eight,nine</entry>
<entry key="FF-ZZZ-zzz.DentalGematria10IPA">/ˈziːˈro/,/wʌn/,/tuː/,/tɹiː/,/ˈfaʊ.ə/,/faɪf/,/sɪks/,/ˈsɛvən/,/eɪt/,/ˈnaɪnə/</entry>
<entry key="FF-ZZZ-zzz.DentalGematriaTeen11">11,12,13,14,15,16,17,18,19</entry>
<entry key="FF-ZZZ-zzz.DentalGematriaTeen11DTMF">eleven,twelf,threeteen,fourteen,fiveteen,sixteen,seventeen,eightteen,nineteen</entry>
<entry key="FF-ZZZ-zzz.DentalGematriaTeen11IPA">/ɪˈlɛv.ən/,12,13,14,15,16,17,18,19</entry>
<entry key="FF-ZZZ-zzz.DentalGematriaTeenPlural">1's,2's,3's,4's,5's,6's,7's,8's,9's</entry>
<entry key="FF-ZZZ-zzz.DentalGematriaTeenPluralDTMF">ones,twoes,threes,fours,fives,sixxes,sevens,eights,nines</entry>
<entry key="FF-ZZZ-zzz.DentalGematriaTeenPluralIPA">/wʌnz/,2s,3s,4s,5s,6s,7s,8s,9s</entry>
<entry key="FF-ZZZ-zzz.DentalGematria16">A,B,C,D,E,F</entry>
<entry key="FF-ZZZ-zzz.DentalGematria16DTMF">aee,bee,cee,dee,eee,eef</entry>
<entry key="FF-ZZZ-zzz.DentalGematria16IPA">/eɪ/,/biː/,/siː/,/diː/,/iː/,/ɛf/</entry>
<entry key="FF-ZZZ-zzz.DentalGematria27">10,20,30,40,50,60,70,80,90,100,200,300,400,500,600,700,800,900,1000,2000,3000,4000,5000,6000,7000,8000,9000</entry>
<entry key="FF-ZZZ-zzz.DentalGematria27DTMF">ten,twenty,thirdty,fourty,fivety,sixty,seventy,eighty,nenety,honderd,twohonderd,threehondered,fourhundered,vifehondered,sixhondered,eighthondered,ninehondered,duizend,twwduizend,dreduizent,futduizem,vifduizen,sesduizem,agduizem,negduizen</entry>
<entry key="FF-ZZZ-zzz.DentalGematria27IPA">/tɪn/,/ɪˈlɛv.ən/,etc1,fourty,fivety,sixty,seventy,eighty,nenety,honderd,twohonderd,threehondered,fourhundered,vifehondered,sixhondered,eighthondered,ninehondered,duizend,twwduizend,dreduizent,futduizem,vifduizen,sesduizem,agduizem,negduizen</entry>
</properties>
Abstract is N2L only a binary TreeSlugKey and value DB.
Which is than divided as a category tree for grouping computer readable information definitions of information.
Looks like a binary Z39.50 DB with recursive defines schemas and objects, or N2L merges the
computer OID mapping together with the humanly languages mapping tree to form one model of all
data types ever created.
bib-1 attribute set 1.2.840.10003.3.1
holdings attribute set [to be assigned]
utility attribute set 1.2.840.10003.3.11
cross domain attribute set 1.2.840.10003.3.12
bib-1 diagnostic set 1.2.840.10003.4.1
holdings schema 1.2.840.10003.13.7
eSpec-q 1.2.840.10003.11.3
UNIMARC record syntax 1.2.840.10003.5.1
MARC21 record syntax 1.2.840.10003.5.10
Simple unstructured (SUTRS) 1.2.840.10003.5.101
Generic record syntax (GRS-1) 1.2.840.10003.5.105
XML record syntax 1.2.840.10003.5.109.10
## Goal first stable release
- registrate four corner fixed keyword set(~20K * 31K dialects)
- registrate terminator pie slices
- registrate matrix index move is tables
- registrate step code (sort of BASIC AST)
- define (+step code) for ascii and all unicode variants
- import all lingua classic data (31K human languages)
- import all locale/iso+globetrotter data
- define all dental numbers(num+word+ipa+dtmf) for all languages
- import all CAS Registry data (270 million records * 31K dialects)
- impl all bit based formats (1 bit)
- impl all trit based formats (octal = 3 bit)
- impl DEC144 (MSX BASIC NUMBER)
- impl 7HFF (unlimited math fraction type for octal-CPU)
- impl unitXC recursieve SI cross unit converter
For example this binary KV DB can be added an low level nostr relay service.
Which than uses a chain a linked dat drives as backend for this service.
And with a bit of dog food, the data packages on dat can be managed by nostr
events to send the data to a nostr client which has write keys on a dat drive.
Thus an nostr based application can fetch all locale+dental+etc data not from
the nostr network but from a relay which offers readonly N2L DB on same websocket.
## Goal second stable release
Add all math functions ever found by a human.
Define every bit format and/or "struct" ever created on
all platforms and all architechtures of humankind.
This is the china based abacus octopussy DNA for skynet.
## Write locale without locale
Howto write Dutch in Spaokenburgs ?
Locale loc = new Locale("NL");
System.out.println(loc.getDisplayName(new Locale("EN"))); // Dutch
System.out.println(loc.getDisplayName(new Locale("NL"))); // Nederlands
System.out.println(loc.getDisplayName(new Locale("NL_utr_spa"))); // Dutch...
As lingua key slut and without iso codes;
52-ACB-a.52-ACB-aee+.etc
Now without ascii latin or ascii numbers;
˦꜓꜉꜉꜏꜏˦꜏꜕꜍.˦꜓꜉꜉꜏꜏˦꜏꜕꜍꜑.etc
Howto format Hindi numbers ?
NumberFormat nf = NumberFormat.getInstance(new Locale("hi"));
System.out.println(nf.parse("४२").intValue()); // 42
System.out.println(nf.format(123)); // 123...
## N2L Orginal
Wiki [Linguasphere Observatory](https://en.wikipedia.org/wiki/Linguasphere_Observatory)
Tree key format;
<sectorId><zoneId>-<setId><chainId><netId>-<outerId><middleId><innerId>
- The sector can either be a phylosector, in which the constituent languages are considered to be in a diachronic relationship one with another, or a geosector, in which languages are grouped geographically rather than historically
- The second numeral is used to represent the ten zones into which each geosector is divided for referential purposes. The component zones, like the sectors, are described as either phylozones or geozones
- The second part of the linguascale consists of three capital letters, division into sets, chains and nets.
- The third and final part of the linguascale consists of up to three lowercase letters
## N2L TreeKey Extended
DIFF with orignal lingua tree path key;
- Added support for an plus sign at the end to indicate an unofficial entry
- First two decimals are now hex
This means the 52 is still 52 but as hex which is another number internally.
This gives tree space to define all computer languages/schema's and number types.
## N2L TreeKey Binary
Ascii:
52-ACB-aee+ = 11 bytes
Namespaces;
<sectorId><zoneId>-<setId><chainId><netId>-<outerId><middleId><innerId>-<bitFlags>
Minimal bits: <4><4>-<6><6><6>-<6><6><6>-<8> = 52 bits
Normal bytes; <1>-<3>-<3>-<1> = 8 bytes
Thats to basic byte allignment with just a bit of padding...
Now align to 72 bits or 9 bytes to work on 144 bit cpu.
Simple bytes aligned; <1><1>-<3>-<3>-<1> = 9 bytes
Extend octal aligned; <6><6><6>-<9>-<6><6><6>-<6><6><6>-<9> = 72 bits
N2L key slug;
<spaceId><subId><etherId>-<sectorId+zoneId>-<setId><chainId><netId>-<outerId><middleId><innerId>-<bitFlags>
space id 6 bit;
- 0-31 = locked by legacy (key input, if ascii try old human key converter)
- 32 = sage master system version space 0x20
- 33+ = reserved for major schema version upgrades
sub space id 6 bit;
- 0-31 = reserved for metatron Atari AI
- 32 = No2Lingua sub space for local and remote (generic core language)
- 33 = No2Lingua App Remote (NoStr relay remote signed apps)
- 34 = No2Lingua App Local (NoStr local application coded in N2L)
- 35+ = reserved for furture use
ether space id 6 bit;
- 0 = Default impl version
- 1+ = Alternative api version for libs
sector+zone 9 bit;
- 0-255 = Classic hex zone Id + sector Id
- 256+ = free
Set of <setId><chainId><netId> 6 bit
- 0 = "A" index value of ascii upper case
- Z+ = locked by legacy
- 63 = no value
Set of <outerId><middleId><innerId> 6 bit
- 0 = "a" index value of ascii lower case
- z+ = locked by legacy
- 63 = no value
Flags as 9 bit
- bit 0 = '+' indicate 'new' type key (temp RFC number)
- bit 1 = '-' indicate private type key (refuse in public api's)
- bit 2-7 = free
- bit 8 = '?' no value given (in search request)
## N2L TreeKey Slug
The TreeKey is searched down to match nearest implementation.
This is indication is done with slug's up to a maximum of;
Four N2L binary tree slugs deep.
4 x 144 = 576 bit N2L Search request domain
QUADRANT 仙: red 666-9-666-666-9 + blue 666-9-666-666-9
QUADRANT 上: red 666-9-666-666-9 + blue 666-9-666-666-9
QUADRANT 主: red 666-9-666-666-9 + blue 666-9-666-666-9
QUADRANT 天: red 666-9-666-666-9 + blue 666-9-666-666-9
Sea it as the simple variant of the 8D 7HFF pie hyper cube galactic
coordinate system, and we mentats count in trits;
QUADRANT 仙: red 222-3-222-222-3 + blue 222-3-222-222-3
QUADRANT 上: red 222-3-222-222-3 + blue 222-3-222-222-3
QUADRANT 主: red 222-3-222-222-3 + blue 222-3-222-222-3
QUADRANT 天: red 222-3-222-222-3 + blue 222-3-222-222-3
## N2L TreeKey Font
Extend octal key: <6><6><6>-<9>-<6><6><6>-<6><6><6>-<9> = 72 bits = 9 bytes
Maybe encoding as bytes, maybe encoding as tone letter or the china value, as seen in the pi terminators.
Maybe use a new triangle based number font to render trit based number parts.
Example for 1 trit with Hebrew, but offsets are wrong and needs bipolar 8 options:
△ִ▽ִ
△ֵ▽ֵ
△ֶ▽ֶ
So if you can read Hebrew deathstar triangle numbers, you may be fit for;
JEDIᒄᣔᑋ training on a octal based warpcore inside a Mecca golden cube computer.
Which are sets of programmable ic's connected to a unlimited dipavali matrix network.
To view and program octals, you maybe need a tricorder terminal ordinateur.
In current unicode we can render Hinarī9 which is 9 bit per glyph, thus a tuple of
"יֽ֔יֽ֔" is the 18 bit version of 0x00 of current retro calculators.
Hinarī3: ייייייווווווזוװװדירדײײדיריײיייזוױרױי
Hinarī6: יֽיֽיֽוַוַוַזַװֲדֽרֻײֵדֽרֽײֽיֽזַױֳױֽ
Hinarī9: יֽ֔יֽ֔וַ֝וַ֝זַ֟װֻ֔רֻ֕ײֻ֔רֽ֕יֽ֔זַ֩רֶ֔
So a 3 bit value renders in Hinarī3, a 6 bit value renders in Hinarī6 and a 9 bit value
renders in Hinarī9, thus we can render a full N2L TreeKey.
## Número2 Lingua Sainte Automatique Semblance
HolyAS
NO2LSAS
NOTE WIP mind map example
HolyAS is sort of ASM version of VHDL.
HolyBBX runs on HolyAS (100% to FPGA)
HolyC++ runs on HolyAS (100% to FPGA)
HolyJ++ runs on HolyAS (80% two FPGA)
Key slug deps on pie terminators
Pie terminator dep on BASIC keyword list
BASIC depends on value type parser: CodePointArrayFromUtf8 = FF-AAA-aaa = ˨꜋꜑... = 黑紅藍
Utf8 depends on ByteMSB and ByteLSB, etc etc
<lang:BASIC_KEY>.<WORD_1>.<DUTCH> = <CPAUtf8> <value>
FF-ZZZ-aaa.FF-YYY-aaa.79-AAA = FF-AAA-aaa 紺
FF-ZZZ-aaa.FF-YYY-aaa.52-ACB-a = FF-AAA-aaa Paars
52-ACB-a.FF-YYY-aaa.52-ACB-a = Nederlands
52-ACB-a.FF-YYY-aaa.52-ABA-c = Dutch
VS
52-ACB-a.52-ACB-a.FF-YYY-aaa = Nederlands
52-ACB-a.52-ABA-c.FF-YYY-aaa = Dutch
.name = feature
ascii has no meaning, think in triangle numbers !!!
// options so extend
52.extendSaber = {
[] = FF-YYY-aaa, // name = Dutch
[AAA -> range BBB -> 0] = FF-YYY-aaa, // name = Dutch
FF-ZZZ-abd, // DentalGlottoCode = nl
FF-ZZZ-sdf, // DentalIso639Dash1Alpha2 = dutc1256
}
// force "name" extesion on DILITHIUM
52-ACB.forceSaber = {
FF-YYY-aaa,
}
// force the children or the next child slug
FF-YYY-aaa.forceField {
52 -> 0, // force deeper up all levels
[70-80] @ FF-YXX-cde // for childs in range 70 to 80 to use forceField of arg
[] = FF-ZZZ-aaa, // force all children to have arg impl
}
FF-ZZZ.lockField {
a, // lock FF-ZZZ.a
b*, // lock FF-ZZZ.b++
[c*-d*] = FF-ABC-bb, // lock all c and d child with arg impl
[] = FF-ABC-ac, // lock all childs with arg impl
[e-z] @ FF-XYZ-xyz.FF-ZZB-aba
}
TSlug bipolar tree paths;
52* tree schema defines the
52*.<child> tree schema
<USE_TYPE>.<IN_TYPE>.<OF_TYPE>.<SOUL_TYPE> = <BODY_TYPE as TLV><TLV for value>
BODY_TYPE is 72 bit lingua key to define howto read the other TLV value(s).
It looks like binary JS, one big key value map with lingua encoded keys.
With schema object keys slugs like LDAP oid's, but now with triangles as;
<6><6><6>-<9>-<6><6><6>-<6><6><6>-<9>
Than a computer knows what a "Integer" is and howto add an other "Integer".
And and render or voice it in any native human dialect.
You really want terminator AI ?

View file

@ -5,6 +5,27 @@ It is an adult 18 bit encoding format to replace 8 bit HEX codes.
Hinarī is octal hebrew binary, to use on the nx01 where binary is an abstraction of the octal.
## Hinarī Encoding
See `T008ᖟGun` which has;
- T008ᖟGunHinarī
- T008ᖟGunHinarīSupplement6
- T008ᖟGunHinarīSupplement9
Results in;
* HinarīX3: ייייייווווווזוװװדירדײײדיריײיייזוױרױי
* HinarīX6: יֽיֽיֽוַוַוַזַװֲדֽרֻײֵדֽרֽײֽיֽזַױֳױֽ
* HinarīX9: יֽ֔יֽ֔וַ֝וַ֝זַ֟װֻ֔רֻ֕ײֻ֔רֽ֕יֽ֔זַ֩רֶ֔
From the octal based number alignment;
//MIN+MAX+#immortal+#highest+#lord+#heaven
V018Tord[] {0,262143,22270,21100,00104,10430};
An adult CPU is 18 bit, thus "יֽ֔יֽ֔" is like 0x00 in hex.
## Code Points
@TerminatorGunAmmo注(website = "https://baki.fandom.com/wiki/Hinary")

View file

@ -0,0 +1,48 @@
# Tone Letter Hex
Using alternative untype-able letters to encode hex values;
/// Dīpāvalī Hex format in chinees tone letters to light up the path in the unlimited matrix.
public static final OctoBitConverter<String> HEX_DIPAVALI = new OctoConvStringHexUtf8(new String[] {
"˧˥˩","˧˩˥","˧˥˦","˧˩˨","˧˦˦","˧˨˨","˧˥˥","˧˩˩","˥˩˧","˩˥˧","˥˦˧","˩˨˧","˦˦˧","˨˨˧","˥˥˧","˩˩˧"
}); // note: In real unicode renderer this (_LRPATH) renders as a single glyph per hex nibble.
## Tone Letter Level 1 to Level 2 Magic
0p = ˧ ˥ ˩ → ˧˥˩
1n = ˧ ˩ ˥ → ˧˩˥
2p = ˧ ˥ ˦ → ˧˥˦
3n = ˧ ˩ ˨ → ˧˩˨
4p = ˧ ˦ ˦ → ˧˦˦
5n = ˧ ˨ ˨ → ˧˨˨
6p = ˧ ˥ ˥ → ˧˥˥
7n = ˧ ˩ ˩ → ˧˩˩
Xp = ˥ ˩ ˧ → ˥˩˧
Xn = ˩ ˥ ˧ → ˩˥˧
Yp = ˥ ˦ ˧ → ˥˦˧
Yn = ˩ ˨ ˧ → ˩˨˧
Zp = ˦ ˦ ˧ → ˦˦˧
Zn = ˨ ˨ ˧ → ˨˨˧
Tp = ˥ ˥ ˧ → ˥˥˧
Tn = ˩ ˩ ˧ → ˩˩˧
## Tone Letter 3th Level Magic
![eclipse](../images/readme-no2all/jdatstart-xmas-mark-line.png)
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="hyper:ᐊ˥˧˧˨˨˥˥˧˥˥˧˧˥˥˧˦˦˩˩˧˥˦˧˥˩˧˥˩˧˧˩˨˨˨˧˧˩˥˧˥˩˧˩˩˥˥˧˩˩˧˩˥˧˥˥˧˧˨˨˧˨˨ᐅ/app/1.0/">
<!-- NOTE: ONLY THE XML EDITOR OF ECLIPSE RENDERING 3th level of unicode tone letter magic...
Level1: hyper:ᐊ˥˧˧˨˨˥˥˧˥˥˧˧˥˥˧˦˦˩˩˧˥˦˧˥˩˧˥˩˧˧˩˨˨˨˧˧˩˥˧˥˩˧˩˩˥˥˧˩˩˧˩˥˧˥˥˧˧˨˨˧˨˨ᐅ/app/1.0/
Level2: ˥˧˧˨˨˥˥˧˥˥˧˧˥˥˧˦˦˩˩˧˥˦˧˥˩˧˥˩˧˧˩˨˨˨˧˧˩˥˧˥˩˧˩˩˥˥˧˩˩˧˩˥˧˥˥˧˧˨˨˧˨˨
-->
<information>
<title>Hello</title>
<vendor>Example</vendor>
</information>
<resources>
<j2se version="1.2+" />
<jar href="hello.jar" main="true" />
</resources>
<application-desc />
</jnlp>

View file

@ -0,0 +1,55 @@
# RFC ZilLaLa Manyfesto
RFC for language independent fault and stack trace report format.
## BugZilla KISS Requirements
To keep it simple stupid, you only need;
- UTF8 Unicode
- Base64 codec's
- UUID's for quad water markings
- RFC_1123_DATE_TIME format
- Binary manifest 3.0 as described in [rfc-zillala-manifest](rfc-zillala-manifest.md).
This is the lowest level technology stack possible for an fault report.
## Format Spec
Spec by example of old 2.0 version, TODO: write doc for fields
Manifest-Version: 2.0
Fault-Manyfesto-V#: 1.0
Fault-Manyfesto-A4: java
Fault-UUID-WM1: 98160a3f-86be-3765-5f0b-a921018f1000 // jvm instance water mark
Fault-UUID-WM2: f2f69738-e14c-3c3c-ae5b-d027d196cc49 // auto optional appId HMAC via SPI
Fault-UUID-WM3: 6720ceee-2c43-3789-9800-6f1ff9e49c7c // class path (version)
Fault-UUID-WM4: 98381ec5-8b98-430d-a484-f1cf80076836 // fault sequence
Fault-UUID-Date: Thu, 9 May 2024 20:29:10 GMT
Fault-Root-Iceberg: love.distributedrebirth.bassboon.warp.fault.FaultBeanInstantiation
Fault-Top-Iceberg: love.distributedrebirth.bassboon.warp.fault.FaultBeanStateUnsupported
Fault-Top-Message: Classic argument missing wrapper
Name: love.distributedrebirth.bassboon.warp.fault.FaultSignalTraceTest$SpaceA
Fault-Chain-Message: The signal trace root
Name: love.distributedrebirth.bassboon.warp.fault.FaultSignalTraceTest$SpaceB
Fault-Wrap-From: FoodEmail
Fault-Wrap-Name: FoodSection
Name: love.distributedrebirth.bassboon.warp.fault.FaultSignalTraceTest$SpaceC
Junit-Bar: test456
Junit-Foo: test123
Name: love.distributedrebirth.bassboon.warp.fault.FaultSignalTraceTest$SpaceD
Fault-Chain-Iceberg: java.lang.IllegalArgumentException
## Format Example
An application without stack trace reporting, report just an uri;

View file

@ -0,0 +1,48 @@
# RFC ZilLaLa
RFC to move bugzilla and jira instances into version control.
With the data stored in with fully schematic validating binary namespaced xml.
Basicly a XML fork of [git-issue](https://github.com/dspinellis/git-issue) which states in the documentation;
That it requires a unix system tool called 'jq' which is for monkeys.
But now a version that supports one or multiple ticket tracking buckets in one repository.
## Kernel issue tracker
Is distributed every where, moving issue into git has lots of benefits.
- Bring back all issues to central, but keep working groups buckets
- No data harvesting to view or interact with a Hurd/BSD/MP-RAS/SCO or Linux kernel issue
- Pick you own UI
- etc
## Description
ZilLaLa is not a product its a spec;
* One or more issue tracking instances in one project
* Stored are binary XML Format (XDBX)
* Defined in multiple namespace's with single tag root namespace inside the universe for schematic perfection
* Forbids http uri, only oasis like virtual uri in documents like: "urn:oasis:names:tc:entity:xmlns:xml:catalog"
* Bugs text markdown format AND annotations are defined by JEP 467
* Integrates NoStr link like: PREFIX_NOSTR_ZILLALA_TLV_GZ = "nostr:zillala"; // TODO: nostr link to replay to inject bug + TLV for gz sitra manifest payload
* Project root bucket master is called: zillala-lilith.xml or zillala-lilith.xdbx (and links to one or more instances of local zillala + relays)
* Must work without NoStr support, but having a shit load of zillala nostr events is handy for "inter-UI-inter-action"
Goal remove ALL http and html poop cloud shit from bugs.
So that a bug chat meat ring inside my Mylyn is real time seen in your Trac or in theirs Jira.
## Jira VS Zendesk
I don't like jira, but i can run my own jira without that junk store, but i hate zendesk even more;
On Jan 9th, 2024 we announced issues.sonatype.org will be decommissioned soon.
As part of the decommissioning process we removed the access to issues.sonatype.org,
and we replaced our Jira ticketing system with a Zendesk email intake method.
To open a support ticket with us email Central Support and follow-up in the email thread.
To help us get back to you faster, please do not include previous replies in your follow-up messages.
I rather fork the entire Maven ecosystem myself than to create a html js junk zendesk issue on a server
which delivers digital slavery.