Adam

https://social.k3can.us/@me

Two-time college dropout who likes radios, computers and other nerdy things.
This instance is self-hosted.

Retro Homepage: http://www.k3can.us
Blog: https://blog.k3can.us
Gopher: gopher://gopher.k3can.us
EveryHam Radio Contest: https://EveryHam.org
eepsite: http://k3can.i2p

Public Key

npub18txepwfcgnvltreqxw6heaaatea4lx870d3344urxy7ea5ee9m2sm4khkw

NIP-05 Address

me_at_social.k3can.us@momostr.pink

Profile Code

nprofile1qqsr4nvshyuyfk043usr8dtu7774u76lnrl8kcc667pnz0v76vuja4gprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntnafyqj

Publishing to

relay.momostr.pink

Author Public Key

npub18txepwfcgnvltreqxw6heaaatea4lx870d3344urxy7ea5ee9m2sm4khkw

Show more details

Last Notes

2026-04-29 17:41:47 UTC

- reply

Fair, I think you're just going beyond what I've got experience with. I'm the only person on all of my sites, so I've never needed to deal with identifying different authors or anything.
I do remember seeing a webring (I think? Or maybe it was a webmention service) a little while back that required relme or indieauth, but I never ended up implementing it.

2026-04-29 17:06:52 UTC

- reply

What do you need a log in *for*, exactly?
If you just want to protect some pages, it might be very simple to implement in your webserver. If you want dynamic user accounts and content, then you may need to look beyond a static site.

2026-04-29 15:44:09 UTC

- reply

My understanding is that web mentions require some action from your site. The only way for full support on a static site is to use an additional service to provide the dynamic content.
As for those building block concepts, some work fine on a static site, but things like a login require some degree of dynamic content (or a lot of careful planning).