Posted by david927 3/30/2025
Ask HN: What are you working on? (March 2025)
Here's a synopsis of the plot, redacted since I've already revealed too much :)
-----, a college student from ----- majoring in -----, graduates from university and is recruited to work for a mysterious company that has links to -----. Initially hired as a translator, his talent with electronics get noticed quickly and his superiors begin training him for a covert overseas operation in which he will visit ----- as an exchange student while really serving as a spy.
With a soft spot for ----- culture, he is excited to visit ----- for the first time. Although he is fully aware he could be killed or imprisoned there, his confidence in his ----- language skills, plus a bit of youthful naiveté, make him jump at the chance. As he carries out his mission in -----, he uncovers a tangled web of family secrets.
[1] https://github.com/kwon-young/units
[2] https://github.com/kwon-young/units/blob/master/examples/spe...
It offers standard features like chatting with videos, summarization, FAQs, note-taking, and extracting sources mentioned in the video. We're taking it a step further by extracting relevant information from video frames and making it easily accessible.
Basically, I've noticed a bunch of social media protocols like ATProtocol, ActivityPub and Nostr are coming out and I think while having these protocols is a good idea, one thing limiting adoption is lack of differentiated social media sites on these protocols. Basically everyone keeps building twitter on a new protocol without offering anything novel. One bottleneck, I thought, is that there isn't a set of utilities to help build a new social network easily so everyone defaults to building twitter as an MVP. I wanted to make an engine, kind of like a game engine, but to make a custom social media for any particular protocol. Hypothetically this should make it so that development for these kinds of projects go way faster. Basically, like a very opinionated django rest framework. Hopefully developers will build more interesting, novel sites and increase adoption for these protocols
https://www.yogile.com/strides-of-march-2025
and Dragon Day at Cornell, where I am spooling out pictures to
https://bsky.app/profile/up-8.bsky.social and https://mastodon.social/@UP8
I'm excited that I'm getting paid to do an event next week because that's been one of my goals. I feel like I'm really progressing at understanding event venues to pair up interesting foregrounds with meaningful backgrounds as well as painting events in a strongly positive light when other photographers might do otherwise.
(2) Coding: I have several applications that use arangodb, a document/graph database that unfortunately, like most innovative databases of the 2010s, has a terrible license. I don't feel I can either commercialize or open source these things so I am switching them over to use JSONB support in Postgres. I am building an adaption layer that works like "python-arango"
https://docs.python-arango.com/en/main/
this is not a complete replacement because I'm not using many features like Pregel or Foxx and in some ways it is more functional because it supports primary keys being integers or uuids. Out of about 50 AQL queries I think there is just 1 that might be challenging to write in SQLAlchemy. It's interesting in that I am triangulating between the implementation being simple, being able to modify my applications if necessary, and also developing the API that I really want in the long term.
This makes Postgres itself stateless and all data storage and transaction processing is handled by FoundationDB, turning Postgres into a fully distributed database akin to CockroachDB and others.
This has a number of advantages: - Simple horizontal scaling simply by adding more nodes, including automatic sharding (no need for Citus or similar) - Distributed and strictly serializable transactions across all your data - Automatic replication for durability and read performance. No need to set up read replicas or configure your client to route queries to them. - Built-in fault tolerance that can handle node failures and full zone outages. No need to configure replication and failovers. - Multi-tenancy through FoundationDB's built-in tenants feature
All this while not just maintaining Postgres compatibility but actually being Postgres, so hopefully all the features/extensions you know and love will be supported.
I'm planning on publishing to this repo if you want to keep an eye on it: https://github.com/fabianlindfors/pgfdb. Likely won't publish any of the source at first but just some instructions for testing it out.
I've seen some pretty fun novel use cases, such as (multiple!) people using it to pick out glasses, wedding invites & so on -- https://apps.apple.com/us/app/rankpic-photo-ranking/id160299... (ios) -- https://play.google.com/store/apps/details?id=app.rankpic.ra... (android)
I mostly wanted an excuse to play with shaders and WebRTC, but I also like the idea of being a sort of “dungeon master” but instead of writing a campaign, I populate the world through procedural rules, and adjust the rules based on how we all end up playing as we go, adding things to stumble upon and keep it fresh in an organic way.