AntsInside's recent activity
-
Comment on Researchers describe how to tell if ChatGPT is confabulating in ~comp
-
Researchers describe how to tell if ChatGPT is confabulating
24 votes -
Comment on I will fucking piledrive you if you mention AI again in ~comp
AntsInside Agreed this is a valuable perspective. More generally, I am also interested to know whether experience with the value of AI at work have lead nacho to use it more widely, or if writing and...Agreed this is a valuable perspective. More generally, I am also interested to know whether experience with the value of AI at work have lead nacho to use it more widely, or if writing and personal assistant AIs generally available just do not measure up to their company tuned examples.
-
Comment on NHS is broken - also, did my Pa have a stroke? in ~talk
AntsInside You can add my sympathies for such a horrible experience. I really hope you get more clarity and treatment for your dad quickly. I also had to go to NHS A&E and various hospital visits this year,...You can add my sympathies for such a horrible experience. I really hope you get more clarity and treatment for your dad quickly.
I also had to go to NHS A&E and various hospital visits this year, and some of my impressions are similar to yours. Staff usually compassionate and helpful but management systems full of inefficiencies. The system has not let me down nearly as badly as it did your family, but I see a lot oddities.
- Waited in line of patients arriving at A&E standing out the front door into the cold, to be questioned on symptoms publicly by (I think) a nurse filling a paper form for each patient, before being able to then register at hospital and then sit down in the waiting area. Appears to be a self-registration computer system sitting turned off to one side. Same questions asked again later by nurse triaging.
- Due to some symptoms, I was put on what the doctors euphemistically called the "two week" pathway - later heard it referred to as the cancer pathway. This really did get me through the system quickly, I got appointments in days and there was a completely separate dedicated team following up. This was great, but actually felt like overkill given the original concerning symptoms disappeared quickly and did have alternative explanations. As soon as it was declared "not cancer", I was back to long delays for things to move forward and no follow up. Good they managed to improve the process for cancer, but it did not feel like a coherent approach.
- Went to hospital appointment to find all parking full. Eventually found a space in what I think was a staff car park but am still unsure because the signage was so confusing. Staff implied this situation was common. I probably could have found someone to drop me off, but there was no encouragement to avoid driving in advance.
- Waiting in line behind someone who had apparently made an hour and half train journey to come for an appointment that had been cancelled.
- Paper letters - appointment letters nearly always sent by paper mail, in a few cases after they were relevant. But then sometimes sent by email - usually when I made a change to appointment, so seemed to be just admin staff deciding this one they would email. Overhearing staff training in CT scan waiting area saying that they always have to send the scans by paper mail, so this can delay by weeks.
I feel like perhaps too long operating in crisis-mode and fighting for resources, has led to an inflexible culture where it is hard to rework how things operate.
-
Comment on SSL.com is evil and deceptive: Don’t do business with SSL.com in ~tech
AntsInside Using LetsEncrypt is usually the right answer, but if setting up automatic cert renewal is awkward for some reason (eg environment not fully under your control), a longer running cert is not much...Using LetsEncrypt is usually the right answer, but if setting up automatic cert renewal is awkward for some reason (eg environment not fully under your control), a longer running cert is not much of an expense from a reasonable provider.
-
Comment on [SOLVED] Debugging a slow connection between local devices in only one direction in ~tech
AntsInside Thanks for keeping us all updated so well. Glad you got a solution!Thanks for keeping us all updated so well. Glad you got a solution!
-
Comment on [SOLVED] Debugging a slow connection between local devices in only one direction in ~tech
AntsInside It seems like the issue must be a confluence of factors whatever it is. One reason for suspecting the APs is that I tried to troubleshoot an issue for years with Unifi APs intermittently not...It seems like the issue must be a confluence of factors whatever it is. One reason for suspecting the APs is that I tried to troubleshoot an issue for years with Unifi APs intermittently not allowing connection from Apple devices. I never managed to pin it down, but I am pretty sure it was a bug with UAP-PRO APs sometimes getting into a problematic state.
-
Comment on [SOLVED] Debugging a slow connection between local devices in only one direction in ~tech
AntsInside If you SSH into the access points you can run a packet capture on the AP itself with tcpdump and see what is coming in and going out. I have done this before but would have to remember the right...If you SSH into the access points you can run a packet capture on the AP itself with tcpdump and see what is coming in and going out. I have done this before but would have to remember the right command line arguments.
Do you see packets getting lost if you just run a ping for a while or only when the connection is loaded?
-
Comment on [SOLVED] Debugging a slow connection between local devices in only one direction in ~tech
AntsInside My (not confident) guess would be a bug in the access points. You could try a different version of the firmware. Are they on the latest firmware? Have you seen the issue on other firmware...My (not confident) guess would be a bug in the access points. You could try a different version of the firmware. Are they on the latest firmware? Have you seen the issue on other firmware versions?
You can SSH into the access points themselves and may be able to see errors in system logs or if they are suffering CPU or memory issues when a transfer from wireless devices to server A occurs.
You could check the wifi status on the laptops to see if they are connected at the full speed profile expected. Not sure how to do that on Fedora or Mac, and probably not as they work in the other direction.
Another thought: are all devices definitely on the same IP subnet and not going through any kind of firewall in the gateway?
-
Comment on Cheap options(?) to run local AI models in ~comp
AntsInside I have also been playing with Fooocus and finding it usable if rather slow with a PC I put together last year for about $1300 with Radeon RX 6600 (8GB RAM). I get some system instability and run...I have also been playing with Fooocus and finding it usable if rather slow with a PC I put together last year for about $1300 with Radeon RX 6600 (8GB RAM). I get some system instability and run out of VRAM if I try some operations like upscaling. It feels like any less VRAM would be too little, but maybe it would work better with an nvidia card.
-
Comment on The morality of using AI-generated art in my web app in ~comp
AntsInside In the terms, Midjourney assign to you the rights that they have in the art. The problem is that for AI generated art current case law (in the US at least) is that no copyright exists in the first...In the terms, Midjourney assign to you the rights that they have in the art. The problem is that for AI generated art current case law (in the US at least) is that no copyright exists in the first place because it was not created by a human author.
At the risk of being pile-driven, this AI news seemed more intriguing than hype reaction. This paper seems to present a relatively easy-to-understand step to progress on the inaccuracy problem that often seems the fatal flaw for uses of LLMs.