81–90 of 110 posts
I can highly recommend Obsidian for long-term knowledge bases. Have been writing about using it well: https://bryanhogan.com/tags/obsidian It's missing collaboration at the core, although it's possible to achieve this currnetly with third party solutions, or the next major update should also include it as it's the "multiplayer" update.
Earlier quoted context omitted.
You would be surprised at how bad the “engineering culture” is at meta. There are surely people who care about page load latency but they are a tiny minority.
I mean, if you look at Meta's main product it's hard to imagine anyone there cares about engineering. It might be the single worst widely used tech product in existence, and considering they produce the frameworks it's built on it's even more embarrassing.
I can highly recommend Obsidian for long-term knowledge bases. Have been writing about using it well: https://bryanhogan.com/tags/obsidian It's missing collaboration at the core, although it's possible to achieve this currnetly with third party solutions, or the next major update should also include it as it's the "multiplayer" update.
We have a novel architecture where you can optionally register a self-hosted relay server with our control plane for complete privacy for all of your docs and attachments.
We know that people typically prefer to have a unified vault, so you can share individual folders with different groups of people within your vault.
Relay is free for markdown docs up to 3 users, and then we have a hobby plan which includes attachment storage (especially popular with D&D and TTRPG players), as well as per-seat plans for businesses and universities. There are a couple of cloud-only alternatives like peerdraft and screen garden as well.
[0] https://relay.md
Earlier quoted context omitted.
I recently started looking for a new(er) laptop, because it often felt slow. But I started looking at when it was slow, and it was mostly when using things like GMail. I guess my feeling was "if my laptop isn't even fast enough for email, it's time to upgrade". But doing things I actually care about (coding, compiling) it's actually totally fine, so I'm going to hold on to it a bit longer.
This is the exact feeling I had. My 2019 intel MacBook Pro has 12 cores, 32gb ram and a 1TB hard drive. Yet, most consumer web apps like Gmail, Outlook and Teams are excruciatingly slow. What is surprising is that a few years ago, these apps weren’t so terrible on this exact hardware. I’m convinced that there’s an enormous amount of bloat right at the application framework level. I finally caved and bought a new M se…
Preloading authorization data into memory does not, by itself, provide the specific security guarantee (consistency) that defines Zanzibar.
The Zanzibar model is famous not just because it is fast, but because it solves the "New Enemy" problem (or causal consistency). Simple in-memory caching (preloading) often fails this test unless it is paired with complex invalidation logic that mimics Zanzibar's Zookies.
Curious about the authors authz implementation. Preloading authorization data into memory does not, by itself, provide the specific security guarantee (consistency) that defines Zanzibar. The Zanzibar model is famous not just because it is fast, but because it solves the "New Enemy" problem (or causal consistency). Simple in-memory caching (preloading) often fails this test unless it is paired with complex invalidati…
Generally, the solution is to keep a timestamp of when the data changed (Zookies as you mentioned) or you can proactively reload or recompute the cache when the underlying data changes (sometimes in very smart ways), but yeah: it adds significant complications over a "simplified" approach to Zanzibar.
Disclaimer: I'm the cofounder and CTO of AuthZed and we develop the SpiceDB [2] and Materialize [3], which have quite a bit of logic around these exact problems
[1]: https://authzed.com/blog/new-enemies#the-new-enemy-problem [2]: https://spicedb.io [3]: https://authzed.com/docs/authzed/concepts/authzed-materializ...
The thing which I've always wanted to see is a knowledgebase system which uses a company's e-mail as an interface: - new e-mail from client comes in which can't be matched to an existing project? New page in the knowledgebase - second e-mail from client comes in w/ an attachment? It's stripped off and added to that page in the kb - employee sends out e-mail with link to the initial version of the project? The link is…
Still baffles me that Outlook won’t let me tie together emails, calendar items and documents. It makes so much sense to combine these things. All my meetings are about documents and their related correspondence but you never have a coherent information space for them.
Earlier quoted context omitted.
You would be surprised at how bad the “engineering culture” is at meta. There are surely people who care about page load latency but they are a tiny minority.
I mean, if you look at Meta's main product it's hard to imagine anyone there cares about engineering. It might be the single worst widely used tech product in existence, and considering they produce the frameworks it's built on it's even more embarrassing.