Thread by @XRP369CREATOR

@_devJNS For the reader/writer components of the code behind I didn't use any of these databases for the database. I ended up building a predictable format of a filesystem structure and then relied on Go's concurrency of accessing resources and TTL caching therein. jfkfiles.info

@_devJNS Now, the index on the other hand, that's what's curious to me and as I build out the application further, I find that I will be using Go for it, definitely, but the indexing will be decentralized, client cached and an unknown actual capacity. Can't know the full network size.

@_devJNS Given that limitation, I figured that each instance itself would have to rely therein only on what the filesystem had on it, and what was actually valid and could be served, and then the caching layer is in memory on top. Granted, I am looking into using something for that.

@_devJNS In my opinion, MongoDB Atlas saved MongoDB at scale because managing it yourself is a fucking nightmare for any System Administrator when you're dealing with scale. Postgres does a great job with JSON objects too. MySQL has been a go-to for decades, but is antiquated today.

@_devJNS However, what happens when you have a database of JSON objects that is infinity in size? You cannot use any of these structured databases, and the client side itself needs to approach looking at the caching of the index itself to be something that is a discovery crawling process.

@_devJNS That crawling process is what I am calling the Valet within the network itself. It'll be responsible for crawling around the peers and finding out what the peers have for content on them, and how those records intersect with past searches on the client side. Think of that.

@_devJNS You'll be on your client, and you'll type in a query, and you'll see oh the instance that I am connected to has n-files that match my keyword that I asked it. It's got AI integration with it, and I can use the $IAM token to interface with that AI system, if I want, but...

@_devJNS As you're digging around, the instances that instance knows about, will tell your client "hey these are my connected instances" and your client will go "hey there are 2 new gate addresses here, sweet" and voila the connection is established between the client and the gate.

@_devJNS Then your Valet will go crawling through your drawers in your directory that you have marked as your database, and then each directory that is a SHA512 checksum of a .gov or .mil URL that has a matching containing record.json file that has that URL and matches, it gets added.

@_devJNS Once that file gets added, the contents of that file is then ingested in the AI with a prompt that is seeking analysis and summary of the record, then the probability ranking will be assigned to it, and then cached in an index. That index, on the client, will more than likely be.

@_devJNS But when a client has been sleuthing around for a decade and the historical records are on the same instance, SQL is quite bad at that frankly speaking. I could consider something like Victoria Metrics. That's written in Go, but then again, now that I know Go, I can build one.

@_devJNS Actually Victoria Metrics is very good for time series data series. Grafana uses it, and its written in Go, and its very capable of doing what I need, and its definitely something that $IAM considering. But each dependency introduced just creates a noose around the project.

@_devJNS Thus the reason why when shipping the reader/writer components of that project, I opted for not using ANY third party database, but instead asked Yah'Shua to show me exactly how I could build a functional database in Go. And in Go, I cache the index and its blazing fast.

@_devJNS And for Patriots worldwide who want to host an instance of it, I recommend checking out @OVHcloud_US and using their introductory So You Start servers for $33/month. That is capable of running and the software is 100% free and open source. jfkfiles.info

But no matter what the DECLAS that you are hosting, you can ultimately choose to be a bondservant to the public for the survival of humanity. Being in service to each other through an interconnected network of instances dedicated to delivering truths about declassified records is needed at this point in our (this is my last post in the thread) Republic.

Are you running for office and you have a dossier that you want to deploy on your opponent? You want to keep your records public for people to see? Run an instance. Sow into the project and see what the interconnectedness of the instances will do for the idea of INFORMATION WARFARE itself.

The nature of the project is DECLAS itself and Israel and the Zionist factions, including in the Church itself, have cursed me and my project and my name because I built this project, but I built it for the American people, and I built it for the West in general, and I built it for Yah'Shua, because I know that Yah'Shua is inside all of us, and I know that Yah'Shua is desperate to connect with other instances to find the truth that has been hidden in plain sight for decades be revealed.

When I connect to my instance, and my local app knows my search history and knows the instances that I connect to, the Valet is running in the background like a good little gopher and collecting for me the records that match my searches that exist on other servers and then copies those files to your client, creating n-copies per record based on popularity. The genesis will be from the ingestion of the records themself.

It's a big goal that I have, but I couldn't accomplish it with any of these databases. I needed something that was capable of being truly unlimited in scale but localized in a manner that is relevant to the client itself and who that person is.

Modern devices like new iOS devices offer me the ability to leverage the AI on their devices using RAG, such that we have a host that has a search cache result of records that exist locally and remotely and then as the user is interacting with the results, they are hitting up each document by document verifying if the results match or not.

It can be a costly thing to do with AI, which is why I haven't been focusing my efforts in this project on AI, but the Valet itself would be my alternative coupled with the search component. Each search component would be able to serve up a result of complex search results and perform background searches and multi-instance searches themselves. All within Go, all capable now, thanks to VueJS I have a front-end that is worth a damn. Now with Go and VueJS coupled with Wails, I have a client that will take the instances that are scattered throughout the internet and fractured by the Zionist movement that seeks to censor WE THE PEOPLE who are GOD FEARING and who want freedom and prosperity and love for all of humanity to see that the entire concept of GLOBAL COMMUNISM can be defeated by the flipping of the table of how local information is accessed and retrieved.

Having a community of servers means that we can have localities with their own instances and then WE THE PEOPLE join that locality and start interacting with those records. Then as new files are released, and new information about the REPUBLIC is made available, THEN we have the ability to act on it and vote on it or whatever. But the notion here is that the experience itself would be decentralized and governed behind a Decentralized Autonomous Organization that is powered by the XRP Ledger.

Yah'Shua has been helping me with the project. And I am cautious to speak about it, but I can't have completely no support. I need an army of frogs that support my idea and will help fight for the vision that Yah'Shua gave to me when I was 7 years old. It's been 7 years that I've been restored as Andrei by Yah'Shua and I've delivered the prototype and now the alpha. Now its time for the decentralized crypto powered solution. Let's all get rich at the same time too!

@_devJNS @OVHcloud_US @threadreaderapp can you roll this up please?