Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
siegers
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
siegers
2y ago
Thanks! Yeah, I wanted to keep it specific for GitHub but can see how the base functionality can be used for something more generic. On each page match hit for a signed in user, the API is checked to see if the user has notes - if the match
62.
▲
by
siegers
2y ago
dev here: feel free to ask any questions!
63.
▲
Show HN: A browser extension for your own private GitHub notes
(github.com)
2 points
by
siegers
2y ago
|
3 comments
64.
▲
by
siegers
2y ago
dev here: feel free to ask any questions!
65.
▲
Show HN: Dossi - browser extension and web app is now open source
(xiegerts.com)
6 points
by
siegers
2y ago
|
1 comments
66.
▲
by
siegers
2y ago
(dev here) Are you thinking to bypass GSheets altogether? Or, go Sheets -> another integration.
67.
▲
by
siegers
2y ago
(dev here) Completely understand the concern. This uses an embedded Google File picker to allow you to select what Sheets to allow access to. Until you do that, the extension doesn't have r/w access. The integration with Google (O
68.
▲
by
siegers
2y ago
Thank you! The goal is to save time and reduce the back and forth of finding tabs - hopefully this helps solve some of that.
69.
▲
by
siegers
2y ago
dev here: feel free to ask any questions!
70.
▲
by
siegers
2y ago
(dev here) Something I've done different for this extension that I haven't done in the past: - had an email waitlist that got some interest for months leading up to the actual release - engaged with potential users in community ch
71.
▲
Show HN: Right-click and save content directly to Google Sheets
(addtosheets.com)
33 points
by
siegers
2y ago
|
12 comments
72.
▲
by
siegers
2y ago
This great feedback - thank you. I like the idea of the TTL. That's interesting if we continue on the current route. Similar to the "open start up" concept and publishing available runway, etc.
73.
▲
by
siegers
2y ago
(cofounder) Thanks and glad to hear! Our main goal was to _not_ try to make it "everything" and while still making it enjoyable to use. We'd appreciate any feedback once you do some testing. Send over to lowercasehq@gmail.com
74.
▲
by
siegers
2y ago
Thanks! So we actually started with offline first originally (a standalone desktop app) and then rebuilt for the web. We had plans to revisit based on interest, etc. so it's good to get the feedback here and use that to shape the direc
75.
▲
by
siegers
2y ago
(cofounder here) Thanks for the feedback! We have some ideas, and to be honest, the feedback here has been great to firm up some of our assumptions. I'd like to follow up on this if you're interested. Feel free to email (lowercase
76.
▲
by
siegers
2y ago
Thank you for the suggestion!
77.
▲
by
siegers
2y ago
Thanks for the feedback. One reason for the username is for cleaner profiles when publishing - https://learn.lowercase.app/publishing/documents.html#adding...
78.
▲
by
siegers
2y ago
Thank you for the feedback! This route is definitely something for us to consider.
79.
▲
by
siegers
2y ago
This is something that we've discussed quite a bit and not completely off the table.
80.
▲
by
siegers
2y ago
(co-founder) Sry about that - if you want to email lowercasehq@gmail.com I can remove and confirm for you.
81.
▲
by
siegers
2y ago
(co-founder) Thanks for the comment and very valid points. When we initially started building we had subscription plans and more of a general revenue model. Over time we transitioned to the donation-based approach. We are open to revisiting
82.
▲
by
siegers
2y ago
Meaning that we'd be limiting users that don't use the provider(s) that we'd support. At that time, we felt that username/password was the lowest friction at the time. We're happy to re-eval if needed though!
83.
▲
by
siegers
2y ago
Wasn't necessary since we weren't intending to share information with another service and felt that the 3rd party requirement could be limiting.
84.
▲
by
siegers
2y ago
co-founder here: Just a little context on the "why" from the site - > We created lowercase as a side project to make it easier for folks to quickly share content without the pressure of having the perfect blog post. Sometimes y
85.
▲
by
siegers
2y ago
Thank you! And cool app too! We had a similar experience in that we built the majority of this ~4 years ago. And it's been stable since.
86.
▲
by
siegers
2y ago
(co-founder here) Thank you! It is realtime across devices/instances for the active user. Currently it doesn't support collaborative editing but it's always been on the back of our minds if there is enough interest. Aside f
87.
▲
by
siegers
2y ago
Folks with technical experience but not necessarily web devs. When you want more out of Google Docs, Notes, etc. but don't want to invest the time in building it yourself. Or, that's not your skillset. - Syntax highlighting - &quo
88.
▲
by
siegers
2y ago
other co-founder here: 1. Currently there isn't support, but not opposed if there is a need. 2. Also, there isn't a way to export (or self host) as of now. Just some background - We originally built this out as a standalone deskto
89.
▲
Lowercase – A simple way to take and share notes
(lowercase.app)
222 points
by
siegers
2y ago
|
178 comments
90.
▲
Your native tongue holds a special place in your brain
(science.org)
1 points
by
siegers
3y ago
|
0 comments
More ›