Showing posts with label AI. Show all posts
Showing posts with label AI. Show all posts

Saturday, August 22, 2026

Handwriting Recognition - A 2026 status check

Background: For years, I had a habit of writing whenever I traveled. No laptop, no apps, just a pen, a notebook, and pages of cursive observations about airports, flights, fellow travelers, and the emotions that come with being away from home. Two decades later, I decided to digitize those notebooks and make them available on Kindle, eventually publishing them as Transit Tales: Between Airports and Emotions: Travel Blog 20 Years Too Late (View on Amazon). As a first step, I assumed modern LLM-powered handwriting recognition would effortlessly convert the pages into text. Instead, the journey led to an unexpected discovery: handwriting recognition is still far from "solved."

The apparent success of modern handwriting recognition is increasingly a combination of imperfect OCR and powerful language-model reconstruction. What users see is often not what the system read, but what the system inferred.

Handwriting Recognition: Better Than It Looks, But Not For The Reason You Think

a hand written page which has been scanned


Modern handwriting recognition demos can be surprisingly impressive. Feed a handwritten page such as the one below into a state-of-the-art OCR system and the resulting transcript may appear almost perfect at first glance. However, a closer examination reveals that the raw recognition quality is often much poorer than it seems. The magic comes not from character recognition alone, but from the language model sitting behind it.

Consider several examples from this handwritten page. The handwritten phrase corresponding to"airport" may initially be recognized as something closer to"surpat". Similarly,"vehicle" can become"valuele","takes a U-turn" becomes"tales a Utum","X-ray machine" becomes"A-vay machine", and"immigration card" appears as"immerdian card". Taken literally, these outputs are poor transcriptions and would be difficult for a human reader to understand without context.

Large language models change the game. Given the surrounding sentence, the model realizes that a traveler arriving at a terminal is far more likely to write"airport" than"surpat","vehicle" than"valuele", and"X-ray machine" than"A-vay machine". The model effectively performs error correction using context, world knowledge, and statistical expectations about language. In other words, it is not necessarily reading the handwriting correctly; it is often inferring what the author probably meant.

This distinction becomes even more obvious with longer phrases. The raw transcription contains fragments such as"want continues - the grove length increase" which are difficult to interpret. Yet an LLM can confidently reconstruct the phrase as"wait continues - the queue length increases". Likewise,"dot Mupose" can be corrected to"what purpose","quese" to"queue", and"lanton" to"London". These corrections are plausible and often accurate, but they are driven at least as much by language understanding as by handwriting recognition itself.

There is an important lesson here. Traditional OCR performance metrics focus on recognition accuracy: did the system correctly identify the handwritten characters? Large language models introduce a second layer that asks a different question: given a noisy transcription, what is the most likely intended text? For users, the final output looks dramatically better, creating the impression that handwriting recognition has become nearly solved. In reality, the underlying recognizer may still be making substantial mistakes, many of which are quietly repaired by contextual reasoning.

The result is both impressive and potentially misleading. If the document contains common travel terms such as airport, boarding pass, London, or immigration card, contextual correction works remarkably well. But when the document contains uncommon names, technical terminology, passwords, identifiers, code snippets, or domain-specific jargon, the same mechanism can "correct" the text into something that is fluent but wrong. Put differently, today's systems often excel not because they perfectly read handwriting, but because they are extraordinarily good at guessing what the handwriting was intended to say.

Summary: Looking at the sample page below, the raw transcription produced words such as"surpat" for airport,"valuele" for vehicle,"A-vay machine" for X-ray machine, and "immerdian card" for immigration card. Yet the final output often looks remarkably accurate because the language model uses context to infer what was probably intended. In many cases, what appears to be excellent handwriting recognition is actually a combination of imperfect character recognition and powerful language understanding. The real breakthrough is not that the machine can read every handwritten word, but that it can often guess the right one.

 Extra Reading:

