Introducing Apario License

Andrei · December 4, 2024

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.

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:

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:

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 )

Andrei · December 26, 2024

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!

Sign In

Introducing Apario License

Recommended Posts

Andrei

Andrei

Join the conversation

Browse

Activity

Store

Support