mfts0

great work, been looking for something like this for a while — love that it‘s open source

First about the comparison with DocSend. Papermark is

1. Open source-first: Papermark is 100% open-source and open to contributions. Host it yourself, fork it, modify it to your desire! Document infrastructure as never been so open and accessible!

2. Fully customizable: you can use custom domains to share a pitch deck or documents and custom branding.

3. Real-time analytics: we use Tinybird's Clickhouse under the hood to enable real-time analytics. We will also add more advanced analytics like heatmaps.

4. AI-driven: this is very much in experimentation, but we aim to add create specific usecases like creating summaries, memos, asking the document questions to Papermark.

To your second question, we are working on a clean REST API that developers can use to access the full suite of Papermark programmatically. This will enable new usecases and integrate much better with existing applications and tools. We are still looking for design partners before we launch it.

There are many millions of documents being created and shared on any given day. However, the moment you share a document you have no idea if the recipient, whether a client, investor or colleague has actually viewed the document or engaged with the document in any way. You are completely left in the dark.

Papermark is providing you actionable insights for your files. Just like you have Mixpanel or Datadog for your application, there is Papermark for your files.

Thanks for the trust jakozloski! Happy to serve you

Thanks :)

Let me know if you have any questions and if you're a developer, how you feel about deeper integrations with your tech stack / apps.

The vision for the v1 is spot on. There were some attempts to turn the open source ecosystem into a creator economy - they are so similar but…

The big BUT is that software needs to be maintained whereas a video once uploaded on YouTube doesn‘t need to be edited again.

I have a feeling that Birk and the Polar team have the right insights to build the right tools to serve the specific needs of open-source software maintainers.

thanks magnusviri - with the tea/gui, it’s also a perfect complement to the tea/cli

Hey tea team here. Building tea/gui was really to enable developers and non-developers to do more with open source software than a command-line interface allows us to do.

tea/gui is fully open source and available on GitHub.

We will be adding more capabilities like actions (turn postgres into a service), scripts store and more.

Donations are not a perfect mechanism, there's significant friction.

tea.xyz will not have fees once it goes live with its funding protocol for open-source software.

Huge fan since Devbook and really happy you found a killer feature of Devbook‘s tooling combined with AI

Also check out the launch on ProductHunt: https://www.producthunt.com/posts/onboarding-love

Onboarding Love is a drop from Marbleflows, an onboarding platform, that covers the first user experience and onboarding from the best software companies like Airbnb, Stripe, Webflow, Slack, Canva, and dozens more.

The user journeys are documented as screenshots and are available for free. Included are pre-built templates that replicate said user journeys in the Marbleflows platform.

Marbleflows makes it dead simple to create flows for user onboarding and other use cases.

That’s interesting threat. I strongly believe in sustainable monetization in open source software. There’s a project called Tea (tea.xyz), a package manager as the evolution of Homebrew.

I honestly believe that understanding the entire dependency graph of open source project will help redistribute money to all packages democratically.

I’m curious to hear what other devs think

I agree that it doesn’t make sense to let some institution define what open source is.

In the end for open source to be open source it should be publicly accessible.

Anything else should be defined in the license as the maintainer/creator wishes.

Love this internal communication tool! It uses my favorite stack Next.js + NextAuth + PlanetScale + Prisma, so I couldn't help it but make a video about it: https://www.youtube.com/watch?v=fMrH444Bvw4

It's a quick code and deploy walkthrough

This should be fixed now :)

Congratulations to Katherine for this amazing project. I do believe this will improve the overall developer experience.

I was so excited I made a video about it and shared my thoughts on why and how GitHub should integrate this. https://youtu.be/kfOimInsnr4

I'm a huge fan of the lightweight nature of Cusdis.

I made this walk-through video of the project inclusive the deployment to Vercel and Railway:

https://www.youtube.com/watch?v=XHr0oBIA2xA

Congrats on releasing it. You definitely see how much work went into Calendly once you parse Calendso's source code. But where there's a will there's a way. Super excited what's possible with Calendso.

I made a quick video to explore the open source project https://www.youtube.com/watch?v=TaIQhG8AL0w

What are your theories why Amazon registered Egghead.com?

Couldn't Spotify argue that the creation of the playlist on Spotify and therefore the resulting object "playlist" is a unique property of Spotify and therefore lockable to their service, excludable from APIs...

https://hackerbay.com/legal/ai-ethics

Disclaimer I'm not from Graphcool or Prisma, but avid user of both

Prisma is the unbundled version of Graphcool.

Graphcool's main selling point was that everything was hosted: "The Parse for GraphQL".

Prisma's main selling point is that you can host your own database wherever you want and Prisma generates the Schema and TypeDefs for you based on CRUD operations. Compared to Graphcool, you get one instead of two endpoints (Relay and Simple API endpoints are the same in Prisma). Now you can connect your client directly to the Prisma endpoint or you build a GraphQL Server (with graphql-yoga or apollo-server) between your client and database.

All resolvers (auth, file hosting, etc) are written on this GraphQL Server level.

Prisma is a lot more flexible and now also bigger enterprises with legacy databases can use them more easily.

Hope that answers your question. Again, I don't work there but really like their product.

The new website looks pretty cool but I wasn’t blown away by the product. The API feels very weird when actually building an app and unfortunately most integrations didn’t work for me.

We’ve tried all available GraphQL BaaS and now use Graphcool which doesn’t have all the features Scaphold provides but the ones they have are very stable and mature. Also their API seemed by far the best one we’ve tried yet (e.g. they are providing an extra endpoint for Apollo client).

Makes me really proud to be a lifetime member of NFX! Great addition to the program. I'm jealous of the fall batch of startups! Pete is a great mentor