Good Morning NOSTR Enjoy free speech while your parents aren't here Soooo, i did it, currently i am undergoing heavy testing to ensure no memory leakage and graceful shutdowns then after that i will hold a comparison between IDB and OPFS versions to see which is more suitable for the final product Anyway, the next step in building a strong client foundation is a Global Strings Dictionary What is that good for? 1- every single chars sequence will be Log(n) searchable 2- a string will never be stored twice (all 'GM' notes will be stored as a single string "GM" and the Global Dictionary job is to map it to where it appears) Why so ambitious? technically if you have a strings search dictionary you already achieved the compression part (zero storage redundancy) i am imagining something like a radix tree

Radix tree - Wikipedia

but a global one where any underlying result is a subtree of categorized results View quoted note →

#Fuck_the_jews

i was wondering why this neat clean service I've been using stopped working and yes i found the "project is fucked" stamp right there

#Fuck_the_jews

#devs we can make that reliable View quoted note →

Real Da'aua content 👇 View quoted note →

For who ever felt offended I am totally ready to debate any "Mother FUCKING" being I AM A FULL QURA'AN NODE MF I know more than you know More than the bangali who thought you Islam know Bring it on useless goy View quoted note →

Islam in a nutshell: As much as Hashim is a Saint, a Sacred to me I can't force Hashim on fellow Muslims AND THATS THE ONLY FUCKING POINT FUCK KHAWARIZMI FUCK MOOAWIYAH FUCK BUKHARI FUCK MUSLIM FUCK IBN TAYMIAH Only GOD IS SACRED NOT A SINGLE "MOTHER FUCKING" Being can revise our contract with GOD View quoted note →

Budah isn't real, Hashim has way a much proven history than budah Hashim was a perfect goy Saint Murdered by FUCKING JEWS ODELL cousins, GIGI cousins and simply JEWS View quoted note →

Evan "something" - "Evan" is a name constraint to jews and Bastards View quoted note →

I was about to start my live stream about The Continuum but WTF is that good for when you can't stop memorizing about #Hashim

#Fuck_the_jews

the Goys know... View quoted note →

That incident going by unnoticed is the most disappointing thing about this space It's like we are just another NPCs space View quoted note →

Who remembers when Jack Dorsey sponsored Bluetooth mesh chat to be used in Iranian protests? Back when Trump and Natenyahoo claimed to be able to flame Iranian protests

OpenSats the Mossad Office of this weird part of the internet View quoted note →

Continuum's backbone structure is at final development stages tomorrow session will revolve around reducing redundant writes back story: -Project Definition Continuum is a browser environment ordered-array-virtualizer, you store an array on the disk then Continuum single job is to retrieve only consumed items without having to load the whole array into memory The Current Drama: -IndexedDB can't do Positional Access the classic b-tree structure powering IndexedDB can only do O(m*k) positional access, like linked-list but worst, so in order to access arr[50] where arr.length is 100 we can only start at either arr[0] or arr[100] then do a O(50*k) to reach arr[50], otherwise, we must keep an in-memory array of all addresses (b-tree keys) in-memory beforehand to achieve O(1) which defeats the propose, also the newer and 10x faster OPFS api doesn't have a native b-tree, its a pure file system so we would need to DIY our own b-tree on top to use it. -Evidently, Continuum needed a DIY Positional Access structure (better known as fancy-ranked-something-something-fancy-trie) by which we solve the downfall of IndexedDB b-tree and also enable us to power the Continuum with the faster OPFS api by that we can have Continuum backbone as an independent core and treat the underlying storage api's (OPFS or IndexedDB) as plug-ins View quoted note →

#Fuck_the_jews till who knows who's

#Row_jews View quoted note →