DEV Community: Adeyeye George

Zion Runtime: Why I'm Building an AI Operating System

Adeyeye George — Sat, 25 Jul 2026 14:57:39 +0000

I want to tell you something before I show you any code.

Right now, if you want to run a serious AI model on your own machine — not through an API, not paying per token, just your own hardware doing the thinking - you almost need a powerful laptop or a GPU most people in Africa will can't afford. A student in Nigeria with a 4GB RAM laptop. A small business owner running an old desktop. A developer who wants to build something intelligent but can't afford cloud credits every month. AI, as it stands today, was not built with them in mind.

I kept asking myself: why should intelligence require expensive hardware? A phone can play a video. A phone can run a game. Why can't it run a model that actually thinks, and think well, without freezing, without draining the battery in twenty minutes, without needing 16GB of RAM it doesn't have?

That question is the whole reason Zion Runtime exists.

What I'm actually building

Zion Runtime is not another wrapper around an existing model. It's a runtime - an operating layer - that looks at whatever machine it's running on, figures out exactly what that machine can handle, and then makes the smartest possible decision about what model to run, how much memory to give it, how many threads, whether to touch the GPU at all. Then it runs it efficiently, without choking the rest of your system.

Plug in a tiny model, it runs fast and smart. Plug in a bigger one, it adapts. Different models can specialize in different domains and the runtime routes between them intelligently, so you're not stuck with one model trying to do everything badly - you get several doing their part well.

The first working piece is alive already: a profiler that reads your actual hardware, a capability analyzer that turns those numbers into "here's what this machine can realistically do," and a planner that picks the model and settings to match. No guessing. No pretending your 4GB laptop is a server.

That's stage one of many. Memory-mapped model loading so a 7B model doesn't try to swallow all your RAM. A downloader that fetches the right model for your hardware automatically, or lets you choose manually if you know what you want. A way to free up memory from idle background processes while inference runs, and hand it back the moment the work is done. A queue system that can hold up under real load - a thousand people hitting it at once - without falling over. All of it built small, in the open, one piece at a time.

There's one more piece I already have working, and it matters more than it sounds: the domain models talk to each other. If you ask something that touches money and then shipping, one small model can specialize in the finance side and another in logistics - but neither should ask you to repeat yourself. The moment the finance model learns the amount and the destination, that understanding sits in a shared memory both models can read. Hand-off happens without you noticing it happened. Nothing gets missed because "that wasn't my domain." This is the difference between a pile of separate small models and one system that actually understands the whole conversation.

Who this is for

This is for the open-source community. Every part of the design will be documented. Once the core is stable, I'm releasing the full specification publicly - not just the code, but the reasoning behind every decision - so anyone, anywhere, can build on it, fork it, improve it, or run their own version without asking anyone's permission.

I believe AI that only works well on expensive machines isn't really solving the problem. The people who need efficient, offline-capable, low-cost intelligence the most are usually the people with the least powerful hardware. That gap is what I'm trying to close.

The part I don't usually say out loud

I'm building this alone, at night, between everything else life demands of me. I'm a father of three, and I carry my family's needs the same way I carry this project - mostly on my own, without a team behind me, without outside funding, without a safety net if a month gets hard. Some weeks, choosing to keep building this instead of only chasing paid work is a real sacrifice, not a figure of speech.

I'm saying this not for sympathy, but because I think it's fair for you to know exactly who is behind this before I ask you for anything.

The ask

I'm trying to raise $5,000 to keep building Zion Runtime properly - research, time, the basics that let me keep my head down and finish this instead of stopping halfway. That number isn't the goal, it's just what would let me breathe while I build.

If this project means something to you - if you believe AI should run on the machine you already have, not just the one you wish you had - you can support it with any amount. One dollar counts. It genuinely does. This isn't about the size of the contribution, it's about enough people deciding this is worth existing.

Every supporter, whatever the amount, gets a permanent place on the project repository as a sponsor, with my full public thanks and respect - this project remembers the people who believed in it before there was much to see.

Please donate here @Support link

What happens next

This is a build-in-public series. Every real piece of progress - every module, every hard bug, every design decision - gets a post here, in plain language, so you can follow the whole journey from an empty folder to something the community can actually run.

