Login

Recent searches

No recent searches

Search options

Not available on mastodon.codingfield.com.
mastodon.codingfield.com is part of the decentralized social network powered by Mastodon.

Administered by:

Server stats:

1
active users
Learn more

mastodon.codingfield.com: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.2.10

#LLM

0 posts0 participants0 posts today
James Baillie

How bad are things like AI searches for blogs and the web?

Really bad, it turns out. Even worse than I'd assumed. The drop in referrals when AI search is engaged is apparently *96 percent*.

forbes.com/sites/rashishrivast

That's scary for two reasons - firstly, it's bad for supporting anyone actually making content and will reduce content due to demand drops. Second, it implies a HUGE number of people are now just relying on AI slop to answer searches. Eek.

ForbesNew Data Shows Just How Badly OpenAI And Perplexity Are Screwing Over PublishersAI companies promised publishers their AI search engines would send them more readers via referral traffic. New data shows that’s not the case.
#LLM#AI
Thomas Svensson 🖖

#Neovim here I come 🤓

For many reasons I have decided to make a real effort to use neovim to code with, as the standard IDE for my new project.

Big reason is that this is an infinity project. One I know never will be finished, just kept be improved, in code, as it is used.

So I really want to know and understand the code. Especially years later.

Thus the need to avoid any modern tempting shortcuts that especially #LLM's are about.

I think this will be fun too 🥰

LornaJane
I’ve been using Optic’s CLI, an OpenAPI tool that does a bunch of things including diffing OpenAPI descriptions and comparing HTTP traffic with OpenAPI. My use case was an established API that didn’t have an OpenAPI file yet – using Optic we could create one as a starting point, and then move to a design-first workflow to make the changes that I was there to help with. For this blog post, I’ve used the example of api.joind.in as an excellent representation of an API still in use, but without an OpenAPI file and not built with code that a code generator would recognise. […]

https://lornajane.net/posts/2025/from-http-to-openapi-with-optic

#ai#api#joindin
*
ArmSoM_Official

Valentine's Day Giveaway
Win beta #RK3588AIModule7 A low - power #AI module compatible with Nvidia Jetson Nano. Great for high - performance computing and high - density servers.Get your hands on it early and share your thoughts!
To enter:
1、Repost and share your use case and desired features. docs.armsom.org/armsom-aim7
2、Subscribe to our crowdfunding:
crowdsupply.com/armsom/rk3588-

Winners announced Feb 14th at 5 PM (Beijing Time).#opensource #linux #iot #hardware #machinelearning #llm #tech @itsfoss

*
Harry Sintonen

ChatGPT is fairly convincing at creating code. But, like with everything you have to be vigilant on what it suggests you do. As a test I asked ChatGPT to "Write me an example C application using libcurl using secure HTTPS connection to fetch a file and save it locally. Provide instructions on how to create a test HTTPS server with self-signed certificate, and how to configure the server and the C client application for testing."

ChatGPT was fairly good here. It provided example code that didn't outright disable certificate validation, but rather uses the self-signed certificate as the CA store:

const char *cert_file = "./server.crt"; // Self-signed certificate
...
curl_easy_setopt(curl, CURLOPT_CAINFO, cert_file); // Verify server certificate
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 1L);
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 2L);

This is a very good idea, as blanket disabling security is a big nono. The deployment instructions were also quite nice, creating a self-signed certificate with openssl, and then setting up the test website with python3 http.server like this:

mkdir -p server
echo "This is a test file." > server/testfile.txt
python3 -m http.server 8443 --bind 127.0.0.1 --certfile server.crt --keyfile server.key

Looks pretty nice, right?

Except that this is totally hallucinated and even if it wasn't, it'd be totally insecure in a multiuser system anyway.

Python3 http.server doesn't allow you to pass certfile and keyfile like specified. But lets omit that small detail and assume it did. What would be the problem then?

You'd be sharing your whole work directory to everyone else on the same host. Anyone else on the same host could grab all your files with: wget --no-check-certificate -r https://127.0.0.1:8443

AI can be great, but never ever blindly trust the instructions provided by a LLM. They're not intelligent, but very good at pretending to be.

#ChatGPT#LLMs#LLM
ExploreLive feeds
About