-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathabout.html
More file actions
189 lines (167 loc) · 11.2 KB
/
Copy pathabout.html
File metadata and controls
189 lines (167 loc) · 11.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>About Dipsana</title>
<link rel="icon" type="image/webp" href="favicon.webp">
<link rel="stylesheet" href="style-global.css">
<link rel="stylesheet" href="assets/about.css">
</head>
<body>
<header id="header"></header>
<main>
<!-- About me section -->
<section id="about-me" class="glass-bg">
<h1>About Dipsana</h1>
<p>
I am a Computer Science student focused on <b>full-stack web development</b> and continuously building
practical engineering skills through real projects.
</p>
<p>
I enjoy working on end-to-end applications such as <b>LokVeda</b>, where I implemented authentication
systems, session management, RBAC, and handled real-world deployment challenges including email delivery
and API integration.
</p>
<p>
My interests include <b>backend development, problem-solving, and system design fundamentals</b>. I
actively use DSA and programming concepts to improve my ability to write efficient and scalable code.
</p>
<p>
I believe in <b>consistent learning through building</b>, and I prefer understanding concepts deeply by
applying them in real projects rather than just theory.
</p>
<p>
Outside of development, I enjoy writing, music, and exploring new ideas across technology and languages.
</p>
</section>
<!-- Education section -->
<section id="education">
<h1>My Education Qualifications</h1>
<div class="cards" id="edu-cards">
</section>
<!-- Work-exp section -->
<section id="work-exp" class="glass-bg">
<h1>My Work Experience</h1>
<p>I'm looking for my first job experience.</p>
<a class="about-link" target="_blank" href="https://www.linkedin.com/in/dipsana">Linkedin</a>
<a class="about-link" target="_blank" href="https://leetcode.com/Dipsana/">LeetCode</a>
<a class="about-link" target="_blank" href="https://www.hackerrank.com/profile/dipsana">Hackerrank</a>
</section>
<section id="digital-awareness" class="glass-bg">
<h1>Digital Awareness</h1>
<!-- Brief Summary -->
<p class="awareness-intro">A journey through critical cybersecurity incidents that shaped my understanding
of digital safety...</p>
<!-- Incident 3 -->
<article class="incident-card">
<h2>Incident 3: Misleading Auto-Pay Refund Experience on Google Play</h2>
<div class="incident-summary">
<p><b>Brief summary:</b> A game pass that was supposed to be “free for the first month” unexpectedly
charged me ₹899. I later found out the offer was linked to the payment method, not the Google
account. I contacted Google Pay for help and waited for days, but they only told me to reach out
to Digital Sathi and my bank before finally suggesting I email Google Play support. After all
the effort, Google Play apologized but said they couldn’t help due to their policies and asked
me to contact the game developer instead. This experience showed how confusing subscriptions and
fragmented refund processes make it nearly impossible for regular consumers to receive fair
treatment.
</p>
<button>Read Detailed Account</button>
</div>
<div class="incident-details">
<p><b>Full detailed story:</b> On 12th September 2025, I purchased a “first month free” pass for a
mobile
game. I already had two in-game accounts — my first activation went smoothly and showed ₹0
charge, so I confidently tried the same process for my second account.
The Google Pay interface looked identical — no visible difference or warning about existing
trials. Even the in-game instructions clearly said that users could “activate auto-pay and
deactivate it later to enjoy the free month.” But the next day, on 13th September, I noticed
₹899 had been deducted from my account. That’s when I realized the so-called “free trial” wasn’t
based on my Google account but on my payment method itself — something that was never disclosed
beforehand.
I immediately contacted Google Pay support the same day. Initially, they gave automated
responses, and for a full week, there was no real follow-up. Eventually, I received a call from
a Google Pay support agent while I was at the bazaar with my uncle. I still remember how
confusing the conversation was — I even recorded it for clarity. The lady asked me to contact
Digital Sathi and my bank, saying they could assist better. After I pressed for clearer
instructions, she finally told me to mail Google Play directly using a specific address she
provided.
Following her advice, I mailed Google Play support on 20th September. After two days, I received
a polite but disappointing response: they apologized for the inconvenience but said they
couldn’t help since it “violated their policies.” They suggested contacting the game developer
for the refund instead.
By that point, I had already gone through an exhausting loop of steps — automated bots, delayed
replies, vague instructions, and constant redirections. It was a tedious process that most
average users wouldn’t have the patience or knowledge to complete.
This entire incident revealed how unclear subscription systems and rigid refund policies can
easily mislead customers. While the visuals and wording on payment pages create an impression of
a free trial, the fine print — or the lack of it — tells a different story. I genuinely hope
platforms like Google Play make these policies more transparent to prevent others from facing
the same confusion and loss.</p>
<button>Show Less</button>
</div>
</article>
<!-- Incident 2 -->
<article class="incident-card">
<h2>Incident 2: The Ransomware Lesson</h2>
<div class="incident-summary">
<p><b>Brief summary:</b> A teacher's habit of downloading movies from torrent sites led to a
ransomware attack that encrypted all his files, with a demand for ₹2000 to restore them. He
reached out for help but never followed through, serving as a stark lesson on the real-world
cost of digital risks.</p>
<button>Read Detailed Account</button>
</div>
<div class="incident-details">
<p><b>Full story:</b> A math teacher, who frequently downloaded movies from risky torrent sites,
found his laptop held hostage. All his personal files were encrypted, and a readme.txt sat on
his desktop, demanding a ₹2000 ransom for their return.
Feeling helpless, he reached out to a former student he knew was skilled with computers. During
the call, he anxiously asked about the student's well-being before revealing the crisis. He
promised to bring the laptop over for help.
However, the teacher never arrived. He broke the commitment, perhaps having found another
solution or resigned to his loss. The incident remained an unresolved lesson for the student—a
clear example of how digital dangers have very real and costly consequences.
</p>
<button>Show Less</button>
</div>
</article>
<!-- Incident 1 -->
<article class="incident-card">
<h2>Incident 1: Pirated Windows</h2>
<div class="incident-summary">
<p><b>Brief summary:</b> His first PC arrived with pirated Windows, immediately flooding Chrome with
persistent ads.
He discovered sophisticated malware disabling Windows Defender and altering
Registry entries daily. After constant manual cleanup, he took control by installing genuine
Windows himself—a hard lesson that led to building his current pure, authentic system.</p>
<button>Read Detailed Account</button>
</div>
<div class="incident-details">
<p class="show"><b>Full story:</b> You might be surprised to hear about a friend's early experiences
with computers. His
very first PC was technically genuine hardware, but it came with an unauthorized copy of
Windows. He noticed something was wrong almost immediately—his Chrome browser would pop up with
ads every couple of minutes. It turned out to be adware.
He followed online tutorials to clean it up. The scary part was realizing how sophisticated some
of these attacks were. They slowly tried to disable Windows Defender, and at one point, his
computer wouldn’t even restart properly. He even found changes deep in the system—like in the
Registry, where Windows manages app and system settings—with values being altered from 0 to 1.
He kept deleting those entries like a daily routine check until he finally decided to just
install a clean version of Windows 10 himself.
He's much more careful now and eventually built his current PC from scratch to avoid those kinds
of issues.</p>
<button>Show Less</button>
</div>
</article>
</section>
<section id="writings" class="glass-bg">
<h1 class="curly-underline">My Writings</h1>
<div class="cards" id="write-cards">
</section>
</section>
</main>
<footer id="footer"></footer>
<script src="script-global.js"></script>
<script src="assets/about.js"></script>
</body>
</html>