Confidence is the LLM estimate of how likely the "best guess" matches the intended handwritten word. 
Handwritten textBest guessConfidence
bleambecause / blame20%
surpatairport90%
valuelevehicle95%
canncame85%
tales a Utumtakes a U turn95%
1000per10:00 pm90%
frightflight99%
instid enquiryinitial enquiry80%
want continueswait continues95%
grove lengthqueue length90%
tweekningscreening60%
whoumhmm / whomm30%
bequinbegin95%
mere slowlymove slowly95%
A-vay machineX‑ray machine98%
boarding fan the west itemboarding pass, the next item35%
had baggagehand baggage98%
lantonLondon99%
yhyes95%
dot Muposewhat purpose90%
fan et aromfrom her arm / from a folder20%
gilt the boarding tamgives the boarding pass85%
should Day are of the ben pleasant girlsshould say one of the best pleasant girls70%
tack your bagslock your bags75%
20 1TSA lock? / combination lock?10%
immerdian cardimmigration card99%
quesequeue99%
sigafare vise pageSingapore visa page80%
Monty me in 3001cost me Rs 300/-65%
hundleyhundred85%

Places where context helps.



Monday, August 17, 2026

Finding Signals in the Noise


Finding Signals in the Noise (September 2026)

From hidden patterns to usable systems 

Sunil Kumar Kopparapu 

Much of science is the art of finding signal in noise. Looking back, that idea connects every stage of this journey, from algebra and signal processing to neural networks, computer vision, and speech technologies.

Looking back, the journey was never driven by a grand plan. Rather, it unfolded through a series of small discoveries, each opening a door to a larger world. 

One of the earliest lessons was that aptitude is often acquired rather than inherited. As a schoolboy, mathematics did not come naturally. It was only around Class V or VI that algebra began to make sense, thanks to my father. What had first appeared to be a collection of mysterious symbols revealed an underlying logic. There was a quiet satisfaction in realizing that abstract notation could describe concrete relationships. In retrospect, this may have been the first encounter with a recurring theme: hidden structure waiting to be uncovered. 

Access to computers was scarce during those years. Even later, during undergraduate studies at College of Engineering, Jawaharlal Nehru Technological University Kakinada, computing resources were very limited. In hindsight it was a boon, allowed one to concentrate on the theory. During my Masters at Regional Engineering College (REC), Tiruchirappalli, most student work was conducted through local area network (LAN) terminals connected to central systems rather than on personal machines. Computing was precious, measured and often indirect. Every minute of access mattered, and experimentation required patience. 

The fascination with signals emerged much later. During the final semester of engineering, a course on digital signal processing provided an unexpected revelation. Initially, it was the long equations filling the blackboard, becoming even longer when extended to two-dimensional signals, that captured my attention. Signals were not merely waveforms plotted in textbooks; they were mathematical objects that could be transformed, analyzed, filtered, and understood. Concepts such as convolution, Fourier analysis, and spectral representations offered a way of looking beneath the surface of observed data. For perhaps the first time, mathematics, computation, and real-world phenomena converged into a coherent discipline. 

Fortunately, this interest carried forward into postgraduate studies in satellite communications. Master's level courses provided a deeper exposure to signal processing and strengthened the mathematical foundation required to appreciate the subject. During this period came an introduction to artificial neural networks, which, in the late 1980s and early 1990s, remained largely an academic curiosity rather than the dominant force they would later become 

Unlike today, there were no readily available software libraries, frameworks, or examples to build upon. Understanding a neural network meant understanding every equation and every line of implementation. Fascinated by the idea that machines could learn from examples, a simple feedforward neural network was implemented entirely in C. The architecture was modest: two input nodes, a single hidden layer, and one output node. Training was performed using the back-propagation algorithm. The objective was equally simple but intellectually captivating: solving the XOR problem, a classic example that demonstrated the limitations of the single-layer perceptron and the power of hidden representations. Looking back, unknowingly, I was also doing data augmentation because the XOR problem had just four data points and to train one required a large number of training data.

The success of that implementation left a lasting impression. The notion that a machine could discover decision boundaries through iterative adjustment of weights seemed remarkable. More importantly, it suggested possibilities far beyond toy examples This conviction led to an opportunity during a sponsored project with the Naval Physical and Oceanographic Laboratory (NPOL). The task involved passive sonar target classification, an area traditionally approached through building an expert system with handcrafted features. Neural networks were proposed as a possible solution mechanism for classification using hand-crafted features. At the time, this was far from a mainstream choice. The resulting work led to a first publication, providing an early glimpse of how learning-based techniques could complement conventional expert systems. 

In parallel, during my masters an image processing system (Matrox frame grabber boards installed on a PC) was procured which allowed practical implementation of image processing theory. This led to a deeper engagement with image processing through the development of a functional OMR (Optical Mark Recognition) sheet correction system Exposure to neural network and image processing fueled a desire to pursue deeper research in computational approaches to signals, images and pattern recognition. 

