Hope you don't mind, but as others are pointing at wiki type sites, I'll plug my own (also using Vercel and cursor)...
https://ont.fyi it's a work in progress ... feedback wanted (no matter how painful), focusing on enabling adding in your own data at present, lots of ideas and work to be done
It will probably really wind the old git up reading that despite all he his best efforts, I never even realised it wasn’t allowed, wanker (that’s just in case he reads this)!
Problem with VSM, is where is the practical evidence of it working, if it's so great surely there would be more uptake of it?
I mean it sounds like a reasonable model, I'm sure there is a lot of nuance to it, but getting it up and running at an existing enterprise would be a very difficult to do, and at great risk without some solid case studies showing significant ROI.
Thanks for the feedback, and for joining the list.
I agree with your points, my plan is to get a basic version in front of some people and shape it on their feedback. Plan to have it available in a couple of weeks.
next.js reminds me of Ruby on Rails, main pain point is they keep changing how they do things, but docs, examples etc can't keep up so I'm constantly seeing the wrong answers to my problems.
An example of this is how they implemented sitemap.xml, but half arsed doing a sitemap index properly (which really wasn't much work), so they will end up doing it properly in some version, in the mean time you have to work around the framework (it would be better if they didn't even have this feature), and when the release a proper implementation new users will struggle to find the answers on how to do it.
This all adds friction to upgrade, I'd like to move to v15 as it has a feature I really need, but they have changed the bloody confusing caching system, not sure it's worth the work. Creating web frameworks that are volatile is fine if your just building short lived projects, but not anything more complex and longer lived, this is the same pain and why I gave up on RoR.
The approach is not to capture all pages you view, rather you can add the pages etc you want in order to reduce the amount of noise/rubbish. It constructs a knowledge graph from these documents, and then a graph rag approach ontop to enable chat.
The core graph is based on wikidata, you can have your graphs either private or public if so they are published like those you can see on the site now.
Lots to do, but making ing good progress, if this sounds like something you might want to use please sign up.
It’s not AI, it’s a collection technologies and practices within the domain of AI, symbolic and sub symbolic. Arguably classic search is another technology/approach/algorithm with the domain of AI.
I'm fine with it, I've forgotten more frameworks and libs for now dead devices/services/OS etc over the years that it's largely pointless memorising these things, I'm very happy for a machine to help me get to where I want to be, and less time faffing about with google/stackoverflow the better, like I said the failure rate is still fairly high, but still useful enough.
I’m working on a nextjs project, nextjs made a bunch of breaking changes and doesn’t document things consistently or comprehensively, I have a lot of grief using LLM on this framework.
This is something framework/libs/apis should factor in for future, how can you make your project LLM friendly in order to make it dev friendly.
Very much this, I have > 25 years programming experience, but not with typescript and react, it’s helping me with my current project. I ignore probably 2/3 of its auto suggestions, but increasingly I now highlight some code and ask it to just do x for me, rather having to go google the right function/ css magic
I'm cobbling together something that includes links to musicbrainz and other encyclopaedia https://ont.fyi/entity/Q15920 just search for your artist (or anything really).
It's very WIP and rough around the edges, but feedback welcome (it is mostly a wikidata wrapper at the moment, but that isn't the intended goal).
Yeah, but you’re kinda missing the point, there is an existing eco system of ontologies and technologies using RDF, without need to reinvent something likely not as well thought out.