GPT Everywhere App for Windows VS ShowdownJS

I canceled my subscription a while ago because I've been using my GPT-4 solely through the API with my GPT app. I haven't noticed any decline in the quality of GPT-4, so my assumption is that the model isn't the problem. Instead, they may have broken the website somehow. Hopefully, they get it fixed! Source: 9 months ago

GPT API returns data in markdown format. You can parse it using a Markdown library and string manipulation. On Electron app I developed https://jhappsproducts.gumroad.com/l/gpteverywhere, I used https://github.com/markedjs/marked and a code syntax highlighting package to display code blocks. And used JavaScript string manipulation to detect when code blocks start and end so I could add COPY/SAVE buttons to the... Source: 11 months ago

I am currently using GPT only through my desktop GPT app even though it is more expensive than the GPT plus. Source: 11 months ago

Hah those were exactly my feelings when I started creating my own Desktop GPT app: https://jhappsproducts.gumroad.com/l/gpteverywhere "My story began as a tale of frustration, tired of the endless copy-pasting from the GPT website. I knew there had to be a better way."! Source: 12 months ago

I wanted to play with LLM but didn't want to buy new hardware. I solved that problem by using private RunPod.io, which offers powerful GPUs for only about $1 per hour. I can start and stop it as needed. First I used Oobabooga, and now I'm using the Oobabooga API along with my own https://jhappsproducts.gumroad.com/l/gpteverywhere to connect it from my desktop. So like a private remote local llama :D. Source: 12 months ago

So you're going to need a Markdown parser that produces HTML. But there's a question of where is the data coming from and where you you want to process it? If it's going to be all on the frontend like a text editor, use a JS library for it (a quick google search produces ShowdownJS). Source: over 1 year ago

Previously, I was required to implement the markdown support manually which meant that the use of public libraries was prohibited. My tool could only support limited styling elements such as header1, header2, links, bold and italics, but now I can finally let my tool have a full markdown support by using Showdown. - Source: dev.to / over 1 year ago

The first two ages are very heavy on content so I decided to use markdown and tailwind’s typography plugin for styling. I also used showdown to fetch the markdown and turn it into HTML. The code for the above can be found on the site’s GitHub repository. - Source: dev.to / over 1 year ago

I'm using https://github.com/showdownjs/showdown for the core rendering-markdown functionality, with a bunch of additional listeners etc on top of it to fit it into the notion-style UX! Hope that helps :). Source: over 1 year ago

It looks like it uses showdown as the engine. Source: almost 2 years ago