That enthusiasm eventually led to IIT Bombay, where the intention was to pursue research centered on neural computation as applied to image processing and analysis. However, the intellectual journey that followed was not one of continuous affirmation. During this period came a closer encounter with the influential critique found in Perceptrons by Marvin Minsky and Seymour Papert. Reading it produced a profound sense of disillusionment. The limitations highlighted in the book cast doubt on the future of neural-network research, particularly in an era when computational power remained severely constrained and the availability of data for training neural networks was equally limited.

As a result, attention gradually shifted elsewhere.

 Conventional image processing and computer vision emerged as appealing alternatives. They offered rich mathematical structure, challenging computational problems, and tangible visual results. Yet even these pursuits were shaped by the limitations of contemporary hardware. Research often involved working on Intel 386-based systems whose hard disk capacities were smaller than today's random access memory (RAM) and computational resources that would appear almost unimaginable by today's standards, 

Simple matrix operations could become significant undertakings. Computing something as small as a 16x16 matrix multiplication required careful attention to implementation and efficiency in terms of freeing the buffer before assigning it to another variable. Data movement itself was frequently part of the workflow. Experiments were conducted through a ritual familiar to many researchers of that era: inserting floppy disks, transferring files, running a computation, waiting, and repeating the cycle. Progress was measured not only in ideas but also in patience. 

The doctoral years brought a return to signal processing, now at a deeper and more mathematical level. A course on wavelet transforms expanded the conceptual toolkit beyond traditional Fourier methods. Wavelets offered a framework for understanding signals simultaneously in time and frequency, enabling representations that were localized, adaptive, and intuitive. They reinforced a growing appreciation that no single representation is universally optimal; rather, insight often emerges from viewing the same phenomenon through multiple lenses.

The postdoctoral period added another important layer to this journey by revealing the practical use of theory, especially through work on stereo vision. Earlier, image processing often began with a given image: one accepted the image as input and then applied enhancement, segmentation, recognition, or measurement techniques to it. The camera that produced the image was seldom questioned. In stereo vision, however, the image could no longer be treated as an isolated object. Working in the three-dimensional world based on what cameras observed required understanding how the physical world was projected onto a two-dimensional image plane, how camera parameters shaped what was recorded, and why calibration was essential for reliable reconstruction. Concepts such as perspective projection, camera geometry, correspondence, and depth estimation turned mathematical theory into working practice. This experience opened a deeper appreciation of theory not as abstraction alone, but as something that must explain, guide, and withstand the imperfections of real devices and real measurements.

These learnings continued to influence later work in ways that were not always obvious at the time. The understanding of cameras, projection, geometry, and reconstruction naturally fed into attempts to build virtual try-on systems for eyewear, jewelry, and clothing well before such applications became widely discussed or commercially visible. These efforts required the same movement from abstract models to usable systems: an image was not just an image, but a measurement shaped by viewpoint, scale, illumination, calibration, and the geometry of the object and the human body. The postdoctoral experience also left a more durable lesson that carried into speech research: technology becomes meaningful only when it can be built into systems that people can actually use Whether the input was an image, a three-dimensional scene, or a speech signal, the challenge remained the same, recovering structure from imperfect observations and turning that structure into practical tools.

In hindsight, the trajectory appears less fragmented than it felt while living through it. Algebra, signal processing, neural networks, image processing, computer vision, wavelets, and postdoctoral work in stereo vision all revolved around a common objective: discovering structure in complex data and making that structure usable. Each stage offered a different perspective on the same challenge. Algebra revealed hidden relationships behind symbols; signal processing and wavelets showed how structure could be exposed through suitable representations; neural networks suggested that patterns could be learned from examples; image processing and computer vision brought computation closer to visible phenomena; and stereo vision demonstrated that theory acquires its full force only when it engages with cameras, calibration, physical geometry, and imperfect measurements. That lesson stayed on in later attempts to build practical systems, from early explorations of virtual try-on for eyewear, jewelry, and clothing to subsequent work in speech research. Across these efforts, the goal was not merely to analyze data, but to turn analysis into systems that could interpret the world, support decisions, and be of practical use.

