IdeaWell

Project ideas from Hacker News discussions.

10 years ago, someone wrote a test for servo that included an expiry in 2026

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Temporary fixes are expected, but a proper long‑term solution is needed
“I bet it’s just a quick and easy fix that will suffice while a proper fix (to avoid depending on external state) is written.” — db48x

2. Fixed time limits are inherently fragile; they will eventually be exceeded
“Any time constant will be exceeded someday.” — bombcar

3. Past tech scares (e.g., Y2K) highlight the importance of proactive preparation “Who here remembers the fud of Y2K?” — fny

🚀 Project Ideas

Generating project ideas…

Eternal Test Constants

Summary

  • Provides a library to declare “eternal” constants for tests that automatically adapt to future date limits (e.g., Unix rolls over, Y2K‑style bugs). - Solves the frustration of hard‑coded expiration dates breaking tests when time advances.

Details

Key Value
Target Audience Developers writing long‑lived test suites that reference time‑based boundaries.
Core Feature Generates dynamic “forever” timestamps that recompute based on current epoch and astronomical constants, preventing sudden test failures.
Tech Stack Python (or Go) library, CI integration via GitHub Actions, optional CLI.
Difficulty Medium
Monetization Revenue-ready: $0.01 per generated constant bundle

Notes

  • HN commenters lamented “end of Unix time” and Y2K anxieties; this tool gives them a painless way to future‑proof tests.
  • Could spark discussion on best practices for versioning test expectations across decades.

ExpiryScanner

Summary

  • Scans codebases for hard‑coded timeouts, expiry dates, or TTL values that will inevitably be exceeded.
  • Flags them for review before they cause silent failures.

Details

Key Value
Target Audience Engineers maintaining legacy systems with hidden time‑based constraints (e.g., token TTL, cache lifetimes).
Core Feature Static analysis rule that identifies literals resembling timestamps or durations and reports their logical expiry horizon.
Tech Stack Rust-based linter, CLI wrapper, integrates with existing CI pipelines (GitHub Checks).
Difficulty Low
Monetization Hobby

Notes

  • Directly addresses comments about “impossibly short periods after the heat death” and “expiry constants will be exceeded someday.”
  • Potential for community contributions to share discovered expiration patterns.

FutureProof Timestamp Service

Summary

  • API service that returns “future‑proof” epoch values based on immutable astronomical cycles (e.g., 27‑year Metonic cycle, 400‑year Gregorian cycle).
  • Allows developers to reference durable time points instead of ad‑hoc year numbers.

Details| Key | Value |

|------|-------| | Target Audience | Product teams building long‑term contracts, licensing, or ownership models that must survive decades. | | Core Feature | Returns epoch timestamps anchored to stable cycles, with built‑in warning when approaching cycle boundaries. | | Tech Stack | Node.js microservice, PostgreSQL for persistence, OpenAPI spec, rate‑limited free tier. | | Difficulty | Medium | | Monetization | Revenue-ready: $0.005 per lookup after 10k free calls |

Notes

  • Echoes sentiments like “using (system foundation timestamp)+100 years as forever ownership” and the desire to replace arbitrary +100‑year offsets.
  • Likely to generate discussion on the trade‑offs of relying on astronomical vs. computational time references.

Read Later