Recent submissions

Comment · 2 years ago
There will be no great migration like we saw in 2010 with users shifting from Digg to Reddit but, instead, only the slow trickling escapes of users to more dispersed communities.

Here the human condition can flourish in a more localized way, with more participation (less lurking). No more winner takes all.

Comment · 2 years ago
I'm thrilled to see Vectara here – they have one of the top Product Managers I've ever had the chance to work with and be mentored by.
Comment · 2 years ago
Lost me at uses AWS cloud services
Comment · 2 years ago
I have a nodejs passkey implementation over at AuthC https://github.com/authcompanion/authcompanion2 a simple user management server. For javascript developers https://github.com/MasterKale/SimpleWebAuthn has been a good way to get started with a poc before venturing deeper into webauthn (passkeys) spec.
Comment · 2 years ago
AI is going to continue to have incremental progress, particularly now in hardware gains. No one can even define what AGI is or what it will look like, let alone be something that OpenAI would own? Features progress is too incremental to suddenly pop out with "AGI". Fighting about it seems a distraction.
Comment · 2 years ago
Woah impressive - thanks for building this platform, I see the possibilities of it.

In terms of fees its polar.sh at 5% + stripe connect at x (us region)? What's roughly the stripe fee expected?

Comment · 3 years ago
Could you let me know what use case or challenge you're seeing? I can help to answer this question more specifically. Thanks for taking the time to reach out!
Comment · 3 years ago
Hi, I've kept the user management server both simple (MVP) and focused on reducing the time it takes for application developers to build/integrate user authentication. My goal right now is to listen and gather any and all feedback developers have in this area (likes/dislikes) so I can understand better.
Comment · 3 years ago
thanks for the feedback.
Comment · 3 years ago
Comment · 3 years ago
A general hypothesis I have is that the Deno team is just taking on too much to make the investment work in terms of, well everything really: version compatibility to reduce breaking 3rd party libs, one-by-one certification of npm module compatibility, deno core module re-writes, a hosting company, maintaining developer tooling/ecosystem - to name a few.
Comment · 3 years ago
Comment · 3 years ago
I share the same sentiment and feel the same, its not you alone saying these things. It's starting to seem the llama.cpp project wasn't so community oriented to begin with - which in itself takes a lot of patience.
Comment · 3 years ago
This is a very good question that will be interesting how this develops. thanks for posting the alternatives list.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton