Never tried this, but it was in a selfh.st newsletter a few weeks back

https://www.dedicatedcode.com/projects/reitti/?ref=selfh.st

I thought I would try it out when I had time. It does ‘memories’ and seems to tell a story about your data.

Related to 100% of memes. Laughed at 90%+

Think I might be a 90s kid.

Thank you so much for sharing your design thinking. I have no comments but will be trying your concepts. I am considering whether it might overlap on Gridfinity bins for organising things.

I switched out the router and things started working. Very weird, but I can’t tho jot anything other than it being the Virgin Media hub not liking it. Apparently they have history on this.

Yes, everything looks right. I moved dhcp resolution from the router to technitium recently, but hadn’t set up local resolution.

I’m currently thinking the router is the culprit. Here in the UK there are lots of forum posts complaining about the Virgin Media gear. Nothing specifically describes my problem but I’m going to try a new router over the weekend.

Thanks for the suggestion, I’ll grab a cap to check.

I’m running tcpdump -i any port 53. I can see the outbound request but not the reply. Will the cap show me anything more?

Thanks for giving it some thought!

I have been testing using dig @192.168.0.249 study.lan

3, 4, and 5 work for TXT, NS and SOA but doesn’t work for A records. I think this rules out a simple network issue?

Thanks for replying, I appreciate the response.

I’m running dig @192.168.0.249 study.lan from my client (a MacBook).

If I run ‘dig @192.168.0.249 study.lan TXT’ I get a correct response (I have added a txt record)

If I run ‘dig @192.168.0.249 lan SOA’ or ‘NS’ I correctly get the records for the zone.

I think this eliminates the possibility of it being a routing error?

I don’t know how tech savvy you are, but I’m assuming since your on lemmy it’s pretty good :)

The way we’ve solved this sort of problem in the office is by using the LLM’s JSON response, and a prompt that essentially keeps a set of JSON objects alongside the actual chat response.

In the DND example, this would be a set character sheets that get returned every response but only changed when the narrative changes them. More expensive, and needing a larger context window, but reasonably effective.

Thanks for the link. I knew nothing about him and that was cool.