t3-turbo-and-clerk VS papermark

In this tutorial, we will implement single sign-on using Clerk, and use GitHub as the OAuth server that'll verify the user’s credentials. We are going to modify an existing application to add protected routes and use the pre-built UI components.

Clerk official example using Nextjs & expo: (no express, webhooks or credential auth) https://github.com/clerk/t3-turbo-and-clerk

I’m currently checking out https://clerk.dev, seems pretty decent so far. The pricing model isn’t ideal but apparently they are redoing it at this moment.

t3-turbo-and-clerk

If you want a complete out of the box easy setup for web and mobile, check this rep out https://github.com/clerkinc/t3-turbo-and-clerk

No I signed up with clerk.dev which made it a lot easier. tbh if it wasn't for them I would have had to hire a developer to help set that up because I had no idea about auth, user databases, and all that.

Some open-source identity solutions I learned could help; integrate with the Logto /Clerk, Ory... API to securely store access tokens that allow Chat GPT to access the user's Logto account; this is a start. But, like these, Security and privacy of service / Technical requirements for integration / User interface for authorization, there’s much to do. It's funny to rethink this topic.

https://clerk.dev meets all of your requirements except ABAC and OSS/self-host. Recommend checking it out if you want something that "just works"

I've def felt your pain before, and it's why I started https://clerk.dev - auth "should just work".

Simple AI assistant for documents made open source

Can be used for your docs or also for shared documents.

It is currently a part of Papermark, open source Docsend alternative for sharing docs quickly and getting analytics on each page.

Thinking on investing more time in it, and building more advanced work with many docs.

Any contributors are welcome here https://github.com/mfts/papermark

Caveat: this serverless implementation only works with files smaller than 4MB. If you need to upload larger files, you'll want to use a client-side upload (see more on GitHub).

Papermark has recently been getting a lot of love from the community, especially for its clean design and intuitive interface. Although it might look simple from the outside, this app packs a lot of functionalities that make everything work smoothly: file upload, email sending, built-in analytics, and custom domains…

I would be grateful if you could give us a star! Don't forget to share your thoughts in the comments section ❤️ https://github.com/mfts/papermark

Papermark - Open Source Alternative to Docsend

Check out the code and setup: https://github.com/mfts/papermark and how to get started: https://www.papermark.io/share-notion-page

Hi HN! We’re Marc and Iuliia from Papermark (https://papermark.io). We're building an open-source, modern document sharing platform with real-time engagement analytics and 100% customization.

It all started as a tweet [1] and led to our launch on Product Hunt [2] last month. We crossed over 1000 stars and over 10 contributors on GitHub (https://github.com/mfts/papermark).

Incumbents, like DocSend, founded in the early 2010s have been acquired already and just don't innovate anymore. Their main priority is enterprise clients.

As founders and developers ourselves we always felt that our needs are not being served. We struggle to get actionable insights when sending pitch decks to investors or sales proposals to customers. We are missing the flexibility and integrations with our existing applications and tech stack.

That’s why we are building Papermark.

Our bigger vision

A developer-friendly document sharing platform doesn’t exist yet! We believe that document analytics should be available to anyone that is creating and sharing documents.

- Rich observability: Don’t get left in the dark when sharing a document. Papermark will provide full transparency by exposing all document-related events through webhooks.