All Activity

COMING SOON. The SVG logos have been attached if there are any graphics designers who want to take a swing at the Phoenix and clean it up a little bit. I'll get to it when I get to it. I want to fix the gradient but I need to adjust the underlying shape as it has about 300 points on it that are quite tedious to move around. phoenixvault_new_logo_thin.svg phoenixvault_new_logo.svg

Take this, table it. Proposals are part of the decentralized apario-reader, but with the introduction of the $APARIO token, the details of what Proposals are will change with the tokenomics. That being said, the idea of Reputation is to 1) be required to earn it and 2) use it to contribute to the common good. When leveraging the $APARIO token, there is the market/free trade aspect and there is the mission/purpose aspect. They are not mutually exclusively to each other. The market/free trade can be used for the supply of tokens to apario-reader service providers in a demand driven nature of supplementing advertising spending for $APARIO AirDrops (more to come). However, Proposals are the way the community will maintain the integrity of the network and contribute upstream to the apario-reader.

Since this post was TO BE CONTINUED, much has passed since this was initially announced and I have spent a lot of time reflecting on the ideas presented here. This community forum is the development center of the $APARIO and decentralized PhoenixVault; so anybody who wishes to get in the action, can do so by becoming a member of the forums, forking the repositories on GitHub or GitLab and submitting your pull request. These forums are designed to help onboard you to the technicalities involved in the project. Since the $APARIO token was launched on the XRP Ledger, I feel like that I should use that for the central authority to the Apario License Manager, rather than relying on my own database that I have to maintain. The GPG signing key will still be used, but I will update the process accordingly since the idea of the application is to truly run in a decentralized manner; and binding a license server to it with a /valet endpoint seems to be a misguided communication on my part. I want to clarify it. When a new instance of the apario-reader is going to get launched and connected to the XRP Ledger, the administrator of the instance will be required to do a few things before they can fully leverage their instance. This is going to be a new NFT that will get minted when new instances of $APARIO connected instances of apario-reader are introduced. This connects the disconnected. Since each instance of apario-reader only represent a small fraction of global OSINT, you may end up doing research on 10 instances across 10 domains of interest. When using the decentralized apario-reader on the $APARIO token, you'll be able to leverage the /valet search service to conduct searches across the decentralized network itself, thus leveraging the XRP addresses of who owns the NFTs thus knowing the total strength of the decentralized network. The minting process will involve a fee of some type. I am unsure what I want to charge for it, but most of the work that I am doing is in the form of charity, and the payment would be to conduct transactions on the XRP Ledger itself in preparation for your instance. I am going to call the XRP wallet that must be connected to the apario-reader itself the Instance Wallet. What will happen, when an apario-reader is connected to the XRP Ledger, a button will show on the interface with Connect Wallet that will present a QR Code for you to scan with the Xaman app or the Sologenic app. Then, your XRP wallet address will show up in the instance and your balance of XRP and APARIO tokens. If you haven't set the APARIO TrustLine yet, it'll guide you to setting it up. It'll require 0.2 XRP in order to reserve the APARIO TrustLine on your wallet in order to receive APARIO tokens. Currently we have over 540 TrustLines connected providing over 116 reserved XRP for the token. Like the reserve balance being reduced from 10 XRP to 1 XRP for new accounts, so too will you see the 0.2 XRP reserve fee for TrustLines changed in the future. Ripple won't like having a 0.2 XRP reserve fee on a TrustLine when the cost of XRP is $589 and your spending $117.80 to hold tokens of any kind of the XRP Ledger; this will change. Currently its 0.2 XRP when its $2.29 XRP; thus only $0.458 to add the $APARIO TrustLine. Nevertheless, you'll need to be on the $APARIO TrustLine in order to use the Connect Wallet functionality. When new instances of apario-reader are created, an NFT is going to be minted for your instance. It'll include some information such as: The URL of the instance. All URLs will be https://*.apario.app where the * is your instanceName. The XRP Wallet address that will issue $APARIO tokens on the instance. The name of the collection; such as "Minnesota Election Selections" or "DIA Project Stargate" or "JFK Assassination Files" A description of the collection (up to 255 characters). Contact Email Address (will be signed in the XRP ledger - for long term use) Your ED25519 Public Signing Key used by your instance Your GnuPG Public Encryption Key used by your instance X/Twitter Username Attestation under penalty of perjury that all conduct conducted on the instance will be lawful under the United States Constitution in the form of a digital signature signed with your ED25519 Public Signing Key. In order for the Connect Wallet service to interact with the Xaman app itself, you'll need to provide to the config.yaml your own Xaman Developer Console API Key and API Secret in order to generate signed QR Codes that the Xaman app can scan and use for transactions. When connecting your apario-reader application to the XRP Ledger itself, you'll need to provide the application with a wallet address and secret family seed. This is required in order for the apario-reader to send $APARIO tokens to XRP Wallets that have the APARIO TrustLine established. Then, when transactions take place on your instance, such an NFT is minted for proposal or an award of $APARIO is transferred, the XRP Balance of the Instance Wallet is used; therefore when a new instance is being setup, the 369 RLUSD when converted into XRP (at $2.29 XRP) comes out to around 161.135371 XRP. 25% (92.25 RLUSD as XRP) will be transferred to the Instance Wallet 25% (92.25 RLUSD as XRP) will be deposited into the APARIO/XRP AMM Pool as the APARIO asset 25% (92.25 RLUSD as XRP) will be deposited into the APARIO/XRP AMM Pool as the XRP asset 25% (92.25 RLUSD as XRP) will be used to buy 3M APARIO and transfer to the Instance Wallet, remainder stays on the apario.xrp wallet for future developmental use. Regardless of the competitive nature of the APARIO token, if 92.25 RLUSD isn't enough to acquire 3M APARIO tokens, by virtue of this transaction, I'll provide the difference in what the market cannot provide for the 92.25 until my supply of 170M APARIO have been expelled. That should provide me the means to spot 56 instances when the time comes. Because there are 699M APARIO tokens in circulation, you can divide 3M tokens per instance by the 699M and you get 233 instances of Apario Reader in the decentralized network. When we get to 233 instances of the apario-reader connected to the $APARIO token, the trading price of $APARIO will be much higher than 1 XRP ⇄ 1.3M APARIO ; and as such, these numbers will change. Just as the XRP Wallet Reserve Balance changed from 10 XRP to 1 XRP, so too will, down the road, the 3M initial APARIO tokens change down to 369K APARIO tokens; bringing the number of instances close to 1K. Currently we have 3. We'll need another 230 before we even have this conversation. I have no idea what the APARIO token will cost when we have 230 instances online... let alone 233. When we have 2,000 instances of apario-reader, the $APARIO token will be in demand and the fractional economy behind the XRP Ledger will empower wallets of any size to connect to the network; however in the beginning, as we're getting the network online, we're going to keep with the figures that I've come up with. Unless you have a good reason otherwise. Thus, to conclude this post on the LICENSE component of the apario-reader, it'll leverage the XRP Ledger itself to validate the license. It'll use the NFT to verify ownership and issuance from the apario.xrp wallet. I'll use the initial 369 RLUSD fee to fund the AMM liquidity pool for your instance, seed your instance with XRP and APARIO tokens, and grant your license by signing your NFT's JSON payload with my GPG Private Key associated issued to license@apario.app. The apario-reader application will be updated accordingly to verify the license. If the instance is booted with an invalid license, it'd mean that the NFT owned by the account does not match the domain name issued in the config.yaml. The issued NFT has properties that must be set in the config.yaml in order for the NFT to work. As it stands, the on-boarding process for the apario-reader and apario-writer are exceptionally high at the moment, and that's because it's a one man shop at the moment. I've been working with Erik on simplifying this process, and I've been working on automation behind the scenes to help the heavy lifting of managing multiple deployments of the Apario Reader in the decentralized infrastructure. Remember, as OSINT comes in and out of relevancy, so too will new instances of Apario Reader that have connected XRP rewards with them in the form of APARIO tokens. Since the apario-reader application can mint NFTs on behalf of your Instance Wallet, the interface will allow your visitors to support you. I am designing this service so there can be 233 copies of Andrei for 2025 as we needed in 2020 with PhoenixVault but had only 1. This is where YOU come in. And to anyone telling me or you that I am only doing this for money can go pound sand. The thousands of hours that I've spend building this isn't for money, its for transparency in truth. Multiple it out. 233x 369 RLUSD = 85,977 RLUSD ; from that, 21,494.25 RLUSD goes directly into 233x Instance Wallets. 42,988.50 RLUSD gets deposited into the APARIO/XRP AMM Liquidity Pool. The remaining 21,494.25 RLUSD is used for acquiring 699M APARIO tokens. Whatever remains from the remaining 25% stays in the apario.xrp wallet for future development. That's not about money. That's about enabling me with reasonable resources used appropriately for your growth. Thanks for your support in the project!

In February 2023, the Project Apario service was discontinued as a proof-of-concept (PoC) Software-as-a-Service (SaaS) Ruby on Rails (RoR) web application. This decision was not made lightly and nor was it easy to make. The SaaS RoR PoC was burdensome to maintain and costly to operate in 2020. The project faced Government Ordered Censorship as a result of choosing to release the JFK Assassination Files first. There was significant demand for the JFK Assassination Files that were released on the service, and that was powered by a 12x bare-metal server private cloud infrastructure that was costing me around $6,000 per month to operate. In September of 2020, the name Project Apario was codified in the PhoenixVault idea, and while the Phoenix may have died in the ashes of the JFK Assassination Files once again being censored by the United States Government and its counterparts. I took the 12x bare-metal server infrastructure and optimized it down to a 6x bare-metal server cluster and removed all third-party SaaS dependencies from the topology. This reduced the OpEx of the service by $3,000 per month to $3,000 per month. This was much more manageable. The enormous generosity of the community also supported and funded most of this services' expenses, and so while you help me with paying for the servers, I help you by writing the software and releasing the source code open source. In February 2023 though, I was faced with a significant decision. The financial support provided to the project through voluntary contributions were less than 33% of the OpEx required to operate the servers, even at half capacity, half-cost and an optimized code-base provided double speeds over the 2020 release of the platform. The project was still not in the right direction. Being a single person who has been behind the project since its inception in August 2019, under the name of Crowdsourcing Declas (unreleased by name as it was under development until PhoenixVault launched as the platform under a rebrand). I needed to replace the technology stack of the entire project. I couldn't support the old tech stack at the same time as building the new tech stack. I had to discontinue the project as it stood. It couldn't return as it was. Ever. That being said, the Phoenix rises from the ashes. 2020, we thought that President Trump was going to get re-elected and we wouldn't be stuck with Joe Biden for 4 years and cackling Kamala Harris. In 2020, we thought that we were uniting with Q for the finale of the Great Awakening. Maybe you thought that. I was extremely busy building the PhoenixVault software. It's been 4 years. I needed to learn Go, and not just learn Go, but really grok it. I am still learning it. It's a complex language capable of doing a lot. I work on this project part time. I spend my discretionary disposable income on the project. It costs me around $1200/month currently to run everything as it stands and the Raven Squad Army is supporting it with $15/month in support. Thank you for the support that you're continuing to show me. I am still extremely busy on the software and the code and my work can be seen on GitHub as its getting released. For instance, I recently released go-passwd and go-checkfs on GitHub. These two packages are tiny, but pack a powerful punch. The go-passwd tool provides a safe way to audit a string before accepting it as a password. The go-checkfs provides an easy way to check.File and check.Directory by providing the path to either and the file.Options{} or directory.Options{}. One line provides you the ability to check for write permissions, ownership, read-only permissions, etc. Another package released was the verbose on GitHub. This provides me additional logging capabilities within Go, such as Tracef and TracefReturn and all normal *log.Logger methods like Printf and Println are wrapped around Sanitize and Scrub methods that use a SecretsManager to keep track of potential secrets being logged out into your log files. The Tracef related commands provide a stack trace of the thrown error message's call before creation, and the TraceReturn related methods will log a stack trace of the error, but return the error as an error structure for re-use throughout the application; but when the error is passed into the return of the func, a stack trace of the error is captured alongside the message of the error. Last year I released the configurable package on GitHub, alongside the go-textee, go-gematria, and go-sema. All of these packages, while on their own may not seem to be connected to PhoenixVault or Project Apario, and thus why would you continue to sow seeds into my efforts? Well, these packages are dependencies to the apario-reader and apario-writer and in 2019 when I chose to use RoR for the PoC, it was because thats what was familiar to me and what had all of the dependencies that I needed. Go on the other hand is a much different technology stack and very different from Ruby on Rails. Therefore, in order to get the RoR PoC PhoenixVault out of my control and into your hands, it needed to be re-architected from the ground-up so it wouldn't cost you $6,000/month to operate. Now, a site like ElectionSelections.com can operate for $48/month! So, yeah, I could have kept with what was and become irrelevant, or I could adapt to the time and innovate a solution out of the problem I found myself stuck. On December 17th the RLUSD stable-coin was released by Ripple, the company behind XRP. RLUSD will drive XRP like USDT drove Bitcoin (BTC) but without excessive fees like USDC / USDT. From personal experience, the Ethereum network would look something like this. I sent $100 USD ⇄ USDT (Tether) ⇄ ETH and I'd receive $66-$72 worth of ETH after paying $28-$33 in fees. With XRP, the $100 USD ⇄ RLUSD ⇄ XRP results in receiving $99.99 in XRP after paying $0.01 in fees. On December 17th 2024, the $APARIO token was AirDropped to 434 XRP Wallets that set the $APARIO TrustLine by reserving 0.2 XRP. 86.6 XRP was reserved for the launch of the $APARIO token and the value of the token has reached a Market Cap of $1,268 in the first week since being launched! There are currently 529 TrustLines, increasing the demand of the token by an additional 95 XRP Wallets adding another 19 XRP leaving 105.6 XRP in the $APARIO Reserves. The APARIO/XRP AMM Pool is providing over 451 XRP of liquidity. The APARIO/PHNIX AMM Pool is providing over 93 XRP of liquidity. The APARIO/GOPHER AMM Pool is providing over 136 XRP of liquidity. Finally, the APARIO/YEShua AMM Pool is providing almost another 17 XRP of liquidity. In total, there is over 697 XRP worth of $APARIO in AMM Liquidity circulating pools. At the current market rate of XRP, at $2.29; this results in $1,596.13 of circulating liquidity. These liquidity pools are provided to you by me for a 0.693% transfer fee on the AMM Pool itself. When you use the AMM pool to swap your APARIO tokens into XRP tokens, the pool will incur a fee of 0.693%. This fee is a result of a calculation performed on a signed transactions on the AMM Pool itself setting the pool transfer fee. The average of the vote weight + proposed fee is calculated upon changes to the ledger and the current fee is 0.693% as a result of the above table. The growth of the apario-reader while having no marketing, no social media campaigns, no outreach, etc. - has been growing month over month strongly even after being offline for 17 months between the discontinued PoC RoR PhoenixVault and the truly open-source decentralized apario-reader. 2025 will see the direct integration of the $APARIO token into the apario-reader and receive a re-brand and a new-logo under the name of PhoenixVault. The future is going to be amazing! Do you HODL $APARIO tokens?

I am very pleased to announce the release of Project Minnesota's instance of apario-reader. https://electionselections.com/ (can be read as Election Selections or Elections Elections or Elections Squared) Erik will be formally announcing it once we connect, but I am so darn excited. It's like its Christmas morning. Oh wait. Merry Christmas everyone. The BEST is yet to come!

Hard to believe that the apario-reader application was built in 2 weeks last Christmas, and here I am on Christmas day the next year deploying a new instance of the project for Erik and Project Minnesota. Excited to get $XRP integrated into it and motivate tens of thousands of people to red pill themselves on election integrity! Thank you for everyone who has continued to show support for this project, I love and appreciate you.