Next up: memory-mapped model loading, so a model bigger than your RAM doesn't take your whole computer down with it.

Thank you for reading this far. If you're still here, you're already part of this.

To contribute on code check GitHub Repo

How I Built MailOS: My Journey With Qwen Cloud

Adeyeye George — Mon, 20 Jul 2026 09:06:17 +0000

I want to tell you a story. Not the polished kind you see on a pitch deck, but the real one — the late nights, the small wins, the moments I almost gave up, and how Qwen Cloud carried this whole thing on its back.

The problem that wouldn't leave me alone

If you have ever run a small business, or even just managed a busy inbox, you know the pain. Email doesn't stop. Customers dey ask questions. Suppliers dey negotiate price. Newsletters dey pile up unread. And somewhere in that pile is the one email that actually matters — the one you missed because you were tired and scrolling too fast.

I kept asking myself: why is email still this dumb? We have AI that can write essays, generate images, even hold a conversation better than some humans. But my inbox? Still sitting there, doing nothing, waiting for me to read every single message myself.

That question refused to leave me. So I decided to build something.

Why I chose Qwen Cloud

I tried a few things before I landed on Qwen. Some models were fast but shallow — they could classify an email as "spam" or "not spam" but couldn't hold a real negotiation across many back-and-forth messages. Some were smart but too expensive to run for every single email that touches an inbox, and email touches your inbox a lot.

Qwen Cloud surprised me. It was strong enough to read a messy, badly-formatted business email and actually understand the intent behind it — is this person trying to sell me something, complain, or trick me? It was fast enough that I could run it on almost every message without my server crying for help. And honestly, setting it up wasn't stressful at all. I created an account on Alibaba Cloud's Model Studio, generated an API key in a few minutes, dropped it into my .env file, and I was talking to Qwen from my code before my coffee got cold.

That was the moment I knew: this is the engine my project needed.

Building MailOS, one agent at a time

I didn't want to build "just another AI email assistant" that summarizes your inbox and calls it a day. I wanted something that could actually act — read mail, judge if it's dangerous, understand what it wants, and in some cases, respond and negotiate on its own, without me babysitting every message.

So I broke the work into small, focused agents, each one doing one job well:

Guardian checks every incoming email for phishing and prompt injection before anything else touches it. I built this one first because trust is everything — if my system can be tricked by a bad email, nothing else matters.
Classification figures out what kind of email it is — customer message, invoice, meeting request, newsletter, spam.
Memory remembers what matters. Not everything, just the important stuff, the way a good assistant would.
Newsletter Intelligence reads through newsletters, pulls out the ideas and trends worth knowing, so I don't have to read fifteen newsletters myself.
Decision looks at everything and decides: archive this, notify the owner, draft a reply, ignore it, or hand it over to a human because it's too important to guess.
Negotiation is the one I'm most proud of. This agent can actually go back and forth with another mailbox — asking for a better price, agreeing on payment terms — all inside a policy I set. It has a hard round limit and a confidence floor, so it never runs wild. If it's not sure, it stops and calls me.

Every one of these agents leans on Qwen Cloud to think. Not blindly — I never let the AI make the final call on money or risk by itself. The AI proposes, my code decides. That balance took me a while to get right, but it's the part I trust the most now.

The moment it actually worked

I remember the first time I watched MailOS negotiate a deal by itself. I sent an opening offer through the API, walked away to make food, and came back to find three full rounds of back-and-forth had happened — politely, professionally, in plain English, over normal email — and it landed inside the price range I had set. Nobody touched a keyboard except me at the very start.

I just sat there staring at my screen. That's when this stopped feeling like a hackathon project and started feeling like something real.

Taking it to Alibaba Cloud

Building it on my laptop was one thing. Making it live for the world was another matter entirely. I moved MailOS to an Alibaba Cloud ECS instance — a simple Ubuntu server, nothing fancy, 2 vCPUs and 2GB of RAM was more than enough to start. I installed Node.js, cloned my repo, set my environment variables, and ran the whole thing under PM2 so it restarts itself if anything goes wrong. Then I put it behind Nginx with HTTPS so my login sessions stay safe.

Watching MailOS run on a real server, connected to a real mailbox, reading real mail, all powered by Qwen Cloud sitting quietly in the background — that was a proud moment for me. No wahala, no drama. It just worked.

