Tho i wanted to open source the tool (spend ~10 years developing it) and thats just not an option.

Don't wanne self advertise here , but for the sake of better understanding if you want to know the details you can read them here: https://blog.laughingman.dev/article/Ishikawa_10_years_of_bu...

This laws, while i wanne say have a good intention, just do the opposite...

I myself, residing in germany, developed a recon/vuln/scanning tool that im legally forbidden to publish cuz of the laws you just mentioned.

Comments URL: https://news.ycombinator.com/item?id=48107065

Points: 2

# Comments: 0

I have no public sources yet (will come at some point) but ill try to break it down into some simple points. After all: this is a research project.

Project: DeepThought

So instead of going for the path to take bigger and bigger models to solve more complex questions, i going another direction. My idea is to use LLM's in a way like an "inner monologue" to replicate a thought chain. Basically create thinking steps that can be dynamically chained.

Additionally, the project contains a 3 layer memory system which is parted into:

1. Frontbrain (this data composes the context for inference, its a set of "hot nodes" which have a temprature that per turn of conversation will cool down a bit, while if they are used in a "thinking process" get warmed up a big again. The idea is to have the context for the inference to only get the currently relevant information, while dropping of things that lost relevance. This should prevent context overflow

2. STM : Basically a session memory. This will keep all information from the current session even if they got to cold and dropped out of Frontbrain

3. LTS : LTS is always query'able for the thought process to retrieve information/structures, but only at the sessions end information is propagated from the STM to LTS. This makes identification of "unique" entities alot easier and has some other advantages.

So when you type something into the DeepThought engine, it will extract all information from your input and convert it into a kinda 2 type structure 1. A bitemporal hypergraph composed of Entities and Hyperatoms. While entities i think are kinda easy to grasp, hyperatoms can either represent "properties" (in form of facts) or relations to other entities. This allows to create a graph structure typed information network containing the relevant information

2. Frame summaries. Since only having a structured graph as just described looses a lot of processual/logical information which are relevant especially in more complex contexts, i also create basically short summary texts that are linked to entities.

This structures allow me to use dynamic graph traversal for searching for data, while also retrieving the related Frame summaries that are a more native variant for an LLM to understand logics and relations.

This is a very very superifical explaination because to go into detail would take quite prolly multiplage pages of info.

Important: Im running this on a local 5090 and it is NOT friendly in terms of amount of inferences (which is fine for me). I try to mimic a thought process not build a fast shipping product. Quality > quantity. If you would run DeepThought on any online inference provider your broke in 1 day.

So, rn i focus on the ingestion and retrieval logics to make storing and retrieving as good as possible with my hw options.

While the ingestions already involves multiple steps in which the "llm" basically works as judge to decide where to traverse in the graph, where to go into recursion and similar, this will become very relevant as soon ill start implementing "task execution" as capability.

If i solved those the next point is to reduce everything that i need in terms of thinking steps in what i would call "thinking primitives". The idea with those is, that i dont want a hardcoded thinking process, but it rather also want to have the thinking process in form of a graph structure. This would allow me to compose the process in form of data in the hyepergraph, which would in return allow me to enable the system to refactor/enhance its own thought processes.

So ye thats what im working on rn, very early concept/alpha phase.

When I referred to "such regions," I was personally referring to a combination of factors: infrastructure, supply chain consistency, reliability, and the general political situation. In this case, I would argue that poor infrastructure impacts transport and storage control when it comes to shipments. Supply chain consistency (even with organizations like UNICEF) is often not guaranteed; local partners change frequently, often influenced by the local situation, making it nearly impossible in some regions to maintain trusted chains. Reliability suffers because of these factors—when it is hard to maintain trusted partners, the problem persists. As for the political situation, I don’t believe I need to elaborate further.

So, when I say "such regions," I mean areas that fit this basic pattern. While not a perfect comparison, a notable example of this is when food supplies sent for civilians are intercepted by local armed groups. The supplies might reach the target location, but they do not always feed the people they were intended for. As you work in this area, you likely know this is not an isolated occurrence.

I am also not from the US, and I cannot speak specifically to the Sudanese American Medical Association. If they are truly creating change, that is a great thing, and everyone is free to donate to them. You will not see me advocating against donating to them.

Regarding your question on why I think you would send aid even if diversion was likely: I don't believe you would willingly fund "warlords." Rather, I believe that in high-risk regions, the intent of the donor doesn't always control the reality on the ground. My skepticism isn't a critique of your virtue or your specific organization, but a reaction to a historical pattern of aid diversion in volatile zones. You do this work because you believe the collected money will reach its destination and will not be abused, and I respect that you follow your beliefs for the "greater good."

You seem to be a good person doing important work, and to do that, you need to believe in the efficacy of your mission.

Lets go for the optimistic scenario in which UNICEF will only take a very small portion for the "processing" and really deliver lets say food and medical supplies to the region. Those warloard will simply come and take it away from those citizens and provide to their armies. Theres nothing those citizens can do against it.

Do i wish it would be different? Absolutely. But sadly the world doesn't work as i would wish it to.

Yes helping is a good thing, tho reality is its not as "easy" as transfer some money. Tho respecting your good intentions

I wrote my own in-Memory Graph (i'd rather call it storage than a DB) some years ago in golang, even there i was wondering if golang actually is the optimal technology for something like a database especially due to the garbage collection/stop the world/etc. Its just there are certain levels of optimization i will never be able to properly reach (lets ignore possible hacks). Looking at a solution in typescript, no matter how "nice" it looks, this just doesnt seem to be the correct "tool/technology" for the target.

And inb4, there are use cases for everything, and same as i wouldn't write a website in C, i also wouldn't write a database in javascript/typescript.

I just would argue this is the wrong pick.

@llms : im not even getting into this because if you dont wanne read "llm" you basically can't read 99% of news nowadays. ¯\_(ツ)_/¯

edit: im a big fan of graph databases so im happy about every public attention they get ^

therefor decided not gonne use any llm for blogging again and even tho it takes alot more time without (im not a very motivated writer) i prefer to release something that i did rather some llm stuff that i wouldnt read myself.

Big props on the no install / no register etc philosophy. If i would had to make any account i probably would have closed it instantly again xD

So the first thing i STRONGLY recommend, add somewhere a help text (before starting game or small on the side of ingame and ability to disable via options) for the controles.

Im on a Desktop, i started the game and i expected some sort of short info about controles. Yes theres a tutorial - no i didnt play it. I mean lets be honest... tryNSucceed :D

So ye i spend the first 2-3 Stages only spamming spacebar because it didnt came to my mind that maybe its with mouse support (visually it really hard compares to vs-likes that dont support mouse).

So i can tell - ice mage with just massive rapid space spamming works perfectly fine through the whole earth stage. ^^

I find the base look finem the overview texts for the different arch types is well done (even tho it confused me that fire and ice dont have weaknesses?).

The point that at least for me was the most well, unpleasent? , is the size of the play area. I guess you made this to fit easy with smartphone screens, but on a desktop its like not even 1/4 of my screen (and im not on 4k or something) so dunno it feels just alot to small. May fit for a smartphone but for a desktop its just very very limiting while the game takes alot of space for basically nothing.

Also, you definatly should have a "Settings" button in the game pause menu which allows for changing sound levels. Not just a "total sound" bar but at least have Music and Sounds (attack etc) seperated. Because, frankly speaking, the music while for the first like 30 seconds is cool, very fast is dunno it just would fit more to the entry video scene of something than as a constant thing (my pov) - so i wish i would be able to just disable the music and still have the attack/battle sounds. Adjusting both tho would be great anyway and i think with phaser should be quite doable.

A smaller point (visual) is the size of the health/mana bars. Even tho i know they are in the top left, i kinda have to squeece my eyes sometimes to see them. So i would probably just make them bigger.

That all said, i mean i just played solo till the fire stage :) and i clearly had a bit of fun.

I would say its a great start and if you go on and refine it i see a chance that people might pick it up as a nobrainer lets just game something solution :)

