Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
laybak
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
Probing fine-scale connections in the brain
(nature.com)
3 points
by
laybak
6y ago
|
0 comments
92.
▲
by
laybak
6y ago
haha fair point. what do you think would be a better title? (or what made the title a bad one)
93.
▲
Persuasion for Product Managers
(informedpm.com)
18 points
by
laybak
6y ago
|
4 comments
94.
▲
My Attempts to Automate Content Writing
(knowledgeartist.org)
4 points
by
laybak
6y ago
|
0 comments
95.
▲
The Bacterial Flagellar Motor
(youtube.com)
2 points
by
laybak
6y ago
|
0 comments
96.
▲
by
laybak
6y ago
Hi HN, Creator of Rumin here. It is not a polished product, but I think the community would find the concept interesting: https://getrumin.com/ Rumin is a combination of free-form drawing (create page blocks anywhere on the
97.
▲
Show HN: Free-Form Visual Note-Taking and Knowledge Graph
(getrumin.com)
2 points
by
laybak
6y ago
|
1 comments
98.
▲
Characteristics of SARS-CoV-2 and Covid-19
(nature.com)
84 points
by
laybak
6y ago
|
40 comments
99.
▲
Simple Multi-Step User Onboarding (Written in React)
(github.com)
2 points
by
laybak
6y ago
|
0 comments
100.
▲
Procrastination is Instructive. Use it as a Tool
(knowledgeartist.org)
2 points
by
laybak
6y ago
|
0 comments
101.
▲
Resources for Becoming a Better Product Manager
(informedpm.com)
2 points
by
laybak
6y ago
|
1 comments
102.
▲
Good Product Manager/Bad Product Manager
(a16z.com)
3 points
by
laybak
6y ago
|
0 comments
103.
▲
Qualitative and Quantitative Data – Let's Blur the Line
(knowledgeartist.org)
1 points
by
laybak
6y ago
|
0 comments
104.
▲
Is Anything Inherently Difficult?
(guzey.com)
2 points
by
laybak
6y ago
|
0 comments
105.
▲
Building an Ideal Knowledge Management System for Content Creators
(knowledgeartist.org)
4 points
by
laybak
6y ago
|
0 comments
106.
▲
by
laybak
6y ago
thanks for checking it out! you can swap out this API call here: https://github.com/jhlyeung/rumin-web-clipper/blob/master/ch... sorry the code is a bit of a mess, I'm working on cleaning up the ent
107.
▲
Is Happiness at Work Attainable?
(hbr.org)
2 points
by
laybak
6y ago
|
0 comments
108.
▲
Don’t quote. Make it yours and say it yourself
(sive.rs)
4 points
by
laybak
6y ago
|
0 comments
109.
▲
Sattolo's Algorithm (2017)
(danluu.com)
100 points
by
laybak
6y ago
|
20 comments
110.
▲
by
laybak
6y ago
totally! I see these tactics as observations about human behaviours and ways to navigate them. the patterns generalize across different domains and are useful for understanding the world
111.
▲
by
laybak
6y ago
author here, this comment already made my day :) feel free to take the code and run with it, and let me know if you have any suggestions/questions
112.
▲
by
laybak
6y ago
Thanks, kapnobatairza! working on cleaning up the product before opening up, will reach out to ask you more about your use cases :)
113.
▲
by
laybak
6y ago
thanks neovive! Yeah Notion's web clipping and table storage approach is quite elegant. It only gets a bit clumsy when we get to the "power user" (not very common) use cases
114.
▲
by
laybak
6y ago
Thanks Lucas! I was a Notion web clipper user as well. For me it worked for the most basic use case of saving a page into a table. But for me these use cases kept coming up: - An idea belongs to multiple collections, as opposed to a single
115.
▲
by
laybak
6y ago
ohh thanks for the heads up! will look into this. Sorry, this is my first time sharing an open source project. EDIT: I've added an MIT license to the code. Thanks again for pointing out
116.
▲
by
laybak
6y ago
thanks Paul! well that's embarrassing lol just pushed the fix
117.
▲
by
laybak
6y ago
great idea! yeah that would seem to be a better design. Regarding the playback time, currently I'm adding the "t=[TIME]s" parameter to the captured url, so it works for YouTube. But there are definitely more elegant solutions
118.
▲
by
laybak
6y ago
haha for now...the main reason being it's just me working on it at the moment, and I'm fixing/cleaning things up before releasing more of the code base. the rest of the product is pretty clunky (with a beyond shitty code base
119.
▲
by
laybak
6y ago
thanks! and yeah that's a very good point, and one of the main reasons why I'm open sourcing this. Community maintained information scrapers/extractors is definitely a direction I want to build towards, collaborating with any
120.
▲
by
laybak
6y ago
thanks for checking it out! yeah the coverage for the metadata capture definitely needs to be improved. At this point, this just includes the top sites for my own use cases (and some early users). I was hoping by sharing it I can get a bett
More ›