• 2 Posts
  • 54 Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle


  • I have just let it grow organically. The front page is an index of various topics from personal things and particular games to household information. Then below that there might be just a page or an index to a bunch of pages often starting just as a list of links. I am often refactoring once a page has a bunch of sub headings of related topics but ultimately now needing multiple pages and replacing the original with the index to those pages. I don’t think I could have designed an index system from the start without the content because I wouldn’t have known what I was going to store.






  • My ISP provides a /48 for IPv6 via prefix delegation so all internal machines that support it have a ULA and DHCPv6. I have disabled SLAAC . In docker I assign a /64 of that prefix to docker containers. The local addresses is what most of the internal network stuff is based on (DNS etc) rather than the globally accessible address. The PD addresses are only about going onto the internet.

    SLAAC actually is just fine, I just didn’t really want to be exposing the manufacturer information of the addresses online so preferred DHCP, but either or both together works from OpenWRT prefix delegation.



  • I keep trying to use the various LLMs that people recommend for coding for various tasks and it doesn’t just get things wrong. I have been doing quite a bit of embedded work recently and some of the designs it comes up with would cause electrical fires, its that bad. Where the earlier versions would be like “oh yes that is wrong let me correct it…” then often get it wrong again the new ones will confidently tell you that you are wrong. When you tell them it set on fire they just don’t change.

    I don’t get it I feel like all these people claiming success with them are just not very discerning about the quality of the code it produces or worse just don’t know any better.








  • The only detail really is that at least 2 of the N machines you are using have to be on at the time so where ever a change was made is synced to another machine that is on and this continues so that you never end up booting a machine to use when nothing else with the latest files is available. This is where having a centralised low power machine is valuable and saves having a desktop or a laptop on when it doesn’t need to be.

    I really wish the desktop version of the world had not become so marginalised as local programs are considerably better to use than websites, they are so much quicker, accessible and easier to use.



  • Every one always says XMPP and there were a lot of recommendations for ejabberd. I tried this recently and it was a total disaster, I do not have a working chat server. If I followed the docker instructions the server would just crash with no details of what went wrong. Where it should have been creating a default server config file it was instead creating a directory with the wrong permissions then promptly crashing. I tried following their documentation but after about 6 hours of messing about and adding more and more I still couldn’t get a client to login to it. I have no idea how to make this work.

    So whatever the solution ultimately is I can’t recommend Ejabberd.



  • Initially a lot of the AI was getting trained on lower class GPUs and none of these AI special cards/blades existed. The problem is that the problems are quite large and hence require a lot of VRAM to work on or you split it and pay enormous latency penalties going across the network. Putting it all into one giant package costs a lot more but it also performs a lot better, because AI is not an embarrassingly parallel problem that can be easily split across many GPUs without penalty. So the goal is often to reduce the number of GPUs you need to get a result quickly enough and it brings its own set of problems of power density in server racks.