<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: kodegod69</title><link>https://news.ycombinator.com/user?id=kodegod69</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 12 Apr 2026 11:43:32 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=kodegod69" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by kodegod69 in "Polymarket gamblers betting millions on war"]]></title><description><![CDATA[
<p>Sure keep saying that to yourself. All of you sound so damn sure when speaking about socialism. Like the first nation to pierce the firmament of human fabric wasn't a socialist one. And that the union wasn't making great strides in technology.</p>
]]></description><pubDate>Sat, 11 Apr 2026 13:34:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=47730460</link><dc:creator>kodegod69</dc:creator><comments>https://news.ycombinator.com/item?id=47730460</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47730460</guid></item><item><title><![CDATA[New comment by kodegod69 in "Ask HN: How Would You Build a Foolproof Attendance System?"]]></title><description><![CDATA[
<p>There is going to be a an application on the phone, which a student/personnel can't log out of. To log out you'd need authenticators existing in applications with the management, along with a log-out request that must be accepted first. 
As for taking attendance itself, at the end of each lecture, a professor would share an OTP, or a qr that changes every 5 seconds and is also valid for that period. Even before, one can scan the QR code, there would be a biometric and a geolocation check. Once all of this is complete, the attendance metadata would be sent to a server hosted in-house, and presence will be acknowledged. The problem is in someways, this system is still not foolproof. And this is the place where I need help.</p>
]]></description><pubDate>Tue, 21 Jan 2025 07:44:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=42777516</link><dc:creator>kodegod69</dc:creator><comments>https://news.ycombinator.com/item?id=42777516</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42777516</guid></item><item><title><![CDATA[Ask HN: How Would You Build a Foolproof Attendance System?]]></title><description><![CDATA[
<p>I'm building a privacy-focused, secure attendance system that works solely with students' smartphones—no additional hardware. Here's my approach so far:<p><pre><code>    Biometric login: Ensures only the phone owner can log in.
    Geo-fencing: Verifies the user is within the classroom perimeter.
    OTP/QR Code: Adds a layer of real-time verification.
</code></pre>
I'd like advice on how to improve this, because there are still some flaws in such a system. I want to avoid buying any additional hardware, and just depend on smartphones, and make it safe and anti-cheat in nature. Please chip in your expertise and experience. Thanks!</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=42777368">https://news.ycombinator.com/item?id=42777368</a></p>
<p>Points: 1</p>
<p># Comments: 4</p>
]]></description><pubDate>Tue, 21 Jan 2025 07:14:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=42777368</link><dc:creator>kodegod69</dc:creator><comments>https://news.ycombinator.com/item?id=42777368</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42777368</guid></item></channel></rss>