not actually sure if this is needed for the raspi but initially i thought metrics weren't working. (they are fine)

bumps the allowed fp error on harmonic sum to be 1.0 instead of 0.5

tls it's always tls

do we need csrf here or...

connecting the bits

instead of panicking

laksdl

whatever

whew ok

do as much per-event work as possible in the consumer, so subscribers can filter as cheaply as possible and have a pre-rendered message ready for them to send to connected clients.

spacedust link firehose

sometimes the socket gets disrupted and we otherwise just wait forever

this *could* (and maybe should) be done by detecting missed pongs instead.

this catches some amount of spurious notifications (accidental like + quick unlike) and also possibly some cases of bsky moderation actions? or maybe would need to listen to labellers for that (and prob should)

just to make more source-like terminology happen

running a little ahead of what actually exists but there's a chance to minimize breaking the api. it will probably break anyway but hey.

logs are still there but they're moved to `trace`.