Notices by wohali 💯 (wohali@octodon.social), page 26

@irl download it and run it yourself. feeds into prometheus, graphite, OpenTSDB, whatever.

it's basically a collection node that has its own fixed-memory in-RAM web server in case your backend goes down, or if you can't set one up for whatever reason.

@irl Prometheus and Grafana are fun.

I also like (in a limited way) Netdata. https://my-netdata.io/

@taweret Modern Times.

So very good.

@bvtsang all of my friends who helped run AX have moved on by now.

@bvtsang this outstrips my nihongo ability:

many years ago I helped run ACen for a few years...

I just can't bring myself to be in the middle of that many people unless absolutely necessary these days. it's super draining mentally.

@bvtsang ええ。コンをすきじゃない。

@bvtsang そうですね

@tom @bhtooefr @sc you need

Sofa King Sans

@matt I know that a lot of the ANC headphones cannot be modified with a mic to be used as aviation headsets exactly for this reason.

FAA regulations require that if the internal power source for the headphone dies, the headset must still function.

Most work around this by feeding power into the headset through a wire. Others require the use of one set of (wired) headphones underneath the other.

@nev awwwww!

@fluffy Well, + the entire concept of circles.

@fluffy Yeah, that's exactly the objection I have. Well put.

@fluffy I'll look into it. There's an attempt to add Fediverse support that I personally feel is ill-advised and glosses over bad actor vectors / data leakage. It could work, but I think it misses the forest for the trees, so to speak...

@fluffy btw I'm a committer with Dreamwidth, so if you get close with your implementation design, lemme know. I can def. make a case for it.

I honestly thing the LJ/DW model has a lot of things people have completely forgotten about that are actually meaningful in this space. (Not saying you don't know these things, I know you do!)

@fluffy Right, if it's *just* post content, or at the directory level, and coarse grained, it can work. but it can't work for fine grained access and will be super leaky.

@fluffy i've thought a bit about static site integration. best I can come up with is the equivalent of .htaccess or nginx stanzas that get included server-side to enforce. but it's still leaky into things like indexes, unless you're comfortable with metadata (titles, tags, etc.) being exposed.

i *really* want to move to a static site but this is presently holding me back.

@JigmeDatse Right! Got it now. Yeah, this slide is for internal comms, not external ones.