Thx, that often works, but that's still inaccessible to me.
- git commit (mostly only code)
- magic or blackblock (meaning back and forth by developer with LLM, before commit)
- git commit (mostly only code)
...
(rinse and repeat)
or - git commit (prompt and/or code)
- git commit (prompt and/or code)
...
(rinse and repeat)
Obviously for that to work the LLM output has to be deterministic and a commit chain has to be pinpointed to a specific weight blob. - wikipedia.org
- HN
- stackoverflow.com
- maps.google.com
- ...
These pages could implement - Knowledge-Base
- Topic-Comment-Community
- Answer-Response-Community
- Interactive-GIS
specifications, that obviously do not exist. E.g. if a newspaper implements a hypothetical "Newspaper-Specification" it would have to provide original, sourced content containing text, images, audio and video via some API (which is often already the case when single page apps fetch content client-side via e.g. JSON). There would be no visual difference between reading "The Guardian" vs. "USA Today" or browsing "OpenStreetMap" vs "Google Maps" as content would be rendered on the client.