HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aaroncpina
Aaron.Pina.Blog.Article.08
C#2026–2026
aaroncpina / Aaron.Pina.Blog.Article.08

Aaron.Pina.Blog.Article.08

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
0GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-03-09 20:08:27 UTC to 2026-03-10 10:22:09 UTC.

012026-03-09 20:00:00 UTC to 2026-03-09 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 9, 20:002026-03-09 21:00:00 UTC to 2026-03-09 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 22:00:00 UTC to 2026-03-09 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 23:00:00 UTC to 2026-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 00:00:00 UTC to 2026-03-10 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 01:00:00 UTC to 2026-03-10 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 02:00:00 UTC to 2026-03-10 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 03:00:00 UTC to 2026-03-10 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 10, 03:002026-03-10 04:00:00 UTC to 2026-03-10 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 05:00:00 UTC to 2026-03-10 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 06:00:00 UTC to 2026-03-10 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 07:00:00 UTC to 2026-03-10 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 08:00:00 UTC to 2026-03-10 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 09:00:00 UTC to 2026-03-10 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 10:00:00 UTC to 2026-03-10 11:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 10, 10:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 9, 20:002026-03-09 20:00:00 UTC2026-03-09 21:00:00 UTC101
Mar 9, 21:002026-03-09 21:00:00 UTC2026-03-09 22:00:00 UTC000
Mar 9, 22:002026-03-09 22:00:00 UTC2026-03-09 23:00:00 UTC000
Mar 9, 23:002026-03-09 23:00:00 UTC2026-03-10 00:00:00 UTC000
Mar 10, 00:002026-03-10 00:00:00 UTC2026-03-10 01:00:00 UTC000
Mar 10, 01:002026-03-10 01:00:00 UTC2026-03-10 02:00:00 UTC000
Mar 10, 02:002026-03-10 02:00:00 UTC2026-03-10 03:00:00 UTC000
Mar 10, 03:002026-03-10 03:00:00 UTC2026-03-10 04:00:00 UTC000
Mar 10, 04:002026-03-10 04:00:00 UTC2026-03-10 05:00:00 UTC000
Mar 10, 05:002026-03-10 05:00:00 UTC2026-03-10 06:00:00 UTC000
Mar 10, 06:002026-03-10 06:00:00 UTC2026-03-10 07:00:00 UTC000
Mar 10, 07:002026-03-10 07:00:00 UTC2026-03-10 08:00:00 UTC000
Mar 10, 08:002026-03-10 08:00:00 UTC2026-03-10 09:00:00 UTC000
Mar 10, 09:002026-03-10 09:00:00 UTC2026-03-10 10:00:00 UTC000
Mar 10, 10:002026-03-10 10:00:00 UTC2026-03-10 11:00:00 UTC101

What Hacker News says

2 sources
There's some odd choices here. - 90 days is a very long time to keep keys, I'd expect rotation maybe between 10 minutes and a day? I don't see any justification for this in the article. - There's no need to keep any private keys except the current signing key and maybe an upcoming key. Old keys should be deleted on rotation, not just left to eventually expire. - https://github.com/aaroncpina/Aaron.Pina.Blog.Article.08/blob/776e3b365d177ed3b779… - You're not allowed to get a new token if you have a a token already? That's unworkable - what if you want to log in on a new device? Or what if the client fails to receive the token request after the server sends it, the classic snag with use-only-once tokens? - A fun thing about setting an expiry on the keys is that
Read the rest
it makes them eligible for eviction with Redis' standard volatile-lru policy. You can configure this, but it would make me nervous.
In Lazy JWT Key Rotation in .NET: Redis-Powered JWKS That Just Works

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.