OpenAI and Hugging Face address security incident during model evaluation
601 by mfiguiere | 406 comments on Hacker News.
https://ift.tt/B9DVNIl... See also Security incident disclosure – July 2026 - https://ift.tt/kjvT2bJ (9 comments)
Tuesday, July 21, 2026
New best story on Hacker News: OpenAI and Hugging Face address security incident during model evaluation
OpenAI and Hugging Face address security incident during model evaluation
552 by mfiguiere | 361 comments on Hacker News.
https://ift.tt/B9DVNIl... See also Security incident disclosure – July 2026 - https://ift.tt/kjvT2bJ (9 comments)
552 by mfiguiere | 361 comments on Hacker News.
https://ift.tt/B9DVNIl... See also Security incident disclosure – July 2026 - https://ift.tt/kjvT2bJ (9 comments)
New best story on Hacker News: Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber
Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber
527 by logickkk1 | 422 comments on Hacker News.
https://ift.tt/dP6NbWg...
527 by logickkk1 | 422 comments on Hacker News.
https://ift.tt/dP6NbWg...
New best story on Hacker News: Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber
Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber
516 by logickkk1 | 405 comments on Hacker News.
https://ift.tt/dP6NbWg...
516 by logickkk1 | 405 comments on Hacker News.
https://ift.tt/dP6NbWg...
Monday, July 20, 2026
Sunday, July 19, 2026
New best story on Hacker News: Show HN: I replaced a $120k bowling center system with $1,600 in ESP32s
Show HN: I replaced a $120k bowling center system with $1,600 in ESP32s
689 by section33 | 69 comments on Hacker News.
I might be the only SRE on Earth with his own bowling center. It's a more in-depth gig than you'd think. My family and I bought an abandoned 8-lane bowling center in the rural mid-west. In our small town there weren't many recreation options for families. You've heard of a food desert? This is an R&R desert. It had been abandoned for a good reason. The roof leaks, the electrical system was constantly surging, and my 70-year-old bowling equipment (still) doesn't work perfectly. The system that keeps your score is particularly interesting to me. It's the thing you watch during your game, but it fades into the background beyond that. Turns out these things are really cool, but absurdly expensive. Ours was installed in 2008 and cost six figures. It's calculating ball speed and trajectory, camera-based pin detection (object detection and trig, on ICs!), runs the fouling, the animations, the pinsetting machine and ball return. Very cool stuff for its age. From the business perspective, my facility only cost me $105k. To forklift-replace the score keeping system runs anywhere between $80-$120k, depending on features, vendor, and unit age. No upgrades or service contracts, mind you, and every feature and customization is a new line item. That's for a 1:1 replacement on a system installed in 2008. Incredible, given how fast the tech world moves. Replacement parts cost a shocking $4000 per pair of lanes. But wait, the bowling machines themselves are 70 years old, so what's this "advanced" system actually doing back there? Actuating a single relay to trigger that big old machine. Everything else is strictly mechanical. Meanwhile I've got a six-figure invoice in my hand. I'm upset. Given the state of open hardware, computer vision, real-time event streaming, and open source running megascale products worldwide, there had to be a way to do this myself. So far I've built an equivalent prototype for about $200 per lane-pair, $400 if you're fancy. ESP32 and ESPNow with an RS485 fallback, reporting to a raspberry pi lane computer that's really just redis and a state machine bolted to an ESP32 gateway for the mesh. Since it's all ESP32, I've got a fistful of spare controllers in a drawer, pre-flashed or waiting to be. All common off-the-shelf hardware: microcontrollers wired to relays, optocouplers, and IR-break-beam sensors, each running slightly different firmware. Writing the firmware and protocol is the actual hard part. It's an ESPNow star-topology mesh: each node emits events from its sensors and accepts commands for its controls, reporting to a gateway node connected to the raspi over UART. From there it's event streaming: RX packets get translated and tossed into redis, commands relay back out to the mesh as needed. RS485 sits underneath as a wired fallback for noisy RF environments. Once the data's in redis, it's familiar middleware/React/websocket/pub-sub stuff. Any React dev can build their own UI and bowling animations. Since it all runs on commodity hardware, I can do legit anything I want as the proprietor, and I own all my data. Repairs take five minutes; I can swap the rig on a lane pair in under 10. I'd bet a house like mine could go from zero to running in an hour or two. We're calling it OpenLaneLink, and I plan to open source the hardware, firmware, and software stack when it's ready. Bowling is fun, and I want to help keep it affordable for alleys like mine. I hate vendor lock-in. I'm not a fan of closed systems, calling support for every hiccup, or paying to "white label" my own equipment. Want to go Tron-themed for a night? Good luck finding a neon neumorphic theme in something bought at the turn of the century. All that bugged me. Sure, bowling equipment is niche, but the open hardware and software landscape is amazing. Thanks for reading! Let me know if anyone's interested in more posts about this bowling nonsense.
689 by section33 | 69 comments on Hacker News.
I might be the only SRE on Earth with his own bowling center. It's a more in-depth gig than you'd think. My family and I bought an abandoned 8-lane bowling center in the rural mid-west. In our small town there weren't many recreation options for families. You've heard of a food desert? This is an R&R desert. It had been abandoned for a good reason. The roof leaks, the electrical system was constantly surging, and my 70-year-old bowling equipment (still) doesn't work perfectly. The system that keeps your score is particularly interesting to me. It's the thing you watch during your game, but it fades into the background beyond that. Turns out these things are really cool, but absurdly expensive. Ours was installed in 2008 and cost six figures. It's calculating ball speed and trajectory, camera-based pin detection (object detection and trig, on ICs!), runs the fouling, the animations, the pinsetting machine and ball return. Very cool stuff for its age. From the business perspective, my facility only cost me $105k. To forklift-replace the score keeping system runs anywhere between $80-$120k, depending on features, vendor, and unit age. No upgrades or service contracts, mind you, and every feature and customization is a new line item. That's for a 1:1 replacement on a system installed in 2008. Incredible, given how fast the tech world moves. Replacement parts cost a shocking $4000 per pair of lanes. But wait, the bowling machines themselves are 70 years old, so what's this "advanced" system actually doing back there? Actuating a single relay to trigger that big old machine. Everything else is strictly mechanical. Meanwhile I've got a six-figure invoice in my hand. I'm upset. Given the state of open hardware, computer vision, real-time event streaming, and open source running megascale products worldwide, there had to be a way to do this myself. So far I've built an equivalent prototype for about $200 per lane-pair, $400 if you're fancy. ESP32 and ESPNow with an RS485 fallback, reporting to a raspberry pi lane computer that's really just redis and a state machine bolted to an ESP32 gateway for the mesh. Since it's all ESP32, I've got a fistful of spare controllers in a drawer, pre-flashed or waiting to be. All common off-the-shelf hardware: microcontrollers wired to relays, optocouplers, and IR-break-beam sensors, each running slightly different firmware. Writing the firmware and protocol is the actual hard part. It's an ESPNow star-topology mesh: each node emits events from its sensors and accepts commands for its controls, reporting to a gateway node connected to the raspi over UART. From there it's event streaming: RX packets get translated and tossed into redis, commands relay back out to the mesh as needed. RS485 sits underneath as a wired fallback for noisy RF environments. Once the data's in redis, it's familiar middleware/React/websocket/pub-sub stuff. Any React dev can build their own UI and bowling animations. Since it all runs on commodity hardware, I can do legit anything I want as the proprietor, and I own all my data. Repairs take five minutes; I can swap the rig on a lane pair in under 10. I'd bet a house like mine could go from zero to running in an hour or two. We're calling it OpenLaneLink, and I plan to open source the hardware, firmware, and software stack when it's ready. Bowling is fun, and I want to help keep it affordable for alleys like mine. I hate vendor lock-in. I'm not a fan of closed systems, calling support for every hiccup, or paying to "white label" my own equipment. Want to go Tron-themed for a night? Good luck finding a neon neumorphic theme in something bought at the turn of the century. All that bugged me. Sure, bowling equipment is niche, but the open hardware and software landscape is amazing. Thanks for reading! Let me know if anyone's interested in more posts about this bowling nonsense.
New best story on Hacker News: Show HN: I replaced a $120k bowling center system with $1,600 in ESP32s
Show HN: I replaced a $120k bowling center system with $1,600 in ESP32s
580 by section33 | 56 comments on Hacker News.
I might be the only SRE on Earth with his own bowling center. It's a more in-depth gig than you'd think. My family and I bought an abandoned 8-lane bowling center in the rural mid-west. In our small town there weren't many recreation options for families. You've heard of a food desert? This is an R&R desert. It had been abandoned for a good reason. The roof leaks, the electrical system was constantly surging, and my 70-year-old bowling equipment (still) doesn't work perfectly. The system that keeps your score is particularly interesting to me. It's the thing you watch during your game, but it fades into the background beyond that. Turns out these things are really cool, but absurdly expensive. Ours was installed in 2008 and cost six figures. It's calculating ball speed and trajectory, camera-based pin detection (object detection and trig, on ICs!), runs the fouling, the animations, the pinsetting machine and ball return. Very cool stuff for its age. From the business perspective, my facility only cost me $105k. To forklift-replace the score keeping system runs anywhere between $80-$120k, depending on features, vendor, and unit age. No upgrades or service contracts, mind you, and every feature and customization is a new line item. That's for a 1:1 replacement on a system installed in 2008. Incredible, given how fast the tech world moves. Replacement parts cost a shocking $4000 per pair of lanes. But wait, the bowling machines themselves are 70 years old, so what's this "advanced" system actually doing back there? Actuating a single relay to trigger that big old machine. Everything else is strictly mechanical. Meanwhile I've got a six-figure invoice in my hand. I'm upset. Given the state of open hardware, computer vision, real-time event streaming, and open source running megascale products worldwide, there had to be a way to do this myself. So far I've built an equivalent prototype for about $200 per lane-pair, $400 if you're fancy. ESP32 and ESPNow with an RS485 fallback, reporting to a raspberry pi lane computer that's really just redis and a state machine bolted to an ESP32 gateway for the mesh. Since it's all ESP32, I've got a fistful of spare controllers in a drawer, pre-flashed or waiting to be. All common off-the-shelf hardware: microcontrollers wired to relays, optocouplers, and IR-break-beam sensors, each running slightly different firmware. Writing the firmware and protocol is the actual hard part. It's an ESPNow star-topology mesh: each node emits events from its sensors and accepts commands for its controls, reporting to a gateway node connected to the raspi over UART. From there it's event streaming: RX packets get translated and tossed into redis, commands relay back out to the mesh as needed. RS485 sits underneath as a wired fallback for noisy RF environments. Once the data's in redis, it's familiar middleware/React/websocket/pub-sub stuff. Any React dev can build their own UI and bowling animations. Since it all runs on commodity hardware, I can do legit anything I want as the proprietor, and I own all my data. Repairs take five minutes; I can swap the rig on a lane pair in under 10. I'd bet a house like mine could go from zero to running in an hour or two. We're calling it OpenLaneLink, and I plan to open source the hardware, firmware, and software stack when it's ready. Bowling is fun, and I want to help keep it affordable for alleys like mine. I hate vendor lock-in. I'm not a fan of closed systems, calling support for every hiccup, or paying to "white label" my own equipment. Want to go Tron-themed for a night? Good luck finding a neon neumorphic theme in something bought at the turn of the century. All that bugged me. Sure, bowling equipment is niche, but the open hardware and software landscape is amazing. Thanks for reading! Let me know if anyone's interested in more posts about this bowling nonsense.
580 by section33 | 56 comments on Hacker News.
I might be the only SRE on Earth with his own bowling center. It's a more in-depth gig than you'd think. My family and I bought an abandoned 8-lane bowling center in the rural mid-west. In our small town there weren't many recreation options for families. You've heard of a food desert? This is an R&R desert. It had been abandoned for a good reason. The roof leaks, the electrical system was constantly surging, and my 70-year-old bowling equipment (still) doesn't work perfectly. The system that keeps your score is particularly interesting to me. It's the thing you watch during your game, but it fades into the background beyond that. Turns out these things are really cool, but absurdly expensive. Ours was installed in 2008 and cost six figures. It's calculating ball speed and trajectory, camera-based pin detection (object detection and trig, on ICs!), runs the fouling, the animations, the pinsetting machine and ball return. Very cool stuff for its age. From the business perspective, my facility only cost me $105k. To forklift-replace the score keeping system runs anywhere between $80-$120k, depending on features, vendor, and unit age. No upgrades or service contracts, mind you, and every feature and customization is a new line item. That's for a 1:1 replacement on a system installed in 2008. Incredible, given how fast the tech world moves. Replacement parts cost a shocking $4000 per pair of lanes. But wait, the bowling machines themselves are 70 years old, so what's this "advanced" system actually doing back there? Actuating a single relay to trigger that big old machine. Everything else is strictly mechanical. Meanwhile I've got a six-figure invoice in my hand. I'm upset. Given the state of open hardware, computer vision, real-time event streaming, and open source running megascale products worldwide, there had to be a way to do this myself. So far I've built an equivalent prototype for about $200 per lane-pair, $400 if you're fancy. ESP32 and ESPNow with an RS485 fallback, reporting to a raspberry pi lane computer that's really just redis and a state machine bolted to an ESP32 gateway for the mesh. Since it's all ESP32, I've got a fistful of spare controllers in a drawer, pre-flashed or waiting to be. All common off-the-shelf hardware: microcontrollers wired to relays, optocouplers, and IR-break-beam sensors, each running slightly different firmware. Writing the firmware and protocol is the actual hard part. It's an ESPNow star-topology mesh: each node emits events from its sensors and accepts commands for its controls, reporting to a gateway node connected to the raspi over UART. From there it's event streaming: RX packets get translated and tossed into redis, commands relay back out to the mesh as needed. RS485 sits underneath as a wired fallback for noisy RF environments. Once the data's in redis, it's familiar middleware/React/websocket/pub-sub stuff. Any React dev can build their own UI and bowling animations. Since it all runs on commodity hardware, I can do legit anything I want as the proprietor, and I own all my data. Repairs take five minutes; I can swap the rig on a lane pair in under 10. I'd bet a house like mine could go from zero to running in an hour or two. We're calling it OpenLaneLink, and I plan to open source the hardware, firmware, and software stack when it's ready. Bowling is fun, and I want to help keep it affordable for alleys like mine. I hate vendor lock-in. I'm not a fan of closed systems, calling support for every hiccup, or paying to "white label" my own equipment. Want to go Tron-themed for a night? Good luck finding a neon neumorphic theme in something bought at the turn of the century. All that bugged me. Sure, bowling equipment is niche, but the open hardware and software landscape is amazing. Thanks for reading! Let me know if anyone's interested in more posts about this bowling nonsense.
Saturday, July 18, 2026
Friday, July 17, 2026
New best story on Hacker News: Thanks HN for 15 years of support and helping me find my life's work
Thanks HN for 15 years of support and helping me find my life's work
412 by nicholasjbs | 39 comments on Hacker News.
Tomorrow is the 15th anniversary of the first day of the Recurse Center ( https://ift.tt/hrAueqo ) My cofounders and I did YC all the way back in the Summer of 2010, with the initial idea of building "OkCupid for jobs." That idea quickly fizzled, and we spent the better part of a year pivoting between other ideas that also failed. Finally, we made something that we wanted ourselves: a self-directed programming retreat, where people built fun projects, contributed to open source, and helped each other become better programmers. After running two small batches, we launched on HN[1] and got an incredible reception. That post on HN helped us reach beyond our personal networks and meet programmers from around the world, many of whom have since become friends. HN brought us the majority of people who came to our next few batches, and in the years since, HN has remained our #2 source of applicants (after word of mouth). Alas, pg's comment[2] on HN when we launched turned out to be prescient: Running free programming retreats isn't a billion-dollar business, but it's still a worthwhile thing to do, and has positively impacted over 3,000 people so far. And 15 years on I still wake up every day excited to keep working on it. So, thanks HN, for helping make the Recurse Center possible, and for helping me find my life's work. [1] https://ift.tt/A3YxQyt [2] "This sounds like a crazy plan for a startup, I realize, but this is the right sort of crazy. In fact, the way the Hackruiters think about Hacker School is a lot like the way we initially thought about YC: if it doesn't make money, it will at least have been a benevolent thing to do."
412 by nicholasjbs | 39 comments on Hacker News.
Tomorrow is the 15th anniversary of the first day of the Recurse Center ( https://ift.tt/hrAueqo ) My cofounders and I did YC all the way back in the Summer of 2010, with the initial idea of building "OkCupid for jobs." That idea quickly fizzled, and we spent the better part of a year pivoting between other ideas that also failed. Finally, we made something that we wanted ourselves: a self-directed programming retreat, where people built fun projects, contributed to open source, and helped each other become better programmers. After running two small batches, we launched on HN[1] and got an incredible reception. That post on HN helped us reach beyond our personal networks and meet programmers from around the world, many of whom have since become friends. HN brought us the majority of people who came to our next few batches, and in the years since, HN has remained our #2 source of applicants (after word of mouth). Alas, pg's comment[2] on HN when we launched turned out to be prescient: Running free programming retreats isn't a billion-dollar business, but it's still a worthwhile thing to do, and has positively impacted over 3,000 people so far. And 15 years on I still wake up every day excited to keep working on it. So, thanks HN, for helping make the Recurse Center possible, and for helping me find my life's work. [1] https://ift.tt/A3YxQyt [2] "This sounds like a crazy plan for a startup, I realize, but this is the right sort of crazy. In fact, the way the Hackruiters think about Hacker School is a lot like the way we initially thought about YC: if it doesn't make money, it will at least have been a benevolent thing to do."
New best story on Hacker News: Thanks HN for 15 years of support and helping me find my life's work
Thanks HN for 15 years of support and helping me find my life's work
393 by nicholasjbs | 36 comments on Hacker News.
Tomorrow is the 15th anniversary of the first day of the Recurse Center ( https://ift.tt/hrAueqo ) My cofounders and I did YC all the way back in the Summer of 2010, with the initial idea of building "OkCupid for jobs." That idea quickly fizzled, and we spent the better part of a year pivoting between other ideas that also failed. Finally, we made something that we wanted ourselves: a self-directed programming retreat, where people built fun projects, contributed to open source, and helped each other become better programmers. After running two small batches, we launched on HN[1] and got an incredible reception. That post on HN helped us reach beyond our personal networks and meet programmers from around the world, many of whom have since become friends. HN brought us the majority of people who came to our next few batches, and in the years since, HN has remained our #2 source of applicants (after word of mouth). Alas, pg's comment[2] on HN when we launched turned out to be prescient: Running free programming retreats isn't a billion-dollar business, but it's still a worthwhile thing to do, and has positively impacted over 3,000 people so far. And 15 years on I still wake up every day excited to keep working on it. So, thanks HN, for helping make the Recurse Center possible, and for helping me find my life's work. [1] https://ift.tt/A3YxQyt [2] "This sounds like a crazy plan for a startup, I realize, but this is the right sort of crazy. In fact, the way the Hackruiters think about Hacker School is a lot like the way we initially thought about YC: if it doesn't make money, it will at least have been a benevolent thing to do."
393 by nicholasjbs | 36 comments on Hacker News.
Tomorrow is the 15th anniversary of the first day of the Recurse Center ( https://ift.tt/hrAueqo ) My cofounders and I did YC all the way back in the Summer of 2010, with the initial idea of building "OkCupid for jobs." That idea quickly fizzled, and we spent the better part of a year pivoting between other ideas that also failed. Finally, we made something that we wanted ourselves: a self-directed programming retreat, where people built fun projects, contributed to open source, and helped each other become better programmers. After running two small batches, we launched on HN[1] and got an incredible reception. That post on HN helped us reach beyond our personal networks and meet programmers from around the world, many of whom have since become friends. HN brought us the majority of people who came to our next few batches, and in the years since, HN has remained our #2 source of applicants (after word of mouth). Alas, pg's comment[2] on HN when we launched turned out to be prescient: Running free programming retreats isn't a billion-dollar business, but it's still a worthwhile thing to do, and has positively impacted over 3,000 people so far. And 15 years on I still wake up every day excited to keep working on it. So, thanks HN, for helping make the Recurse Center possible, and for helping me find my life's work. [1] https://ift.tt/A3YxQyt [2] "This sounds like a crazy plan for a startup, I realize, but this is the right sort of crazy. In fact, the way the Hackruiters think about Hacker School is a lot like the way we initially thought about YC: if it doesn't make money, it will at least have been a benevolent thing to do."
Thursday, July 16, 2026
Wednesday, July 15, 2026
Tuesday, July 14, 2026
Monday, July 13, 2026
Sunday, July 12, 2026
New best story on Hacker News: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k
Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k
276 by systima | 147 comments on Hacker News.
This started based off of a hunch. We usually use OpenCode, but were 'forced' to use Claude Code for a while due to issues with Meridian. In that time, we saw the usage meter rise much, much more quickly than when using OpenCode. This was the initial anecdotal evidence, but we undertook this small study to collect empirical data: We added logging between the agentic coding tool (Claude Code and OpenCode) and Anthropic's endpoint, and captured all requests (and the returned usage blocks). With one caveat (toward the end of the post) we found unambiguously that Claude Code was far more inefficient in terms of its cache strategy and its harness token usage than OpenCode.
276 by systima | 147 comments on Hacker News.
This started based off of a hunch. We usually use OpenCode, but were 'forced' to use Claude Code for a while due to issues with Meridian. In that time, we saw the usage meter rise much, much more quickly than when using OpenCode. This was the initial anecdotal evidence, but we undertook this small study to collect empirical data: We added logging between the agentic coding tool (Claude Code and OpenCode) and Anthropic's endpoint, and captured all requests (and the returned usage blocks). With one caveat (toward the end of the post) we found unambiguously that Claude Code was far more inefficient in terms of its cache strategy and its harness token usage than OpenCode.
Saturday, July 11, 2026
Friday, July 10, 2026
Thursday, July 9, 2026
New best story on Hacker News: GPT-5.6
GPT-5.6
742 by logickkk1 | 549 comments on Hacker News.
https://ift.tt/LSHlay4 https://ift.tt/XBty3wA https://ift.tt/yUStBo3 , https://ift.tt/RTMfIs8
742 by logickkk1 | 549 comments on Hacker News.
https://ift.tt/LSHlay4 https://ift.tt/XBty3wA https://ift.tt/yUStBo3 , https://ift.tt/RTMfIs8
New best story on Hacker News: GPT-5.6
GPT-5.6
705 by logickkk1 | 499 comments on Hacker News.
https://ift.tt/LSHlay4 https://ift.tt/XBty3wA
705 by logickkk1 | 499 comments on Hacker News.
https://ift.tt/LSHlay4 https://ift.tt/XBty3wA
Wednesday, July 8, 2026
Tuesday, July 7, 2026
Monday, July 6, 2026
Sunday, July 5, 2026
Saturday, July 4, 2026
Friday, July 3, 2026
Thursday, July 2, 2026
Wednesday, July 1, 2026
New best story on Hacker News: For first time, a cell built from scratch grows and divides
For first time, a cell built from scratch grows and divides
557 by defrost | 184 comments on Hacker News.
https://ift.tt/7U2QbEh
557 by defrost | 184 comments on Hacker News.
https://ift.tt/7U2QbEh
New best story on Hacker News: For first time, a cell built from scratch grows and divides
For first time, a cell built from scratch grows and divides
521 by defrost | 172 comments on Hacker News.
https://ift.tt/7U2QbEh
521 by defrost | 172 comments on Hacker News.
https://ift.tt/7U2QbEh
Subscribe to:
Posts (Atom)
-
เคตเคฐोเคฑ्เคฏाเคค เคถเคธ्เคค्เคฐाเคจी เคตाเคฐ เคเคฐूเคจ เคฏुเคตเคाเคा เคेเคฒा เคूเคจ เคตเคฐोเคฐा เคชोเคฒिเคธांเคจी เคेเคฒी เคเคฐोเคชीเคฒा เค เคเค เคตเคฐोเคฐा : เคตเคฐोเคฑ्เคฏाเคคीเคฒ เคेเคธเคฐी เคจंเคฆเคจ เคเคฃเคชเคคी เคเคตเคณ เคเคฐोเคชी เค เคฎो...
-
เคตเคฐोเคฐा เคเคฎเคเคธเคเคฌीเคे เคธเคนाเคฏ्เคฏเค เค เคญिเคฏंเคคा เคช्เคฐเคซुเคฒ เคฒाเคฒเคธเคฐेเคी เคตเคฐोเคฐा เคถเคนเคฐाเคคूเคจ เคนเคाเคฒ เคชเค्เคी เคเคฐा.... เคฎाเคीเคฒ เค เคจेเค เคตเคฐ्เคทांเคชाเคธूเคจ เคตเคฐोเคฐा เคคाเคฒुเค्เคฏाเคค เคाเคฐ्เคฏเคฐเคค...
-
เคญเคฐเคค เคुเคช्เคคा เคต เคธเคนเคाเคฑ्เคฏांเคเคกूเคจ เคฏुเคตाเคธेเคจा เคिเคฒ्เคนा เคช्เคฐเคฎुเคाเคตเคฐ เคीเคตเคेเคฃा เคนเคฒ्เคฒा ; เคंเคฆ्เคฐเคชूเคฐ เคถเคนเคฐाเคคीเคฒ เคช्เคฐเคाเคฐ เคเคฒेเค เคฐเคฎेเคถ เคฐเค्เคे เคฏुเคตा เคธेเคจा เคिเคฒ्เคนा...
