There has been some [recent discussion in the comments](https://gist.github.com/0xdevalias/5a06349b376d01b2a76ad27a8...) on my gist of notes related to figuring out the Serum preset file format; with a lot of the recent comments relating to the Serum 2 `.SerumPreset` file format.
That tool doesn't have support for Serum v1 `.fxp` preset files (though Serum 2 can convert the legacy presets.. so you could technically access them that way); but this recent discussion did [inspire me to find/share my old notes/tools](https://gist.github.com/0xdevalias/5a06349b376d01b2a76ad27a8...) from when I was digging into the `.fxp` format. While it's not fully figured out, it's definitely a good starting point for anyone interested in looking deeper; and I also made this issue on the tool to summarise the relevant context/resources for the `.fxp` format:
Looks like ChatGPT Plus will be getting annual subscriptions soon, for the equivalent of US$16.66/month (So probably US$200/year accounting for rounding errors)
I've just released ChatGPT Source Watch, a repo dedicated to finding and documenting upcoming ChatGPT features (before they've been announced/released).
> ChatGPT Source Watch
>
> Analyzing the evolution of ChatGPT's codebase through time with curated archives and scripts
This is an evolution on the very manual / high effort techniques that I (and others) have been using to identify and leak unannounced / unreleased ChatGPT features by studying the minified frontend source code.
The most interesting part of this repo for most people will be the CHANGELOG, where you can get an overview of what changed in each new ChatGPT build / release:
If you're interested in some of my (and some others) past ChatGPT feature leaks, you can find a timeline of them + relevant links to the sources over at this gist:
This week Beeper's support has been a little busy and unable to help reset my password; so with a few Matrix spec pointers from the Beeper Community chat, I hacked together a PoC Beeper password reset tool for the email/code (JWT) flow.
With this, you can reset your Beeper password (or set one if you never had one) by using Beeper's new 'login by email/code' method (you don't need to have your old password set/know what it is to use this)
You can find the code and other notes over on GitHub:
Depending on your needs, you absolutely can do it in software. The first few steps are about software, and in particular, probably just using Wireshark + USBPcap or usbmon is sufficient for basic cases.
The hardware side of things is the area that interests me more though, if you want to get into higher speeds than can be handled in software only, or if you want to start doing weird/interesting things in the 'emulate' side of it (not just capturing (eg. facedancer). Coming from a security perspective, those sorts of tools are invaluable for getting to some of the depths that I may want to reach.
Definitely agree here. I tend to like to get the gist of things/cliffnotes from people that have already broken it down, and then deep dive into the spec if I need to know some explicit detail.
Most of the time when I want to hack on something, a super high level abstraction is more than sufficient for my needs (eg. don't need to understand the inner workings of a CPU if all I need is an API). But then there are those times when the spec, in all it's verbose rawness, is the perfect tool for the job.
I originally wrote this as a way to collate all of the things I was reading as I went from zero knowledge on the subject. I like to document the path I took, and don't really see the point in reimplementing the wheel when someone else has already done a good job of it. That might not align with everyones style.. but can't please everyone.
When I [shared some podcast notes](https://gist.github.com/0xdevalias/5a06349b376d01b2a76ad27a8...) of Steve Duda talking about how he eventually wants to open the preset format, it [inspired another user to dive deeper](https://gist.github.com/0xdevalias/5a06349b376d01b2a76ad27a8...) into figuring out the v2 preset format; which as of yesterday, they have [basically figured out completely](https://gist.github.com/0xdevalias/5a06349b376d01b2a76ad27a8...), and created a tool that can pack/unpack v2 presets:
- https://github.com/KennethWussmann/serum-preset-packager
That tool doesn't have support for Serum v1 `.fxp` preset files (though Serum 2 can convert the legacy presets.. so you could technically access them that way); but this recent discussion did [inspire me to find/share my old notes/tools](https://gist.github.com/0xdevalias/5a06349b376d01b2a76ad27a8...) from when I was digging into the `.fxp` format. While it's not fully figured out, it's definitely a good starting point for anyone interested in looking deeper; and I also made this issue on the tool to summarise the relevant context/resources for the `.fxp` format:
- https://github.com/KennethWussmann/serum-preset-packager/iss...