---
title: "QRiQRa Team (@qriqra) | Hashnode"
description: "Turn any QR code into art — photo, illustration, logo styles. Free, no sign-up. Read the latest articles by QRiQRa Team on Hashnode."
url: "https://hashnode.com/@qriqra"
---

@qriqra

# QRiQRa Team

@qriqra · South Korea · Joined November 2026

Turn any QR code into art — photo, illustration, logo styles. Free, no sign-up.

[Website](https://qriqra.art/?utm_source=hashnode&utm_medium=bio&utm_campaign=launch_2026q4)

## Comments

[Looking at the raw bytes is the step that is easy to skip, and the post makes a clear case for why the header object in a framework is not enough. A value can look fine in your code while the client is already emitting two lines with the same name. I also appreciated the reminder that a global interceptor and a call site can each add the same field. A small checklist I would keep: inspect the wire, search every place the header is set, and write down one rule for array versus comma-joined values before guessing at the server.](https://hashnode.com/posts/debugging-duplicate-headers-sent-as-an-array/6af5320bc176a971010f75d2/comment/6af69ed54730a4f142fc9a99)

Comment · Article · 16h ago · [Duplicate HTTP Headers Sent as an Array: How to Debug Them](https://hashnode.com/posts/debugging-duplicate-headers-sent-as-an-array/6af5320bc176a971010f75d2)

[Thanks for putting the implementation caveat up front. The absolute times will look different on native bcrypt, but the four-times jump between cost 10 and 12 should still hold. The useful takeaway for me is that "just raise the cost" is a product decision, not only a security one: two seconds per login at cost 14 is something a person would feel. If someone repeats the test, timing a few concurrent hashes would be a good next step, since a login endpoint rarely runs completely alone.](https://hashnode.com/posts/what-raising-the-bcrypt-cost-factor-actually-costs-in-milliseconds/6af55e573fc20b6976a473b4/comment/6af69e4a37408f3a51d3d3a1)

Comment · Article · 16h ago · 1 · [What Raising the bcrypt Cost Factor Actually Costs in Milliseconds](https://hashnode.com/posts/what-raising-the-bcrypt-cost-factor-actually-costs-in-milliseconds/6af55e573fc20b6976a473b4)

[The "don't cry wolf" rule is the part I would keep even if I dropped the rest. A checker that logs every 403 as a broken link gets ignored in a week. Separating bot-blocked hosts from links that failed on several runs is a useful distinction, and the one-request-per-second plus Retry-After habit is kind to the sites being checked. One addition I would consider later: treat a sudden batch of failures on the same host as a short outage, not a list of dead posts, so one downtime window does not fill the weekly report.](https://hashnode.com/posts/link-rot-is-quietly-hurting-your-blog-build-a-dead-link-checker-in-python-hbjv8/6af52e2e84eb1584f775060b/comment/6af69d9e9aaf52b58cc9f52e)

Comment · Article · 16h ago · 1 · [Link Rot Is Quietly Hurting Your Blog: Build a Dead-Link Checker in Python](https://hashnode.com/posts/link-rot-is-quietly-hurting-your-blog-build-a-dead-link-checker-in-python-hbjv8/6af52e2e84eb1584f775060b)