Public vals
86
yawnxyz
og
HTTP
Ever wonder how GitHub generates their images when you share a repo on social media? In this example we're using satori and a Deno-friendly SVG WASM creating an OpenGraph image dynamically. E.g. this image can be used when sharing a website, and it'll show up in iMessage or Twitter / other socials. Generated images are cached in Valtown's Blob system. To check metatags, you can use https://metatags.io/?url=https://yawnxyz-og.web.val.run
0
yawnxyz
breakdown
HTTP
This project is an argument summarizer that leverages AI to analyze and extract key arguments from a given text. Goals: Provide a user-friendly interface for inputting text Process the input using a large language model (LLama3 via Groq) Extract and structure key arguments, explanations, and relevant quotes Present the summarized arguments in a clear, organized format The main pipeline: User inputs text through a web interface The input is sent to an AI model for processing The AI extracts and structures the arguments The results are validated against a predefined schema The structured arguments are displayed to the user This tool aims to help users quickly understand the main points and supporting evidence in complex texts or discussions, making it valuable for research, debate preparation, or general comprehension of argumentative content.
2
yawnxyz
squishyform
HTTP
- this version collects data from three ways: a free-form paragraph, a JSON text area, or a table (mimicking a form)
- it's really tempting to create a form that lets people "write anything" in a text box and have the data properly formatted by the AI, it's still kind of an accessibility nightmare.
- I can see this appearing everywhere, maybe for the novelty, but current forms with labels and ARIA etc. will still reign supreme for data-heavy bureaucratic data collection tasks
- for casual inputs though like guest books this could be a simpler alternative
- for "real data applications" like collecting info for shipping and CC, still use a "real" form
- for "real applications" this can still be used to catch errors quickly, like misspellings (which happen a LOT)
- using a really fast/cheap model like llama3.1 8b (or even smaller) is a good use case, but it should support structured outputs
0