okhuman

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.

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.

Lost me at uses AWS cloud services

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.

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.

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?

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!

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.

thanks for the feedback.

Would you consider a project like https://github.com/authcompanion/authcompanion2 for the authentication side? Missing anything?

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.

Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment:

"The single executable application feature currently only supports running a single embedded script using the CommonJS module system."

https://nodejs.org/api/single-executable-applications.html

Should be an awesome game changer for node.js when the feature gets rounded out.

Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291

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.

This is a very good question that will be interesting how this develops. thanks for posting the alternatives list.

You're right. I just wish this decision was taken to the community, we could have all came together to help and supported during these difficult/transitional times. :( Maybe this decision was rushed or is money related, who knows the actual circumstances.

Here's the Matt K article https://mattklein123.dev/2021/09/14/5-years-envoy-oss/

Agreed with you 100% - its not easy. Sometimes I just wish someone as talented as Georgi would innovate not just on the core tech side but bring that same tenancy to the licensing side, in a way that aligns incentives better and tries out something new. And that the community would have his back if some new approach failed, no matter what.

The establishment of ggml.ai a company focusing ggml and llama.cpp, the most innovative and exciting platform to come for local LLMs, on a Open Core model is just laziness.

Just because you can (and have the connections), doesn't mean you should. It's a sad state of OSS when the best most brightest developers/founders reach for antiquated models.

Maybe we take up a new rules in OSS communities that say you must release your CORE software as MIT at the same time you plan to go Open Core (and no sooner).

Why should OSS communities take on your product market fit?!

+1. VC involvement in projects like these always pivot the team away from the core competency of what you'd expect them to deliver - into some commercialization aspect that convert only a tiny fraction of the community yet take up 60%+ of the core developer team's time.

I don't know why project founders head this way...as the track records of leaders who do this end up disappointing the involved community at some point. Look to matt klein + cloud native computing foundation at envoy for a somewhat decent model of how to do this better.

We continue down the Open Core model yet it continues to fail communities.

Would you have the link handy? Can't seem to find.

run your own passkey server with https://github.com/authcompanion/authcompanion2

Looking for early feedback on AuthCompanion - a webauthn server (w/ JWTs) to make integrating user authentication with your web apps simpler.

https://github.com/authcompanion/authcompanion2

Twitch's gambling phase was brutal and no doubt harmful.

Whats going on at Roblox? Curious, as a parent myself.

Why couldn't we take something like https://github.com/mckaywrigley/paul-graham-gpt but more general purpose for a doc site? Would that approach to a chat bot trained in product documentation work?

Bun and deno are in an arms race for nodejs compatibility in order to leverage node's vast ecosystem of libraries (think the "embrace" stage of embrace/extend/extinguish). This compatibility layer will take a long time... and will require early adopters to take more time to produce work which their nodejs counterparts can perform faster.

One downside: core devs only prioritize bun features which can enable use cases for running your code in their edge/hosted platform.

Missing some of the other general purpose use cases that devs would want to build - which wouldn't fit into bun's flavor of hosting.

Check out AuthCompanion, a user management server that brings passkeys to your users and is pretty straightforward to setup.

https://github.com/authcompanion/authcompanion2

Thanks for the nice reply and congrats on the launch!

"ADHD" needs a rebranding... move away from clinical diagnosis from medical professionals which can be "heartbreaking" or "liberating" to coaches/advisors running community groups which build frameworks for these like minded, like personality individuals (and their associated family/friends) to operate in (like a 'club') and to help educate others (advocacy).

People with "ADHD" are already covered by the Big Five Personality Traits https://en.wikipedia.org/wiki/Big_Five_personality_traits like every other person is.

Check out AuthCompanion, a passwordless login implementation for ideas. https://github.com/authcompanion/authcompanion2