I did the same last year and I’m having a lot of fun. Good luck!

My old Twitter account: posts/following/followers. Not long before Elon Musk took over the company, I was prompted for my age in the app. I decided to comply and got banned. Apparently I was less than 13 years old when I created the account, and they retroactively ban for that. Mind you there was no law in my jurisdiction about using social media at a young age, at the time. Still sad about that.

I’ve been doing this manually by having a static development-only route on my website and taking a “node screenshot” using the Chrome developer tools. This is definitely a better way, well done!

I experimented with this idea a couple years ago, using the Language Server Protocol to make it some what universal. The output gets messy pretty quickly, maybe these days an LLM could be used to only show the interesting calls.

Fun idea, I want to be posting more so this seems helpful! Might be nice to have a screenshot in the GitHub repo / Marketplace page. Is it available in Cursor? I can't seem to find it. Could be useful as a CLI utility as well.

Hey friend, thanks, I'm glad you found it useful :D. I'll post it on Cursor soon. I still need to research which extension store that editor and the others use, but I'll do it and post it when I have it there :D.

I'll keep your suggestions in mind,my friend,they sound great. For now, it's just version 1 I'll be adding things little by little.

Sounds very interesting, but the README has me pondering the downsides. Is the latency very high? Are requests not immediately durable? Is it super expensive?

Yes We'll provide a report to explain how we tradeoff these things, please stay tuned.

Sounds interesting, are you also thinking about inbound email?

Inbound emails using AWS SES make sense, but not planning that as the part of the MVP.

Is that a commonly requested use case for AWS SES users?

I'm working on a meta framework for building "full-stack" libraries. I.e. libraries that bundle frontend hooks, backend routes, and a database schema into a single package.

This allows library authors to do more, like defining webhook handlers and (simple) database operations. The idea is to move complexity from the library user to the author, making (API) integrations easier.

I think libraries being able to write to your database is a pretty powerful concept, and can enable a number of interesting use cases.

https://github.com/rejot-dev/fragno

I'm not sure 2015 counts as new, but that's same release that first introduced the JSON extension. There isn't a version of SQLite with JSON expressions but without indexes on expressions. Also, the JSON extension wasn't enabled by default until 2022, so most people using SQLite with JSON have got a version much newer than 2015.

i initially misread "2015" as "2025", too... But no, it was part of SQLite for ten years already!

I'm working on a meta framework for building "full-stack" libraries. I.e. libraries that bundle frontend hooks, backend routes, and a database schema into a single package.

This allows library authors to do more, like defining webhook handlers and (simple) database operations. The idea is to move complexity from the user to the author, making integrations easier.

I think libraries being allowed to write to your database is a pretty powerful concept, and can enable a number of interesting use cases.

https://github.com/rejot-dev/fragno