I have to agree. I've been playing around with this for a while at https://github.com/outages/ (which includes the bchydro-outages mentioned in the original comment).
While it's easy to gather the data, the friction in analyzing it has always pushed the priority of doing so below other datasets I've gathered.
There's a lot for large and small thematic communities around, for instance there's a sizeable Python Slack, my university has a few, and I'm in a few geographic ones for developers in different cities.
This is very cool, particularly as it's a nice way of supporting pkpass files on Android.
However, I do wish it would also accept PDF files (planning a trip right now and many museums just give you a PDF), as well as that it had some level of in-app organization. I have a lot of items and it's just one live. I suspect I need to use the calendar function to do the latter.
Make sure you use a bigger one I guess. The instance i chose wasnt one of the major ones, but did have traffic.
Its now down...not showing on the trackers either.
I am guessing its gone....dunno. Maybe it just crashed and whoever runs it hasnt fixed it or realized.
Similar to why i run my own email domain (but use workspace), i considered building an instance. But have had some reservations that I talked about here:
Sounds like this is only about public information (username, posts/comments, media). I'd expect those to be scraped and archived somewhere regardless of what the first party server does. For example in the case of reddit pushshift collected that information and published it via torrents and sites like unddit showed it.
