Glenn 'devalias' Grant
banner
devalias.net
Glenn 'devalias' Grant
@devalias.net
Hack. Dev. Transcend. // Polyglot Developer | Ethical Hacker | Biohacker | Youth Tech Advocate | Certified Human Potential Coach

https://www.devalias.net/
https://twitter.com/_devalias
https://github.com/0xdevalias
x.com
September 1, 2025 at 1:03 AM
Also, interested if anyone knows of research or benchmarks for assessing/scoring the quality of variable/function/identifier names? Goal: to rank/benchmark restored names after reversing minified code.

Related: github.com/Ch3nYe/JsDeO...
Consider evaluating identifier naming in a future version of the benchmark · Issue #2 · Ch3nYe/JsDeObsBench
The following idea / note came from discussion on j4k0xb/webcrack#189: Afaik the evaluation metrics don't consider renamed identifiers so humanify would also have a pretty similar or the same score...
github.com
September 1, 2025 at 1:03 AM
Today's deepdive was probably also the most productive one yet for finding the bits and pieces I need to pull together a user script / Chrome extension to help make this 'keep up to date' / 'triage' process much less painful / time consuming...

But that's a story for another day
May 20, 2025 at 2:37 AM
...but by that stage you've run out of time in the day to actually look through them all... 😅

At least I can quantify how much effort it will take now; which should help remove the 'do I have enough time for this' paralysis and maybe actually process them more often.
May 20, 2025 at 2:37 AM
...and then with all of that, you build up some little helper functions and gadgets to stitch the data together, then a few more to process that hydrated array and count the tweets per day/user/etc, and then finally end up knowing that you have ~560 tweets to look through...
May 20, 2025 at 2:37 AM
...but then you remember about React fibres and start looking through those to see if you can find where the full list of notification tweets are, and you find it but it's just a list of IDs, so you crawl deeper into the rabbit hole until you get a reference to the datastore...
May 20, 2025 at 2:37 AM
...so you accidentally find yourself in the familiar rabbit hole of skimming through the DOM looking for relevant bits to build selectors off, and then remembering that the timeline only renders a slice of the list to the DOM so you can't just count rendered elements...
May 20, 2025 at 2:37 AM
April 28, 2025 at 6:58 AM
For now the code/extension is unpublished, but eventually will be made open source and probably published to the Chrome extension store as well
April 28, 2025 at 6:55 AM
48 windows with 121 tab groups and a total of 954 open tabs is fine.. right?

(Note: that 'open' is a bit nuanced, as I have Chrome features enabled that unload/freeze/etc closed tab groups / tabs that haven't been used recently, etc; without necessarily 'closing' those tabs)
April 28, 2025 at 6:55 AM
This afternoon I decided to hack in a new feature to tell me how many Chrome windows, tab groups, and tabs I have open; so now I no longer need to guess/count how big of a problem it is!
April 28, 2025 at 6:55 AM
And similar to my original gist, to better direct people to the appropriate details in a slightly less scattered/chaotic way than in the past:

Serum 1 Preset File Format (.fxp):

gist.github.com/0xdevalias/5...

Serum 2 Preset File Format (.SerumPreset):

gist.github.com/0xdevalias/5...
April 22, 2025 at 1:55 AM
I also added 2 new sections to my new gist, summarising the Serum 1 preset (.fxp) file format notes:

gist.github.com/0xdevalias/1...

And the Serum 2 preset (.SerumPreset) file format notes:

gist.github.com/0xdevalias/1...
April 22, 2025 at 1:55 AM
The Serum v1 .fxp file format hasn't been fully figured out yet, but I summarised links to my old notes/tools/progress on this in the following issue, in case it helps anyone else make further progress on it:

github.com/KennethWussm...
Support for legacy Serum v1.x `.fxp` preset format · Issue #1 · KennethWussmann/serum-preset-packager
I know the README explicitly states that it isn't supported: The legacy .fxp is NOT supported. But I figured since sooner or later someone is probably going to ask about it anyway; I'd preemptively...
github.com
April 22, 2025 at 1:01 AM
Speaking of the discussions in the comments on my gist, KennethWussmann was making good progress on the Serum 2 preset file format: gist.github.com/0xdevalias/5...

And has since figured it out: gist.github.com/0xdevalias/5...

And published a tool to decode it to JSON: github.com/KennethWussm...
April 22, 2025 at 1:01 AM
If reverse engineering / figuring out the Serum VST preset format is something you have any interest / insight in, I'd love to collaborate on it with anyone who's interested.

(I find it hard to find the time to push forward all of my projects as quickly as I would like to)
April 21, 2025 at 4:34 AM
Which I then summarised/mused over to fill in the context as best I could remember it in this comment back on the main gist:

gist.github.com/0xdevalias/5...
April 21, 2025 at 4:34 AM
This also inspired me to dig out some of my old notes and code (that I had forgotten where they were it had been that long.. 😅), and made a new gist to upload those to:

gist.github.com/0xdevalias/1...
Reverse Engineering Serum Preset Format - Supplementary Notes
Reverse Engineering Serum Preset Format - Supplementary Notes - 1-reverse-engineering-serum-preset-format-supplementary-notes.md
gist.github.com
April 21, 2025 at 4:34 AM
The main gist is here:

gist.github.com/0xdevalias/5...

But check the comments for recent discussions and insights, for both Serum v1 and v2 preset file formats:

gist.github.com/0xdevalias/5...
April 21, 2025 at 4:34 AM