@EDM115 bots & updates ❤️‍🔥

damn, I really wonder what's behind the Mystery Opaque Glass not obvious at all

so results are in and the results are kinda what I expected (did my own choices influenced you ?) but it's much closer than I anticipated lol "Packet Loom" came 1st and will be miniproto's logo, "Packet Plane" came 2nd and will be MPGram's logo you can already check a preview of the documentation at miniproto.edm115.dev/ I will rewrite nearly everything by hand (fuck this AI tone), the landing page have some of the most boring turns of phrases, I will rework the theme (for ex it's not legible on the sidebar), fix the search's filtering, add more interesting plugins, … in short, over-engineer it like I love to do 😭 plus your usual code cleanup phase currently my mom is in vacation at my home and we will go to Paris on Sunday so I probably won't release it right away. more review rounds will also have to be made, + a large security review by a friend 🤗

yeah, I am very much in The Stack

Keep in mind that I will also need to choose a logo for MPGram later on, so we might reuse the choices here. My personal opinion is #3 for miniproto (backend lib) & #5 for MPGram (what devs actually use, will be seen more often). Tell me about your choices in the comments ! Each of them have kind of a signification, either about packets, the Rust core, ... Choose at most 3 options :)

CI is mostly ready and it builds + minimally runs on (Python 3.13/3.14/3.14t) × (Linux glibc/Linux musl/Windows/MacOS) × (x86_64/aarch64) I think most of what's left is documentation ? however I'm slightly worried lol, I'm currently building a smooth frontend for my Codex chats as the desktop app is laggy and just like for miniproto docs & my website, it uses Pagefind to have a super fast search index for ~450 chats it creates 11k+ indexes, builds them over an hour and averages at 15 Gb of ram generating that 😭 most of it being swap but still miniproto will fortunately have smaller pages by design & less common terms but I preshot 10-20min of generation for the docs site