What began as an effort to understand a simple algebraic equation eventually evolved into a lifelong fascination with extracting meaning from signals, images, and patterns. The technologies changed the computational resources expanded dramatically, and entire fields rose, faded, and re-emerged. Yet the underlying motivation remained remarkably constant the desire to understand how information is represented, transformed, and ultimately interpreted

In that sense, the journey was never really about moving from one field to another. It was about following the signal wherever it happened to lead.



Sunday, January 18, 2026

Valedictory Chief Guest Thoughts ICNTE-2026

Thank you for the kind welcome. I am truly honored and very pleased to be in the midst of this august gathering—both on the stage and in front of me. More importantly, I am delighted to be in front of the young minds present today. I am also thankful to Professor Choudhury, who made my coming here possible through the invitation and the follow‑up communication. Thank you, ma’am.

I have a couple of thoughts I would like to share, simply because of my years of professional experience may offer some perspective. One thing that strikes me is the title of this conference. The fact that it is held every two years and continues to grow indicates the energy and enthusiasm of the organizers. I am sure the conference has seen many leaps in the quality of presentations and in the novelty of the work showcased. While I have only had the opportunity to look at the titles—not the full papers—I can easily imagine that the presentations must have been valuable.

Coming back to the title, it is very apt to say that “International Conference on Nascent Technologies” One thing that stands out about this conference name is its perennial relevance. It will never become outdated. As technology changes, the content of the conference may evolve, but the name will always remain appropriate. In contrast, a name tied to a specific domain—say “knowledge‑based systems”—might become less relevant over the decades. In that sense, this title is beautifully chosen. I congratulate the organizing committee and the advisory committee for selecting such a timeless name.

Let me take the liberty of sharing a few thoughts. 

First, I want to talk about the way we write papers and technical documents. This is common advice I give to my own team of young researchers. When you step into a domain because you have read someone else’s work, it is important to acknowledge that earlier contribution. Giving credit to previous work is not optional. Literature surveys are a part of academic writing, but beyond that, proper citation is essential.

The second point I emphasize with my team is that if you want someone to really read and benefit from your manuscript, you must guide them on what they can do after reading it. A reader should not reach a dead end. They should not walk away thinking, “I know what the authors did, and I know the conclusion, but what next?” You must articulate possible extensions of your work, open questions, or new directions that arise from your study. Think of these as seeds in your paper. Without planting these seeds, there is no way for the literature to grow from what you have contributed. Citation metrics on Google Scholar may be indirectly hinting at this idea.

My third point relates to an analogy: imagine a wagon carrying goods on a railway track. Today, irrespective of the domain we work in, much of our activity touches machine learning and artificial intelligence. AI is embedded in our digital and even physical environments. For example, we hear about AI‑based washing machines. I am not entirely sure what AI they actually use—it may just be a marketing gimmick—but the point is that AI has become ubiquitous.

Now, many of us in India may not have access to the ideal infrastructure. It can feel like batting against Wasim Akram or Kapil Dev with one hand tied behind your back. The world is not always fair, and we have to work within our constraints.

In the analogy, the wagon represents the modeling mechanism—the AI model. The goods it carries represent your domain knowledge or data. The rails represent your computing infrastructure, your internet connectivity, and your processing capabilities. If you have a strong wagon (a good model), you can carry more goods (data). If your rails are smooth (good GPUs and infrastructure), everything moves effortlessly. But getting all three perfectly aligned is rare, and it requires significant investment.

In India, we often have plenty of data—large volumes of it—but our wagons may not always be large enough, and our rails may not always be world‑class. This means domain understanding becomes crucial. You might have to “massage” the data so it fits into the wagon and can move along the rails you have. If you have powerful GPUs, your approach may be different. But the key idea is this: as students, faculty members, and researchers, we must identify what we can control and use that to innovate. Complaining about what we lack—poor rails or small wagons—won’t help. Focus on what you can influence.

From the awards I saw distributed today, it is clear that this conference has been an excellent venue for all of you. One remarkable feature of this event is its inherently multidisciplinary nature. I noticed topics ranging from smart manufacturing and automation to embedded systems, networking, and security. Such multidisciplinary forums enable interaction between people from different departments or sectors. This broadens perspectives and enhances the way we think. I encourage all of you to interact with peers from other areas, because that is one of the best ways for all of us to grow together.

With these comments, I thank the organizers once again for inviting me. I truly enjoyed spending time among you. I wish you all the very best and a happy new year.

