dector
Joined 9 years ago
Karma
199
Submissions
25
Member since
Aug 30
Recent submissions
Comment · 1 month ago
Btw, they had 3D pelican-on-the-bicycle easter egg in one of the promo videos: https://youtu.be/bOC3DisEOfg?t=117 so I'm pretty sure that they spent some small amount of resources to train the model to produce good svg version as well. :D
Comment · 7 months ago
The request was totally opposite. But I genuinely wondering where is this hostility comes from. :)
If you have suggestions how to improve my initial request to make my intentions more clear - I would love to hear them!
Comment · 7 months ago
Hi HN!
I'm considering myself as quite enthusiastic about integrating "AI" into SWE processes. HOWEVER I'm really tired of reading AI-generated or heavily post-processed blogs.
So I would really appreciate if you can share with me some blogs (mostly about engineering but other topics are fine I guess) where authors declare that they prefer not to use "AI" for writing.
I guess it's fine to use some tools to fix grammar lightly or cherry-pick some suggested improvements. But I __really__ want to "hear" voices and ideas of real people, not from Internet-averaged generative algorithms.
Thank you very much and have a nice day!
Comment · 1 year ago
Been playing around Bluefin recently [1]. Which is based on Fedora Silverblue [2]. These are atomic OSes which seems very nice and innovative indeed.
I'm Debian user for 15+ years. But stable version is too old and testing for some reasons breaking quite often (last year I wasted more time on fixing Debian Testing after updates than my friend which uses Arch -_-). Now I'm looking for good alternatives and I think I will stick with containers rabbit hole. :)
Thanks @jcastro [3] and contributers for fantastic work! <3
[1]: https://projectbluefin.io/ [2]: https://fedoraproject.org/atomic-desktops/silverblue/ [3]: https://news.ycombinator.com/item?id=38992292
Comment · 1 year ago
I frequently discover useful and/or thought-provoking and/or inspirational information on numerous small indie-dev blogs.
If you are the author of one of these or similar blogs: thank you, and please keep posting.
Comment · 2 years ago
My point is that token stays the same all the time instead of changing it over the time even for the same session.
Comment · 2 years ago
Usually on low-risk projects where I don't want to bother myself with handling token pairs (or where it's impossible) I have similar simplified approach but regenerating token:
- Session token has two timepoints: validUntil and renewableUntil. - If now > validUntil && now < renewableUntil - I'm regenerating session token.
This way user is not logged out periodically but session token is not staying the same for 5 years.
But maybe I'm just overthinking it. :)
Comment · 2 years ago
Would be nice to see alternative documents for similar topics (e.g. something like OWASP Cheatsheet but from more practical point of view).
With all the respect, I'm a bit skeptical about this document for such reasons:
- Name is quite pompous. It's a very good marketing trick: calling some document like if it was written by group of researchers from a Copenhagen university. :)
Yes, Lucia is a relatively popular library but it doesn't mean that it is promoting best practices and that its author should be considered an authority in such important field unless opposite is proven.
- I don't like some aspects of Lucia library design: when user token is almost expired - instead of generating new security token Lucia suggesting just to extend life of existing one. I see it as a very insecure behavior: token lives forever and can be abused forever. This violates one of the security best practices of limited token lifetime.
But both Lucia and "Copenhagen Book" encourages this practice [1]:
``` if time.Now().After(session.expiresAt.Sub(sessionExpiresIn / 2)) { session.ExpiresAt = time.Now().Add( updateSessionExpiration(session.Id, session.ExpiresAt) } ```
[1]: https://thecopenhagenbook.com/sessions#session-lifetime
Comment · 5 years ago
Thanks! Very promising. Another thing that surprised me is low latency and usability: I signed up, clicked "New Project" and it showed me editor. Like INSTANTLY.
I hope it'll be more or less on the same level later. It feels like magic especially after extremely slow and laggy Figma (seriously, modern 3D games with tons of polygons are working much smoother than web-based tool for drawing colorful rectangles).
Awesome work!
Comment · 5 years ago
> It's physics, not perception.
I guess both counts. :)
But I agree with you that core problem is that many websites are ACTUALLY slow and bloated.
Comment · 6 years ago
It's very obvious (in many different places: landing, documentation, streams) that TailwindCSS is made with love. Thank you for that!
P.S. Trailer is cool!
Comment · 6 years ago
Except that whole project is done side-by-side with Google team that works on Jetpack Compose AFAIK. ;)
Comment · 6 years ago
Nothing.
Comment · 6 years ago
Accessibility (and testing) in Jetpack Compose is done via [Modifier.semantics](https://developer.android.com/jetpack/compose/testing#semant...).