What I learned

Building MailOS taught me something I didn't expect: the hard part of AI agents isn't making them smart. It's making them trustworthy. Anybody can wire an API call to a language model and call it "AI-powered." The real work is in the guardrails — the policy checks, the round caps, the moments where the system says "I'm not sure, let a human decide." Qwen Cloud gave me the intelligence. I had to build the discipline around it.

Where this is going

MailOS isn't stopping here. I'm working on a way to export an agent's whole memory so you can move it between servers without starting from zero. I'm also building something wild — a trust score that remembers how every contact behaved in past negotiations, so MailOS treats a trustworthy supplier differently from a stranger, automatically. And the one that still makes people's eyes widen when I explain it: teaching MailOS to pick up the phone and make an actual voice call when an email negotiation stalls, then write the outcome back into the thread like nothing happened.

Email was never designed for this. But with Qwen Cloud doing the thinking underneath, I don't think that's a limitation anymore. It's just the starting point.

If you want to see it, break it, or build on top of it, MailOS is open source. Come and look at https://github.com/mitmelon/mailos.

Built with a lot of coffee, a lot of debugging, and Qwen Cloud carrying the intelligence the whole way.

Thanks for reading.

How I Built CampChat: A PHP-Powered Chat Engine That’s Changing the Game

Adeyeye George — Sun, 08 Jun 2025 16:22:21 +0000

As a developer, I’ve always been fascinated by the magic of real-time communication. There’s something thrilling about crafting a system where messages zip across the internet, connecting people instantly. But building a chat app from scratch? That’s a beast—encryption, scalability, bots, oh my! So, I rolled up my sleeves and created CampChat, an open-source, PHP-based chat engine that’s secure, scalable, and packed with features inspired by Telegram. It’s the kind of project that makes you lose sleep (in a good way). Let me take you through my journey of building it, why it’s a game-changer, and how you can start using it with a few lines of code.

Why I Built CampChat

It all started late one night, fueled by too much coffee and a frustration with existing chat solutions. I needed a backend that was lightweight, developer-friendly, and didn’t require a PhD in distributed systems to scale. Most frameworks were either too rigid or overly complex, and I wanted something that could power a community app, a support portal, or even a social platform without breaking a sweat. PHP, with its accessibility and vast ecosystem, felt like the perfect fit. So, I set out to build CampChat—a chat engine that combines modern tech like Slim Framework, MongoDB, Redis, and RabbitMQ with Telegram-style features like group chats, end-to-end encryption, and extensible bots.

The goal? Make it easy for developers like me (and you!) to spin up a secure, real-time chat system without reinventing the wheel. After months of coding, debugging, and more coffee, CampChat was born. It’s not just a tool—it’s my love letter to the developer community, and I’m excited to share it with you.

What Makes CampChat Special?

CampChat isn’t just another chat backend. It’s designed to be your Swiss Army knife for communication apps. Here’s what sets it apart:

Privacy First: End-to-end encryption for messages and media, because no one should snoop on your users’ chats.

Scales Like a Dream: Redis for caching and RabbitMQ for async event handling mean it can handle thousands of users without hiccups.

Bot Magic: Create bots with webhook support to automate tasks, like welcoming new group members or moderating chats.

Feature-Packed: Group permissions, message reactions, pinned messages, and media sharing make it feel like a modern social platform.

Open Source: Under the MIT license, it’s free to hack, tweak, and build upon.

Think of it as Telegram’s core, reimagined for developers who want control and flexibility. Whether you’re building a niche community or a customer support system, CampChat has your back.

My Struggles and Triumphs

Building CampChat wasn’t all smooth sailing. Early on, I wrestled with MongoDB’s schema design to balance performance and flexibility for storing users, groups, and messages. Getting RabbitMQ to handle bot events asynchronously was a headache—until I finally cracked the queue configuration. And don’t get me started on implementing end-to-end encryption without sacrificing speed! But every bug squashed and feature added felt like a small victory. When I sent my first encrypted group message and saw a bot respond via webhook, I did a little happy dance. This is the kind of project that reminds you why you love coding.

Let’s Get You Started

Enough about my journey—let’s get CampChat running on your machine. It’s surprisingly simple to set up, and I’ll walk you through the basics with some code examples to show off its power.