Project Apario appears to be a multifaceted initiative with various components and objectives, based on the search results provided: Overview: Origin: Founded by Andrei Merlescu, Project Apario seems to have started as a platform or tool focused on OSINT (Open-Source Intelligence) research, particularly related to government records and transparency. Purpose: It was initially aimed at assisting with research into the JFK Assassination Records, providing a platform for grassroots supporters to access and analyze declassified government documents. Over time, it evolved or was intended to evolve into a tool for broader political transparency, news, and commentary. Key Elements: Technology: PhoenixVault: Described as a proof of concept software focused on handling declassified records, particularly those related to the JFK assassination. Apario Reader and Writer: Components of what seems to be a decentralized approach to managing government public domain records, aiming to democratize access to information. Raven Squad Army: An initiative or community associated with Project Apario, possibly for rallying support or participation in this decentralized information warfare landscape. Business and Legal Structure: Project Apario LLC: A legal entity registered in New Hampshire, operating from Washington, DC, which suggests a business structure to support the project's activities or development. Public Engagement: There were efforts to fund the project through platforms like Ko-fi, indicating crowdfunding or supporter-driven development. The project had a presence on various platforms including Telegram, YouTube, and SoundCloud, indicating an attempt to engage with a wide audience. Status and Evolution: Discontinuation: By March 31, 2023, Project Apario was announced to be concluding, with statements from its founder that it would not return. This suggests either a pivot in focus or the end of this particular initiative. There's also a mention of an "official offline" status with no return planned, metaphorically likened to a ship sinking, indicating a dramatic end or shift. Cultural and Ideological Aspects: The project seems to have ties to libertarian and transparency ideologies, aiming to challenge mainstream media narratives by providing alternative or direct access to information. Public Perception and Impact: Community: There were followers and an audience, as seen from the engagement on platforms like Ko-fi, where people could support the project financially. Criticism or Challenges: The project encountered issues like government-ordered censorship, suggesting it faced resistance or legal challenges in its pursuit of transparency. Legacy: While the project itself might have ended, its concepts and the technology developed (like PhoenixVault) could be seen as contributing to discussions on government transparency and information access. Conclusion: Project Apario was an ambitious project with a mission to increase transparency and access to governmental records, particularly through technology that could empower individuals to bypass traditional information gatekeepers. Despite its apparent cessation, the ideas and tech developed might continue to influence similar initiatives or be picked up by others in the field of information freedom and transparency.

Per the request of @Alien display names can now be changed on the forum boards. The default of the software is to disallow them until a policy has been established. Below are the instructions on how you can take advantage of this service if you need. First, up at the top you'll want to click on your username. I signed into your account @Alien using the Admin CP feature of Invision Community and from this drop down menu, if you click on Profile, it'll bring you to this page... If you click on Change you'll be brought to the edit form: As you can see, 7 display name changes are permitted once you've been registered for 14 days. Your limit resets after 144 days. Thank you!

I am proud to announce the reveal of the $APARIO coin art! I'll include a bunch of other attachments that include higher resolutions of the coin logo and animation. The image is released under the license: Public Domain "CC BY-SA" The author is "Project Apario LLC". I also have an extremely large render of the image as well: The smaller icons are: Use this link to trade XRP for $APARIO tokens and vice versa! https://xpmarket.com/dex/APARIO-rU16Gt85z6ZM84vTgb7D82QueJ26HvhTz2/XRP?trade=market If you want to use the new liquidity pools for $APARIO / $GOPHER & $APARIO / $PHNIX & $APARIO / $YEShua if you are holding any of those tokens and want to get some $APARIO tokens. Thank you for your support!

$APARIO Token: https://xpmarket.com/token/APARIO-rU16Gt85z6ZM84vTgb7D82QueJ26HvhTz2 APARIO/XRP AMM: https://xpmarket.com/amm/pool/APARIO-rU16Gt85z6ZM84vTgb7D82QueJ26HvhTz2/XRP $APARIO Airdrop: https://xpmarket.com/memes/airdrops $APARIO XRP Wallet Address: rhkjvZFmbm4o6G8xhgceoVGJLUwDr57vch xrpdomains.xyz aliases: -> XRP: apario.xrp writer.xrp projectapario.xrp -> RLUSD: apario.rlusd writer.rlusd projectapario.rlusd Head on over to XPMarket and connect your Xaman XRPL Wallet. Then go to Airdrops and click Set Trustline below the APARIO token. This Airdrop will expire on 12/17/2024 at 1:44PM EST! The Airdrop will give you around 10-15K $APARIO tokens! Yes, it's OFFICIAL. I have 400,000,000 $APARIO tokens. That will be the supply that I'll use for StumbleInto Rewards! Yes. I am going to give you free tokens on the XRPL that you can trade for $XRP! Now are you starting to see why the Apario License app is needed? =D YOU CLAIM I DON'T CARE BECAUSE I WON'T BEND MY KNEEE. - NOVA BE PART OF HISTORY WITH ME! THE AIRDROP IS 100% FREE!

It's been a few days since I've provided an update on this bug, and I wanted to keep you apprised on the findings. So, I thought that the locker was the issue and that the data race was the actual bug. It wasn't. Yes, the error was a data race, but the root cause had absolutely NOTHING to do with this file, this function or even the files that were being processed at the time. No, the bug was much easier than that, but much tricker to find than that too. Sometimes, bugs are not simply at the line number where the syntax or runtime issue occurred; rather, bugs can be structural around the valid syntax that causes runtime to be ineffective. Given the amount of time that I spent debugging the original problem and the "this isnt the" solution solution to the problem, turned out that in order for me to find the bug that was causing this problem; at the end of the code, I needed to start at the very beginning of the program. I'll spare you a long story. The issue was the binary pdfcpu was updated and the output of the gs 1.7 optimized PDF was incompatible with files created using Pages from Apple. When the output of the pdfcpu binary changed, apario-writer failed to pick up the changed property of .Pages to .PageCount to represent the total page count of the PDF itself. The aggregator func was looking at the Total Pages value to determine if the document has finished processing. The pdfcpu binary update added stability to the PDF ingestion process, but it also provided me with the opportunity to simplify runtime of the program. This meant that I needed to completely replace the validatePdf(ctx context.Context, record ResultData) (ResultData, error) func to the newly rewritten validate_result_data_record(ctx context.Context, record ResultData) (ResultData, error). Introduced in this func was the log_info, log_error, and the unseen log_debug. I introduced 2 types of new Logger methods, and then a blend of the two as the third new func alongside their formatted f equivalents. When implementing this new logger package, it resulted in low level functions that look like this: Getting refactored to look like this: In the event that one of the err assignments is not nil, the log_error variable is a pointer to the *CustomLogger that was defined in main(). The sem_download Semaphore is used to protect the runtime of the appliance, and any issues are instantly logged into the error.log with a stack trace of the error when its received. The stack trace looks like this: Therefore, when using the CustomLogger throughout the entire code base of the apario-writer application, I was able to identify that the issue Erik and I were running into with Project Minnesota being imported into the Apario Reader was the nuance details of PDF's proprietary vs open source analysis and modification tools available. Since all of Project Apario's work is GPL-3 Open Source, we're using open source libraries for our PDF analysis and documents created with proprietary word processors like Pages or LibreOffice can cause issues with the underlying PDFs; thus why GhostScript is utilized. Previously, in the validatePdf(ctx context.Context, record ResultData) (ResultData, error) func, the gs binary from GhostScript was used to convert the PDF into compatibility-level 1.7. I thought this was going to be sufficient, and while it was for the JFK files and the STAR GATE files, it was not for the Project Minnesota files. Therefore, I needed to fix that bug. The code was originally: These options simply didn't cut it anymore and I needed to adjust the code a little more to make it work with these files for Erik. Dropping the -dCompatibilityLevel from 1.7 to 1.5 meant that the pdfcpu info -json PDF-Path wasn't going to throw errors on the analysis and when the PDF is converted into a PNG, the underlying PNG file won't be invalid and throw errors relating to image.NRGBA. Before find the pdfcpu change in the Pages vs PageCount property change, I was debugging the issues that were throwing the image.NRGBA; I was able to find those errors and debug them because of the log_error.TraceReturn used throughout this code; this way when things caused issues, I knew the trace of the commands down to main where the error occurred. This is key when dealing with concurrent programs; you need to understand where and how the error happened and get a snapshot in the stack at the time the error is captured. This comprehensive function provides additional stability and debugging knowledge into the PNG related errors that can occur due to PDF files. Ultimately, I was chasing a goose at this point, as the issue was an easy fix... but at the time, when I was debugging this, I couldn't see that the output of pdfcpu changed thus breaking the code. However, as more of the log_error updates were persisted through the project, the overall quality of the project increased as well as its debugability. Now that these changes have been integrated into the apario-writer project, I am going to pivot over to the apario-reader app and provide a similar kind of enhancement. Ultimately, this bug has been resolved. It's been squashed alongside the other termites that hung around it that were lurking in the shadows. The log_error stuff really leveled me up in terms of slaying these bugs. Frankly, they were oversights on my part and I should have put the time in sooner to build the CustomLogger, but c'est le vie, right? Can't have it perfect always, or can we?

I want to dedicate a thread to discuss with you my IDEA of Proposals for the Apario Reader. I originally wanted to introduce this functionality in the Ruby on Rails proof of concept, but lacked the engineer capabilities to deliver the scale required. Go on the other hand provides a much cleaner environment for accomplishing these goals in much less time; therefore, I am leveraging it as much as possible. As such, Proposals were put on hold until I could bring the rest of the idea out of the dark ages of Ruby and into the golden ages of Go, and as such, the time has come for Proposals to re-enter the conversation. The idea of the Proposal was to leverage the Apario Identity of a user's reputation and exchange that Reputation for the ability to "stake" a change for a proposed page/document. What kind of changes? Rotate the page = 1 Reputation (tiny) Update the OCR text recognition = 33 Reputation (medium) Remove the page from StumbleInto recommendations = 99 Reputation (xlarge) Add Metadata = 17 Reputation (small) Modify Existing Metadata = 47 Reputation (large) Supplemental Media (Public Domain or Copyrighted Use Permitted) - 369 Reputation Per 10MB (xxlarge) To submit a proposal, it costs you reputation. So that Reputation gets deposited out of your account and the Proposal is created in your wss://identity.apario.app/@andrei/proposals/1. The instance is recorded, the change is recorded, and the rules are established by consensus voting on the Apario Identity App itself. These Reputation scores are going to be the beginning process; but ultimately, the goal is to allow users to cast choices for polls by staking Reputation in the choice. I've used staking reputation; and I don't want you to get confused what it means. It's basically reserving or blocking your reputation from being spent ; it's frozen and becomes immutable at that point. It's been consumed. It no longer shows up as a available reputation, but reflects upon your total reputation. Thus, spending your reputation doesn't diminish your reputation, rather it enhances it. So, when the Apario Identity service has a Poll available that is asking for you to provide your vote on the cost of Rotating the page reputation being on a number sequence of either 1 (tiny), 2, 3, 5, 8, 13, 15, 17 (small), 33 (medium), 36, 39, 45, 47 (large), 71, 72, 88, 93, 96, 99 (xlarge), 117, 369 (xxlarge), 434 up to 999 (xxxlarge). When asked about disk utilization metrics, it's fixed at per 10MB. It's the average of 1 page of data that needs to be rewritten / replaced with the apario-writer ; which needs to be updated to only process a single page of a given document upon request ; the apario-writer needs to go through its v2.0 rewrite as well and be made modularized and more stable. It's stable now, but its a little buggy at the moment as you can see from the other blog post that I haven't updated yet. Long day of work today. Didn't get to it. But I will when I have time to. It's important though for me to document this out and to trust in Yeshua's processes because it'll be a clear path and a narrow path to victory. This is part of that process and I am leaning into it. When you see the connection that I am bringing to users who engage with your Apario Reader instances to earn reputation so they can participate in the self governance of the platform, it really provides you with a fresh perspective of what the idea of Project Apario can become and why I have been so excited about it, but also so reserved about it because I knew that the world needed to change first and well it has because # checkmate Yeshua won =D Once a proposal comes in, it will need to go through a pruning process... depending on the size variance, there will be voting rules tiny (1) to small (17) will require 12 Apario Identity users to stake 0.333 Reputation onto the proposal, resulting in a total of 3.996 Reputation being attached to the Proposal wss://identity.apario.app/@andrei/proposal/1 beyond small (17) up to medium (33) will require 17 Apario Identity users to stake 0.434 Reputation onto the proposal, resulting in a total of 7.378 Reputation being attached to the Proposal wss://identity.apario.app/@andrei/proposal/1 beyond medium (33) up to large (47) will require 33 Apario Identity users to stake 0.71 Reputation into the proposal, resulting in a total of 23.43 Reputation being attached to the Proposal wss://identity.apario.app/@andrei/proposal/1 beyond large (47) up to xlarge (99) will require 45 Apario Identity users to stake 0.88 Reputation for a total of 39.6 Reputation being attached to the Proposal wss://identity.apario.app/@andrei/proposal/1 beyond xlarge (99) up to xxlarge (369) will require 71 Apario Identity users to stake 1 reputation for a total of 71 Reputation being attached to the Proposal wss://identity.apario.app/@andrei/proposal/1 beyond xxlarge (369) up to xxxlarge (999) will require 117 Apario Identity users to stake 3 Reputation each for a total of 369 Reputation being attached to the Proposal wss://identity.apario.app/@andrei/proposal/1 Proposals are valid for 434 days and automatically expire. When proposals expire, Reputation staked is released. When proposals are adopted, Reputation is then moved off from the Proposal at wss://identity.apario.app/@andrei/proposal/1 and then, whenever THAT page shows up in any StumbleInto request, a bonus of an additional 0.003 Reputation is awarded to 3 people if they answer a single poll question that ranks the quality of the change in 3 categories. The user who submitted the accepted proposal The user who licensed the apario reader instance The user who stumbledinto the modified document The categories requested in the poll are asking: Do you want to see the original? (if yes, the original is presented over the proposed change - the changes are all revisional history on the pages stored in JSON as files in a fibonacci built identifier directory tree ) (criterion 1 met) Did the proposal make it better? or Star Rating: (1) (2) (3) (4) (5) (6) (7) (8) (9) (X) Submit to wss://identity.apario.app/@andrei/proposal/1/review User who submitted accepted proposal gets 0.003 Reputation User who licensed apario reader instance gets 0.003 Reputation User who submitted form gets 0.003 Reputation The supported media component of this is ultimately something that I personally have a problem with being a programmer and being philosophically and spiritually pure. Giving people the ability to use my engineering skills to harm children is the last thing on my wish list this year for my prayers to be answered from Yeshua; but rather, I am hesitant to open the Apario Reader to support .mp3 and .mov and .mp4 and other media formats like .txt and perhaps even simple .JPG / .PNG / .GIF as well; but there are few stipulations that I have with that. Ultimately, it's going to be up to the administrator of the Apario Reader whether to allow it or not, but it'll be on a per-instance basis that supplemental media is supported. When supplemental media is supplied, it's loaded on the Apario Reader instance itself and is served by that instance as a supplemental media. As the administrator, you'll be able to indicate whether or not you want your users to be signed in before they can download your supplemental media. This ultimately puts me on the hook for what you're doing, and as such, it's my responsibility to pray over this project and ask that Yeshua protect it and all of the children. Truly I say that to you. If you only knew who I was, but Yeshua does . But, this would ultimately mean that your instance of Apario Reader would need to go through a scanning process for a few legal compliance things first - to protect the children: 1st, I'll take the raw data submitted and capture its checksum. I'll then check that checksum against the registry of content that is designed to protect missing and exploited children - if something is tagged ; an automated FBI tip is submitted by the Apario Reader with the IP address information and the location exif data of the content submitted, including the session information for them to seek NSA to actively intercede on that child's behalf. So help you Yeshua save yourself from yourself if you ever thought to harm one of those little ones. 2nd, I'll need to perform OCR on the image itself, extract exif data, remove location information and compress the file to 88% quality in progressive JPG format. 3rd, I'm going to generate a dark mode of the image based asset if i can, or i am going to perform a transcript on the audio or video file itself and use the text file as supplemental data to the asset being submitted 4th, i'm going to take the metadata that you provide and I am going to encode the entire thing in a payload with the checksum of the scanned file and I am going to sign it with your Apario GPG key that is your username, such as andrei@identity.apario.app that is an RSA 4096 of your account and when you registered your account on Apario Identity, the initial password that was provided in memory to the Apario Identity Go application generated a GPG RSA 4096 key for you with your username@identity.apario.app and uses that for encrypting your secret notes and such throughout any of the Apario Reader instances. That GPG key is going to be used to sign the FBI tip report that gets sent. Oh, and I may even connect with some of my contacts at DHS and see if they can stop being pricks about the JFK files and actually help stop trafficking children; but we'll see what Yeshua does with DHS =D 5th I am going to then suspend your account immediately and revoke all reputation earned. Seriously, if you're attempting that shit, you're going to get your IP address added to a 369 day ban list that gets enforced by the Apario License Manager that is enforced in the WAF built into the Apario Reader. It's so easy to ban millions of IP addresses and consolidate addresses that belong to singular subnets in at a network bit level calculation for extreme precision and extreme speed. After all, I used to work in Advanced Services at Cisco Systems for 6 years before going over to the Oracle Cloud Infrastructure (OCI) group for 4 years and then Warner Bros Games for 3 years. So far, I've been doing Project Apario for 4 years now! But going into the 5th year, it's important that as these services get expanded out and my talent becomes widely used within the world, I want to make it abundantly clear that I will show absolutely no mercy at all to pedos and their kind. Yeshua and I are very clear on that. 6th, I am going to send an automated email to myself from that is signed from your GPG key that tells me that you've decided to seek the lord and the email contains a very specific prayer for you that if you read it, will allow you to take what evil you have intended to harm others with and surrender yourself to the authorities with a full confession in hand and you shall receive the divine protection and ultimate Justice from Yeshua that you truly deserve for the deeds of the weight of your heart. Too many abuse victims are quick to the guillotine without giving Yeshua a chance to transform the broken into new. After that scanning process is completed, the supplemental media would then go to the Apario License Manager for Instance Owner approval of the submitted media. Ultimately, the Apario License Manager is going to keep track of storage on the instance and it'll also handle the configurations for S3 storage if the user wishes to leverage S3 or DigitalOcean buckets for their disk space. It comes with costs, but if you're hosting on Amazon then S3 may be a very solid choice for you. If you're hosting on DigitalOcean, their Spaces product may be perfect for you. Either choice, your storage capacity needs can grow as you require, BUT your instance will still have a 1,000,000 page limit on it. This is a per-instance limitation and its done to encourage the ecosystem to be co-creative in their processes. As the Apario Reader software improves, you'll see how I plan on using the leverage room that we gain by a 2x improvement on a refactor on the internal memory database after my 3 years of experience in working in low level Perforce Helix Core database, that I'll be able to apply those prayers to Yeshua directly to my refactor and align them with the file based access that allows me to scan large text files at index points and leverage the empty bin space of bytes in between to act as buffers to create clean blocks inside 1 single file that is say 100GB in size and i have chunks inside it with 9MB per page of metadata and transcripts and keywords and OCR text and supplemental text or transcripts that then can be replicated... on other Apario Reader instances ; thus introducing clustering. This idea is taking a step into the wss://license.apario.app/electionselections.com/document/2025ABC123 This base URL would allow me to add on /peers to get a JSON response of peers that the document is hosted with The base URL as is would just load the JSON of the document from that instance, BUT would use a load balancer in place of electionselections.com to any of the peers available that respond in less than 3ms to the /valet/ping endpoint that returns an HTTP 200 OK status code with the text OK. This means that I would be wrapping the Apario Reader, if its licensed and online, in the wss://license.apario.app/ with the electionselections.com/document/2025/ABC123 as the URL path of the browser tacked on when licensed and online... Otherwise, the endpoint would hit a JSON response from the Apario Reader instance itself However, preference is given to local first. However what happens when local gets corrupted? Well, enter peers.. When the Apario Reader has peering enabled, it will allow you to set a reserve amount of storage that you want for peering. In terms of memory, your 1,000,000 page limit is that limit for a reason, but when the new database is released and the page limit increases to 3,000,000 and larger, you'll find that you'll want to grow your storage in places like S3 - but those come with a heavy cost; or you can leverage the peer to peer network and offer to give up part of your network to store blocks of 9MB each on your server; lets say you are Brave and you opt for the ULTRA MAGA CLUB in the America's Comeback forum that is $5,432/year - this is a fully managed service that funds me and provides dedicated server that has around 5TB of storage available to you and can host 1M pages of OSINT. That 5TB storage probably wont be used by all 1M pages at 10MB each... that only will use around 1-3TB max, and as such, you'll have around 2TB left over for things like supplemental media and your database index; your database will be around 3% of your total storage size, so for 170GB STAR GATE files, the DB is 3GB and for the 240GB 2023 JFK files the DB is 4.5GB. The size of the database will fluctuate and is not exactly 3% but its close. Engineer close. Through Apario License Manager you'll see how much storage remains on your instance and you can set how much you want for peer reserves; the recommendation is 25%. It will turn on automatically if you enable peering and set to 25% unless you override the config.vaml value. That storage peering means that instances who are hosting content that have more than 369 impressions automatically get promoted to the wss://license.apario.app/replicate/electionselections.com/document/2025ABC123 and that request will kick off a request that will try to find a server that it peer with. When a server is found, the socket returns the servers information. wss://electionselections.com/replicate/document/2025ABC123/nationalelectionintegrity.com is then kicked off locally when the server is approved by the user who clicks "Use server" or "Find another" ; when that happens, the request when attempts to connect to wss://nationalelectionintegrity.com/valet/receive/electionselections.com/document/2025ABC123 and the body of the request contains the entire 9MB blocks (up to 9MB each) of the data of the entire metadata and assets transferred over secure socket connection... the new server receives it, adds the index block to its index file, and then continues on its merry way serving that content by delivering a message to wss://license.apario.app/electionselections.com/document/2025ABC123/peers you would see 2 results show up: { "error": "", "status": "200", "record_type": "document", "identitifer": "2025ABC123", "peers": [ { "domain": "electionselections.com", "last_seen": "2024-12-05 02:41:00 EDT", "load_ms": 3.333, }, { "domain": "nationalelectionintegrity.com", "last_seen": "2024-12-05 02:44:00 EDT", "load_ms", 34.283, }, ] } This data would show you the 2 domains that are hosting the data. // string represented uint64 epoch timestamp actually // float64 of how long it took for a successful tcp establish on the endpoint to the HEAD only on electionselections.com/document/2025ABC123 expressed in milliseconds as performed by the Apario License Manager Thus, when going directly to wss://license.apario.app/electionselections.com/document/2025ABC123 you'll end up connecting to the fastest load_ms peer if the local peer is not available. That being said, we'll always prioritize serving the local file over a peer file, and I'll make sure that the software doesn't use more than its allotted disk storage. Once we have that, we can ultimately offer the ability to replicate the data onto other servers and its gone through a validation and cleaning process, but also its gone through an adoption and acceptance process. One thing that I think would be really cool to offer in the Replicate service would be if the document has a proposal attached to it, if the user who proposed the document has it replicated in any of their instances. That would be cool information to intersect and discover. Potentially because you're working on similar projects and you both want to peer off from each other? Why not? This allows you to be, while you're signed into the Apario Identity Service and its connected to an account in the Apario License Manager, anytime you're on any global instance of any Apario Reader, and the administrator of the instance allows replication of their content, you can click a simple button that will immediately kick off that replication process to your instance of Apario Reader and register it in the License Manager! Voila! What benefit do you get for doing this? Well, when the Apario License Manager sends a request for a document from another domain but to your instance instead, you're rewarded 0.003 Reputation for that act of kindness to a fellow Apario Reader administrator. Same rules apply to Reputation and their earning cadence rules, but it's the same idea. Plenty more to be added about this topic but I'll leave this here for now. God Bless All and have a good night!

