hot3eed
166 posts
In other news, we sold Beeper to @automattic. The deal closed on April 1. The next day was my first day as their Head of Messaging!
Beeper, as you know and love it, will continue as an independent team and product within Automattic. Our whole team has moved over, joined by new friends from Texts.com who were acquired last year. Together, we are the most capable set of chat reverse engineers on earth!
This time round feels quite different from my Pebble→Fitbit acquisition experience. As I blogged on the 10 year anniversary of our Kickstarter (@ericmigi/why-pebble-failed-d7be937c6232" target="_blank" rel="nofollow noopener">medium.com/@ericmigi/why-…), basically after almost a decade working on smartwatches, I was kinda out of ideas and ready to move on.
Not this time! After years in beta, Beeper officially launches today. We're just getting going. I have TONS of product ideas that we haven't even started on yet. Chat feels like a bottomless well of potential, haven't even scratched the surface yet. We each use chat apps hundreds of times per day. Each interaction is an opportunity. Chat as a product has been woefully underexplored. Due to platform lock in, there effectively have been no new entrants into the market in the last 10 years. We believe we can sidestep the chicken-and-egg problem that kills new chat companies. Instead, we spend the majority of our time actually building a better chat app, rather than requiring users to spam their contact list with invites just to grow the network.
One of our long term goals is to help the world migrate to an open chat/communication protocol. Imagine 50 years from now - do you think the current set of chat networks will be around? What about email? I have high confidence that we will be emailing til we die (for better or worse). I think open beats closed in the long term.
That's why I'm so excited to join forces with Automattic. @photomatt and his team have built foundational open source software, like WordPress and WooCommerce, that power huge swathes of the internet. I've known Matt for years. He was an early investor and user of Beeper. I've learned over the last 3 years of working in this space that a) it's harder than it looks, b) you need to know who your friends are. With Beeper, Automattic is doubling down on chat, after their acquisition of Texts.com last year. I can't think of a better partner out there for us to work with on our quest to build the best damn chat app on earth.
Read more about the acquisition on our blog: blog.beeper.com/2024/04/09/bee…
English
hot3eed retweetledi
What happens when you play a sound on an AirTag using the Find My app? Let's follow the Bluetooth packet through various system components. We'll analyze cross-process communication (XPC) in multiple daemons for this. #reversingshorts
youtu.be/eW-pq_aQPfQ
YouTube
English
hot3eed retweetledi
Today I'll be sharing what's new with @fridadotre, and my co-conspirators @trufae and @as0ler will be giving you the latest on @radareorg and r2frida, among many other exciting speakers/topics! 🎉
To join: events.bizzabo.com/NSConnect2022?…
English
help, my M1 Max thinks it's x86_64…
any ideas what could be causing this? it's stopping me from being able to target arm64-apple-macos lol
English
@NSBiscuit @oleavr I haven't tested them but the calling convention implementation should at least allow you to support throwing functions easily I think, which would be nice to catch and then throw as a JS error in the wrapping function. There's still lots of work to be done on the bridge.
English
@NSBiscuit @oleavr Feel free to check out the docs for more details or hit me up with questions: github.com/frida/frida-sw…
English
@NSBiscuit @oleavr IIRC also this list is in the same order as the fields as they're laid out in the struct, but better to confirm this manually. From then on it's a matter of `readUtf8String()`, `readU64()` on the handle if the fields are of primitive types, or parsing other structs otherwise
English
hot3eed retweetledi
Where are my mobile app and SDK developer folks at? DM me if you a) are a dev and care about security and love trying out shiny new tech, or b) are an SDK developer/framework person and looking for a gig or some interesting technical work. Appreciate retweet for the reach. Thx 🙏
English
hot3eed retweetledi
@LOLgrep Shameless plug: you can dump types for those Swift dylibs (and even hooks some of their functions) using github.com/frida/frida-sw…
English
Seasons greetings everyone 🎄 - I hope you enjoyed the holidays. Wishing you a happy Hogmany tonight. I hope 2022 brings you great success and happiness 🥰🎉
English
hot3eed retweetledi
DRUMROLL, please 🥁
Our most popular post of 2021 is another @hot3eed gem, "Reverse Engineering iMessage: Leveraging the Hardware to Protect the Software" 💎
Learn how @Apple hardware production is an important element in safeguarding its software 👉loom.ly/7EE_dGQ
English
hot3eed retweetledi
hot3eed retweetledi
the @ManishEarth uncertainty principle states that you can't know both the gdb command and lldb equivalent with complete certainty.
Manish@ManishEarth
with my physicist hat on i kinda view debuggers as "state space" views; you debug by looking at state at particular time slices whereas printf/etc are more "phase space"-like, you look at the evolution over time of particular state slices (yes, this is a Fourier transform)
English