Best of luck !

- golang based architecture

- information is dynamically mapped into one central directed knowledge graph

- default multithreading

- utilizes existing tools (such as nmap/nuclei/katana/wfuzz/....) instead of reinventing the wheel

- architecture is (tldr) a self supervising logic in which every worker is also a scheduler that based on delta causality uses cartesian fanout and graph overlay mapping including local only witness nodes to dispatch new "jobs" without having a central scheduler or the necessity to scan a central total job queue to prevent duplicate executions.

In this architecture every "action" that can be executed defines an input structure necessary. If the previously mentioned mechanic identifies a possible job execution it will create a job input payload which will automatically be picked up by a worker an executed. Therefor every action is a self containing logic. This results in a organically growing knowledge graph without defining a full execution flow. It is very easy to extend.

I worked on this for the past ~10 years (private time). The sad truth tho is, while this project was initially planned to be open sourced - after i not to long ago for quite some bucks consulted a lawyer, i basically was presented with the fact that if i would publish it i could get sued due to germany's hacker and software reliability laws. So for now its only trapped on my disk and maybe will never see daylight.

Im right now working on a blog article (thats why i even mention it) about the whole thing with quite more detailed description and will also contain some example visual data. Maybe will post it on hackernews will see.

PS:The tool does not need llm/nn.

Very nice article - good read !

Big props for the creators ! :) Nice to see some others not just relying on condensing a single context and strive for more

If its actually the next big thing im not 100% sure, im more leaning towards dynamic context windows such a Googles Project Titans + MIRAS tries to accomplish.

But ye if its actually doing useful proactivity its a good thing.

I just read alot of "this is actual intelligence" and made my statement based on that claim.

I dont try to "shame" the project or whatever.

I don't say it doesn't "work" or serves a purpose - but well i read so much about this beein an "actual intelligence" and stuff that i had to look into the source.

As someone who spends actually a definately to big portion of his free time researching thought process replication and related topics in the realm of "AI" this is not really more "ai" than any other so far.

Just my 3 cents.