mfester

5 ms·

1.
All the wrong ways to think about AI customer support(mux.com)
3 points by mfester 1y ago|0 comments
2.
by mfester 3y ago
Interesting. Could you share more about the performance characteristics of EdgeDB + TypeScript vs say Prisma + other DB?
3.
A “prompt engineered” solution to process Markdown(markprompt.com)
5 points by mfester 3y ago|0 comments
4.
by mfester 3y ago
Embeddings are created using OpenAI's ada model. They are stored in Supabase with the vector extension, which offers a simple way to compute vector similarities. Then the associated sections are added to the prompt context.
5.
by mfester 3y ago
Thanks!
6.
by mfester 3y ago
Yes, we plan to do this in background workers soon so that it can carry the load.
7.
by mfester 3y ago
The way it went is: we built this as part of Motif for the past month, and our users loved it. Many asked for a way to add this feature to their existing sites, so we made a standalone platform that streamlines the process, and open sourced
8.
by mfester 3y ago
Yes, this will come, we had to start somewhere. Would love a PR on this, should be straightforward.
9.
by mfester 3y ago
Handmade, but indeed Tailwind.
10.
by mfester 3y ago
Haven't made a comparison yet but would love to hear about any findings. So far, for the intended use cases, meaning narrative docs with lots of text, images and code, it works really well. We're still breaking up the Markdown int
11.
Markprompt: An open-source GPT-4 platform for Markdown/Markdoc/MDX docs(markprompt.com)
5 points by mfester 3y ago|0 comments
12.
VSCode-mdx 1.1.0 adds support for IntelliSense(twitter.com)
2 points by mfester 4y ago|1 comments
13.
by mfester 4y ago
Not yet. We do support file sync though ( https://motif.land/blog/syncing-text-files-using-yjs-and-the... ) so you can use your mobile Markdown editor of choice.
14.
by mfester 4y ago
Nice work! Regarding your question on how to handle undoing a command on a shape that doesn't exist anymore, is there a way we could automatically recreate the shape?
15.
by mfester 4y ago
Co-founder of Motif here. We're building Motif because we think that ultimately, there is no difference between a document and a full-blown website. The tool needed to author such docs should be at the intersection between a coding env
16.
Motif: A collaborative authoring platform for MDX and Markdoc(motif.land)
9 points by mfester 4y ago|1 comments
17.
by mfester 4y ago
Thank you!
18.
by mfester 4y ago
Sure! Motif is an MDX editor running in the browser, with a full-fledged JS build system inside (based on esbuild). It allows you to publish your content instantly (in fact, as a Next.js app, deployed on Vercel, benefitting from things like
19.
by mfester 4y ago
With pleasure. Feedback welcome! :)
20.
by mfester 4y ago
Thank you!
21.
by mfester 4y ago
Awesome! Happy to hear this :)
22.
by mfester 4y ago
Yes that's one of the goals, and CRDTs are pretty much built for this. Also, browsers are starting to support Progressive Web Apps (PWAs), which enables the websites/apps themselves to be opened while offline.
23.
by mfester 4y ago
Thanks!
24.
by mfester 4y ago
Yes, this is an interesting topic. In Motif, we are using MDX for the page content, which has an associated AST and a nice set of tools (Unified.js [1]) to manipulate it. We plan to use this to track semantic changes in the content, and act
25.
by mfester 4y ago
We're in an exploratory phase on this. We have been experimenting with reading the .git folder to determine the current branch, and store this info alongside the CRDT in the client. Still early to say whether this is a fruitful approac
26.
by mfester 4y ago
We wish! Currently, the API is supported on Chrome 86+, Edge 86+ and Opera 72+: https://developer.mozilla.org/en-US/docs/Web/API/File_System... . It's all quite new, and we hope other browsers will f
27.
by mfester 4y ago
Yes, the goal was to make pragmatic choices in order to make the data freely available, here and now, to other apps (most of which operate on plain text files), despite running in the browser. I do have hope that the POSIX file system still
28.
by mfester 4y ago
Indeed, there's always the risk of breaking a document, since we are dealing with raw edits to a Markdown/MDX/code file. This is very well described by the Ink & Switch team working on Peritext ( https://www.ink
29.
by mfester 4y ago
Once we figured out the "CRDT trick", i.e. simulating file changes as CRDT update operations, it was surprisingly quick to implement. If you look at our repo [1], you will see that the code is fairly straightforward and succinct.
30.
by mfester 4y ago
The starting point for this work is really: how can we take what exists (text files) and make it work in a CRDT setting, without tainting the data in any ways. For instance, if you decide to host your data on Git, we want the repo to look e

More ›