Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lukevp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
53 ms
·
631.
▲
by
lukevp
6y ago
We’ve got an app we’re building, currently in alpha, that is tuned for both of these requirements. It is also super easy to get started. Try it out at https://NoteBrook.app early access code ALPHA2020. The version in production
632.
▲
by
lukevp
6y ago
We’re building a new note app on top of Quill. ProseMirror is great but it’s lacking a little in out of box usability. We’ll consider moving to another editor as we get more traction. In our app, we have a dynamic flexsearch index for full
633.
▲
by
lukevp
6y ago
This seems like the right approach... We store persistent data in DBMSes, which have a schema defining the layout of our data, and use versioned migrations to upgrade the data. All new data either has optional parameters with default value
634.
▲
by
lukevp
6y ago
If you are round tripping because of data, you’re having to traverse the network to the origin and likely composing your queries with dependent data, so http2 is little benefit. For example, if you are loading a book detail page, and want t
635.
▲
by
lukevp
6y ago
I prefer commit messages to be of the form #issueid - summary of issue - additional details - more details Without a blank line anywhere. This makes it really easy to review in graphical git clients because the hyphens collapse into a singl
636.
▲
by
lukevp
6y ago
I have yet to see development of a js search engine continue for the long term. Used FlexSearch in a recent project but it too appears to have been abandoned. Mini search seems nice and it’s a bit newer. It has a focus on low memory usage s
637.
▲
by
lukevp
6y ago
You should absolutely use TypeScript for this. This is exactly what TS is for, to assert your types (proptypes, interfaces, classes, etc.) Switch to .tsx files too. There's a bit of a learning curve for TS, but it's well worth
638.
▲
by
lukevp
6y ago
Butter starts browning at 266. Most oil smoke points are below 375. You are heating your pan to the point your fats are blackening to cook eggs? Cooks illustrated even refers to 250 as an acceptable temp for omelette and 350 as “egg toughen
639.
▲
by
lukevp
6y ago
Do you honestly cook eggs without butter or at least some type of fat? My carbon steel will stick certain things if I throw them in when the pan’s not fully heated and completely dry, so I concede that point to you. I don’t cook like this t
640.
▲
by
lukevp
6y ago
Carbon steel is stamped, cast iron is cast. Back in the day they used to polish them completely smooth but don’t anymore due to the labor involved. I used to use a seasoned cast iron pan and the carbon steel is massively more nonstick.
641.
▲
by
lukevp
6y ago
If you use a carbon steel pan and season it properly, it’s just as nonstick as a nonstick pan. We don’t use Teflon or any other coated pans because we have birds and it can be lethal for them if a pan is overheated. 379+ degrees sounds way
642.
▲
by
lukevp
6y ago
Thanks for the shout out. The problem with auth is in the authorization realm, not the authentication realm. It's super easy to do authentication in nginx for example using client certificates, basic auth, api keys, or in your app lay
643.
▲
by
lukevp
6y ago
I would agree if couchdb wasn't positioning itself as being exposed directly on the internet. If CouchDB is meant to be proxied behind another system / auth stack, then why does it have CORS support and cookie auth built in? Both
644.
▲
by
lukevp
6y ago
Thanks for sharing. They’re obviously inspired by that one from a materials point of view, but the technical implementation is far different. There are some major limitations on the YouTube one. First of all, it’s a potentiometer not a rota
645.
▲
by
lukevp
6y ago
That RFC/PR adds ACLs at the document level to CouchDB, but it has been open for a year now. I hope they merge it as well. Until that PR the party line has always been to do ACL outside the DB like you would with any other DB, which re
646.
▲
by
lukevp
6y ago
We really shouldn't be writing our own authentication layers (or anything security-related for that matter) unless necessary. Case in point, this example code has a massive security issue that allows anyone to impersonate without token
647.
▲
by
lukevp
6y ago
Right, but if your application is just a straight proxy that’s stripping out a bearer jwt or something to validate, you can’t control which documents are being synced. So you have to have 1) some understanding of the underlying protocol so
648.
▲
by
lukevp
6y ago
No, the problem right now is couchdb has no ACLs at the document level so a common pattern is to use a separate DB per user. If there are document level ACLs, you will still have to create a user in couchdb per user but can now use a single
649.
▲
by
lukevp
6y ago
If you made your own board pcb and ordered them populated with everything but the rgb ring and switches, I bet you could get the soldering time down to 2 minutes or so per device, especially if you made custom jigs to hold everything in pl
650.
▲
by
lukevp
6y ago
Great perspective. Totally agree. We are using nginx to proxy to couchdb and do the ssl termination, and it’s great that we can proxy the DB traffic like this since it’s all just http, but couch has always felt one step away from being an a
651.
▲
by
lukevp
6y ago
Thanks for the reply, that’s the RFC I was referring to, and it’s great that that’s being reviewed! If you look back on the history of couchdb on HN for example, the lack of document based ACLs continues to come up as a serious limitation o
652.
▲
by
lukevp
6y ago
You can, but one of the big advantages of couch/pouch is that you can replicate all the way down to the edge and back in real-time. If you have to put up an auth layer in between it becomes more of a traditional architecture. You can s
653.
▲
by
lukevp
6y ago
This is really cool, thanks for your work! I really love couchdb. I have seen tickets for document based ACLs on their github recently, I think this is the last feature they need to open up usage across many more domains. The core app works
654.
▲
by
lukevp
6y ago
Totally agree. Organizing notes into hierarchies is not necessary, most of the time you just care about whether it’s a business note or personal. Chronology is an organization method already available regardless of the note data, and we as
655.
▲
by
lukevp
6y ago
I can't help but feel that even in this "clear and direct communication" the author is continuing to look for ways to manipulate situations and people. What seems to be lacking is empathy. The communication is based upon th
656.
▲
by
lukevp
6y ago
This is great! We have a chihuahua though and I don't think he could eat these. Looks like all you would need to do to support smaller dog breeds is include a smaller silicone tray. If you end up exploring that, hit me up at my e-mai
657.
▲
by
lukevp
6y ago
I have been a .net developer for a long time. More recently, I’ve been using TypeScript in VS Code, with automatic Prettier and eslint on save. It’s ridiculous how much more productive this is. I don’t have to worry about semicolons, code f
658.
▲
by
lukevp
6y ago
If they’re salting like they should then rainbow tables aren’t useful. They would just have a plaintext list of weak passwords and do a direct lookup. Rainbow tables are just a compression technique for hashed password lookups which wouldn’
659.
▲
by
lukevp
6y ago
gnur, Thank you for the kind words! While you are writing a draft note in the editor, the notes are auto saved in your browser every second. As soon as you submit the note (either by hitting enter 3 times at the end of the note, or ctrl+ent
660.
▲
by
lukevp
6y ago
This is great! I totally agree with the concept of just taking notes in sequence. Notes are a record of moments in your life. The act of taking notes quickly, without distraction, and moving on, is so important. Organizing notes in any o
More ›