miniproto v0.1.0 could be released as early as the end of this week consider every version under 1.0 to be beta territory and under 0.100.0 to be alpha (yes I'm creating new conventions again. and ? 😭) API contract could change at any point, breaking changes are expected. I have prepared today a strong plan for the release including best-in-class documentation like no other project 🤭 note that MPGram isn't ready at all so far. so if you wanna try miniproto v0.1, it will be a less smooth experience, although close to existing libraries tbh and ofc don't use it for anything else than tinkering with new stuff, this is far from production ready

you can now request any page on my website as markdown, just append .md at the end or use an Accept: text/markdown header it's also clanker-ready : root llms.txt & llms-full.txt are available (and will be refined over time). search, ai input & ai training are also allowed (for the ones who respect that). I didn't restrict access through Cloudflare because some of my content could be genuinely useful (or it's all a plan to poison them… who knows) best part is that it adds nearly 0 overhead & time on website prerender 😎 so yeah, you can now direct your shitty ai agent to my website and they'll figure out their way better

little progress report : the Codex App (now ChatGPT App but fuck it) is just an Electron app first thing I did was run it in bundled mode : just provide the original app.asar to the exact used Electron version + provide all external assets (codex.exe, computer use stuff, …) this is what yielded the previous screenshots, as the debug stuff is just included in the final payload lol (I have the past 70+ versions backed up just in case it gets removed later, so we'd can restore it) second step was running in unbundled mode : extract all assets from the app.asar and run from those files directly. this unlock proper dev and hot-reloading later on but Rolldown-minified JS files aren't really useful (although might stay used for later patching with shims just pointing at the resulting function/variables aliases… will figure that out later) next step was properly reverse all that shit into readable code a custom classifier have been written (thanks the Oxc tools team for providing such fast tools 🙏) to separate resolvable dependencies from actual OpenAI-written code. this drops the number of .js files to process from 19k+ to 4.5k+ 2 tools are then used to speed up the process (takes around an hour to run on all those assets). I might run one of them in a more aggressive mode and the second with a proper sandbox to obtain better results a third tool is then used to transform minified code into proper function and variable names (well, a custom reimplementation of a tool I randomly found out). this uses a shit ton of LLM subagents to do the work. if you need an estimate, with the current modules splitting between 5.6 luna, terra and sol (a more economic split wasn't done by an abundance of caution), you're looking at roughly 60 million tokens spent, which equates to roughly 250$ at current pricing (without counting the validation that will happen afterwards) although I'm also working on a way to make that cost massively reduced (<1$) for subsequent updates by just processing the delta of recovered files. messing around with using the new DeepSeek V4 Flash could also lower the pricing tbh anyway I'm currently halfway through this last step (which accumulated lasts for 50+ hours non-stop) and will then be able to work on the actually modding SDK 😈 l already have multiple mods I wanna make, including a performance optimization one and a multi-profile one I'm also working aside for @juznem, making a super cool bot. it's in the last stages of development and I can't wait to share more about it later 😋

https://github.com/CodexMods dev is happening in an private monorepo for now will be made public and split per the structure outlined in the org's readme once working :)

what if you just had… free will ?

For quite a while now (at least 2+ years), I've been thinking about a feature that's missing on GitHub : Private branches. Today, I finally took the time to write in details why I want it and how it could be implemented. Please upvote it if you think you could benefit from it too 🙏 https://github.com/orgs/community/discussions/202434

we are so back 😤

interesting feature of the new twitter dislikes don't behave like downvotes on Reddit as we initially thought but rather as feedback

After removing dislikes on shorts, likes are turned into hearts Clearly heading towards the Instagram Reels interactions

so I created a new Telegram account + bot to test it properly without polluting my main account progress is being done... auth is working properly :)

It's time i talk about this officially lol This project have been in the back of my mind for the greater part of the last 2 years. I always wanted to have the perfect solution fitting my needs for making/maintaining bots, and was tired of seeing all Pyrogram forks implement good things separately then dying. The repos were private for a moment while I claimed the names on PyPi and crates.io They are mostly empty for now, and don't expect a beta release anytime soon, let alone a stable one. However I'll try to advance on it on my free time, including letting agents implement small parts of it and testing in the background while I work at my job. I strongly believe that this project could be the best you've ever seen. And this will be a strooooong basis for the unzip-bot rewrite. The idea of splitting the lib core from the framework came today tho. Can't wait to have it working hehe ! Go star the repos if you're interested. Expect half-working features to be ready by the end of August maximum. https://github.com/EDM115/miniproto https://github.com/EDM115/MPGram

already found on Twitter lol Windhawk's author also posted on my behalf on r/Windows11, go give an upvote 🫡 https://www.reddit.com/r/Windows11/s/w59FnxEMjH 101 users, 9 ratings (all 5 stars), great to see good feedback 🥰

so do you know how, on Windows 11, if you have multiple monitors, the tray icons only appear on the primary display ? and the control center too ? well a friend of mine got pissed off with this, and asked me to create a Windhawk mod to fix it. i tried, but with only my laptop I couldn't really test this fast forward 2 months, I have now a job with 3 (three) monitors, so I got back to work after countless versions (check https://pastebin.com/hjWNEPLx for the complete Changelog and fixed bugs list), I finally got it working and merged into the official mods list 🥳 see the images for a preview of what it can do nobody else created a similar mod in the past, and apps can fix it but they're paid. anyway You wanna know the funniest part ? Windows does create the space for those elements on non-primary display's taskbars, but just doesn't fill them up 💀 It's however not as simple as "copy on other empty areas", check the code if you're interested in how it works, and there's a section on the mod's readme that gives a clear overview of how it even works without requiring you to read 5k+ LoC :) The TL;DR is : - you can duplicate the tray icons hidden icons area - you can duplicate the control center - you can choose on all monitors or just some of them - you can apply the choice between tray/control on all monitors or only non-primary one(s) mod link : https://windhawk.net/mods/taskbar-multi-tray

hello, it's my birthday today :) ze frenchie is now 22 (okay boomer) i don't have much to say, apart from "thanks everyone for sticking with me for so long 🫶" updates to the bot will happen soon™ (more code push this weekend probably) and i'll send another post today about something i made that i'm very proud of 🥰