Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
evnp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
61.
▲
by
evnp
3y ago
I'll admit the UX there took me a while to figure out, once you move one point in the mini-map everything makes sense. Incredibly fun to play with. It has rough edges, and showing its age (at least a decade), but here's my contrib
62.
▲
by
evnp
3y ago
Lovely to see. I'm especially excited to discover it also seems to work for horizontal auto-sizing of <input> elements! Have grid-hacked that one more often than textareas. If anyone wants to play with this, the flag is called &q
63.
▲
by
evnp
4y ago
Yes, we're using Vue 3 and composition-style components over at https://radiopaper.com . My only gripe is that Vue's standard templates can't be typed as thoroughly as JSX can (IME - after mixed experiences with Ve
64.
▲
by
evnp
4y ago
const isRandNumOdd = Math.round(Math.random() * 100) |> % % 2 |> Boolean; Excruciatingly contrived, but does this sort of arithmetic work in the Hack syntax? I'm genuinely curious, couldn't find any mention of modulo (or rem
65.
▲
by
evnp
4y ago
Fair points. I feel the need to clarify that you don't _need_ to use `FunctionalComponent` in bare JS, it just gives you an opportunity to type your component props (all `FunctionalComponent` is is a TS interface). This works just fine
66.
▲
by
evnp
4y ago
Thanks for weighing in, that's good to know. After wondering if this could be auto-refactored, I came across https://github.com/jsx-eslint/eslint-plugin-react/blob/maste... , will definitely have to give
67.
▲
by
evnp
4y ago
We've been leaning heavily into Vue3+TSX over at https://radiopaper.com which addresses some of these gripes. It's true there's more "magic" and ceremony around creating components than just a simple fun
68.
▲
by
evnp
4y ago
Similar nit, when you ask "Will theorems() discover `theorem halting_problem (n) : ¬ computable_pred (λ c, ..." I don't believe it will since `const alphabet` does not contain λ or ¬. Apart from my very slight indignance af
69.
▲
by
evnp
4y ago
While not as tight to the blade as a riving knife, I've found these splitters[1] paired with a zero-clearance insert are an excellent alternative, and can be custom-fitted to almost any saw with nothing but a hand drill and the saw its
70.
▲
by
evnp
4y ago
Thanks for the feedback - we have actually discussed how the current footer UX isn't the most discoverable (not due to infinite scroll though :) We're looking for ways to communicate the concepts better - please feel free to messa
71.
▲
by
evnp
4y ago
Should read "Don't place footers below infinite scroll." I appreciate the brevity but this fails to notice the nuance, and ends up being too reductive to be useful advice. Footers can work just fine combined with infinite scr
72.
▲
by
evnp
4y ago
A worthy goal indeed! We are very much looking at expansion of the team, as there are a number of additional features we'd like to roll out to strengthen the product (including a stronger mobile offering). We're exploring options
73.
▲
by
evnp
4y ago
Sorry it's a little hard to find – if you hover your cursor at the bottom of any page there'll be a link to the "about" and "policies" pages, https://radiopaper.com/about
74.
▲
by
evnp
4y ago
Thanks again for the bug report. We've managed to get someone on the team to reproduce the issue, it seems login-by-email doesn't work correctly in Safari for iOS. We found that after you click the email login link, it'll app
75.
▲
by
evnp
4y ago
Fantastic suggestions, thanks – we have a notifications system on our road map but are still formulating the exact mechanics. We would also love to support RSS! One of many things that we will try to get to soon.
76.
▲
by
evnp
4y ago
This is also correct, you can comment on any message in an existing conversation. The same publication rules apply here – this spins off a new one-on-one conversation with the message's author.
77.
▲
by
evnp
4y ago
Sorry about that! Would you be able to let us know which browser and device you're using? We're seeing some errors come in through Sentry about Firebase auth being unable to persist things in local storage, that may be what's
78.
▲
by
evnp
4y ago
Thanks for the question! There's certainly a risk that some kinds of abuse patterns will get through our reply-to-publish model. Eventually we'd like to try and detect bot traffic and challenge them with a CAPTCHA or similar.
79.
▲
by
evnp
4y ago
Yes, all the threads are one-on-one. We've toyed with the idea of group discussions, but haven't landed on what the path forward is there just yet. Thanks for highlighting the image caching issue, we'll look into it! As for t
80.
▲
by
evnp
4y ago
Thanks very much!
81.
▲
by
evnp
4y ago
A few obvious gaps to highlight that we're actively working on: * The OAuth scopes for login with Twitter are overly broad. This appears to be a limitation of Firebase Auth's SDK, it only supports the Twitter OAuth 1.0 API, wherea
82.
▲
Show HN: Radiopaper – Troll-resistant public conversations
(radiopaper.com)
346 points
by
evnp
4y ago
|
323 comments
83.
▲
by
evnp
5y ago
I'm glad OP didn't end up recommending Quill, though their representation of that library seems way off. To help others avoid the state we're currently in, a PSA: https://github.com/quilljs/quill/iss
84.
▲
by
evnp
5y ago
I'd suggest you re-read this[1] section of the article -- they're talking about "server-side generation" where rendering happens at compile time, not at request time (to avoid delaying responses with on-the-fly render co