taldo

I've experimented with some of these whatsapp-web-esque hacks (whatsappweb.js, whatsmeow, ...) and every now and then I'll get banned. It's quite inconvenient if you live in a country where WA is the universal contact channel for pretty much everything.

Also replacing Intercom right now. Their pricing just doesn't make sense for us.

This REALLY is the year of the Linux Desktop

You mean the cost of EDA software directly (paying Synopsys/Cadence for the software used to design, verify, and synthesize your own chips)? Or the actual R&D cost to design the chip itself? Or paying for prepackaged IP blocks (major ones like CPU cores, or lesser ones like I/O)?

Sooo they're finally launching a Spanner contender?

I'm itching to read more details into what this actually is under the marketing blab.

Cursor has been an enabler for unfamiliar corners of development. Mind you, it's not a foolproof tool that writes correct code on the first try or anything close to that.

I've been in compilers, storage, and data backends for 15ish years, and had to do a little project that required recording audio clips in a browser and sending them over a websocket. Cursor helped me do it in about 5 minutes, while it would've taken at least 30 min of googling to find the relevant keywords like MediaStream and MediaRecorder, learn enough to whip something up, fail, then try to fix it until it worked.

Then I had to switch to streaming audio in near-realtime... here it wasn't as good: it tried sending segments of MediaRecorder audio which are not suitable for streaming (because of media file headers and stuff). But a bit of Googling, finding out about Web Audio APIs and Audio Worklet, and a bit of prompting, and it basically wrote something that almost worked. Sure it had some concurrency bugs like reading from the same buffer that it's overwriting in another thread. But that's why we're checking the generated code, right?

There's also yotoplay.com, although that one does seem to require wi-fi and cloud thingies.

Ouch, open Cosmos DB with geolocation logs publicly accessible...

Since the read part is handled by another chip (feeding off of USB power, therefore not terribly power constrained), you could present as a MTP device, or even mass storage, while generating the file structure on the fly. Maybe TIFFs are simple enough so you don't have to mess with the actual image bytes.

And yet they couldn't agree with Apple on a protocol that could be implemented by both. Imagine how much better tracking you'd get with tags that could be picked up by either Android or iPhones. Especially in the _third world_ where Android phones are way more prevalent.

The customer is always right... unless they are not.