grandslammer

hahahaahhaha nice one

That argument really skips over what most people actually need. Nobody outside of a tech bubble wants to learn half a dozen Pandoc flags, stitch together shell commands and temp files, or write Lua filters just to reshape a document. With our drive layer you literally rename a file or type “make this header bold and export as PDF” and the work just happens, no scripts required.

This isn’t about replacing power-user workflows, it’s about giving anyone on your team the ability to reshape data and documents without ever opening a terminal. You getflexibility with the simple UX of renaming a file. Calling it “Pandoc plus AI” misses the fact that 90 percent of users neither know nor care about Pandoc’s internals. They just want “I have a file, make it look like this, or formatted with these sections to share with X person who works in X field...” and that’s exactly what our natural-language, filesystem-driven approach delivers.

The friction isn’t “can I call an LLM,” it’s every time I want to do anything with this file I have to:

open it in a tool that understands the format,

export / paste the part I care about,

phrase an LLM prompt,

paste the result back,

do this all again if i want the data formatted differently for different use cases.

adding the ability to format your data and view/download that natively, fast is like giving python scripting capabilities to normal users. You're thinking like a dev not like a business owner who may want to take a picture of a timesheet and have that immediately become a CSV then have it reformatted for a management system they use, all on the fly through natural language... there's so many ways that normal people navigate files and formats and I want to give these people some superpowers that they won't seek out themselves.

the gpt-wrapper argument is so played out. just like you’d say “my app is a GPT-wrapper” (it wraps the OpenAI API in a file-centric UX), you could say “Google Drive is a distributed-storage-wrapper” or “a cloud-storage-and-sync wrapper.” It’s the polished frontend and glue that makes the raw backend useful to end users.

really appreciate you adding to the discourse here - I'm not sure if you got a chance to test out the site but I refilled my credits after the surge of attention and would love if you checked it out! also @boshjerns on X if you want to reach out to chat

i need to work on the pptx conversions and some of the other file types specifically- now i'm on this

i think i hit credit limits because so many people were using the app all of a sudden and i'm just like using my own funds for api costs and had a cap on my openai account

i think we have some similar thoughts - i am working on a file format that accomplishes something like this

I’m like a mid-level developer though so if I messed up the authorization access and you worked around it in someway if you let me know that would be sick @boshjerns on X

Also, as far as the enumeration users are only authorized to access the files that they’ve created in our system, but I should definitely obscure the file count

It’s not about hoarding data rather it’s about the malleability of the data itself so for me, I’m constantly working with data but need to format the way that it is displayed whether it’s the file type or the way that the data is given in the specific file if it’s a CSV for example so an application like this allows me to quickly reformat the files with natural language to maybe make them an HTML where I could share a certain form of document HTML file or take that information and reverted into a CSV format. I need to configure it with a management system or something like that.

It’s basically an access layer that gives you quick access to all the different conversions of the files in one place, but it also allows you to redesign them with natural language so that you can configure them for your needs on the fly

I may need to work on the short pitch

Hahahahaha thank you??