Saturday, May 31, 2025

The Curious Case of the Overachieving LLM

The essay explores the absurdity of overcomplicating simple communication through the use of advanced AI. It narrates a scenario where two humans use a language model to draft and summarize an email about a 3 PM meeting, highlighting the ironic inefficiency of employing sophisticated technology for mundane tasks. The tale humorously questions whether AI is simplifying processes or merely adding unnecessary complexity to human interactions.

This was entirely generated using Microsoft Copilot with little or no modifications. The prompt used was Given the scenario “Human A uses LLM to compose a mail to Human B and Human B uses LLM to summarize the received email!” Compose a humorous essay keeping in mind if using LLM was necessary in the first place.


The Curious Case of the Overachieving LLM
{Or the absurdity and ironic inefficiency of overcomplicating simple communication using advanced AI, specifically large language models (LLMs).}



In the age of technological prowess, one might imagine that communication has become simpler, faster, and perhaps even more meaningful. But then, there exists *the scenario*. A scenario so absurdly unnecessary, yet so hilariously emblematic of modern times, that one cannot help but marvel at its ingenuity—or perhaps, its inefficiency.


To set the stage: Human A has a straightforward piece of information to convey to Human B. We’re not talking about complex geopolitical strategies or the secret recipe for grandma’s lasagna. No, it’s likely something as mundane as, “The meeting starts at 3 PM.” But here’s where the plot thickens: Human A does not simply type out the sentence and send it to Human B. Oh, no. Human A decides that this task requires the intellectual gravitas of a cutting-edge language model (LLM). Why bother with simplicity when you can involve artificial intelligence?

So, Human A opens their laptop, logs into their favorite LLM interface, and begins the prompt. A symphony of keystrokes ensues: “Generate a formal yet approachable email informing Human B that the meeting starts at 3 PM. Use a tone that’s professional but friendly and maybe add a touch of humor so it doesn’t seem too stiff.” Human A leans back, satisfied, as the LLM whirs to life, producing an email that reads more like a Shakespearean sonnet than a logistical memo:


--- 
Dear Human B,

I hope this message finds you in good spirits and perhaps enjoying a cup of coffee or tea as the afternoon unfolds. I am writing to let you know that the meeting we’ve been eagerly anticipating will commence at 3 PM sharp. How thrilling, right? Please don’t be late, for the clock waits for no one. Looking forward to seeing you then!


Warm regards,
Human A

---

Human A beams with pride. The email is a masterpiece—an Olympic gold medalist in the sport of overcommunication. But the saga doesn’t end here. Enter Human B.

Human B receives this poetic missive and, instead of simply reading it, decides that *they too* must harness the mighty power of the LLM. After all, why expend mental energy extracting information when artificial intelligence can do it for you? Human B prompts the LLM: “Summarize the email I just received. Focus on key details and remove any fluff.” The LLM dutifully complies, responding:

--- 
Summary: The meeting starts at 3 PM.

---




And there it is. Two humans, two interactions, two uses of advanced technology. And yet, the final result is precisely what could have been achieved if Human A had simply texted Human B, “Meeting at 3 PM.”


But let us not be quick to judge. The LLM is, after all, the unsung hero of this tale. It played mediator, translator, and even humorist, ensuring that the essence of the message survived the gauntlet of unnecessary embellishment. Without the LLM, Human A might have agonized over word choice, and Human B might have spent a full 30 seconds reading the email instead of 3 seconds skimming a summary. Clearly, this is progress.


The scenario raises important philosophical questions about the role of technology in human communication. Are we outsourcing not just our tasks but also our reading comprehension? Are LLMs becoming middlemen in conversations that could be as direct as handing someone a sticky note? And perhaps the most pressing question: What are we doing with all the extra time saved?


The answer, of course, is obvious. We’re spending it prompting LLMs to write essays like this one.


In conclusion, the curious case of Human A, Human B, and the overachieving LLM underscores our unyielding commitment to efficiency—even if that efficiency involves circuitous routes and redundant processes. The LLM, in all its glory, is not just a tool; it is a testament to humanity’s ability to complicate simplicity. Who needs direct communication when you can have an artificial intelligence-powered extravaganza? Now, if you’ll excuse me, I need to ask an LLM to summarize this essay.

Original PDF Article

Sunday, January 29, 2023

