Admiral Patrick

I learned to play the guitar growing up as a young rapscallion in Mississippi. But things didn’t really take off until I moved to Memphis. There I met the Colonel and the hits just kept coming. Unfortunately, the fame went to my head, I gained a lot of weight, started wearing a white jumpsuit, and ate tranquilizers like they were trail mix. Then, in 1977, I died on the toilet.

Or did I?


I also develop Tesseract UI for Lemmy/Sublinks

  • 75 Posts
  • 1.1K Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle
  • I’ve been in an airbags deployed accident while wearing glasses. I was fine, and so were my glasses.

    Getting hit in the face with a pillow is actually worse than hitting the airbag at 50 mph. The airbag also partially deflates nearly as fast as it inflates. i.e. you don’t smack into it hard and it just cushions you and keeps you from smacking into the steering wheel. It’s also designed to work with the seatbelts, so those should also be keeping you from being right up in the airbag’s business. Hence, the technical name for airbags, SRS (supplemental restraint system)

    You’d have to be eye-level with the center of the steering wheel, not wearing a seatbelt, and right up on it for that to be a concern.


  • It’s annoying AF, agreed, but there’s no provision in the API to do anything about it. That’s just how the platform is designed to operate.

    The only things we can do about it are:

    1. Notice who does that frequently and refuse to interact with them (block them, tag them, remember their username, whatever works). If mods notice this, it would be nice if they’d ban those users from the community because what they do IS disruptive to the community.
    2. Optionally, don’t interact with accounts younger than a week in the “ask” communities because those are known to self destruct.

    If a user deletes their account or nukes the post, even admins can’t restore it as it just says “Permanently deleted”












  • What do you want to practice? Just general sysadmin stuff? Networking? Clustering? Horizontal scaling? All of the above?

    Old PCs are just Debian servers waiting to happen. Depending on their specs, you may be able to do VMs or you can utilize container frameworks like Podman, Docker, or LXC to deploy individual applications or application stacks. Or you can just bare metal install anything you want.

    Years ago, I bought a batch of 16 Wyse thin clients on eBay for about $15/each. These had 4GB SSDs and 2 GB RAM, so I upgraded about half of them with 64-120GB SSDs (whatever I had lying around) and 8 GB RAM. Thin clients can usually be found pretty inexpensively and are pretty power efficient, but they’re not performant workhorses. They’re great for practicing networking, VLANs, system orchestration (e.g. Ansible, Cockpit) application clustering and horizontal scaling, diskless workstations, setting up a demo office server and workstations, and even VMs if you’re just practicing; they’re a little underpowered to run a lot of VMs, but you can certainly run a few small ones just to practice managing them.








  • Technically, yes. But colloquially, when we’re talking about “analytics” we mean embedded 3rd party trackers that feed to Google or another outside entity. Those are embedded much deeper in the application and track things much more invasively such as how long you hover over certain links, how you move your cursor around the screen, your viewport size, browser fingerprinting, and more.

    The analytics I’m utilizing and referring to here are passive in that they’re collected anyway as part of the standard logging that happens when you access the webserver which is also part of our basic security posture. They’re not as granular or invasive but can still give you useful information about what parts of your site people use the most, how many clicks it takes a visitor to get from the homepage to where they want to be (by following the IP, URI, and seeing where that ends), how many visitors the site gets per day/week/month/etc, and such.


  • Logging is standard practice if you give even the slightest damn about security (read: you should), so I don’t see it as a problem. It’s what you use those logs for, how long they’re retained, and whether you sell them off.

    So as long as you’re only using them for security auditing and website analytics and don’t keep them forever and don’t plan to sell them to data brokers, there’s really nothing to fret over. A good place to disclose how you use the logs, how long you retain them, and what is logged is in the site’s privacy policy.


  • I do the occasional website for local businesses, and I never add any analytics code/trackers. One: they rarely ever ask. And two: the one time someone did ask for it, they never once logged into it or asked for trends. Three: I’d prefer not to unless they demand it.

    However, since I’m actually hosting the website for them, I can get decent heat maps from the access logs since they have the IP (which can be roughly geo-located), which URI’s are accessed (and those map to pages, and pages map to products/services), how often those are accessed, which page linked them to it or if they came directly to it (by checking the referrer header), which are most accessed (by count of the URI in the logs), and whether they’re accessing the site from desktop or mobile (via the user agent header). That can also be combined with any data from their “Contact us” form.

    One reason they’ve probably never asked for it is because I provide a quarterly report for them using that passive data, and they seem happy with it.