I get very far by just keeping a set of folders for each piece of equipment in a git repo.

Pictures, etc, and sometimes the PDF manual if I bother.

The difficult part here is being consistent over time - making sure you mark down when you bought things, serial numbers, etc. a proper website/app will force you to do this, but there is flexibility in having whatever convention you like most

Strongly agree. A guide for dead simple setups would be incredibly useful (e.g. gsuite as idp, oauth for a single app).

It took me a few days to get that basic setup working, and a few days more to improve it. But once it was up, it was rock solid.

Keycloak might seem a little daunting to start with, but is basically glue between your idp (ldap) and whatever apps need to authenticate.

Having worked with data.gov extensively, this may be a huge nothing burger. The number of datasets fluctuates constantly, and ultimately the vast majority of those are just links to specific agencies. If you’re lucky, they link the to actual data, but most of the time the link just goes to a landing page for the team that collected the data.

The project stopped running years ago, or I’d pull actual statistics on what was removed or if there’s a shared keyword.

But running and syndicating articles based on two screenshots is not particularly useful. At least send in a FOIA request to find out which ones were removed.

The anti-Israel crowd are basically the MTG and Boeberts of the Democratic party. Right on down to outlandish claims about crisis actors

Dwarf Fortress almost made me fail a few courses in undergrad.

That is a game that redefines the concept of fun.