[LewisCowles]well GitHub is doing Http 5XX errors (a range of them) to express how upset at my use of npm they are. I think I should take the hint and avoid Node / NPM
[tw2113], nickodd, gRegorLove, [mapkyca] and jamietanna joined the channel
[tantek]it would show no content other than the datetime of the most recent post by the person, perhaps with a calendar view so you could see who has been active this hour / today / this week etc.
[snarfed](also there are definitely open messaging and realtime services! matrix, jabber, etc. we just don't think about them much here since they're not web first)
[snarfed]or at minimum, you'd want to base it on how often that person posts normally. and even then, it would fail when they go on vacation or camping or whatever
[tantek]lol jacky I feel this is one of the things we discussed in that reply-context brainstorming sprint with [schmarty] on the afternoon of day 2 of Summit last year
jackyeh I think it's fair to have it; it's less processing for some people (I have to convert things into jf2 manually on my site which is why I don't even provide it as an explicit feed type)
Zegnatjacky: I love content negotiation, but it can lead to some … interesting code. I think bridgy (or was it a different service?) hard-coded rhiaro’s site
[snarfed]tantek: none of my family (sister, parents, partner) really post anything public on the internet at all. a couple maybe once a year or so, if that. afaict only the minority of my friends or coworkers do either. private, eg messaging and email and maybe social, sure! but *public*? no.
[tantek]snarfed, sure, the family use-case is handled by direct messaging already. the "heartbeat" reader is not for that, no need to coarsely solve an already more fine-grain solved problem
[snarfed]honestly i'm not convinced about using posting regularity for this "are you ok?" use case at all, public or otherwise, so i'll backa waay slowly
[tantek]it differs for different people, e.g. some do wikipedia edits (which as a per author contributions feed), some do github commits, etc. little bits of public activity, feeds, what we consider things we might otherwise post / want to post on our own sites
[tantek]you can build more from there, e.g. when someone otherwise active goes dark, a UI could highlight that, and then you could take direct action, reaching out, messaging etc. like you would today
[tantek]and it's less the "regularity" and more the "how recently did they do something that shows they are active" hence why I framed it as a "heartbeat" of sorts though I suppose that does imply regular=good, irregular=bad
[tantek]it can be an important way to watch out for warning signs for community health, i.e. if we start losing a bunch of folks who used to be excited, it might indicate that there was something that turned them off / drove the away, not enough to raise a fuss about it, just enough to stop bothering.
[tantek]Here's a thought about Indiewebify.me, in the "results" page for testing your site, it could display various achievements as badges! E.g. many (most?) of these would apply: https://indieweb.org/badge#Discourse
jackythe thing is, I plan to make it so that I don't rely on my in-built solution for a media endpoint (I'd want to use a fixed folder in nextcloud for it)