localstorage

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 0.2% — this entity appeared in 6 of 2,852 analyzed posts/comments in the seven days ending that day (6 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-11 17:13 UTCPost

   How I count unique visitors without cookies or storing IPs, and where it breaks - I've been building a small web analytics tool, and the part people ask about most is how it counts "unique visitors" without cookies, localStorage, or stored IPs. Here is the approach and its honest limitations. The ID For every request, the server computes: sha256(daily\_salt | site\_id | ip | user\_agent), truncated to 16 hex chars \- daily\_salt is 16 random bytes, generated once per UTC day and stored in the DB. Old salts are deleted after 24 hours, so once that happens, nobody (including me) can recompute yesterday's IDs from an IP. \- site\_id is included in the hash so the same user gets different IDs across different sites (preventing cross-site tracking). \- The IP is used solely for the hash and a country lookup, then immediately dropped. It never hits the disk. Sessions are defined simply as "same ID, active within the last 30 minutes" (one upsert per event). Where it breaks (by design or trade-off) \- The same person visiting on two different days = two visitors. That's intentional, but it means "monthly uniques" is effectively a sum of daily uniques. \- Same office/NAT + same browser version = counted as one visitor. Rare outside large enterprise networks, but real. \- A phone switching from Wi-Fi to cellular mid-visit = new ID, new session. \- iCloud Private Relay / VPNs rotate IPs, which slightly inflates counts. Based on my data, the margin of error is small enough to answer "is my traffic growing?", which is all most small sites need. It's not suitable for per-user product analytics; for that, you need explicit user identification. The Client Side \- SPAs: I patch history.pushState and listen for popstate events, tracking route changes as pageviews without requiring framework plugins. \- Transport: Uses navigator.sendBeacon, falling back to fetch with keepalive so events survive tab closure. \- Engagement/scroll depth is flushed on visibilitychange, not unload (since unload is unreliable on mobile). Happy to dive deeper into any part! Curious if anyone has a better trick for the NAT collision case that doesn't rely on client-side storage.

2. 2026-10-11 11:29 UTCComment

   I've built the same shape of tool (Astro, client-side, localStorage), so a few things from the other side of the same decisions rather than a design critique. The print-media route for the PDF is the one I'd push back on. It works beautifully on desktop Chrome and then falls apart in exactly the places invoice users live: iOS Safari's share-to-PDF ignores a chunk of @page rules, Android's print dialog is a coin flip, and the user has to understand that "Print" means "Save as PDF" in the first place. A 20-line-item invoice that crosses a page boundary is the other test, repeated table headers and "don't split this row" are flaky across engines. Rendering the PDF yourself (pdf-lib or jsPDF, both run fully in the browser so you keep the zero-backend claim) gives you a real file, a real download button, and the same output on every device. More code, far fewer "it printed blank" emails. Two smaller ones: logo upload into localStorage hits the quota fast if you store the raw base64, downscale to something like 600px on the canvas before saving. And for the i18n routes, number and date formatting should follow the invoice currency, not the UI locale (a German user billing in USD still expects 1,234.56), Intl.NumberFormat takes a currency option that handles that. Astro was the right call for this, by the way. The islands model is exactly "static SEO shell plus one interactive component".

3. 2026-10-11 09:39 UTCPost

   [Showoff Saturday] Built a 100% client-side, zero-backend invoice generator using AstroJS & Tailwind CSS v4 - Hey r/webdev, For this week's Showoff Saturday, I wanted to share a utility micro-tool I recently completed: **Quick Free Invoice** ( # The Technical Objective: Build a zero-maintenance, zero-database utility tool hosted at $0 operational cost on Cloudflare Pages that delivers instant browser performance without server latency. # Stack & Architecture: * **Framework:** AstroJS (zero-JS by default, islands architecture for interactive engines). * **Styling:** Tailwind CSS v4 using CSS-first configuration and Geist/Vercel-inspired dark/light design tokens. * **State & Storage:** Vanilla Web APIs + `localStorage` for offline persistence across sessions. * **PDF Generation:** Client-side vector rendering with custom `@media print` style normalization. * **i18n:** Dynamic multi-language routing (`/es/`, `/pt/`, `/de/`, `/fr/`) with crawlable HTML links. I’d love any feedback on the DOM performance, responsive layout breakpoints, or print media styling!

4. 2026-10-10 18:57 UTCComment

   LOL fair catch on how I worded it. There is a backend, and a database. There are no user accounts. All progress, stats, streaks, and achievements live in localStorage, and the OG images are pre-rendered from the share URL alone with no user record. So the server exists, it just doesn't know you.

5. 2026-10-10 18:32 UTCPost

   [Showoff Saturday] A daily logic puzzle with a client-side solver that powers the hints - Hence ( is a daily logic puzzle I built: a modern twist on the classic logic grid puzzle (zebra puzzles, Einstein's riddle). You get a grid and picture clues (instead of boring sentences), and you work out what goes where by pure deduction. The same puzzle for everyone, difficulty ramps from gentle Monday to tough Sunday. Every puzzle is generated ahead of time and run through a solver that verifies it has exactly one solution by pure deduction, then trims the clues down to the minimum each difficulty needs. The part I'm proudest of technically: the hint system runs a constraint solver in the browser against your current board state, so instead of revealing an answer it points at a clue that still rules something out from wherever you are. No framework, no signup: everything (progress, stats, streaks, achievements) lives in localStorage, so players get what feels like a full account experience with zero server. Sharing is personalized too, still with no account: the OG image for link previews is pre-rendered on the server from the share URL alone, so when you share an achievement or challenge a friend they see your unlocked character and stats in the preview, even though there is no user account on the server. The Instagram Stories share card is rendered entirely in the browser, and it came out really nice: your character, your stats, your achievement, all composited client-side into a vertical card ready to share. Happy to answer questions about the generator/solver or the picture-clue rendering