@animesh_varma

Phewwww, finally pushed the last commit, and this will be my last devlog before the ship (and the last one for Stardance). Anyway, I would like to summarize what happened over the past months. To start, I was very excited to work on this project and did a quick proof of concept at the start, though I didn’t think much of it and didn’t establish a solid pipeline. I just realized that when I revisited the project again, this time I focused mostly on the pipeline, and sadly that (the pipeline that is used to intercept Instagram requests, i.e.) would be internal for most of the duration of the project since Meta would likely patch the method I am using (it requires a rooted device and is fairly difficult as well as risky too, so it might be good overall). Going forward, for what I have done now, instead of making a complete profile sign-in (which was practically impossible in the time I have left), I just validated all the secret extraction from the Android device against the Meta endpoints, so I can at least guarantee that I can generate all the nonce and cryptographic signatures required by the Instagram backend. Currently, the problem I am running into is the client being out of date (even though its the latest blocks and client version)…? Anway this seems to be a temporary issue since instagram seems to be overhauling many things, but the point is that making a client right now was not my end goal, it was to make a pipeline I can use repideatly to keep up this project and to verify if I can extract what Meta need from the android device and I seem to have achieved both of them and can conveniently display them to you folks, hence the ship [to see your own instagram params, just install Aetherion, go to preview demo and click saved secrets and it will show you everything, though the keys can be rotated, is was still very difficult none the less]. Anyway, I seem to have run headfirst into nearly all the issues that currently plague subzeroid/instagrapi on GitHub, so I must be doing something right… Anyway, SHIP INBOUND!!!

Yayaa, just extracted the data I would use for the login POC [this ship will mostly be a pipeline POC]. again, the front end it mostly AI generated but it was NOT agentic, I verified each line manually, now I am working on implementing this into the kotlin app… most of this was done in the last devlog but it was’t completed hence omitted… LETSSS GOO!!!!

Whewww! it was some long work but I finally restructured my internal logger to work with the new instagram version! (it took soo long probably before it has been around 2 months and many changes compounded into a nearly complete overhaul). Anyway, most of the work today was done on Aetherion internal, a internal branch of Aetherion which will only be used to update Aetherion, it is unlikely to be made public as meta would likely quickly patch the methods used… either way, entirely of the project other then this would be FOSS!! Attached are screenshots from the private dashboard, the UI is mostly AI generated as this is never ment to be used on production…
Tomorrow I will work on the analyzer to get useful data out of these recordings and will they to ship it before stardance ends, but I will sure be cutting close :( Also, I am able to do all this interception as I rooted my old realme device (which is a whole story on its own), it is not at all possible on stock androids!!

Well I am back after a long time and to no ones surprise, nothing works :(
I now have ahead to me:

1. To find a new to way to intercept instagrams traffic
2. Make a serviceable prototype/PoC before StarDance ends (in just 6 days :()
3. Reimplement and clean up the android app

AAAAA, it will take soo longgg :( [BTW I got login working 2 months ago but it does’t wok anymore, instagram just refracted their backend :(]

Wohoooo!!! v2.0.0 is finally live!! I will ship it tomorrow, till then I will announce it on reddit! [the coderabbit suggestions were really something this time, it took me some time to understand and fix em :(]

Edit: I forgot to mention the reason for the longg break, just had some family issues :(( But now its full speed ahead :D (after this I will be focusing on some of my other projects, so it is going to be stalled for around a month or soo)

Wohooo!! PR created successfully!! lets see what coderabbit has to say… [I will see that and make changes tomorrow, I hope it is’t too bad :(]

WOHOOOO!! I am finaly doneee, now for the dreaded part of the documentation, I will be back with the ship when it is done… for context I have the project live with the pyodide-worker on gihub pages

Did I take too long writing this log, yes, oh yes I did. But if you have been reading it has alwayes been a bumpy cadence :( Anyway, I have made many, many, many changes in the mean time, so many in fact that I dont have time to list them here. So you’ll have to read them in the Readme. Anyway, curuntly I am working on making Bambuscribe work on GitHub pages, so hope that works out well, the attached image is from all the algorythems I added in the hours (sorry for my grammar I am in a rush, and a family emergency to handle :( )

AAAAAAAA!!! I am basicly forced to write this devlog as it has been around 8 hours without one… I thought that I would not make a devlog until I at least make the login work consistently, but here we are… Anywho, this will be my first devlog, till now I just have created a rough app for testing out calls and responses to the instagram endpoints, a majority of the time was spent trying to break Instagrams SSL pinning (No I wont be telling you how I did it, or will I [cue vsauce music]). Anyway, I wont be telling you much now, I am stuck between by class 12, SAT and my project, I just hope it turns out well… As for what Aetherion does, ill be sure to explain it in the next devlog!

Wohaaa, so this was hectic… I had only had a very, very limited time to complete this update as my periodic tests start from tomorrow (hence the very minor bump). So this update was more or less a backend one where I just tied some loose ends here and there and added some little cosmetic updates (like a clear button for the images). My intention was also to add multi-color printing, but the time I had was far too little for that, but not for a lack of trying :( Anyway, I won’t be shipping it right now as it was just a minor update, so see you after my exams when I come around to pushing v1.2.0!!

So I spent the rest of the time hunting and fixing bugs in the PR (which were found by coderabbitai), this was the first PR and now we are at v1.1.0 ;D

Andd now I have optimized the zhops and the overall travel so it now does everything at the set speed and not just the pen strokes (and increased the max movement speed)
[and I am pushing the V1.1.0 right now so this will me my first ship of Stardance!!!]]

So long story short, I forgot that I had to write a devlog ;( anywho, here it is, so I spent some time building Bambuscribe, you can understand what it does from the Readme and description (do note that the time logged is not the actual time I spent as a considerable amount was also spent on failed plots and fighting the printer and reading docs…) as for what I did now, after the v1.0.0 I have some change on my radar, the first one was to make the ploting autonomous and uploaded to the printer, that is what I just added, enjoy! (as for the challenges the printer refused to acknowledge that I sent it somthing, so that was really something)

Just implemented the zero-width text steganography section; it was a pain to optimize and to get work across platforms, but I did it in the end. Attached are screenshots of it. I tried to get it to look like the main tab, but I don’t think it worked out quite as well, or it could be that I have looked at the main tab for too long. Anyway, next on the agenda is the whitespace section, also just to be clear, the zero-width one, though not visible, takes a shit ton of characters as it essentially encodes all the data in binary, so even though it isn’t visible, it’s still there and easy to find out. I have thought of making the LLM section specifically to combat it. Stay tuned to find out how well it works (I probably won’t survive implementing the LLM section, but oh well, problem for future me, I guess….)