Setting Up CampChat

Clone the Repo:

git clone https://github.com/mitmelon/campchat.git
cd campchat

Install Dependencies:

composer install

Configure the Environment: Copy .env.example to .env and fill in your MongoDB, Redis, and RabbitMQ details:

MONGODB_URI=mongodb://localhost:27017
REDIS_HOST=localhost
REDIS_PORT=6379
RABBITMQ_HOST=localhost
RABBITMQ_PORT=5672
RABBITMQ_USER=campchat
RABBITMQ_PASS=1234567890
STORAGE_TYPE=local
STORAGE_PATH=/path/to/storage

Set Up Storage:

mkdir -p /path/to/storage
chmod -R 775 /path/to/storage

Run the Server:

composer start

Start the Bot Worker: For bot event processing:

php src/Workers/BotWorker.php

Your API is now live at http://localhost:8011/v1. Time to have some fun!

Code Examples: CampChat in Action

Here are a few examples to show how easy it is to integrate CampChat into your project. These use curl, but you can adapt them for any HTTP client in your preferred language.

1. Creating a User

Let’s create a user account to get started.

curl -X POST http://localhost:8011/v1/users/create \
-H "Content-Type: application/json" \
-d '{
  "first_name": "Bob",
  "last_name": "Jones",
  "username": "bobjones",
  "password": "mysecret123",
  "phone": "+1987654321",
  "dob": "1995-03-15",
  "country": "US",
  "gender": "male"
}

Response:

json
{
  "ok": true,
  "result": {
    "id": "user1234567890abcdef"
  }
}

This gives you a user ID to work with. Pro tip: Store it securely!

2. Creating a Group

Now, let’s create a group for Bob and his friends.

curl -X POST http://localhost:8011/v1/groups \
-H "Content-Type: application/json" \
-H "Authorization: Bearer jwt.token.here" \
-d '{
  "name": "Code Warriors",
  "creator_id": "user1234567890abcdef",
  "members": ["user456"],
  "permissions": {
    "locked": false,
    "allow_member_messages": true
  }
}

Response:

json
{
  "ok": true,
  "result": {
    "id": "group1234567890abcdef"
  }
}

This sets up a group where everyone can chat freely.

3. Adding a Bot

Bots were my favorite part to build. Here’s how to create one that welcomes new group members.

curl -X POST http://localhost:8011/v1/bots \
-H "Content-Type: application/json" \
-H "Authorization: Bearer jwt.token.here" \
-d '{
  "user_id": "user1234567890abcdef",
  "name": "CodeBot",
  "commands": {
    "welcome": "Welcome to Code Warriors!"
  },
  "webhook_url": "https://your-server.com/bot-webhook"
}

Response:

`json
{
  "ok": true,
  "result": {
    "id": "bot1234567890abcdef"
  }
}

When someone types /welcome@CodeBot in the group, CampChat hits your webhook, and your bot can respond dynamically. I spent hours tweaking this to make bot interactions seamless—it’s a game-changer for automation.

What’s Next for CampChat?

CampChat is a living project, and I’m already dreaming up new features based on my own needs and community feedback. Imagine AI-powered bots that can moderate chats or generate witty responses, or maybe Stories and Reels for a social media vibe. I’m also working on 2FA, push notifications, and quantum-resistant encryption to keep CampChat future-proof. The possibilities are endless, and I’m excited to see where the community takes it.

Why You Should Jump In

Building CampChat was a labor of love, born from late-night coding sessions and a passion for solving real developer pain points. It’s not just a chat engine—it’s a foundation for your next big app, whether it’s a community platform, a support tool, or something totally new. The MIT license means you can hack it to your heart’s content, and the GitHub community is ready to welcome your ideas.

So, what are you waiting for? Clone the repo, fire up the server, and start building something awesome. I can’t wait to see what you create with CampChat. Drop by the GitHub repo to get started, share your thoughts, or even contribute a feature. Let’s build the future of communication together!

Difference between array() and []

Adeyeye George — Thu, 06 Jun 2024 15:15:36 +0000

In PHP, array() and [] are both used to create arrays, but they are slightly different.

array() is the traditional way to create an array in PHP, and it's a language construct. It can be used to create both indexed and associative arrays.

Example:

$fruits = array('apple', 'banana', 'orange');

On the other hand, [] is a shorthand syntax for creating arrays, introduced in PHP 5.4. It's an alternative to array() and is used to create arrays in a more concise way.

$fruits = ['apple', 'banana', 'orange'];

Both methods can be used interchangeably, but [] is generally preferred for its brevity and readability.

Introducing GIM: Revolutionizing Identity Management with AI and PHP

Adeyeye George — Mon, 22 Apr 2024 16:09:17 +0000

In the fast-paced digital age, ensuring secure and reliable identity verification processes is more critical than ever. Traditional methods often fall short in accuracy and efficiency, leaving room for fraud and security breaches. This is where Gim steps in - an innovative open-source General Identity Management application that leverages the power of artificial intelligence to redefine identity verification.

Gim's cutting-edge features set it apart from conventional identity management tools. By seamlessly collecting personal information, facial biometrics, ID card details, and digital signatures, Gim creates a robust profile for each user. The data is then processed using advanced AI algorithms to generate a comprehensive verification score, ensuring a high level of accuracy and reliability.

What makes Gim truly stand out is its versatility and user-friendly interface. Whether you are looking to streamline customer onboarding processes, enhance security measures, or simply improve the efficiency of your identity management system, Gim offers a customizable solution to suit your needs. With the ability to store data securely on Convex, generate detailed reports in PDF format, and seamlessly integrate with email or webhook notifications, Gim provides a seamless and efficient user experience.

One of the key benefits of Gim being open-source is the transparency and flexibility it offers. Developers can not only customize and tailor the application to meet their specific requirements but also contribute to its continuous improvement and evolution. This collaborative approach ensures that Gim remains at the forefront of identity management innovation, adapting to the changing landscape of technology and security.

If you are looking to elevate your identity management processes to the next level, Gim is the ideal solution for you. Its powerful AI capabilities, combined with its intuitive interface and customizable features, make it a game-changer in the field of identity verification. Whether you are a small business looking to enhance security measures or a large organization seeking a scalable and efficient solution, Gim has got you covered.

To experience the future of identity management, visit our project page at https://github.com/mitmelon/gim and take the first step towards a more secure and reliable verification process. Join us in revolutionizing identity management with Gim - where innovation meets security, and reliability meets efficiency.

GIM Is Born

Adeyeye George — Sat, 09 Mar 2024 09:16:09 +0000

Gim, an open-source General Identity Management application, goes beyond traditional identity verification methods by incorporating artificial intelligence (AI) to enhance the accuracy and reliability of the process. With Gim, developers, individuals, businesses can collect personal information, facial recognition data, and ID card images from users, which are then processed and analyzed using AI algorithms to generate a comprehensive verification score.

Key Features :

AI-Powered Data Processing:

Gim utilizes state-of-the-art AI algorithms to process data from facial recognitions and ID card images. This advanced technology ensures accurate and efficient identity verification.

Data Matching and Comparison:

The AI engine in Gim compares the data extracted from facial recognitions and ID card images with the information provided in the personal input section. By analyzing various data points, Gim generates a verification score for each identity.

Scoring System:

Identity verification results are categorized into two scores:

Excellent :

Data that matches between facial recognition, ID card images, and personal information input receive an excellent score, indicating a high level of confidence in the identity's authenticity.

Average:

Data that does not match entirely are scored as average, prompting further review or verification steps to ensure accuracy.

Benefits:

Enhanced Accuracy:

By harnessing the power of AI, Gim achieves higher accuracy in identity verification, reducing the risk of fraudulent activities and unauthorized access.

Streamlined Processes:

The automated data processing and scoring system streamline the KYC process, saving time and resources for businesses and individuals.

Increased Security:

With AI-powered identity verification, Gim offers heightened security measures, protecting sensitive information and ensuring compliance with regulatory requirements.

Test the Demo here and provide your feedback to manomitehq@gmail.com

If it's something your organization or company or someone will need send me a message through the email above.

Thank you..🙏🏻

Demo link

https://gim.manomite.net

🌟🏥 Calling All Change-makers: Join the Open-Source Healthcare Revolution! 🌟🚀

Adeyeye George — Fri, 29 Sep 2023 06:07:46 +0000

Hello, compassionate souls! 💖

Are you passionate about accessible, high-quality healthcare for all? Do you believe in the power of open-source technology to drive positive change? Welcome to our vision of a state-of-the-art, open-source, and completely free Hospital Management System (HMS) that could revolutionize healthcare management nationwide, catering to both individual hospitals and entire healthcare networks. 💪💻

Imagine a sophisticated HMS that breaks barriers, empowering healthcare facilities with robust tools for patient care, resource optimization, and seamless communication. Envision a system that operates on transparency, community collaboration, and inclusivity. 🌍✨

We are reaching out to you, our fellow advocates for a brighter healthcare future, to gauge interest and support for this ambitious undertaking. Your enthusiasm and engagement can fuel this project's growth and impact millions of lives by providing innovative healthcare solutions. 🚀🌟

Whether you are a healthcare professional, software engineer, a designer, a philanthropist, an investor or anyone who believes in equitable healthcare access, your involvement is pivotal. This project is not just about creating software; it's about creating a movement, a shift towards a more compassionate and efficient healthcare ecosystem. 🌱🌏

We wholeheartedly welcome partnerships, sponsorships, and donations that will accelerate the development of this open-source HMS. Together, let us ensure that every person, irrespective of their background, can access the healthcare they need, when they need it. 🤝💖

If you share our vision and want to be part of this transformative journey, let's connect! Reach out to us via email at manomitehq@gmail.com or send us a direct message on LinkedIn. 📧💌

Let's unite to build a world where quality healthcare is a right, not a privilege. 🌟🌈

Onwards, towards a healthier world! 🏥🚀
Manomite

OpenSourceHealthcare #AccessibleHealthcare #CommunityDrivenChange 🌟

Unleashing your creativity through cyber security

Adeyeye George — Sat, 26 Aug 2023 14:01:06 +0000

🔒🌐 Calling all aspiring cyber defenders! Join our cutting-edge online training course in Cyber Security and unlock your potential in the exciting world of digital protection. 🚀🔐

🎯 Are you ready to become a skilled cyber security expert? Look no further! Our comprehensive training program offers both beginners and seasoned professionals the opportunity to enhance their knowledge and master the art of safeguarding digital assets. With hands-on modules, practical exercises, and real-world simulations, we ensure you're equipped with the tools to tackle any cyber threat head-on. 💪💻

🔐 Why choose our Cyber Security Online Training Course? 🔐

1️⃣ Expert Tutorship: Learn from industry veterans and renowned cyber security professionals who will guide you every step of the way. Their wealth of experience and practical insights will help you excel in this dynamic field. 🎓🌟

2️⃣ Comprehensive Curriculum: From fundamentals to advanced techniques, our curriculum is meticulously designed to cover all aspects of modern cyber security. From network security to risk management, ethical hacking to incident response, you'll gain a holistic understanding of the cyber landscape. 📚💡

3️⃣ Interactive Learning: Engage in interactive sessions, virtual labs, and group discussions with fellow learners to enhance your understanding and share valuable perspectives. Collaborate with like-minded individuals and build a strong professional network. 🤝🌐

4️⃣ Real-World Simulations: Work on real-world case studies and simulations to apply your knowledge in practical scenarios. Gain hands-on experience, develop problem-solving skills, and be prepared to face cyber threats in real-time environments. 🌐📊

5️⃣ Flexibility and Convenience: Our online training platform allows you to learn at your own pace and convenience. Access the course materials 24/7, complete assignments on your own schedule, and progress through the modules as per your availability. 🕐💻

6️⃣ Recognized Certification: Upon successful completion of the course, you'll receive a highly recognized certification that demonstrates your expertise and boosts your credibility in the cyber security industry. 📜🔖

🔐 Don't let the ever-evolving cyber threats intimidate you! Equip yourself with the knowledge and skills needed to protect individuals, organizations, and critical infrastructure from malicious attacks. Join our Cyber Security Online Training Course today and embark on a rewarding journey toward a secure digital future. 💻🔒🌟

📢 Limited seats available! Enroll now and turn your passion for cyber security into a thriving career. Together, let's secure the digital world! 🚀🔒💪

Join this group below to start your application process

https://chat.whatsapp.com/FaFWHCipAZzLX8iXisuDNm

Please re-post to help someone.

cybersecurity #training #onlinetraining #cyberdefense #securethefuture #learnbydoing #experttutors #cybersecuritycourse

File Compresser 2.0.0 is here

Adeyeye George — Sat, 12 Mar 2022 18:52:05 +0000

2 years ago I released a library called compress which compresses all files including zip, tar etc. using PHP without using any third party online tools.

At the initial testing, compress compressed a zip file from 9.5MB to 8.2MB, over 1.3MB was removed from the actual zip file which was cool.

Since the release, over 1,450k developers have downloaded the library without issues. This has been a very great score for me and has given me more strength to keep working on the library.

Today am here to announce that the version 2 of Compress is now available.

In the version 2, I included AES-256-CBC encryption function for encrypting the files before compressing.

If you are upgrading to the new version, please note that there are few changes you will need to make to your code.

CompressFile() third argument now accepts optional array options. You can take a look at the changes below and compare it with the old version before upgrading.

If you are going to be using
the encryption function, You have to set the compressFile option argument like this;

$compress = new Compress\Compress;

$options = ["removeMeta" => false, "encrypt" => false, "key" => "password"];

$compress::compressFile($filePath, $storePath, $options);

Let me explain the option values.

The removeMeta : removes additional comments and junks from file. You can set this to true if you want to remove meta from file.

Encrypt : Set this to true if you want to use encryption.

Key : If you set encrypt to true, then you must provide the encryption key else compress will generate one for you and the response will be the key generated so you can store it in your database vault for future decryptions.

Now let's look at the few changes in the whole new version.

Install:

Use composer to install

composer require mitmelon/compress

Usage :

require_once __DIR__."/vendor/autoload.php";

// Initialize library class
$compress = new Compress\Compress;

/**
 * @param String $filePath
 * File location to be compressed
 * @param String $storePath
 * Path to output compressed binary file to
 * @param Array optional $options ["removeMeta" => false, "encrypt" => false, "key" => "password"]
 * Options to remove meta and encrypt file
 */
$compress::compressFile($filePath, $storePath, $options = []);

//Compress Image file
$compress::compressFile(__DIR__.'/image.png', __DIR__.'/image.txt'));

// Compress PDF
$compress::compressFile(__DIR__.'/file.pdf', __DIR__.'/file.txt', true));
//Compress as lot of files you want including zip files

/**
 * UnCompress Image file [Get original file back from stored binary]
 * @param String $storePath
 * Path containing binary file which was compressed
 * @param String $fileOutputPath
 * Path to output original file to
 * @param String $encrypt_key
 * If your file was encrypted then provide the key for decryption as third argument
 */
$compress::uncompressFile($storePath, $fileOutputPath, $encrypt_key = null);

//Uncompress Image
$compress::uncompressFile(__DIR__.'/image.txt', __DIR__.'/image.png');

// Uncompress PDF
$compress::uncompressFile( __DIR__.'/file.txt', __DIR__.'/file.pdf')

If you have not yet started using Compress and wish to, you can check it out using the link below;

https://github.com/mitmelon/Compress

In the near future, I will be adding more features. You can check the feature update on the readme to see the next features that will be added.

Also don't forget to donate for the project progress. Your donation will really help me on a long run.

Please feel free to make a pull request incase you find any bugs or want to add something to it.

Best of wishes.

The Ripper Tool Is Here

Adeyeye George — Mon, 21 Feb 2022 18:20:46 +0000

Few days ago I was reading a post on a website and suddenly, my router stopped connecting. I reloaded the website page multiple times and I kept getting connection not possible.

So I was forced to check the router to see what's happening underground but discovered that my data plan has expired. It was so sad because at that time I was healthy with funds and could not instantly renew my plan.

Face squeezed and I was like Hey telecom "Gbam" that's a punch on their face.

Sat down comfortable later and began to stir at the ceiling, then started counting how many nails were used for the roof😂😂. Sounds very funny since I had nothing to do.

After counting the nails multiple times then I realized that the carpenter didn't include one nail at the corner of the wall. Mtcheeeeeew this carpenter eeeeheeen, I said it again and again until I heard a very sharp voice inside my head saying.

Hey man! next time clone the entire website and store it on your computer drive, then you have offline access to read all the entire post even if the ISP decides to shut down.

Wao!!! I said to myself and immediately I stopped counting the nails and got straight to work.

Overall It took me 6 hours to come up with the final codings and designs. I completed the API and keyed it into a telegram bot.

You will ask me why telegram? That's because I wanted to avoid form fillings, reduce resources loads and also be able to clone any website anytime even on my mobile phone.

I called the tool Ripper. The name sounds horrible but that's what I got for it at that time. I wanted to call it carpenter but refused because they don't relate.

Ripper tool helps to clone any website including https sites for offline access. You can take a look at it. Use it and give me feedback on what you think.

May be in the future I will add more advanced functionalities such as multiple clonings and the rest or may be do for WhatsApp too.

Check it out at.
https://t.me/rippertoolbot

We launched Copytraps

Adeyeye George — Tue, 15 Feb 2022 15:05:43 +0000

Hi, For years, creative minds, authors, copyrighters, publishers, content editors, actors and actresses, book publishers, media owners, company and many more organizations have been facing content phishing attacks, content theft and infringements on the internet.

There have been many situations where an author or organisation spend so much efforts and time to craft creative contents while waiting for great rewards but instead another takes the credits and gets more rewards.

Your assets are extracted and used without your consent or permission which is very annoying. Bloggers losses more of their audiences and traffic's to copycats.

Today is the day that changes.

We’re proud to announce our product known as Copytraps.

It’s the most powerful tool capable of preventing and finding those using your hard earned contents for further law investigations with your lawyer.

Let them copy it🙄... I will find you🧐, close down your platform and request for damages cost. Those should be your words when you have Copytraps in place.

With Copytraps, you grant access to only people having your permissions to use your contents and the whole rewards gets back to you.

Let's keep the internet safe again by stopping content phishing attacks, junks and theft.

Be among the first 50 to try out Copytraps Beta Version at Copytraps with exclusive offers.

FILE COMPRESSER USING PHP

Adeyeye George — Sat, 22 Aug 2020 14:33:23 +0000

Today i was looking for various means to compress all files using PHP without using any third party online tools but unfortunately what i found was zip archives compress, zar and the rest. There was no single library on the internet designed with PHP to handle file compression including compressing zip files. I was curious and i had to design one.

I eventually did the design which i tested with a zip file having size of about 9.5MB and my PHP Class was able to compress this down to 8.2MB which was still okay for me. At least over 1.3MB was removed from the actual zip file.

I know you will want to ask whats the difference. The truth is that assuming you have a whole bunch of those zip files lets say 10 in which each had 9.5MB. Calculating this will give you a bunch of 95MB, thats lots of memory.

Looking through this you will see that over 13MB difference was removed when compressed. This 13MB could be used to save other files.

Designing a class that does this job took me 4 hours with over 15 test analysis.

If you are also curious about me and wish to use my library for your applications below is how to use it.

Install:

Use composer to install

composer require mitmelon/compress

Usage :

require_once __DIR__."/vendor/autoload.php";

// Initialize library class
$compress = new Compress\Compress;

/**
 * @param $filePath string
 * File location to be compressed
 *
 * @param $storePath string
 * Path to output compressed binary file to
 *
 */
$compress::compressFile($filePath, $storePath);

//Compress Image file
$compress::compressFile(__DIR__.'/image.png', __DIR__.'/image.txt'));

// Compress PDF
$compress::compressFile(__DIR__.'/file.pdf', __DIR__.'/file.txt'));
//Compress as lot files you want including zip files

/**
 * UnCompress Image file [Get original file back from stored binary]
 * @param $storePath string
 * Path containing binary file which was compressed
 *
 * @param $fileOutputPath string
 * Path to output original file to
 *
 */
$compress::uncompressFile($storePath, $fileOutputPath);

//Uncompress Image
$compress::uncompressFile(__DIR__.'/image.txt', __DIR__.'/image.png');

// Uncompress PDF
$compress::uncompressFile( __DIR__.'/file.txt', __DIR__.'/file.pdf')

You can also find the github library here.
https://github.com/mitmelon/Compress

Please feel free to make a pull request incase you find any bugs or want to add something to it.

Best of wishes.