Demo uses postgres compiled for WASM so demo runs on an actual postgres db.
404 karma · joined November 5, 2018
Demo uses postgres compiled for WASM so demo runs on an actual postgres db.
Very strange behavior honestly.
We discussed this very thing on supabase
https://github.com/orgs/supabase/discussions/18061#discussio...
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."
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.
"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."
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.
If you can build a crm without these limitations, why not get your 80% without the limits?
Currently the biggest blocker, even for simple use cases that don't have to add automation (there is no clear way to add customized automation), is the lack of permissions. Everyone has the same access to all the data!
User permissions: https://github.com/twentyhq/twenty/discussions/209
I'd have loved to have made it a full fleshed app like this. Kudos!
According to this
https://klangable.com/blog/quantity-has-a-quality-all-its-ow...
It was not Stalin who said that
None of the prompts at https://github.com/0xk1h0/ChatGPT_DAN/ or https://www.jailbreakchat.com/ work anymore with gpt4. Some are still working with gpt3.5
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.