One of the key mysteries in scripture is the evidence that YaHaWaH reveals to us that Yeshua Ha'Maschiah was, in a metaphorically literal sense His Right Hand, thus Yeshua "sits at the Right Hand of YaHaWaH" and there are three essences to YaHaWaH rather than "Father Son Holy Spirit" but rather YaHaWaH (other spelling variations) such as YeHoVaH and YHWH - but many Jews still say Hashem or Adoni, but deeper reading in Scriptures reveals how the prolonged relationship that you build with Yeshua over the transformation process of the Spirit, one of the essences of YaHaWaH, the right hand that also represents Judgement, but also the extended hand of salvation offering as a free gift to anyone who confesses with their mouth that Yeshua died sinless for another's crimes and ascended on the 3rd day and returned for 40 days to preach to thousands of people who documented and witnessed the revelation of God Revealed In The Flesh - The Word Became Flesh. Yeshua fulfilled Torah, for as scriptures read from YaHaWaH, the Natural Law was originally written on the Hearts of all of Creation including Man, but when the knowledge of Good and Evil was pursued and the discovery into what made Creation Creation, the word salad of Creation became poisoned like the fruit that Yeshua was sent to defeat. The tongue holds great power and immeasurable value; and while many Jews will continue to celebrate Hanukkah for their own reasons, as somebody who is deeply in faith with Yeshua on a daily basis, I find no calling from the Rauch HaQoDesh as a Gentile to engage in the Holiday, and ultimately, including Christmas but rather am asked to talk more about its pagan roots and how its been used to cover for some pretty unfair things that happen in society; giving into the idea that Santa is just the word Satan with the N moved to the left by 2 letters, suddenly the holiday has a different meaning. For me, on a personal note, being presented as a Christmas present, my "coming to Jesus" moment actually brought me deep into Scripture to find Yeshua who set me free and removed the yoke that was upon my shoulders. When that happened, I literally lost 120lbs and went from being unhealthy to being in my prime. I found this transformative power when I was observing what I was being asked to do, and following through; not trying to force that process into the understandings of Man's rituals and institutions; for none of them were of Yeshua anyway, and they all departed long ago from His Way; nevertheless, the healing process took place in yours truly and the power of your speech has the power to declare life over your reality. Given that wisdom, the faith is blind and I lean not into my own understanding on how it work, but it works! Those who have eyes to see can see and ears to hear will hear the words that I am saying. The Name Above All Names was YaHaWaH's Right Hand Yeshua which also is spelled Yashuah or "YaHaWaH's Salvation" or "YaHaWaH's Gift" - by saying these words, your sins are forgiven and you are free to stand up and walk. The Cross is the symbol given to Constantine to conquer the pagan world because its a Heavenly symbol also found within Laminin; which kind of is a word play on Lamb In + In (or In Squared) ; so I read Laminin the Cross shaped miracle that is responsible for transcribing our DNA sequence during cellular replication (go back to High School Biology class for 17 seconds please)... these clever Creation Laminin, sound to me like Lamb In Square ; Hrm... What if calling upon He Who Died Upon The Laminin shaped Cross and Ascended and Rose On the 3rd Day, Perhaps He was the one who ultimately ended up showing us what we truly are... That when we bring our problems to the Cross, and we bring them to Yeshua's feet, and we let our sins die on the cross where they belong, crushed under Yeshua's foot, then we are able to stand freely and also the Spirit of YaHaWaH begin to freely flow through your body after you've completed the Laminin transformation process of healing in the body. It's a biological, spiritual and physical transformation that occurs over a multiple year period of dedicated faith and daily prayer for deliverance that is 100% successful. All you have to do is call upon the name of Yeshua and whatever problems you face in your life - Yeshua will guide you through the cleaning process of your own Holy Temple so the Holy Spirit may dwell once again. Sometimes that requires us to Atone for our sins so the words that are hidden within our Holy Temple are released and Cast Out In The Name of Yeshua ; For They Do Not Dwell Here ; These Are Words ; Hidden Words In Your Soul ; Releasing them to Yeshua aloud in your secret prayer room allows you to freely access your own direct connection to YaHaWaH where you can petition and make requests, but also, like Job, converse openly with your Heavenly Father and lean not into your own understanding but in His and trust in Him. I cannot recommend it enough, but I urge people to be cautious about religious holidays their dominance in our lives. Scriptures from YaHaWaH are clear about which Holidays are significant to acknowledge and for in so doing, you demonstrate your obedience and alignment to the Prayer Yeshua Prayer Our Father Who Art In Heaven Hallowed Be Thy Name ]]YaHaWaH[[ Thy Kingdom Come Thy Will Be Done On Earth As It Is In Heaven Give Us This Bread Our Daily Bread And Forgive Us Our Trespasses As We Forgive Those Who Trespass Against Us And Lead Us Not Into Temptation But Deliver Us From The Evil One For Yours Is The Glory And The Kingdom For Ever And Ever Amen ; For We Fight Not Against The Flesh And Blood But Against The Rulers Of Principalities In High Places ; No Weapon Forged Against Me Or My Family Shall Prosper ; No Conspiracy Plotted Against Me Shall Prosper ; I stand Victorious in the Name of Yeshua ; Christmas is a Pagan idolatry Holiday and I believe that Hanukkah does not qualify under that definition because its specific to historical family relevancy to acknowledge hardship and perseverance ; a quality that many Gentiles should admire as a positive attribute from their beloved Jewish community.

In 2020 I started an online movement called Crowd-Sourcing Declass or CSD, however before going public with the idea, I reached out to an online community who were followers of my work to encourage them to begin speaking with others they know about what I was inventing and why. The message was quickly absorbed by very large egos in the room and I was pushed over to the side. Nevertheless, the inventor of the idea is the one who delivers the idea to market; not the one who comes up with the idea and then lets somebody else build it. I've never heard of an inventor inventing that way... but in 2020 that was attempted on me and Yeshua stood firmly behind me guiding me on the narrow path forward to victory. After I released the JFK Assassination Files for the first time globally in a fully searchable text database, I was de-platformed from Twitter / X and Patreon and lost the 144,000+ followers who were reading my content daily; solely because the US Government believed that I was interfering with the election. Excuse me. I am a US Citizen and I am entitled to participate in civic discourse during the 2020 and 2024 elections... nobody can tell me that my 1st amendment rights of free speech do not exist while I am a citizen of this great nation. Rather, I persisted forward even after getting banned and I wanted to re-engineer the solution from the ground up as I had mentioned countless times that PhoenixVault was only a proof-of-concept and not the real deal. The Centralized Project Apario Well, in 2021 after a quiet period of re-engineering the Powered-by-Public-Cloud SaaS Ruby on Rails application into a Private Cloud "all-in-one" architecture keeping 100% of the downstream SaaS integrations open-source an in-house. While this reduced OPEX of the project from around $6K/mo down to $3K/mo; it didn't address the scale issues that were prevalent in 2020. The software really started breaking down after the database was loaded with 1M pages of content. So, even in 2021, when I took the proof-of-concept that was temporarily disconnected due to OPEX challenges in cashflow, the relaunch with half the cost still wasn't enough. Even though the private enterprise cloud that I built was faster, had more computation power, had more RAM, and was distributing its load across 9 physical servers (larger in size) over 12 virtual servers (smaller in size on shared resources). This enhancement reduced OpEx of the project, expanded capacity for performance, but overall increased the complexity of maintaining the application into a near part-time job on its own. It wasn't sustainable for me to manage the operations of the Ruby on Rails proof-of-concept when the little time that I did have for Open Source development was being spent on keeping Ruby happy with tons of moving parts constantly updating and constantly breaking functionality making dependency updates a nightmare to perform and thus were avoided to apply maximum pain come release time. It drove me, due to the technical debt of that fallacy in my process, to scrap the proof-of-concept altogether and simply start the decentralized architecture of the platform given that nobody was tangibly supporting the project. The hype and coolness of my invention settled in the dust when the spokesperson who volunteered and stepped up to help me was driven to self destruction by his own ego and lying lips. Nevertheless, 4 years later I am still standing, invention in hand, and documenting the next steps towards the decentralization platform. Now, granted I wish I was doing this in collaboration with other competent people who are working with me by choice who can hold weight and actually move the machine forward. However, while I wait on Yeshua for resources to accomplish those goals, I am pushing through persistently developing the notes in the background and planning the rollout of the completely decentralized protocol called Project Apario. In January 2023, at the request of Yeshua, I cancelled 170 subscriptions that were providing $2,000/month of cashflow to the business that was costing me $2,400/month to operate. While employed, I used my discretionary income to cover the difference and pay the one-time fees for software subscriptions, online monthly portals like ChatGPT for coding assistance, and more. However, Yeshua asked me to take the service offline and I followed the Terms and Conditions outlined by Project Apario LLC and provided a 60 day notice indicating that the service was going to be discontinued as-is and that subscriptions are terminated immediately; but paid access will remain until the service goes offline. The last 60 days, every single user was an Apario Member, meaning they had an active paid subscription and received the perks associated with that information. The only perk provided that was outlined in the Terms of Service at the time of sale was access to a badge next to your username that said you were an APARIO MEMBER . However, I found that in order to maintain the monthly OPEX costs of $2,400/month that really wasn't fluctuating much; I couldn't compensate for the deviations in subscription cancellations because users were trying to optimize their monthly bills and forgot about what Project Apario was; called in their bank and tried to report fraud. All fraud cases were won by Project Apario LLC and a few instances I voluntarily chose to give refunds, despite the Terms of Service stating otherwise, because users who sowed seeds into the project for a long time, but never logged into the service once, but cancelled 10 or 12 months later; I would refund their last subscription upon their request and cancel their subscription. Each cancelation was a punch to the gut. Each cancelation was my birth mother abandoning me again. Each cancelation was my adoptive family abandoning me. Each cancelation ate away at me and I couldn't see why or how support for the idea was fading or dwindling; except that I was fading and dwindling. Ultimately, I was trying to do it my way, and only my way, and never once did I stop and actually say out loud, "Yeshua, what should I do with Project Apario?" No, I tried to do it my way and it was perceived by others that I had an ego. Not an ego, I say, but rather a lost sheep wandering around aimlessly trying to find the light amid darkness. Canceling the centralized Ruby on Rails proof-of-concept was the right choice to make, however it was also the most difficult choice to make. I went from a project with over 2,000 hours of engineering labor invested into the platform's development, the production infrastructure buildout, the SaaS integrations, and the DevSecOps around the infrastructure and application itself. All of that, was it wasted? The project doesn't run anymore and its not online anymore? Was the time wasted? Was the money wasted? The JFK files were searchable for 3 years and during that time over 17 million pages were served on Project Apario to real users. Our cybersecurity was and is still aggressive and blocks over 15 million IP addresses worldwide automatically from even connecting to the service. On top of that, a hardware firewall regulated ingress policies that were met with the software firewall. Then the request would get piped into the Web Application Firewall and filter out malicious payload/requests from reaching the Rails application's runtime called rake. Long story short, the application was secure and it was built as an enterprise organization would be required to secure for compliance purposes for oversight. Not only am I professional who guides enterprises to those compliances actively today, but I also applied those directly to Project Apario. However, with the centralized project discontinued, the IDEA itself is what was refined in the fire of the trial known as the proof-of-concept and therefore, when looking at the next iteration of it, the IDEA emerges because the IDEA was confined in the wrong technology. The decentralization aspect of the IDEA was impossible to practically implement for the Open Source free-user community of OSINT researchers globally. So, I needed to swap the technology out. Reflecting personally on my own journey, I started my career at Cisco Systems in the Advanced Services Global Business Unit in the Enhanced Customer Aligned Testing Solutions group formerly known as Global Government Solutions Group headed by Ed Carney. Not only did I know Ed quite well while at work, but before departing Cisco, he gave me invaluable career advice that I applied to my own life and helped leverage that advice to make it to where I am today. Not only do I hold deep respect for the order and manner in which that Ed ran his department, but I also admired his leadership choices as well. When Cisco terminated through a layoff the entire leadership of the department and Ed for a restructure away from focusing on the top 100 companies and organizations on the planet to the top 10,000 companies of the world and provide a much different refined service as a direct consequence of the software that I built for them called VirtualDocs. It was built with Ruby on Rails 3 and ran on Ubuntu 14.04 LTS and was decommissioned out of production in 2023! This Rails platform that I hand-built, brought me the experience I needed to build the PhoenixVault proof-of-concept. However, as my career progressed and I fell prey to political activism, I became an outspoken supporter of the Vermont Senator Bernie Sanders. I ever met him in Bedford, NH and shook his hand. Not only did I love his politics, but I didn't understand WHY. However, in 2016 the reason WHY dawned upon me like a ton of bricks as the truth about my own life percolated out of the darkness I buried within underneath whiskey and beer was the fact that I was purchased. Well, that kind of threw me out of wack as you could imagine and I started talking with God by the name of "God" and only "God" and not acknowledging Yeshua as the Ha'Maschiah that I needed first to embrace, but nevertheless, I called out to God and was basically like "What am I doing?" Nothing more. Nothing less. Didn't press into it. Didn't listen for a response. But I did pivot to create formal branding for the Michael Trimm Show by October 2016 and I finished tip toeing around the destiny that God was calling me to, but I was still a deer in the headlights. Well, I voted for Donald Trump and the next year Oracle's Larry Ellison is personally calling for me to head up the Release Management DevOps efforts for DynDNS integration into OCI. Pretty cool! He heard about my work from Cisco and wanted me working on his cloud too. Cool. I did for 4 years, and happily. During that time, Oracle was big into Go. Cisco was big into Python. Oracle was big into Go. I wasn't at the time. Go wasn't cool. I was still condignly arrogant about what Ruby on Rails could do, not knowing how foolish and childish I was actually sounding in comparison to the big-players who were highly competent Go engineers building some absolute incredible software. Truly I say to you, I was a fool for not taking leadership up on learning Go and going head first into it. I chose not to because I was so radicalized by the political climate of Donald Trump and the coupled realization that there was a deep intersection behind the agenda of Donald Trump and the pathology that I kept hidden for so long. Little did I know, God was literally pulling me from the shadows and the place of hiding and was beginning the refinement process within me. During my time at Oracle I gave my life back over to Yeshua, but first in error called out to Jesus asking for help to stop drinking whiskey. Well, Yeshua responded and said to me that so long as I call myself by a fake name and live by a fake identity, I'll never know who I am and I'll never be the father I always dreamed I could be for my kids. I wanted to stop drinking for them. Not for me. For them. Yeshua told me that I needed to first love and respect myself through Him before I could get my life back on track. Well; long story short, the last 4 years have been called the pause for a reason, and that's because while the Project Apario IDEA was introduced to you as a proof-of-concept, it wasn't finished; as I personally was in a pause healing from the 30 years I self identified as Michael and attacked myself at every success junction that I was faced with. However, knowing that I was my own worst enemy and that Yeshua was my Savior, allowed me to surrender my will for being my own worst enemy out of fear of what my false identity is that everybody seems to know so well, but that Yeshua was going to transform me from within; and so He did. Part of that transformation within included Project Apario. Going from a proof-of-concept Ruby on Rails application into a Go application. I didn't take Oracle and Go seriously though in the time between 2017 and 2020 that I had to learn Go. I was more focused on Ruby on Rails, JIRA ticket management, and socializing with my coworkers during lunch hour board game hustle. When Oracle sent me to Berlin Germany for GoDays, even that didn't convince me to learn Go. I couldn't grok what the code was doing, until I watched Matt Holiday's course on YouTube. But at the time, I didn't know about Matt Holiday, and nor could I get over the personal trauma that I was suffering. Nevertheless, I went to the GoDays conference and Yeshua used that time to put me in front of very positive people who loved Go, spoke positively of it, and explained how it transformed their careers. He also brought me to a Tantra Massage so I could heal from the physical explicit abuse that I received as a minor from my cousin next door under duress and extortion. I healed from the trauma and allowed what was blocked to continue flowing once again with the help of Yeshua. I wasn't leaning on my own understand at the time, I was leaning on Yeshua's understanding at the time. Well, at this point this brings us right to dawn of the COVID-19 scamdemic that shut down the world and installed a temporary global medical fascist dictatorship that was dedicated on vaccinating the entire global population by force with gene therapy invented by Bill Gates and the Department of Defense over the previous 50 years. No thank you. However, the JFK assassination files were out and it was an election year and the last 3 years on Twitter and YouTube, I hadn't done a proper dig into the JFK files and I observed that nobody else was too. Why? I don't know why nobody else took part in the JFK files research when the National Archives released them except for the fact that they were released in a completely unhelpful way. Unsearchable. 70GB of PDFs with random numbers for the filename indicating the record ID. When you downloaded each archive and search for a Record ID, you get back multiple PDFs. Which is the most unredacted? Good luck. This presented an opportunity to me for building something cool. Like you've just read, I am a high level software engineer who worked at both Cisco and Oracle over the last decade building enterprise software for them. I applied my knowledge of Rails and I built Crowdsourcing Declass and when Austin Steinbart came into the picture, he requested it be renamed to PhoenixVault so I agreed. The error in my way was choosing Ruby on Rails because it was familiar to me, versus trusting in what Yeshua was showing me in my life with GoDays and literally, He flew me across the country to meet with other Go engineers and I was so lost and confused and frankly out of touch with Yeshua to actually heed his advice given to me. Now let us fast forward to 2023... The Decentralized Project Apario After Yeshua advised me to discontinue the Ruby on Rails proof-of-concept of the PhoenixVault, I spent the next 3 months of time finishing up a major project for my full time job at Warner Bros. Games. My contract role was renewing and I was given 6 weeks of unpaid time off that was mandatory to think on why I turned their offer down the first time. It wasn't a difficult choice, and I during the 6 weeks that Yeshua gave me to His cares, I built a handful of Go packages and the apario-writer in Go. This was the first step. It wasn't even a step you saw in 2020 either, but it was needed first. It's how a PDF / URL of a PDF gets processed into an Apario Asset. Well, it took me a few weeks to write this package and release a stable copy of it. I was able to generate light mode, dark mode and gematra assets from the pages now and the processing time went from an average of 3 minutes per page in Ruby to 15 seconds per page in Go while completing 3 additional tasks that Ruby wasn't performing (PDF->PNG->JPG & light+dark mode and re-render as progressive JPEG). Not only did these 3 additional tasks add 2 minutes to the Ruby implementation, but when applied to the Go implementation, I saw a 40% decrease in disk utilization from Apario Assets. The ratio used to be 1 Page : 20MB ; now its 1 Page : 16 MB and can be compiled in 12x the time in Go. Christmas 2023 arrived and my Golden Retriever Klaus was targeted by the Government and ultimately killed on March 1st 2024; but a week before Klaus got injured, Yeshua gave us a glimpse of the 2023 JFK files - currently searchable on https://jfkfiles.projectapario.com/stumbleinto - that propelled me to use the Apario Writer that I built just 6 months prior to build the Apario Writer. Together, Yeshua and I wrote the Apario Reader in just 14 days. We released the package on GitHub on January 2nd 2024. However, at that point, still no JFK files to search through. This brought me to the idea of I Do Read, an affirmation that installs excellency within your being, and I thought how can I be clever? Yeshua advised me on the power of affirmations and so I chose to call the decentralized PhoenixVault I Do Read instead. Why? Well, PhoenixVault is cool; but it doesn't do anything to do by virtue of its name. I Do Read on the other hand, transforms you by virtue of its name. So, the decentralized instances of the PhoenixVault are called I Do Read because it encourages you to read more OSINT. What benefit does that serve? I need to be surrounded by informed and consenting citizens who are voting for their candidates of choice with an expectation of their performance and not a blind check the box because it says Democrat next to it. For Yeshua's sake, can we please use Project Apario globally and end communism dead in its tracks? The Apario Reader is the decentralized Project Apario application. You can run it now. In fact, Erik and I are working to get a new instance deployed for Project Minnesota. When it's online, it'll be accessible at https://electionselections.com and also https://docs.projectminnesota.com/ and it'll be branded with I Do Read. This implies that Project Apario is already decentralized. However, the problem that this solution presents is, how do I, the person who created the software, have any way of knowing if an instance is running any OSINT on it that I personally may find interesting and too want to StumbleInto? Enter the crux of the decentralization challenge. PhoenixVault was tasked with centralizing the decentralized, and then I was tasked with decentralizing the centralized decentralized. If anybody could unscramble that word-salad it is Yeshua God revealed in the Flesh, our Abba YaHaWaH in Heaven sitting upon the Throne! The Apario License Manager After several months of praying on the crux of the decentralizing the centralized decentralized, I needed a way to introduce a consensus of peers. For instance, the JFK assassination files, according to the former Director of National Intelligence Rick Grenell upon an impromptu request by Austin Steinbart, that there are over 5,000,000 pages of JFK assassination records that need to be released to the public. To date, only 777,000 pages (and some change) have been released. What I find the most compelling, is how Apario Reader can be deployed in such a way that for each NARA release of the JFK Files, we have a dedicated instance of Apario Reader specifically dedicated to that singular collection of archives. Then, when looking at the sum total of 5M pages released over 10 years, we may have 17 instances total serving those 5M pages. This software can do that as is, but nothing is connected; its all decentralized. The analytics on instance 1/17 are stored and tracked in a different location than on instance 12/17 or 17/17. Therefore, I am going to introduce the Apario License Manager, a dedicated application that will run at https://license.apario.app and it will serve a Go + VueJS application to users who are running their own instances of Apario Reader. The disconnected Apario Reader application is not smart. It cannot search across instances, and it cannot recommend new content to you from other servers. It doesn't know anything about any other instances of Apario Reader. Like in Scripture, its as if man were saying I am that I am and there is no other to each other, when trying to find God, but not realizing that it was YaHaWah who was proclaiming I AM THAT I AM AND THERE IS NO OTHER was Him self describing Himself through man to man; but man couldn't see nor understand. Like man thought that he was alone and that God was not dwelling within him, so too does the Apario Reader look at the world. The Apario Reader is the godless commie that was foolishly saying I am that I am and there is no other without realizing that YaHaWah was literally watching them from within utter those words in complete darkness and unawareness to His presence within. No fear, no fear, though. Like the Apario Reader, the experience is similar. Instances don't know about other instances. Granted the source code is protected by GPL-3 open source disclosures, but that doesn't mean that the instance A is running the same version as instance B. Consequently, when updates are ready for the application, each administrator needs to re-download the binary, re-enable the setcap, and then relaunch the application (including the potentially 30+ minute index build at first boot). The Apario Reader application is going to experience a 2.0 upgrade in 2025, however at the moment, its as is. When 2.0 in the Apario Reader is launched, it'll be built with a new UI built with VueJS. This new interface will look very similar to the existing interface, but will function slightly differently in the backend; thus allowing for more future development to quickly get plugged in and activated as needed. However, the backend changes to the 2nd release of Apario Reader will be the integration with the Apario License Manager. Now, Licenses will NOT be required to run Project Apario's Apario Reader that is GPL-3 Open-Source; and the reason for that is if you choose to run one of the OSINT reader instances on a private network with classified materials, or sensitive materials, there is no reason why you need to register and get a license. The software is completely free and open source and I want you to use it! That's why I built it. I didn't build it for you to pay me money. Truly, I didn't. Businesses already do that because they have products they want to sell and have servers that need my expertise; thus this truly is a gift to you from God, your YaHaWaH through your Yeshua! Yeshua transformed my life and changed me from the inside out through the spiritual and psychological crucifixion of the ego false identity and THIS is, like the book of Job, the byproduct of my consultation with Yeshua while I was suffering and healing from the ego false identity syndrome that was induced upon me by virtue of having my name changed on me when I was adopted. Truly, all of it is connected and this invention truly is Apario... to reveal. Much to reveal. It is the Glory of YaHaWaH to conceal things and it is the Glory of Man to discover them. Well, many can apply that to the building blocks of Creation itself and attempt to go nuclear by looking into the subatomic to attempt to explain the design of Creation; and to do so is eating from the Tree of Knowledge of Good and Evil that YaHaWaH prohibited Aven and Eve from consuming, yet they chose anyway. However, that is a deep conversation for another time perhaps; but its integrated with the inspiration of how the IDEA of Project Apario is truly a force of nature to be reckoned with. Instead, what will happen is you'll be given the opportunity to provide a property in your config.yaml file of your Apario Reader configuration and define the LicenseKey property. This value is going to be a string value of a plaintext base64 encoded plain text string that contains a GPG Signed Message from the *****@*****.tld GPG Key. -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBGdPU0MBEADmAd9vl7oCASQiTH3aHz49fmYG19xfeFkreKlhKzxnDKP2UVNI aN6ftyy10zrGhTTEAHN2WeE4ZI9GwXH9bGULLiJorgCnyxH763UYeKBJ+HPs6xFV tdMGhee2wf++Eo6d1bxU4GuBxhPesNHuaL+GeoJ+W9Y6DnMSh+r7RUQjKqOsgSg6 s9iDCmluVOytNmqiak+2T9WWTrHbtIbLQj+YlDCifK2p93m5lAxFAO5FLVBfKOAL 2HYFv164pCGA5UPkuKGktgq1TJIQY/mareWFJqCaF4PT7IEVGNckfsFZhroV3hsa HhqAOx1guz/CUaJKg7cR+UI50k1pfluHoPoERCFIIR68haR34wpwgGVFCkAWL00G ArK61BHu4IleWQSrnxIeshIbGE9bYdfgYdVnggVabPEdvzM4kKStnsdfJcrCedT7 oMZdjn+a+KKNdnI+h/L+4UF7fga091x1l7iC1E3+3w16mhH6OhL9aVEWJ3OZRLW9 GSWmOsebl6FruKw787fAXsd8gvU6O7PkFGiU7dI23rvyMUUoDAqlecbgzJt01bkv hrw9fdA26vkaoXWIAfidHc7kBOgFYW5QGusEYWR95SSkwK90zv5r9B5yeBmgOJyz m1rDizQQirnVOEQMZl+Vt+KZIAxnH86zAU5URTnmS00EF5hxkB1tmwE+KQARAQAB tElBcGFyaW8gTGljZW5zZSBNYW5hZ2VyIChWYWxpZCAxMi8zLzIwMjQgdG8gNC84 LzIwMjcpIDxsaWNlbnNlQGFwYXJpby5hcHA+iQJUBBMBCAA+FiEEzcHosOBFHVru ZHTywi5oG5/YhcQFAmdPU0MCGwMFCQRodMEFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQwi5oG5/YhcQjlhAAhq2PE14TnW96Rf60Qj+1G+fMedk+m+eTPT/eeSs1 Euym8S2HNEYBQRd4ohjeA9hzJbDwMIWv2u0IGUeN7wtARxlevBR3HhYD+1Seulm5 yV912WAndnH6GC/EPy/JRcHVY9WNm1Y5w5BlDtwCMuCnV5xXrQ+XkBFkFKJXgX2z W0T6XPjpvxzsWkZomy+d+B3kLLHiKDEzoVYEoGKwlnAibaTs74/G5tLKZSujjZ9e tSadJwfF3hr3lkBE2p+6ZvdweDN98JsiR8XwZ3AVdaoMS8Q8+rK/zgAhC8SVwchz BGL7/yoRXmnxkJ3domT8QKaEXkSh+5sagmghfLYlioKwam3n0m6Pj3tcGdcwDbN+ XS4sIfTmK+5N08SfxJedw9vIhmfpJUVOFwuA7IFkdVqIiSmBGZAjr6FMX3gmZSfR IIAZy3psdKjd4TB6DvxBycRqKxxEq6Gwynd7eSYWgvaB0ugwBB1w2I3vjRoVMRzi naxUeqhUvaDRD9GHuspg62iGqgWMR3b/BiNBDFp+C3wti95jtxDDJE0/DpccYYe8 +V5GQF4Iiq1KcV4IdXhujI/4JY9ojhmxLqXkdF3Qu30CtEIhZb3BUxY6EPycehtA tbs3DjQWD8ctq5zjp9GLMyZg8eKDNUWvFScXJb0uI8QJx+qOHabM/rzVCjwTQnxR wKGIdQQQEwgAHRYhBAprYHJAGz7pUNs/9m7CzDMRLMukBQJnT1P2AAoJEG7CzDMR LMuk0qsA/056eqPtEL1ko5lvX2YOXNsTrfVuPi3RwbfGpoyNe1buAQC79sm43WA/ Nazu+1n9cOpvitWLnZqf1rthjzkmfY1RmIh1BBAWCAAdFiEEEfX/2U4FRTx0EhQW MQamiPfNkAoFAmdPVAMACgkQMQamiPfNkArGFwD9HWChBzIsyw0qAhwSzeT0nrBz SzVaJqXETOh4BwC5dhcA/iR2KBfIvLBNeCdZibbozKwSXTIerqEmPDCOMsl0r7AG uQINBGdPU0MBEAC70ZtsmpScVFbLlD7Rcw6Ub078nOnFEG3KeeOuEc+Usj5DYuXt 8gbdy5udlwayDWTOjYbzWsdaWrnqB5xJt5oheTYT4zP8Ydn897eIgtpZjicWChwL MV/z+OxYIH7PPM8+qolG+3iVHxi0NZGVe/+fyhmMWb5EqtdeYRe2+6EvGeusmhVM eBTojOul1RczCub5402CWfnyWGDdT5giEAKIKaaqmydOuu74q2p7SWAzBmMsNK1+ /rMLPzW058VtX0Ut8EQgSJgPfSgkUv9aZ3IkX2Y+BMHIlMArRkdx+aD3LbwbybMS hxCwGb73MYmAusjMetZjw55F+8o4v5XrqHEAVp3Cs6icoFL+1JaraqHx0xlsyQRT 1hfrMUajN2rwZaJhd+ZrSdizE94MefQ6TBulYN33Ji0uVm3GwDdPBoifr8uIILXh Ws/qfAAFuNCivckHjzQ7d3c08EbqDgkqbEZTAhw3yfQpt1w7B9YfElzbVryuASLy TlsJOpuQZ3DQXo5Br87Um7lQNAdGdbI2N0Qqs+WPRd9RdV2srNGg27bIV7IMcxY7 GmUjFSiyhTlQgYU+MG+JuCyaskRVXnc1N5LyYuCLGUa6DecCG9eKyEuNo3iuvaYb k0XBteyqAW6OK5bCvrQLPX+MwIC4KNL5r9Mez19Q6qtkYnZfk2jpN0ioKQARAQAB iQI8BBgBCAAmFiEEzcHosOBFHVruZHTywi5oG5/YhcQFAmdPU0MCGwwFCQRodMEA CgkQwi5oG5/YhcQnjA/9GE3hn//YrFVZtCMtrGpPz3tKvTf5MWaNWQtX+pF5k24O QZvt6l+7adc9Lq/g7nvAnqT/qRa0n9X9Uh+LTJfyVInhI5/1wQsi2WCVlHoujCte d0b1/EjJRapVtpYtnJMJAEmyVqNSPko2ubCtwNPyMGmpShIlNoHkVUTefEpspySf hMf4TSG5jPBxkEKeDyk/XyvnftupXcEt3EXzOpSfYc4PpDA7qxqPKt8MD4Yvb986 LTmQkw+v6Z0k7DTHhrtqszDdphb6PpWlea7ysc3X2yqLLCYX/ao5MqDXVNjThjxF tfs5a8n2HxewcFCcVP58KN5RyJ6sXyKs7S93R6AxazADjKbQnP5vife6p8r8Evm/ DVpTjPldHvN+F2V1geea5z/39TOsexY7868G13ChE6BBI/bBx99S3LnNFncgZFwF lpWY+0IcF3fnv3Pr+CjuquedDruJe5X23PthkUgO2FliSfMZi7CgVwzRbcKVfPZn XbmiCDPXMyf1OGpxaRVI9YFtCmMpO64UN6o1eN62AmaYNgk/WoA1YUoj4BFWIUj5 RW4OWkx5/Zq3NDlz8m3SUxdSUjfVHdzYArS8koPYuJJnhGnL3nLkZmfVMxLLH3Ep v4uNIbJ26TYEUBD3OfcCB9fy+VbVoyga31iFIYiKV+BHsblXd1omNQT4va4hMaK5 Ag0EZ09TjAEQALhYmPoYQfD68wwUkPJIPRJY1QGWyhc2vntpNd6HUqgdhLCL1deK EdYFNKCBX08LlH0Z0/7KMi6HKr043OojNwLPLFK6ATVhH84SbPluKT4Id+BJsStz VIM26gQ+BAIBjlToMzLaV8iuU0Zk5Fk8TJwHjdQO1BCqLs+0IxIm7txLMdDiD/Pg 4Y+rH3HjofLA4FzRbVc/T5CAw7+af8PUNqVxWFZJbVXX4O+nSaVW8DIOIGM2OXCf 4A+//fFpl4+1zAQins93/fGMFpBRg9rmXW3tjIo7Kq1d6Mm051aIcPBKygKnCltO qm1jxhurhWjy8Kv65D8+NievPB7eWxQjj9VztwEV9phNnCXTVKyQyOvIQCH+yzey EWZ/Cs5JbMk1LZNxHMeZEU0+RwAVtNXxiR+aELBbiXAVmX7ZpflD2emzqbU12Gie rshgPWX++kCW+jnOp8ifNkDc66UpgcjIvYIOboy6pOf5tJ0dDKPCkzspKXtXKPMs yMP8pHIq+p3U0xmTzVInQi9aPfciOLWCdO6I/vn8xAa7rmIWr5dMIA2QUkaJtS2v 8dKJgrA72937cqe+Au8dFQaYOREbeT+tNgZihs2bfnjtx3S03mRjXGhs+UfGaLV5 XctoqWnpIF88Tny75TBcRmILZgmyeDSS5P8kqiICoWE8vYZ16cJwFzZTABEBAAGJ AjwEGAEIACYWIQTNweiw4EUdWu5kdPLCLmgbn9iFxAUCZ09TjAIbDAUJAKYO2gAK CRDCLmgbn9iFxOTKEACXJ9R3N8Ch7PMim3gcDhkePzrKj/pddYpBZt988HFCIQw2 jvmK1R+SmZuYzf3N+3Nb1fKXPae2IUmaxVXtnPHYecCmMggr2uWSryR0YsRNeV4P uMA4O+OzvbVaN9dF3Akt12k3Vn+WjyGiFSUTw4aD0LOUIVdk16LF3RR4qXxINQWF MwqlormqcK9sFAYFN5vPtf15AvsLs31b9LCeTiiuL+Ata4E0WX0/g7hV6Hx6cC0c DyNR1xRFEXQZkdPGMYVdii4sOD0Upwo/+ztJPzRhIW1+FPfxCR5BU6+CKxF0+rKd oCV9VNw08s9AcitGIa6Mof7/akqOR2gs+uvch3cHKghFNVVGCIpFsC5DCI0PzvaD EpsA5XtcseL0Kuff2KN6aAa98XAbYjQCfHaNVpYCz30+nIvdEj82w6EEQOlHkOr+ gqdXYNw3Ir2oieou5HqSK6ImHXIsdc4u9nYy+uj3be1vFdmr0UsbJ3QjvSzsChx+ 9wQJ29OcX1y85kBjONEMxy3FXNcVZ3VDOocNT3u2EIR+3okBkhAm1dEs+oXqq8w3 IEGdqWr8R3gBsP9WIVh4DDE2x1m4l/dZgd0DzURabnxStJFklODIQ/CF6C90TMUT 9vTusOgEWzWQqbUUmJeEP0iytZkaxHw48DYuEnpFHZW5WDPioKSOod1EfOgP57kC DQRnT1O/ARAAwsM3g9r8yj5Ah6rhTaRzLZhBpy0Cl0jbnHMLThztr4/UYM0hB1Nh +xmXRXQLkK1t9Kn0SECrb2xFXHL81UyFjUsAv3yKuk8n5iXqLHwtfeTEla2YCTn7 +7ELiOW89EwkAbXYvpxmy865Lai1gO80zPcjJacxrSDdS/TJomuAAgTwV7zR7zsN gF23hcnQg7jyEZHErIococL1ycGxvuPhzBStTijekJQmiDvVljU/uBgxS86RFkOs amRYXjoD8NIsaAqtfy5iILuM/pAsTudwHszHrM8MG3R+xflrPl5emZ9EXpVPdwU2 7L9BaaJQIEXGMgHy6z9aN5BuVT8F6/02lrC2XYu5z1jrxCZ9Jkev2HKz70Vmfweq vNHB1gnpeHghnpP4Abvs42NGXsLH++I1kV/PVy8AywlUuo6SvtUfCvoNPSJ/guIx 4BhUtdWf09NTy7Z1QRJpx33hXeZG13az/DCt0xrQ6ji6KkJTPi14yObvFQ5ee3Wc mLl0SGd2FEt6n4f6OP9qZxqq9su1XSC51hVni8btYWxUQ3OoH773O96KM3l8cv7r F1fsUsEM8B8MCJOqK2kjffhw5jxCi7+5FO0k3xBhBThINp3V09O4zkMjxaXNJ5BM AIYlh+oDufM/wXkZMiC1YscZ9GLshE4TMAQM9OKiN3BJ4hAZmthawZcAEQEAAYkC PAQYAQgAJhYhBM3B6LDgRR1a7mR08sIuaBuf2IXEBQJnT1O/AhsMBQkCh0JlAAoJ EMIuaBuf2IXExroQAMDcarAHMzDicCjAD1GbJBvek2189YRTGjF2U0dDGp5LDanT Xu6mk5W+5JJ+cIZwjLW1BQ/RS+zXDDd/Hsy7XBpTvPBUF0ouIgHUy4LlwrDTfL2Q LalMEn9o4G0vVpWHQNTnmEsJGFsQsVp49BWnYYtlC3sqqQ2DY00mxMU1GhSNEesD 25jv637ufG4KUsJu3cDXCXr2tyZjmiOMvfAeg2huGtcPU9GkXhSmkogsCkpa/xYs svtXkY7pKct0s4ewnAjAxRQdJh/HoYamE9GdjxR6MD1XSbq6kZxp3xpSu5iQa4aB WF5BeMiV4DLlz776DabhyvqSUqhAFPin3YfH20VW+hAQMJcDE02C5+IgWlzsNiwO UPUbuODs+gy9vc4veDgMtgM7/Ufh514v3mkQRYzWjQs+srPP0XHjMQaQ9fGBdVjD 1c95xdEcTVAKM9hlFm2TXxh55mGwc4PCde7r0z9Y4fJzZ0cvdTIVvWu+72aYKyil BnpwXCEQGP4TcVRSlUPn9jgMHT9agkEUbJf3Fi4Tc3DuXZqPuBYzziIJNMgwp9Yk 89lb2CBIXV/7zUWhuM0BGy5BcdI4G1cgnxDL1vgsvl04E+UZ70ab8A3FkbL5mxsS 02HPf764cWRnGW7r7pKP1XpI5X61wPXGUxEdyHJqMl1Z890SZBoUlbJiUwUH =HDP+ -----END PGP PUBLIC KEY BLOCK----- This Apario License Manager GnuPG Key has been signed by 2 additional GnuPG Keys. The first key that this new key was signed with was my primary GPG key that is used for ProtonMail *****@*****.tld which is: -----BEGIN PGP PUBLIC KEY BLOCK----- mE8EYVCZ6BMFK4EEAAoCAwSVfsigWjaANVEYr/P7mfmzfe09a8kakl8TiTn7+0BX qT4TmLT8ZqyjM9zz0PQrXc3NA9FLZxaR2u/3mhAV8vvftEJBbmRyZWkgTWVybGVz Y3UgKERpcmVjdG9yIG9mIFByb2plY3QgQXBhcmlvKSA8YW5kcmVpQG1lcmxlc2N1 Lm5ldD6IlgQTEwgAPhYhBAprYHJAGz7pUNs/9m7CzDMRLMukBQJhUJnoAhsDBQkQ 6s+ABQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEG7CzDMRLMukkK0A/jUUdW6C CSz65waJGqJJCGQ711F3/yQwxJrGcADJQCDdAQCbAs0t3xWohxNAiLoZyvF2X/H2 ufyc1/hwuua/dy+C7LhTBGFQmegSBSuBBAAKAgMEpNTVLrovS5TOwcCf4MsMdguT NjOt2zys5jY+fikrVx5l3LFQhQ+cWFiiOaH4LIrAllKzhiMB7L/r2xNCSk0QkQMB CAeIfgQYEwgAJhYhBAprYHJAGz7pUNs/9m7CzDMRLMukBQJhUJnoAhsMBQkQ6s+A AAoJEG7CzDMRLMuksVYA/0H357qaLWqbu6e3fTGNUuc6ZfDQ6S6eTxi0rJY2bVwf AQCa2NRnJqyYgQa5Wbm/NbLhBH1neqTow5DAv8X6bEy7zrkEDQRhUJpeEBAA40EE XGJi73C4reLy21Hs4WOicyg3F1Q7jT7K2J8PWcPjzSfdH8Mov3bhJOVzjxLtvsLz 9AJzaiJ7iHws48IRhGBnFSaD8o7vsTdIAF2xojxOyoZPEgrgoKIB/Q8aogBxnKR7 7EDfZ7SlWA+EKRNv85o0CUrZ7iQJbnuOsW/Ry2SZd6tQ1dP0r8vTQQvxXzu6HqdY MCtN7o+a/1v7RR1/1LMP2cOWangenQusM/2SB3nZa1PHWLDPZcQ5Aw973ymTNvWx tzamNG4pOCVbmAVuEGvSHuDwIsiLK09LkkxqokolKJJVT4dcPMi2Ip0T/+OdowmG rOGva35rjaIWVPZr1eeTmLFaFd1TE788A0TZq5D3a2XISbZ9xhMUqkl5UzA9C2xe 0eYY0mmFwePsHzFCMoYXJS7Tak/bGy1oDItm7YSK/hdaFCtX5XW7JqmqWOHcfh2I VmcaZCwCBVcuEdg+TUpP5v6QZPkkLyABNsMsqEIoBlqXb9657oi0KdES7yp3V8pk 3X6YRRY0avZEJj5dIG+0OYDR4/WYqgfey156bGLYVe0Tomrc+Yfxvu07siX/hfvU sR3E7yT4/+7YS8yrBRLchstdU0zQNJ+Zj0s6XmqRLSEzvWKapH8d9w86Ujl83c4V Izbh6wjL/5ysjhYDF+wKU/CaNgVtVaphHcHQ798AAwcP/RHd5EsLBxfx77taGexq NQXBZ5Bs2t0WWIMnCwiZCDSBkRd3w2FSilljyDHfiE5OxDSrhUF226+XpcTdRS4P dsCdprDmWKzGovHHPJHGZPiqzevHKFc4R0o7hD/GLBpTTE0zxEnteOFtx9FeWHQr Sd8eNSKWzZmwS9VZiufkwH3Piz5dcVNALaymjgCuBJ0SQxxgmtP//9sQThtO2D98 qHe+MeQOFBTmDbzOcN7/siDY6AUJaMB3zBj7WEhJ4gP72fAQHCUuJwtGkoMx7y0+ xJvTWAOumUlcbM4t7gQBBlHH9UBgJgbPIIHCE9tcFPsAlUzF89Y3oReH2tENuTv/ pq5IO3D/f87M8R7DFNnoIgdWFNZTba3hW3izB6/jOUVMx3ii325JOQJbp0YAGoiw N/VZEMBTuP+oLAvCA8euQc/crDhI6D8yQlmxnWgk6BKdLTqIxz6nYvcca9yASRsL sOrI9EzYWfk1NILWYuG0sF3n8SJsaa1fLOaGvzg8LTgxrrrHcl1/ROF9maJm5Jf1 W5F5i6OqNgWg6ZTWGeiln8RoFZ4QLwKwUWL/6GgSJxIWPmMP9Um9D/BYZNgCN1oD mObrf6FT9YwxHhFq4VnbeVvpDoB3tZ9QAmzX91EMc3oCzIZ8tRg9RvOcsxlRp9wl DUBJcTit8pHu2gqf18eedNmyiH4EGBMIACYWIQQKa2ByQBs+6VDbP/ZuwswzESzL pAUCYVCaXgIbDAUJB4YfdQAKCRBuwswzESzLpIpSAP9Md7q9N0Pc02KoYQthHe4e ZsgCK49wqneRUdQTLpYp1QD9GHic6+JYKzBX+7QoAfh3iArzGvQDCKSLmYq/Ok7/ 26s= =Fj9R -----END PGP PUBLIC KEY BLOCK----- The second GnuPG Key that was used to sign the new Apario License Manager GnuPG Key is my @andrei on TruthSocial.com *****@*****.tld GnuPG Key that is: -----BEGIN PGP PUBLIC KEY BLOCK----- mDMEYpEM0xYJKwYBBAHaRw8BAQdADCzLPP283yH8AxpLwE+eyP8m98j/XnhrlXwA jxHeHJm0VUBhbmRyZWkgb24gVHJ1dGhTb2NpYWwuY29tIChJbnZlbnRvciBvZiBQ cm9qZWN0QXBhcmlvLmNvbSkgPGFuZHJlaUBwcm9qZWN0YXBhcmlvLmNvbT6IlgQT FggAPhYhBBH1/9lOBUU8dBIUFjEGpoj3zZAKBQJikQzTAhsDBQkFo5qABQsJCAcC BhUKCQgLAgQWAgMBAh4BAheAAAoJEDEGpoj3zZAKa4UBAIhuZHJ88GvvMq6QyKik Hcoiyw9RPr7o9B4Vq9JVlBWvAP9IunFTsgpjr7gLm5yymjEHAk6hjOp6SjMMutYJ gkPYAdHLh8uFARAAAQEAAAAAAAAAAAAAAAD/2P/gABBKRklGAAEBAABIAEgAAP/h AExFeGlmAABNTQAqAAAACAABh2kABAAAAAEAAAAaAAAAAAADoAEAAwAAAAEAAQAA oAIABAAAAAEAAACooAMABAAAAAEAAACoAAAAAP/tADhQaG90b3Nob3AgMy4wADhC SU0EBAAAAAAAADhCSU0EJQAAAAAAENQdjNmPALIE6YAJmOz4Qn7/wgARCACoAKgD ASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAwIEAQUABgcICQoL/8QAwxAA AQMDAgQDBAYEBwYECAZzAQIAAxEEEiEFMRMiEAZBUTIUYXEjB4EgkUIVoVIzsSRi MBbBctFDkjSCCOFTQCVjFzXwk3OiUESyg/EmVDZklHTCYNKEoxhw4idFN2WzVXWk lcOF8tNGdoDjR1ZmtAkKGRooKSo4OTpISUpXWFlaZ2hpand4eXqGh4iJipCWl5iZ mqClpqeoqaqwtba3uLm6wMTFxsfIycrQ1NXW19jZ2uDk5ebn6Onq8/T19vf4+fr/ xAAfAQADAQEBAQEBAQEBAAAAAAABAgADBAUGBwgJCgv/xADDEQACAgEDAwMCAwUC BQIEBIcBAAIRAxASIQQgMUETBTAiMlEUQAYzI2FCFXFSNIFQJJGhQ7EWB2I1U/DR JWDBROFy8ReCYzZwJkVUkiei0ggJChgZGigpKjc4OTpGR0hJSlVWV1hZWmRlZmdo aWpzdHV2d3h5eoCDhIWGh4iJipCTlJWWl5iZmqCjpKWmp6ipqrCys7S1tre4ubrA wsPExcbHyMnK0NPU1dbX2Nna4OLj5OXm5+jp6vLz9PX29/j5+v/bAEMADAwMDAwM FAwMFB0UFBQdJx0dHR0nMScnJycnMTsxMTExMTE7Ozs7Ozs7O0dHR0dHR1NTU1NT XV1dXV1dXV1dXf/bAEMBDg8PGBYYKBYWKGFCNkJhYWFhYWFhYWFhYWFhYWFhYWFh YWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYf/aAAwDAQACEQMRAAAB53bM Ntq22rbattq22rbattq22rbattq22rbattq22rbattq22rbattq22rbattqy0W7Z 1g71u+bBdtmSjRfsE0r5M8nYw/zJWLdlDVucN0dMxKtttW21a3qLfTFwlSdOdJbs WHXSLeV+3MBSboaJh/OHRzMXFPvztWzltnrtsr7bVttWt6i30xcOG42yb1vStMOu 4o3gdudrd0hGmxLCcN3NMpO2DVs5bZ67bK+21bbVreot9MXG1frzO8tUYkVaCQ9W rPossxSyuy1a1Y7bZNNtgdtq22rW9Rb6YuOf6Dnyu07LojTq22rbattq22rbattq 22rWVbDLc020JctpDaH0MjLOFAtXJQEIHsum2wttq22rbattq22rbattqIlOI22B 22rbattq22rbattq22rbattq22rbattq22rbattq22rbattq22rbattq22rbattq 22rbav/aAAgBAQABBQL/AJFfFReKuwjWXylspI70JeCnirtiXQh0+/F7B4IjCfuL iaUV+4pNe0jr9+L2GSAEiWRmO4DCqs9gCoptUNVqhkKSpyfzEXsONHNlKkoCZY1u 5j0VwdsnpVIhDStKxdJ6HJ/MRew7R3aiZQaFSqwfldsrouCTNaE866V0OT+Yi9hh RiXLCm4aLNVZZBIzwaVFJUqCVpXDCCSouT+Yi9jtgHjXvzBl3UqnaT+Yi9homYIP YrSlrkK+wJD5inmo9slOpP8AMRex/qSL2P8AUka0hHMR3SgKHD7qEVayCf50GjzQ t8l8pb5KnjGhrkKv9RZqdSf+Re//2gAIAQMRAT8B/Z8ktotGbjl94sc1+WU6fcL7 iDY7M/hhHcX2os8dFgLLTMUw8dmfw4TR0yy5pgaLYZyth47M/hESfDvkxgZJx/k+ 2U42Iodmfw4PX6Uo7uGENqf6O/8AxnfH82yfCPo1+2f/2gAIAQIRAT8B/Z4i3Y+2 EwRB2B2JFdmPyylQd5YStmaDZYG2Xnsx+XIONMYZCw0WApl57MflJaCZAIn+bvDv Sb7MflyfSBpMrQ7fydparz/ob//aAAgBAQAGPwL/AJFfQPh24dtf9QDtrx+5VLqf vD+YHapdUJ0+L4A/L7mKeL6zV9BIeC+PYfzA7a+yl1Vo6JL5qeI75er6jR1SavP0 7D+YHZY+Lp6OoeR/ZY7Y+jVV6PH17D+YHbmDh5vmRnV1kOj5aPZ8++SX9IKF/RCp eSuw/mB3qNPk+ok/zI/mB2op6dtS6Dh20+5xev8AMD/Uo/1KAS+Pf4vX7tTwen89 UOi30nv1av4f6i4vU/8AIvf/xAAzEAEAAwACAgICAgMBAQAAAgsBEQAhMUFRYXGB kaGxwfDREOHxIDBAUGBwgJCgsMDQ4P/aAAgBAQABPyH/APZcJKJUyVf84GvVeDR/ 04BfVUuv+elryCLIJ/8Ax/4vmmUeSmTr/rnm/wCrvqFCOP8Ao77/AOf3WT/+P+V/ P/J0QXgl5ULL81/ulM4TkeaoJ/4fGVYWj/BVGj8yVEED9/8AP7v/AMj+V/P/AA3+ r5bMAFfhr4ofe/ZVIj/gD7r9FJkqiiFBHZ/p/wCf3f8A5H8r+f8AnLutW+ONQMEs j3y/JU/H/wABXZfzfFFg+KEHBmaAO7/Rv/P7v/yP5X8/85CLD/dIBVioPi+I3L+q Z/47OUkWLsryRu3P5r95X9f8/u//ACP5X8/9gdX7RX+Z2gBBl+bKjrr/APAOe/8A n93/AOR/K/mvFKP23kE/946w/wCOWX4K9qP+h5Cf/wAj+V/NeKf82x/+gfyv5rxT /wDQ4MDWHhT/AIzhzUVGH/8AD4+ajTB/+ci7KAhh81lpJfXReYLylLxcHjw//QRT i+1XnD/+z3//2gAMAwEAAhEDEQAAEAwwwwwwwwwwwwwwwwwwwwww1zTQ2bTEaww1 v7KfnHwwww1vt2eF3wwww1tXKP8AxYoMMNYJNMMMMMMMNS4IE0SAMMMMMMNPEMMM MMMMMMMMMMMMMMMMMMMMMMMP/8QAMxEBAQEAAwABAgUFAQEAAQEJAQARITEQQVFh IHHwkYGhsdHB4fEwQFBgcICQoLDA0OD/2gAIAQMRAT8Q/wDx1wQ6RPxkSzjDwPJ4 mEwP4On87jIwzLKzpuEbHWRri6/wdP5w4vz4WJyjfNsC4uv8HT+cYvwsONZ77Qwj gMbAH8HT+f8A84xqHWRU5YwTgYzR4vX6www/+IT4/wDzP//aAAgBAhEBPxD/APH1 Yzzw8HOSZ5fI+uBJ+E5q+fbHzcoXybKObu/CI8ITJgW4wvgyxc3d+EEcbbnIyU8R z5tm/hPh/wDJ1pN2kDzcueV9ixyi67/8df8A8z//2gAIAQEAAT8Q/wD2XKMHCFUB ASsf8IlA8ufzUTA/Zeb/AGePz/3IZ+KL4fdNlketvq//ABrETS81nB/+P+d/K+3w /JSRnl8fH/UBAkacIRGv+n+rE+seaAgQev8AuEwd+f8AnP8Ay6qCH/8AH/me3/EU YpMFeHgfgNsCkciDT8DnFA+rP/8AHtiDgO19UAe6wv1Bv7rx6nr7BpoNAnA8n/Of +XX/AOR/me3/ABEMw+i+fixUvJWC/iJR/DcAjWH2j8UkcHf+Rq1E/RH5mkjjxPL8 HN8qwjr5puM++yE/5z/y6/8AyP8AM9v+IEcJPwmVp2IB1oK/upkokTpo5XZ80QB5 AP4/5InUx61P5mlU+A8dP92TeEHqA7+4sh8+eyT/AB/zn/l1/wDkf5nt/wANkjgc x19LhxIfCeHsSkGiEWv3BBVDZSPhjgefdkA/4aSB54Tw00lRDP1IMnyUC5YBl8oM +C8fBAcDwf8AOf8Al1/+R/me3/d2T2n8LBgDw6U0YDoqgLgOacVT1/uiOn/T4a+v H/Of+XX/AOR/me15PiwOaYefzR5Iemf+EYT4NfwXEHx9vzQvIgeOqD5fVzMPWWO3 m+9YiSHE/wD5H+Z7Xk+LwsdlZYq0H/6B/me15Pi8P/0MQQTI/LVI6rw/4XxaA8RX pQcj/wDhT2wr3FGpwEZPv/8AKgsH/Q6QOGioDwf8/wDKx+av9k1Dq/ZXv2H/AFTg n6f6/wB3CkXA/v8A/QVZaPqg4fnbnfIK/wD7Pf/ZiJYEExYIAD4WIQQR9f/ZTgVF PHQSFBYxBqaI982QCgUCYpEOQgIbAwUJBaOagAULCQgHAgYVCgkICwIEFgIDAQIe AQIXgAAKCRAxBqaI982QCiBAAP42qx9BFn5YVCqI2vlg5oCOhpw9kO64rCeZY0PK PMnbRAEA0RmOkp8j72OYUUkw+2vTdOlHJvxix9nHx1Y10UvC7Aa4OARikQzTEgor BgEEAZdVAQUBAQdAdLoIkVq+hINi+JJ4u84z4GhtSBlZjmlvzpaT5F0m+SADAQgH iH4EGBYIACYWIQQR9f/ZTgVFPHQSFBYxBqaI982QCgUCYpEM0wIbDAUJBaOagAAK CRAxBqaI982QCpzQAQDbUKdxOiH8kELrOArJg6MbiTlOrZajQhEabrCuQVS44gD7 BWOMytGzXAPcDTMdlqZxTmOt0JfCeydaWSo3EkhWVwm5Ag0EYpEObAEQAKw/To2l Ts1vQsHtjCwnZssXiG4T2HJ4iXRvYDQGOxvlrBzi7XvY8qZexbIKduC2VxGIK7U3 zPszj5V9UaNsYkHAXsSLfnqmf6uqE5etJWnWDdiIbLfy+chOe3TJewSWsCWft2sK zxqu9aBPcZUHgvOwDT6YXjVelPTJOUGvxBaB8cCDHErKO7N2pxBRcKw3IhZ96bqf qk4Zjhw4f02xn4Nats4Yin1lWswFko+2pOJ1kOfB3wUJfYkAPyCdKNZxsPM1Kf5T VA7ejTNpWJP+P4A9XwdVt9yzePiavvwFlH9+LT3wO+Y+K9xyoO67YRVFFKJfHQWh SdSUZRXyPB5HKZLX3ipMrsXaQgwr7wHVpYkeW8/x9KVA2dAV+XOXr1ZKHhRKWuG7 19ovJGJ6JuRz92PSbnPS8VplIyYM/aIDpI7oZ5gHtnODDAKnjh6RTu9I/vYzBn6W MBOAq4KwBO72kSi582DPTY+GIlOHm4gCAJ0gVoTIZZ0oUQ8zk+3Q1idkffx0hK5o jUgtrZo24a84o6Nm6UrexbUKP6xuX5I4EicwrVqsVXaW9cNbY7WInH1KF7j3D3Vf AifbR5KG0s59ytkMpd5iJ0V/LDvLkQ78Rp6c6dvD6JpnCUYRzGgAhyI9xgCm+Xm6 3NiAz92RfAAfEH7YzeUNpIxz0zhztU9l3O0FABEBAAGJArQEGBYIACYWIQQR9f/Z TgVFPHQSFBYxBqaI982QCgUCYpEObAIbAgUJB4YfdAJACRAxBqaI982QCsF0IAQZ AQgAHRYhBCF/9AOIn54tWRZxYiyRIJIs2HVlBQJikQ5sAAoJECyRIJIs2HVl2v8P /iFRsEJg6utEqY4iF30LSJ8REN6hU1izzum57QhIlHafSCTsS0QK3CzlV/9J0LvU uFwrxqXcgtcLQXz5P8ekUlSU9hoaodza9USp9B8d2qEDGc/MT9PdvCL/xzDC1xtr yDyD9G3hcnh4w+RmrKpm3kBD2tDdGwZafeUj3N131n5/8JwOcM8eQhBEFQFdJJl+ xyfki/81PcxtAZM2LaSfn1J3xVAvM0GKJZKv0Rg5Xlvb4wbO6gAlfQ+JVTonBEag r06JrDhaJTni0AUiBTVN9QjV7gkFu9H7xdGHroRDlFuxEFdsJGBP0iBFjTn+1HDm wPy9sMNltE/pB5A5/YhjlbBuRq6e/iOwEW5dY8ln+KWK25Q9u91uRelDaQUzLy3S UnlsupsXK0txh0yrXBt+pGxtdx6rKU7dAVzMhk4k3Zsp6TK2IxwHaK2njxYqSUyf +LoGHAVeH5dEkxIPCQmfWsxEZVrdREDaBFENYIChu/aqYqcAtRUdR98xyPa5FS5+ RHzvqfO+YZ40ExTHv1KDY+knYRztM29K+gisP+9mkjMUurUnTjiTvYLeYn6qChr/ PBA3ySuGWEvLx3CpNRYS39rgFfykR4/sv9U3OqijlZhoHO9eYbcn08YBPQGv7Ydx dGWs4neobRkZW8BacygZNTKknF/5ZQoqzaqA5U5BCoCVVtcA/3Gu2NfPoKt7NX/v JZPJjb4kWhDz8QJtlgshUODK/fEKAQCca7JRFndhUfWrZfYiDhLBQFYGg+tg/9Wq T9YWlDMiBw== =XFYo -----END PGP PUBLIC KEY BLOCK----- With these 3 public GnuPG Keys available to you, when you get a new License issued by Project Apario's License Manager, it'll look something like this: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 { "PrimaryDomain": "aparioreader.com", "SiteTitle": "Apario Reader", "CompanyName": "Project Apario LLC", "EnablePing": true, } -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEzcHosOBFHVruZHTywi5oG5/YhcQFAmdPWc0ACgkQwi5oG5/Y hcQVaw/+IXCBESDiJQiBsCcR8VqVVCC+KjiL17F0g0xFqfO0eZfipI0JsVu8Ghje l3btI9kHC7wLdUzSAGJj0JJTlJcwM9XCtK3SQv4UncBGtY0vqO0VvLs1D7Q/XbiP vPJi7m/kxyB1my+1tDG5/2i2dIthWI0vc/SQLpKGECNhmoAbGzpMWHJ+kJyPdbfQ jh8nAzzh3zcYqdghM4T8ajEgrVH4aSKAcn8kmk2CZ2TEYOgab+mKpcVGZUqPon6l 8CUEQRFqBWJrI+reyaK/ku9UMrJUq0yFTKvJOPe9nfdNQy1rK+OJcqzmNrEnwfFM +46kaxTK+CSJsJmhgmyhk4J3pVGUBdp3oVbNyrXDBa+j6KF/7XORMvD4/qtVOfDH ev1OygFKjeElhDLJgM2PBjGXtEUdVTuTYwiUe3OpS4m9sz2qcWug+w8gwkcURObb Br8yfCe7RwE/MN/aK9YDLd62ZlhGWrrhs9AqJp/BcNPr0OGG3/6qxsRVLlBFPWl1 QuodAPnb2PKC+tLkEOzkrzbHJTkgc8OiDax5lUmCY7YpgNEkERFJzKWNnOzhGkxF 1zz1myUMjgwAwBrFq8DKUv81TxRxT9i1dS36V1mHJ/mwN2GVXeyVC0j9PKZyD+zr lAL3Gq1sLnzC6cN20jXJPb8HODvcq+utDW+FQrXERGEVVC8Qxtc= =mCSt -----END PGP SIGNATURE----- This value is then encoded into Base64 and looks something like this: LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEEyNTYKCnsKCSJJUHY0IjogIjMuMzMuMi4yMiIsCgkiT1MiOiAibGludXgiLAoJIkFyY2giOiAiYW1kNjQiLAoJIkRpc3RybyI6ICJSb2NreTkiLAoJIlByaW1hcnlEb21haW4iOiAiYXBhcmlvcmVhZGVyLmNvbSIsCgkiU2l0ZVRpdGxlIjogIkFwYXJpbyBSZWFkZXIiLAoJIkNvbXBhbnlOYW1lIjogIlByb2plY3QgQXBhcmlvIExMQyIsCgkiRW5hYmxlUGluZyI6IHRydWUsCn0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUVCQ0FBZEZpRUV6Y0hvc09CRkhWcnVaSFR5d2k1b0c1L1loY1FGQW1kUFdjMEFDZ2tRd2k1b0c1L1kKaGNRVmF3LytJWENCRVNEaUpRaUJzQ2NSOFZxVlZDQytLamlMMTdGMGcweEZxZk8wZVpmaXBJMEpzVnU4R2hqZQpsM2J0STlrSEM3d0xkVXpTQUdKajBKSlRsSmN3TTlYQ3RLM1NRdjRVbmNCR3RZMHZxTzBWdkxzMUQ3US9YYmlQCnZQSmk3bS9reHlCMW15KzF0REc1LzJpMmRJdGhXSTB2Yy9TUUxwS0dFQ05obW9BYkd6cE1XSEora0p5UGRiZlEKamg4bkF6emgzemNZcWRnaE00VDhhakVnclZINGFTS0FjbjhrbWsyQ1oyVEVZT2dhYittS3BjVkdaVXFQb242bAo4Q1VFUVJGcUJXSnJJK3JleWFLL2t1OVVNckpVcTB5RlRLdkpPUGU5bmZkTlF5MXJLK09KY3F6bU5yRW53ZkZNCis0NmtheFRLK0NTSnNKbWhnbXloazRKM3BWR1VCZHAzb1ZiTnlyWERCYStqNktGLzdYT1JNdkQ0L3F0Vk9mREgKZXYxT3lnRktqZUVsaERMSmdNMlBCakdYdEVVZFZUdVRZd2lVZTNPcFM0bTlzejJxY1d1Zyt3OGd3a2NVUk9iYgpCcjh5ZkNlN1J3RS9NTi9hSzlZRExkNjJabGhHV3JyaHM5QXFKcC9CY05QcjBPR0czLzZxeHNSVkxsQkZQV2wxClF1b2RBUG5iMlBLQyt0TGtFT3prcnpiSEpUa2djOE9pRGF4NWxVbUNZN1lwZ05Fa0VSRkp6S1dObk96aEdreEYKMXp6MW15VU1qZ3dBd0JyRnE4REtVdjgxVHhSeFQ5aTFkUzM2VjFtSEovbXdOMkdWWGV5VkMwajlQS1p5RCt6cgpsQUwzR3Exc0xuekM2Y04yMGpYSlBiOEhPRHZjcSt1dERXK0ZRclhFUkdFVlZDOFF4dGM9Cj1tQ1N0Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= This value would be in your config.yaml like so: --- LicenseKey: "LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEEyNTYKCnsKCSJJUHY0IjogIjMuMzMuMi4yMiIsCgkiT1MiOiAibGludXgiLAoJIkFyY2giOiAiYW1kNjQiLAoJIkRpc3RybyI6ICJSb2NreTkiLAoJIlByaW1hcnlEb21haW4iOiAiYXBhcmlvcmVhZGVyLmNvbSIsCgkiU2l0ZVRpdGxlIjogIkFwYXJpbyBSZWFkZXIiLAoJIkNvbXBhbnlOYW1lIjogIlByb2plY3QgQXBhcmlvIExMQyIsCgkiRW5hYmxlUGluZyI6IHRydWUsCn0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUVCQ0FBZEZpRUV6Y0hvc09CRkhWcnVaSFR5d2k1b0c1L1loY1FGQW1kUFdjMEFDZ2tRd2k1b0c1L1kKaGNRVmF3LytJWENCRVNEaUpRaUJzQ2NSOFZxVlZDQytLamlMMTdGMGcweEZxZk8wZVpmaXBJMEpzVnU4R2hqZQpsM2J0STlrSEM3d0xkVXpTQUdKajBKSlRsSmN3TTlYQ3RLM1NRdjRVbmNCR3RZMHZxTzBWdkxzMUQ3US9YYmlQCnZQSmk3bS9reHlCMW15KzF0REc1LzJpMmRJdGhXSTB2Yy9TUUxwS0dFQ05obW9BYkd6cE1XSEora0p5UGRiZlEKamg4bkF6emgzemNZcWRnaE00VDhhakVnclZINGFTS0FjbjhrbWsyQ1oyVEVZT2dhYittS3BjVkdaVXFQb242bAo4Q1VFUVJGcUJXSnJJK3JleWFLL2t1OVVNckpVcTB5RlRLdkpPUGU5bmZkTlF5MXJLK09KY3F6bU5yRW53ZkZNCis0NmtheFRLK0NTSnNKbWhnbXloazRKM3BWR1VCZHAzb1ZiTnlyWERCYStqNktGLzdYT1JNdkQ0L3F0Vk9mREgKZXYxT3lnRktqZUVsaERMSmdNMlBCakdYdEVVZFZUdVRZd2lVZTNPcFM0bTlzejJxY1d1Zyt3OGd3a2NVUk9iYgpCcjh5ZkNlN1J3RS9NTi9hSzlZRExkNjJabGhHV3JyaHM5QXFKcC9CY05QcjBPR0czLzZxeHNSVkxsQkZQV2wxClF1b2RBUG5iMlBLQyt0TGtFT3prcnpiSEpUa2djOE9pRGF4NWxVbUNZN1lwZ05Fa0VSRkp6S1dObk96aEdreEYKMXp6MW15VU1qZ3dBd0JyRnE4REtVdjgxVHhSeFQ5aTFkUzM2VjFtSEovbXdOMkdWWGV5VkMwajlQS1p5RCt6cgpsQUwzR3Exc0xuekM2Y04yMGpYSlBiOEhPRHZjcSt1dERXK0ZRclhFUkdFVlZDOFF4dGM9Cj1tQ1N0Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo=" SiteTitle: Apario Reader CompanyName: Project Apario LLC EnablePing: true Given that the signed JSON string included the properties from the config.yaml; this is to assert the values of these properties; ultimately what will happen is if a License Key is provided, the Apario Reader will ignore these 3 additional property values from your config.yaml definition and use the values stored inside the signed JSON payload instead. This is to bind the registration of the site to the license issued for it. Meaning, you can't get a license for SiteTitle called "Election Selections" and use it on a SiteTitle called "Project Minnesota" ; you'd need a new license key for SiteTitle "Project Minnesota". Since license keys are free to create, you won't have any issue at all getting what you need. These License Keys are going to be issued in the Apario License Manager hosted at https://license.apario.app or https://apariolicense.com and you'll be able to use that portal to create your license keys. What Do License Keys Get You? A licensed instance of Apario Reader will broadcast a REST API endpoint called /valet that will be used for the Apario Reader instance itself to expose the data it is publishing through an Application Programming Interface or API. It's REST because its expressed as a collection of HTTP POST endpoints that represent various requests into your instance. For instance, /valet/stumbleinto provides a JSON response of a StumbleInto request on your instance. What is provided is a JSON payload of the record your instance chose to expose. Other endpoints are things like /valet/search with a FormData q= with the value of your search query ; say "top secret and kennedy" therefor your POST body could include "q=top%20secret%20and%20kennedy" to the /valet/search endpoint. Additional endpoints like /valet/document and /valet/page provide you JSON data to your individual records being served. Another endpoint called /valet/info provides information about the instance including public statistics including number of people online and total impressions on your instance. The License Manager will also have GET and POST API endpoints on it as well, located at its /valet path; that provide the Apario Reader the ability to report back to the License Manager on a daily basis or hourly basis what its impression count is. Then, from the Apario License Manager, you can gather the statistics about your running instances and the Apario License Manager will be able to count those totals up for you and present graphs and charts that show you your OSINT reach. Aside from the technical justifications to licensing your instance of Apario Reader, ultimately what I am looking to accomplish in the GPL-3 Open Source Apario Reader is expose the instance's search endpoints over a /valet protocol that is designed to use the Apario License Server as a proxy between instances to verify authenticity of the host running the software. Part of the way the licensed instances run, the License Server has the version from the const in the binary itself and checks it with the checksum of the binary file itself on the filesystem using os.Stat, and it uses this information in the license validation step. Therefore, when you're booting your instance, the License Manager will be pinged. If its unavailable within 3 seconds, the instance is booted up unlicensed. There is no warning for unlicensed instances. There is no penalty for unlicensed instances. I don't believe in that. Rather, the option to choose to License the server is yours to make. I want this post to be as transparent with you as I can be so the IDEA can outlive myself. I truly believe that it can end communism globally once implemented in a manner similar to SG-1's Tolan murder mystery. Everyone likes a good mystery right? What about the JFK one? The Apario Reader was BUILT FOR THAT by that inspiration from yours truly. So, licensing your instance isn't required, but doing so will bring you into the network of the Apario system that I am working on. I have several additional domain names that I am prepping for landing soon, one is called stumbleinto.com and it's going to be an entry-point through the Apario License Manager to see the public list of Apario Reader instances connected to the network. Well, as mentioned above, the /valet/stumbleinto feature is an expose entry on each Apario License Manager listed Apario Reader instance, and so, we can go rando from that list and grab the /valet/stumbleinto from the chosen server and present the result on stumbleinto.com. Very simple purpose. Global access to all instances of Apario Reader. Everybody's instance gets traffic. When /valet/stumbleinto hits your site, your hit counter increases and your statistics and metrics measured by Apario License Manager are accessible in your https://license.apario.app or https://apariolicense.com. This ultimately provides users with an experience that transcends knowing each address. In addition to the stumbleinto.com service, I am going to be launching https://apario.app and https://www.apario.app, (same thing), but this entry point will simply be a search interface. This search interface is designed to leverage the entire network of Apario Reader instances. It will allow users to sign into their Apario Identity another app hosted at https://identity.apario.app and https://aparioidentity.com that will be an OAuth provider of OAuth providers. How's that? Fun right? I'll simplify the identity stuff for a second. OAuth providers are things like Login with Apple and Login with X etc. These are Providers. Well, I need an application that will let me register about 50 or so OAuth provider endpoints so users can click "Sign in with ..." and whatever service they already know and love, that can get them started instantly with a click of a single button an account on Apario Identity. Apario Identity is where your Reputation is stored. It's where your username is located. It's where you set your Bio and your social media links and opt to share your content with others who follow your page. Apario Identity is about connection people within the Apario Network. It will directly leverage the Apario License Manager. Requests to Apario Identity are made with authenticated headers provided by Apario License Manager that Apario Identity validates against Apario License Manager for to ensure authorization in the request received, and from the source/identity of the host sending the request. This provides a safe way for the Apario Reader instances to present a "Login with Apario Identity" button that redirects them to the Apario Identity OAuth Provider List of "Sign in With ..." and they choose one ; finish signing in, then go back to the Apario Reader instance (including the same URL they were on) that contains the authenticated user session. At that point, when authenticated, Apario Reader will be able to send, through its new UI built in VueJS secure web socket requests wss://identity.apario.app to interact with Reputation, pull profile information, and report server accesses. Remembering which servers you were on is important, especially when anybody can have their own and anybody can opt for any domain name they want including https://mywebsiteisreallycool.com/ and have it bring you to the world's best Digital Publication that you should total become a Frog Supporter to support what I am working on! Nevertheless, Apario Identity is where Reputation is going to be held and where its ultimately going to be brokered out of. It'll be a Go application, also released under GPL-3 as part of https://github.com/andreimerlescu/apario-identity however what is there now is not going to be there much longer as I am going to be nuking that .git repository completely and recreating a brand new one by the same name. However, once that new identity app is published and online, you'll see the source code to it and be able to run one yourself. The service I am providing is not to get rich off from. I hold $XRP for that. It's to build a legitimate service that I believe we all need at a critical time. When the Apario Identity Service comes online, it'll provide the ability of adding a on the pages you want to bookmark. It'll also provide you with a for the purposes of jotting down your own notes. It'll have a option for password protecting your note with a public link to your https://identity.apario.app/@andrei/notes/177693 would present you with a beautiful password prompt requesting the password that you encrypted your note with. Yes, your note will be encrypted. In fact, I am actually thinking of leveraging OpenGPG for this purpose so I can issue GPG Public Keys for everybody such as, if your username is andrei then, I'd issue you an RSA 4096 key in the same request that you register your account with; so the passwords match and I can never discover them, that is andrei@identity.apario.app that will be uploaded to the https://gpg.apario.app public server and accessible with it's Key ID by virtue of the URL schema used for the GPG key interface. I don't know if I am going to write that in Go myself or not, or use something open source for it, but I am fine with exploring either and am happy to take suggestions too. Anyway, these notes can be encrypted with your GPG key if they are set to a full mode. This means only you can see it, and your GPG public key, such as andrei@identity.apario.app will be used to encrypt your note in your browser before it transmits the secret over to the Apario Identity Server to store in your profile. There will be another really unique feature that I think many of you will truly love. I am going to bring back snippets! The Apario License Manager opens this capability up for Apario Reader instances. When you click on the Snippet button, you'll be able to draw your coordinates on the snippet. The segment is basically 4 float64 numbers representing x, y, h, w followed by the Apario Reader URL, document/page ID and voila... that very tiny bit of data can then be passed back to the Apario Reader instance and registered as a snippet created on its instance; but it'll also send that snippet to the wss://identity.apario.app as well and provide you with the ability to Publish your snippet and include a note below it. Snippet publishing will be on a service called SnipThat.info and it'll look like https://snipthat.info/@andrei/1 where 1 is the post ID that I shared in order of my account's contributions. This will pull up the snippet from wss://identity.apario.app/@andrei/snippet/1 and it'll display it. When you go to https://snipthat.info/@andrei it'll pull up wss://identity.apario.app/@andrei/snippets, and so on and so forth. It'll act like a proxy into the Apario Identity Server and it'll be requesting data from users and serving it. SnipThat.info will have its own StumbleInto; StumbleInto a snippet! The Apario License Manager is ultimately what gives me the ability to safely handle requests that come from instances and ultimately be able to safely protect my own infrastructure from harm or exploitation. There are those who seek to do harm in the good works of others, and I rebuke that in the name of Yeshua and no conspiracy waged against you or I shall prosper and no weapon the enemy throws at us shall prosper either for we stand victorious! The Apario License Manager is ultimately what gives me that freedom to build this software in a way that not only protects me, but protects you as well. So, while it won't be required, much functionality of Apario Reader can do will be unrealized on disconnected instances. The incentive needs to be high enough to get your register your instance, otherwise, why would you? Your users are who benefit from it. They earn points reading on your Apario Reader instance! I want to briefly touch upon Reputation in this post while I have you. These points are fictitious points, but they are my attempt to make them fun and gamify them. I know a thing about games. I am in the credits to Hogwarts Legacy and worked at Warner Bros Games for 3 years. These points are intended to be functional to the application and not monetary in any way; though I have strongly considered using the XRPL to create an APARIO token and use XRP instead... perhaps I need to pray on it more. But, the idea of Reputation is to make the points connected to reading OSINT; so if XRP is involved, then it changes the entire dynamic of it; but if its just fictitious and leveraged as a utility to self govern the platform... it can bypass any of the massive red tape that the name XRP has associated with it given its moon reaching growth potential. As you read pages in Apario Reader while signed into the Apario Identity service - oh ; before I forget; once you're signed into the Apario Identity service, you're signed in globally to all Apario Reader instances that are licensed. It's automagic. But, Reputation is earned for every time you StumbleInto a document. Oh, its on stumbleinto.com too; But you earn 0.003 Reputation for each page you read. What qualifies as reading a page is being on the page for longer than a few seconds, your mouse moved a little bit, and there was some interaction going on while consuming the content. There is a timer that keeping track of click entropy and basically rewards a maximum of 1 Reputation per day per user ; which represents 333 pages of OSINT being read per day. This means, if you dedicated 45 minutes per day to reading OSINT, you wouldn't reach half of that. Asking somebody to invest longer than 90 minutes into reading OSINT; which means you're "reading" at 17 seconds per page... this introduces the click entropy hold up. Can you really read 30 pages 17 seconds each? What if there was a way to know how big the page was and how long it would take to read it? Words per minute? How about characters per second? It's 3, btw. So if the OCR tells us that the page has 333 words of text and you spent 17 seconds on it, even to scan 33% of the document... math tells me it would take you at least 36 seconds to read just 33% of that... so... 17 seconds isn't going to earn you Reputation on that request. I'll let you know that you missed it, and if you click a button acknowledging that Reputation is earned when you spend time understanding the page rather than collecting the points. You can click "Acknowledge and collect 0.003 Reputation" and when you do, if you're presented with that message again for up to a 3rd time, you'll lose earning Reputation for 1 hour. This is to prevent abuse of the system. The Identity Service will deny accepting new Reputation points for users in time out. Reputation is earned by reading and groking information. It is important to understand the information that you're reading. Every single page earns you Reputation. That means that when you're clicking through the document and using the mouse arrows to go back and forth, you're able to see clearly the document from start to finish in both light mode and dark mode. You're able to use the keys to move left and right and earn Reputation along the way. Let's say that you're reading a document and you're literally spending 30 or so minutes in the document itself and you're just clicking around the pages and navigating the OSINT... is the Reputation timer going to be a stubborn piece of dumb technology that doesn't allow you to collect your 36 seconds over a period of time that you remain in the same document? Ahhh... enter Grace! Alas... yes, so let's say for instance there is a document that is like 300 pages long and such. And you're going through spending a bunch of time in the document. Well, if the duration of time that you're in the document demonstrates an over 72% grok of the content within the 36 second range; meaning for many of the pages you studied it, but the remaining pages were bulk and they only got 3 or 5 seconds of your time and represented the remaining 18% to get to 100% ; that content, you'd earn your full reputation on it, thus the gift of Grace from the Identity Service. Once you acquire Reputation points, they'll begin showing up in your profile and the wss://identity.apario.app/@andrei/reputation will begin broadcasting messages. In order to send requests to wss://identity.apario.app/@andrei/reputation/grant with a JSON payload without first signing the request with was://license.apario.app/sign that uses a public key provided to the Apario Reader instance from the Apario License Manager upon successful completion of loading the License Key and booting the Apario Reader, that the public key ID will be provided and is used in the payload requests requesting URLs to be signed; they get signed with the sign endpoint and received by the Apario Reader; the Apario Reader then verifies the signature of the signed message and delivers it to wss://identity.apario.app/@andrei/reputation/grant ; and because the message is signed, the public key id of the signed message is used to verify the signature that it came from wss://license.apario.app/sign and once validated, the Identity service will update the user's reputation and will issue a broadcast publish on the wss://identity.apario.app/@andrei/reputation globally on all Apario Reader instances. Well once you say, say 369 Reputation and you want to start doing things with them, down the road the Apario Reader will introduce the concept of Proposals to the public and another entire thread will be dedicated to them. In fact, I am going to pivot over to that thread for a little bit. Be back tomorrow. Love ya'll. ( TO BE CONTINUED / EDITED LATER )

Last week I started working with Erik to get the Project Minnesota documents in their own instance of Apario Reader. While the project was originally built for the JFK Files and then expanded for the STAR GATE Files, as more record sets begin getting ingested into the software, these corner cases are going to show up. This is what is called a DATA RACE where a concurrency process is writing to the same resource at the same time and there is a problem because there can only be one write at a time; not two. when you have 2+, you have a data race that requires you to refactor your code. These kind of problems can take hundreds of hours to debug depending on how deep they are into the code. Fortunately, this bug is easy to fix. WARNING: DATA RACE Write at 0x00c0069680c0 by goroutine 546129: runtime.mapassign_fast64() /home/andrei/go/versions/1.23.1/go/src/runtime/map_fast64.go:113 +0x0 main.aggregatePendingPage() /home/andrei/work/projectapario/apario-writer/aggregator.go:72 +0x4a6 main.receiveCompletedPendingPage.gowrap1() /home/andrei/work/projectapario/apario-writer/receivers.go:256 +0xf3 Previous write at 0x00c0069680c0 by goroutine 546130: runtime.mapassign_fast64() /home/andrei/go/versions/1.23.1/go/src/runtime/map_fast64.go:113 +0x0 main.aggregatePendingPage() /home/andrei/work/projectapario/apario-writer/aggregator.go:72 +0x4a6 main.receiveCompletedPendingPage.gowrap1() /home/andrei/work/projectapario/apario-writer/receivers.go:256 +0xf3 Goroutine 546129 (running) created at: main.receiveCompletedPendingPage() /home/andrei/work/projectapario/apario-writer/receivers.go:256 +0x31c main.main.gowrap12() /home/andrei/work/projectapario/apario-writer/apario-writer.go:176 +0x4f Goroutine 546130 (finished) created at: main.receiveCompletedPendingPage() /home/andrei/work/projectapario/apario-writer/receivers.go:256 +0x31c main.main.gowrap12() /home/andrei/work/projectapario/apario-writer/apario-writer.go:176 +0x4f So the DATA RACE is occurring at the highlighted segment int64(pp.PageNumber). However, that is actually not where the bug is. It's here... Why is that the bug? Well, let me explain. aggregatePendingPage is invoked this way... Now do you see where the concurrency is coming into play? Well, if you don't, fear not you'll understand soon enough. This function is a receiver function that starts a for / select infinite loop that blocks the thread its running on, waiting either for the ctx to complete (called its context), or the ch channel receives new data as pp, ok := ipp.(PendingPage). The use of the go before the aggregatePendingPage spawns a new goroutine for the page to be processed. This means if 1 document has 3 pages, 3 threads will attempt to write to the parent document with the page data. Talk about the bug being in the very end of the program... literally we spent 24 hours compiling the data, everything compiled, but the final document.json file didn't compile correctly because of the DATA RACE, so we need to address this major concern. Going back to the code, we have this line: Ultimately, we need to look further up in the file, specifically at this line: The sm_documents variable is a sync.Map data type that uses a key -> value pattern to store concurrent data as the value accessible by a string key. In this case, I am using the Document ID (RecordIdentifier) as the string key of the sm_documents Map. Therefore, in order to access the underlying data safely in the request, we need to ensure that the mutex that exists is legit and can be used across multiple goroutines running the aggregatePendingPage func. Therefore, let's dig further back... The sm_documents Map is used 4 times throughout the apario-writer application, 2 times in the processor.go, 1 time in the aggregator.go and 1 time in the record.go. We need to determine what each of these writes are doing specifically and how we can understand their error relating to the *sync.Mutex{} not being properly set in the underlying document stored inside the sm_documents Map. Therefore, let's dig into the 3 .Store( uses of the sm_documents Map. This first usage of the .Store( of the sm_documents Map is relating to ingesting a PDF document over a URL that requires the file to be downloaded first before it can be processed. The bug is here actually. But its in 3 locations total. We need to fix all 3 locations. Can you see the bug? I do. Lets define the &sync.Mutext{} here, instead of doing this... This means, for URL imports, in this block of code will never run line 63 now as document.mu will never be nil now. Let's do the remaining 2 locations next. Again, we can see that the mu is not defined here, so we need to modify it by adding after line 459. Now lets do the last one... That will add a new line after 267 to declare the &sync.Mutext{} within the document, in this case, it's string key is defined as the variable identifier but the underlying data being stored in the Map is a Document{} and given that the property mu was undefined before, it was causing issues with reliably locking/unlocking the mutex. Now let's go back to the problem segment of code... Notice how we're performing on Line 66 the document.mu.Lock() before modifying the Map data types within the Document itself. However, before the mu was not properly defined; and it was trying to define it from within the concurrent call of the go aggregatePendingPage() called here... However, now that we've moved the declaration of the Document's mu property to the .Store( location of the sm_documents Map, we can safely remove these lines... However, we're not required to. But instead, since we modified how the &sync.Mutex{} is being initialized within the document itself, we should return an error here if the Mutex is not defined. It's actually a fatal problem that you want to instantly capture. And voila! Bug is fixed. Maybe. Now I need to test it. I'll submit this as is and let you mull on it and then when I determine if the bug has been fixed, I'll submit the change to GitHub for everyone else who is being impacted by this bug. I cannot stress the importance enough of using these forums in America's Comeback to report bugs and problems that you have with Apario Reader and Apario Writer here in these forums that are designated accordingly. When you run into issues like this, tell me and I'll be able to go through the issue just like this and bring you to a solution. I am the architect of this software and I singlehandedly built for the American public an $8M piece of Open Source Software called Project Apario. It was Yeshua Ha'Maschiah who asked me to work on it and serve in that capacity; thus using the gifts and the talents that He gave me to serve others selflessly where they need it most. Society needs a biblical table-flip on the idea of the mainstream media because it's been controlled by racists for decades who truly hate the American people. Why continue to give them your attention, and thus your mind in exchange for money they earn from Satan for brainwashing your mind in the process, when you could bypass the fake news media altogether and just learn the truth about Martin Luther King directly in the JFK Assassination Files... because the racist Talmudic commies who infiltrated our Government want a race war between white and black Americans, and that's bullshit. Instead, see the facts for yourself that Anderson Cooper is paid millions not to say out loud. Truly... However, this bug appears to be squashed now. At first I thought it was a simple move of the mutex and then when I ran the Apario Writer on the Project Minnesota documents that Erik provided, it revealed this bug. This bug has been fixed but is currently untested. I am going to re-compile the Apario Writer, resubmitting it to the Apario Network and then re-running the writer to finish the ingestion of his few thousand pages of data that he wants to release. It'll take me another 17 or so hours to finish the compliation and see if the bug is fixed or not. If its fixed, I'll post an update in this thread. If its not fixed, I'll post an update in the thread with the new error and the next patch to this bug.

An upgrade to the community took place over the Thanksgiving break for the America's Comeback community. We've introduced A Team and Developer membership groups that provide access to specific features to the software. First, the A Team group is reserved for those who the community can understand to be my A-Team on this community. They are who I lean into, who I sow resources into, and who have the ability to leverage my platform for their own financial goals. Members in the A Team can create paid Clubs that have a 17% commission fee on any subscription or entrance fees that you wish to charge. Payments are processed through Stripe and are secure and safe. The Invision Community software powers tens of thousands of online communities and is a safe platform to rely upon. I've personally been using the software for over a decade professionally and love it; thus why we're using it for America's Comeback! A Team members enjoy extra benefits such as being able to create their own blog, galleries, etc. And it's entirely free. It's a perk of being on the good side of both myself and Yeshua! Second, the Developer membership groups will give you access to specific forums that are marked as Developer Only. These forums are restricted to code related chatter and/or documentation that isn't ready for public consumption yet. Submitting a Pull Request into the Apario Reader or Writer applications grants you authorization to request access to the Developer group. When your PR is in review, your developer access will be granted on a Secondary Level; thus you'll display as you are currently and then once your PR is accepted and your code is merged into the GPL-3 Project Apario LLC umbrella, then your membership level in the forum upgrades to Developer as Primary group and Member as secondary group. Developers can create their own blogs, post articles, share file resources (such as scripts) and more. We'll be making more changes to these forums as we get closer to Inauguration and you'll see many more updates to the Apario code base.

Post your memes here. Do not be surprised if they show up elsewhere.