Andrei Posted December 5 Posted December 5 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! Quote
Andrei Posted 17 hours ago Author Posted 17 hours ago 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. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.