HN user

samanator

404 karma

My name is Shmuel Kamensky. My email is my first name and then my last name at gmail.

Posts16
Comments141
View on HN

The two top comments since the November 7th updatee have thousands of upvotes because of affected users. Comments:

ThSAWistheLAW WC (11/7/24) "I like this app but it is not functioning correctly at the moment. If your video that you're viewing must be interrupted by a message notification or if you simply turn your phone right side up to read the messages or comments the video will stop playing and it will not start no matter how many times you hit the play button. Other than that it's a fine app."

---

michael. jacqui (11/8/24) "New update is awful. It no longer saves where you left off on a video. If you swipe down and leave the video going to search for a new one it automatically paused the video. When you go back to play the video it cannot play unless you select a new video and then have to reselect the video you want to watch to get it to play. The app is horrible and extremely frustrating."

Yes it can be done with rules, inheritance, triggers, and updatable views.

See my answer on stack overflow

https://stackoverflow.com/a/78694335/4188138

However, in my experience, it's more easily maintainable to use normal deletes, have a trigger to move it to a schemaless table (jsonb column type that contains all of the data at the time of delete), and have manual restore logic via a good UX.

You can't use cancellation or heavenly bodies:

"He is far away, or in some strange location, and he cannot see anything we can see. For instance, we cannot say, “Look at Ursa major; now see how those stars are arranged. What we mean by ‘right’ is …” We are only allowed to telephone him."

Mind share isn't necessarily an issue when you build a platform based on standard tools (e.g JavaScript, graphql, etc.).

In my experience those limitations are not just nuisances,they are expensive. They require a lot of custom work and and less reliable since you're leaving what's well known and supported. For example, many companies hit the "100 active concurrently scheduled jobs" limit very quickly. Then they need their own scheduler, or deal with the consequences of stale data.

Those limitations are not just nuisances, they change real business workflows.

Yes, there are definitely good business justifications for choosing Salesforce, but I definitely think there is real business value to be found in improved CRM systems.

Salesforce is slow (the lwc frontend I mean), and has legacy (aka governer) limits. E.g. you can't have synchronous code run for more than 10 seconds, you can't update more than 200 records in a standard transaction, the query language has only very basic joins, and much more.

If you can build a crm without these limitations, why not get your 80% without the limits?

I've written a locally running app that is a lightweight version of this. You can download all your emails, it loads it into sqlite, and you can browse and sort by aggregate email counts (how many emails each sender sent). Once you select a sender, you can archive all of the emails it sent you.

I'd have loved to have made it a full fleshed app like this. Kudos!

The paper's implementation is to essentially append memory text as part of the prompt.

Why don't they use a storage/retrieval system that doesn't consume context window tokens? E.g. Storage could be to automatically categorize data with tags at insertion time (i.e. upon user prompt) and retrieval could be a query that filters using a tag guessed by the LLM (before responding to the user).

With a few initial rules like hard coded tag names/styles, my intuition is that this would produce great results.