alias1

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.

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...

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).

https://github.com/0xdevalias/chatgpt-source-watch

> 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:

https://github.com/0xdevalias/chatgpt-source-watch/blob/main...

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:

https://gist.github.com/0xdevalias/4ac297ee3f794c17d0997b467...

And I'll often also share details about leaked upcoming features on Twitter when I find something interesting:

https://twitter.com/_devalias

Such as when I leaked the early versions of code interpreter and browsing mode way back at the start of Feb: https://twitter.com/_devalias/status/1622102312994099200 , or the 'Share Chat' feature almost a week before it was leaked on Reddit: https://twitter.com/_devalias/status/1658104103090651140

Anyway, I hope others find the discovering upcoming ChatGPT features as interesting as I do, enjoy the content!

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:

https://github.com/0xdevalias/poc-beeper-password-reset

Another day, another ChatGPT unreleased 'INTERNAL ONLY' feature: Share Chat

---

Code / API refences:

https://chat.openai.com/_next/static/chunks/pages/_app-ab949...

createShareLink: POST /share/create

updateShareLink: PATCH /share/:share_id

deleteShareLink: DELETE /share/:share_id

https://chat.openai.com/_next/static/chunks/734-d34f3efd388e...

See tweet for code screenshots: https://twitter.com/_devalias/status/1658104103090651140

---

You can find my other past ChatGPT code deepdives (that also turned up a number of alpha features before they were publicly announced) on this gist:

https://gist.github.com/0xdevalias/4ac297ee3f794c17d0997b467...

Seems this leaked ChatGPT API model got taken down already..

https://github.com/acheong08/ChatGPT/issues/523

https://github.com/acheong08/ChatGPT/issues/523#issuecomment...

Seems this leaked ChatGPT API model got taken down already..

https://github.com/acheong08/ChatGPT/issues/523

https://github.com/acheong08/ChatGPT/issues/523#issuecomment...

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.

Thanks for the links! Definitely interesting, and kind of annoying how hard it seems to be now :(

Would running a VM on top of windows and passing the device through to that be an option given your use-case? Could then run *nix or similar in there, and avoid the windows driver hell.

I can definitely understand the marketing/psychology appeal of it.. but it also feels like a bit of a rip that I either end up with a) a less good product, or b) paid more for the same thing. That is.. until we figure out the ways to DIY upgrade them ;)

Glad I inspired you to hack it the right way! Thanks for sharing the cached link :)

Sounds like a really interesting project! Hopefully you manage to figure it out. Glad I could help start your own rabbithole of a journey! ;p

My tl;dr

* Listen to music to block the distractions/world

* Get out of your old environment (coffee shops seem to help me, +caffeine source!)

* Travel: It just always seems to put things in perspective for me.

* Probably won't work for everyone, but I tend to have 'The Holstee Manifesto' on the wall near my computer, and probably read through it a few times a week. Makes you think.

I can't remember if this was an official style guide anywhere, or whether I just saw it on a project and liked it, but this is what I have been using.

  // Project Name
  // https://github.com/myuser/my-project-name
  //
  // Copyright (c) 2012 My Name
  //
  // Licensed under the Apache License, Version 2.0 (the "License");
  // you may not use this file except in compliance with the License.
  // You may obtain a copy of the License at
  //
  //    http://www.apache.org/licenses/LICENSE-2.0
  //
  // Unless required by applicable law or agreed to in writing, software
  // distributed under the License is distributed on an "AS IS" BASIS,
  // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  // See the License for the specific language governing permissions and
  // limitations under the License.

I have seemingly endless (1k+) lists of links on the likes of Pocket[1] (formerly ReadItLater) and the Read Later list in Rockmelt[2]. Found Pearltrees[3] a couple of months ago and been absolutely loving it!

The easiest way to describe it is sort of like a mindmap for bookmarks. Currently has a flash interface (shudder) but seems to work fairly well, lets you export all of your content at any time, has some social aspects (follow others pearltrees, etc), iPad app (iPhone coming soon) and an API supposedly out later this year (I hope sooner rather than later)

Hope you find something that works for you!

[1] http://www.getpocket.com

[2] http://www.rockmelt.com

[3] http://www.pearltrees.com

Clickable: http://vertx.io/

From a technical perspective it's definitely possible. I can't remember off hand, but i'm almost certain I came across something that did this before..

A quick google turned up the following:

http://www.bytestrom.eu/blog/2009/1120a_jpeg_encoder_for_jav...

https://gist.github.com/1245476

Hope it helps

Wouldn't something like this be doable with PhantomJS?

http://www.phantomjs.org/

Clickable links: http://s0rce.com http://s0rce.com/issue-event/republican-primary http://s0rce.com/blog/post/fixing-the-news

Will have to give this a go when I get home. From what I see so far it looks really nice. Well done!

The icons look very clean, simple layout yet effective layout, and quite glad to see such a reasonable price :)

I noticed only 49 icons are showing on the front page image, yet the site says 55 though?

Good work. The lack of availability in anything other than Ruby has been a bit of a pain. Now if only GFM was ported into Javascript.

Clickable link: http://www.StartOpedia.org

Very nice idea and so far the service looks pretty good. Congratulations :) I did find it a little hard to find the different pricing levels/what I get for them. I think having a page dedicated to the different account types (free, premium, etc) linked off the main menu would be good.