| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-www(at)lists(dot)postgresql(dot)org, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Contributors <contributors(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Introduce contributor badges |
| Date: | 2026-10-16 09:09:24 |
| Message-ID: | atHpxC2BMrej6SuR@msg.df7cb.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Re: Dave Page
> The fix is xkeys, which the docs already
> describe as the better option: tag the badge, people and profile responses
> with something like `pgbadge_<id>` and give `Badge` a `purge_xkeys`. That
> also replaces the per-holder URL loops.
I don't think we'd want that. The people URLs have to be stable so
people can link to them. if /contributors/people/myon/ gets replaced
by /contributors/people/myon_123/, that's much less personal. The same
applies to badges. (Or did I misunderstand the fix?)
I remember rejecting some of the invalidations for "too much looping",
I guess we should just implement it and then hopefully be done.
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2026-10-16 12:39:17 | Re: Introduce contributor badges |
| Previous Message | Christoph Berg | 2026-10-16 08:59:52 | Re: Introduce contributor badges |