<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Junaidul Islam Jarif</title>
    <description>The latest articles on DEV Community by Junaidul Islam Jarif (@junaidul_islamjarif_f892).</description>
    <link>https://dev.to/junaidul_islamjarif_f892</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3712625%2F368ba029-e27c-4fb5-a88f-46016f56e9e7.jpg</url>
      <title>DEV Community: Junaidul Islam Jarif</title>
      <link>https://dev.to/junaidul_islamjarif_f892</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/junaidul_islamjarif_f892"/>
    <language>en</language>
    <item>
      <title>When You Need Unique Users but Can’t Force Login</title>
      <dc:creator>Junaidul Islam Jarif</dc:creator>
      <pubDate>Mon, 19 Jan 2026 13:20:26 +0000</pubDate>
      <link>https://dev.to/junaidul_islamjarif_f892/when-you-need-unique-users-but-cant-force-login-2jk2</link>
      <guid>https://dev.to/junaidul_islamjarif_f892/when-you-need-unique-users-but-cant-force-login-2jk2</guid>
      <description>&lt;p&gt;I got a course project where I need to present some information and then collect user data through a survey. While working on it, one major concern was how to ensure that each user submits only &lt;strong&gt;one unique response&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The most straightforward solution is to use an email-based authentication system, such as Google login. However, this approach felt like &lt;strong&gt;overkill&lt;/strong&gt; for a simple survey website. Additionally, many users are reluctant to participate in surveys when there is no incentive or reward involved.&lt;/p&gt;

&lt;p&gt;To avoid a full authentication system, I considered &lt;strong&gt;IP-based identification&lt;/strong&gt;, where users are identified by their IP addresses. I implemented this solution, but I quickly realized its limitations. IP addresses can change frequently, especially on mobile devices when users are traveling. I initially assumed this method might work better for desktop users, but that assumption turned out to be wrong. Even from my home network, I was able to submit multiple votes after some time.&lt;/p&gt;

&lt;p&gt;At first, I suspected that refreshing the page might remove the restriction, but that wasn’t the case. The issue seems more complex, and I am still investigating the exact reason behind this behavior.&lt;/p&gt;

&lt;p&gt;Next, I explored using &lt;strong&gt;cookies&lt;/strong&gt; to identify users. This solution also has significant drawbacks. If users switch devices—such as moving from a mobile phone to a desktop or laptop—it becomes impossible to prevent multiple responses. Furthermore, some browsers and browser extensions block cookies by default, making this method unreliable.&lt;/p&gt;

&lt;p&gt;Through this research, I came to the &lt;strong&gt;harsh realization&lt;/strong&gt; that reliably identifying unique users is extremely difficult without a traditional authentication system like Google login.&lt;/p&gt;

&lt;p&gt;Ultimately, every approach has its &lt;strong&gt;advantages and disadvantages&lt;/strong&gt;, and the best solution depends on the specific requirements and constraints of the project.&lt;/p&gt;

&lt;p&gt;Project Link: &lt;a href="https://face-rank.vercel.app/" rel="noopener noreferrer"&gt;https://face-rank.vercel.app/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>softwaredevelopment</category>
      <category>ux</category>
      <category>web</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