Need for Detect ChatGPT to protect ChatGPT

Some Background

ChatGPT has attracted a lot of attention because of the ability to generate text which while being grammatically correct most of the time happens to also be very conveniencing  to an extent that unless you are _actually_ aware of the _reality_ you might believe what the machine learning model, which is estimated to have cost 1.2 billion USD to build with your and my contributed English text data, is factually correct.

This has spiked debate on if students will outsource their school homework to ChatGPT when they are asked to do their homework. Lets keep aside the fact that even before ChatGPT attracted our eyeballs there was homework outsourcing, it was to pay for the service of an actual _human_ do their tasks.

Note that using ChatGPT to do homework is interpreted as cheating. Teachers always think that students are out there to find an easy way to accomplish the task assigned to them;  never questioning their inability to frame tasks that would actually require the students to demonstrate their learning.

Consequently, there has been an engaging debate on identifying text generated by ChatGPT to _help_ teachers identify if the student is indeed the author of the text or if s/he used the services of a AI bot used (underlying assumption is if they were unfair in completing their task)!

Detect ChatGPT is an outcome of this, a portal (I was not aware there was a portal for this until now!) that will allow one to differentiate between human generated text and machine generated text. A plagiarism checker if you wish.

First we research and build ChatGPT and then we realize that this can be used unfairly (by students!) so we come up with a brand new research problem to detect ChatGPT generated text & newspaper headlines "Stanford introduces DetectGPT to help educators fight back against ChatGPT".

 

"Solved Research problems lend themselves to new research problems --Anonymous" 

can not be less true!

 Going Forward

 

 Note that according to openAI, the creators of ChatGPT, ChatGPT has digested almost all the visible English text data that was available on the internet. So at some point of time in the near future the current version of ChatGPT is going to lagging in terms of being informative. 
 
For example say if a company released a new oral vaccine for COVID19 after the ChatGPT was released, then it would not be aware of it because the information corresponding to that would not been digested by the AI model ChatGPT.
 
Sooner or later,  for the above stated reason, at some time in future, the creators of ChatGPT will see a need for their large language model to be upgraded. 
 
See the above picture; "A" is when the ChatGPT was released and say "E" is the point at which, the upgrade is deemed required; the distance between "A" and "E" is the time between two versions of ChatGPT! 
 
The period between A and E, the world is doing what it does best, generate lots of text data. Except that there is an additional source (you guessed right, ChatGPT) generating data. This is shown by the "red" line. It text generation starts with the introduction of ChatGPT (point "A") and it is likely to overtake the "usual modes of" text generation by humans in terms of volume of text generated. 
The hump on the red line indicates the hype - more and more people trying things out using ChatGPT and then putting the generated text out on the internet to shout their findings!
So at some point E, when a ChatGPT upgrade  is envisioned. The upgraded version would digest more of its own generated text (pictorially the area between the two red lines) that the text that has come from usual sources (human; pictorially the area between the two blue lines) of text generation. In some sense it is learning from itself! 
 
This scenario could lead the upgraded ChatGPT into chaos especially if the output of the current ChatGPT is bullshit (as mentioned in  this article). So if more  and more bullshit text generated by ChatGPT is used to train the next version of ChatGPT; the output is going to be more bullshit (what ever that means). Making the upgrade unusable ...

Unless
  1. After the initial hype the text generated by the ChatGPT is reduced (pictorially it is the area between the red dotted lines; denoted by length between points "H" and "I") compared to the usual modes of text generation (by humans; pictorially it is the area between the blue lines; denoted by length between points "G" and "J"). So that the next version of ChatGPT learns from the "new" and "usual" text data than data generated by itself.
  2.  there is a way to identify the text generated by ChatGPT, namely detect ChatGPT! This mechanism can then be used to filter out text generated by ChatGPT, thereby allowing the upgraded version of ChatGPT to only learn from human generated text and not be biased by the text generated by its older version. All this can happen if the detect ChatGPT works to perfection. However, like all explorations, the ability to achieve good accuracy takes time.

While time will tell about #1. There is a definite need put all research might behind exploring methods to detect ChatGPT generated text data. This is probably the only way that ChatGPT will survive.
 
What do you think?

A Lesson Hidden in Two Simple Words

Sometimes profound ideas are hidden in the most ordinary places. Recently, while looking at two common English words, I stumbled upon an int...