[–] [S] 2 points 5 months ago*

Ok fine. But just to be clear: it can be combined with traditional HTML sites and the LLM is only used to derive the player's situation based on the current world's situation. The exploratory aspect is kind of cool I think; however, it at least seems to me that LLMs are currently kind of bad at this and always render the most generic new scenario. Would be cool to have a CERN for LLMs like Tim Berners Lee proposes ... could result in more creative LLMs.

  • source
  • parent
  • context
  •  

    It's a distributed system for browsing fictional scenarios through LLMs that could be applied to TTRPGs. It still a work in progress, where lots of stuff needs to be fixed (I also want to add multiple playable characters), but you can get the idea. The core is that its an open system, documents can link to one another, also over different servers.

     

    A fantasy world, in which social web, semantic web, agentic web and world wide web all co-exist, with competing factions for each web paradigm (Fedi Tribes - Decentral social networks, Inference Nomads - Semantic Web Technology/Declarative Programming, Fungi Nation - Machine Learning and Marble Kingdom - Incremental Programming/Web Technology).

     

    Attempt of an allegory of our digital present. It is set in a world, in which algorithms and neuronal networks are not abstract ideas but physical entities. Hopefully, this can better explain the technology, their relationship to society and their historical context. The goal is that the underlying mechanics of the world function like a consistent framework of the digital, in which digital entities can be build; a literary sandbox like Minecraft or LEGO but for the digital.

     

    Prequel and Sequel to "Harry Potter and the Methods of Rationality", bridging first into a medieval setting in which the magic system works like incremental programming and then into the present day, in which it works like logical programming. Philosophically, the medieval setting is post-modernism and the present day is analytic philosophy, while HPATMOR is enlightenment rationalism. It's a bit like a digital Alice in wonderland.

    [–] 1 point 1 year ago

    For me, social media clients already act as a kind of browser. Theoretically, if all sides on the web would be connected to ActivityPub, you could access the whole web over a social web client. There exist bridges to the semantic web and of course (regardless of whether this is positive or negative) you also have bots connecting the social web to AI.

  • source
  • [–] [S] 1 point 1 year ago* (1 child)

    i’m no longer sure if you’re envisioning a web browser or a website builder. your terminology is all over the place.

    I's blurring the line in-between. It's trying to set the interaction with the web on a lower level that is closer to the data. It's like you are live-coding the website you want to use for a specific use-case. But then just call the high-level API-endpoints right away. Basically making the dev-tools and the dev-console of browsers the main way to interact with the web (which assumes a web that is build in a similar fashion).

    and no, the semantic web is in no way an an open, global codebase. it’s just a way of structuring html. i know berners-lee wanted the web to be more like what you are describing but the web we have today is not that. you’d need a new protocol.

    Yeah, that's true :(

  • source
  • parent
  • context
  • [–] [S] 2 points 1 year ago* (3 children)

    I don't know. Basically, if you already know what you want, maybe you only want to type down a couple of statements (maybe even from a template or a tutorial that you found online), modify some stuff and then hit enter. And maybe this modifying of language could be the "browsing" part of the browser.

    If you look at it like this it would also be immediate and precise. You would only need to add very good code completion tools, e.g. when you click on a noun, you see all the attributes it has in your ontology. Much like in a IDE. There you also "browse" the space of all potential programs with the interface of language with code completion for keywords and defined concepts, which act like links in traditional browsers.

    In contrast, the semantic web is like a open, global code base, where everybody can contribute to. And traditional browser could not successfully implement a language interface because the code base had no defined semantic, this would be possible for the semantic web. And using LLMs, it could be propagated into other web paradigms.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago (1 child)

    "

    Basically with an app like ChatGPT, you have before you a black box that you can send commands to and that gives you unpredictable answers and consumes huge amounts of energy.

    Instead, the semantc web browser with the precision controller starts with a complete white box, where you can control the ontology, have full control of the language, the outcome and consumes much less energy; but you can move on the ratio towards a ChatGPT-like black box with the precision controller.

    With the default level, the ACE-syntax is enforced very strictly and semantic web data is expected to have the same syntax as defined. With a lower precision level, an LLM is stuck inbetween, syntax is not enforced as strictly and the ontology is enforced even if the data does not match it, also propagating to other web pradigms like MCP/AI-web and traditional web-services with REST-APIs.

    The precision controller basically let's the user move between a very strict semantic web browser and the lose cannon of a ChatGPT+MCP-app. And I think this moving of ratio is only possible if you start developing a strict semantic web browser, which has a precision controller integrated.

    Another merit is that the energy consumption can be adjusted at will. If money/energy is low, for example in a state's administration, the semantic web browser can still be used, while ChatGPT-like apps become unfeasible. "

  • source
  • parent
  • context
  • view more: next ›