- jj is actually perfectly fit for this and many other problems. In fact, this is actually the default behavior for jj -- if you squash a bunch of jj commits, the bookmarks on top automatically point to the updated rev tree. Then when syncing the dependent branches to git they all rebase automatically.
The problem however lies in who or what does this rebasing in a multi-tenant environment. You sort of need a system that can do it automatically, or one that gives you control over the process. For example, jj can often get tripped up with branch rules in git since you might accidentally move a bookmark that isn't yours to move, so to speak.
- How do GraphQL based systems solve the problem of underlying database thrashing, hot shards, ballooning inner joins, and other standard database issues? What prevents a client from writing some adversarial-level cursed query that causes massive internal state buildup?
I’m not a database neckbeard but I’ve always been confused how GraphQL doesn’t require throwing all systems knowledge about databases out the window
- “use insecure”
- That’s just Rust in general. But what you lose in disk space you gain considerably in optimized executables. The tradeoff is well worth it.
- If they didn’t have the nodejs dependency then the Tauri bundle could be as small as 20mb.
Another pro not mentioned is that native integrations (i.e. obj-c on macos) are much easier to do since rust has great ffi integration with other native libraries.
The biggest pro to electron is that it has extensive plugins that are often widely used in production by large companies. But Tauri is definitely winning and any new project should use Tauri no matter what essentially.
- Perhaps non-browser usage?
- Safari browser is not supported at the moment, we’re working on it!
- Zero! Raw human talent.
- I'm not sure what you're referring to. On the landing page animation, out of 8 search results, only 3 have the word "upcycling", and 5 have either "upcycled" or "upcycling". In the segment after that, two files have neither "upcycling" nor "upcycled". What you're referring to seems already to be the case.
- We are creating things! You can create reports, summaries, documents, etc. via the agent. And yes we can mass edit your files through prompts. The agent can take both single and batch actions. That's the power of the harness we built for the agent. It actually understands and can take action on your file system.
- You really would get results for "upcycling" based on an internal LLM-based summary of disk content!
- Huh! Very cool. We do want to integrate MCP servers for sure. There are some amazing use cases — downloading and organizing email attachments, importing or exporting from other services, using citations/references. And because we have a desktop app we could support local MCP as well. But nothing immediate as far as timeline on our end.
- Hm.. I think because the requirement for approval adds additional arms to the state machine. And the approval step is a message you send to the server that you don't want passed straight to the agent so it doesn't follow the rest of our pattern.
Stupid, not good, unsatisfying reasons I agree!
- That's literally the point! <3
- Agreed. We chose it for the Hacker News crowd.
- There’s nothing more powerful than an idea whose time has come.
- You choose which files to use in Poly, we don't scan your hard drive either.
I don't know about the other services, but Dropbox _does_ read your files. https://help.dropbox.com/security/privacy-policy-faq
> We may build models that identify keywords and topics from a given document. These models may be trained on your documents and metadata, and power features within Dropbox such as improved search relevance, auto-sorting and organization features, and document summaries.
- The file browsing is fully offline supported (as in the files get synced locally). We also allow text search offline, but smart search is not yet offline (we need to embed the search prompt), however, we would like to support fully offline use soon!
- Yes it does! We support web links, PDFs, documents (with annotations!).
Of course, this kind of interactive deep engagement with a topic is fast becoming obsolete. But the essence to me of “knowing” is about doing and experiencing things, updating my bayesian priors dialectically (to put it fancily)