Andrei

I am retiring from being a software engineer and a programmer. I am changing careers entirely and I never want to do computer programming work again, so help me Yahuah. I had the America's Comeback forum offline while President Trump was inaugurated and the first wave of the administration was in play, but its clear to me that nobody - and I genuinely mean that - nobody wants me to be involved with Project Apario and so long as I am involved in it, nobody wants anything to do with it. Fine, I love you too. Remember, I pray for my enemies and I consider all humans to be my enemy. Humanity has not yet repented or faced its tribulation for the orphanages and those who were running them.

Project Status: ABANDONED ETA: Entropy will collapse the universe first I am abandoning the project because I want nothing to do with it anymore. It was needed, but you didn't want me to build it for you, and because I did build it for you, you chose not to use it. I lost over $60,000 trying to help you, the American people, and while my efforts were not in vanity, I refuse to spend another dime on a group that has shown me how grateful they are for the effort that I put into making this project. Truly, I am bitter at the world and I do not want to have anything to do with this project anymore. Anybody who comes at me to support this project, please don't. I will tell you to fuck off and then I will get upset at you for reaching out to me. The software is open source. You can run your own copy if you want. If it doesn't work, you can fix the code. I do not want to help you anymore on this project and I refuse to be abused by this project any further. Thanks for all of the help. I really appreciate you.

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!