• 7 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle



  • Hey, this might be something I’m interested in, but I’m not sure because there aren’t many details in your readme.

    Some questions I’d suggest you answer in the readme:

    [Edit: after looking through the code quickly, some of my questions probably don’t male sense because this seems to be an alerting style monitoring tool, not a observability style monitoring tool. Answering my own questions for others that are curious:]

    What does it monitor?

    [Disk space and CPU use]

    What is the interface? Web? It does compare itself to grafana, so maybe. TUI? Maybe that’s what makes it more light weight?

    [It doesn’t have one, it sends telegram messages when alarm thresholds(?) are hit.]

    Does it only work on Debian? If not, are there deps that are required that are installed as dependencies of the deb?

    [Looks like it should work anywhere, the ‘watchers’ use the nix crate and read procfs, so I assume that means it should work anywhere without depending on anything besides the Linux kernel.]

    Is there history or is it real time only?

    [Realtime only, well I guess there’s the telegram history.]

    What does it look like? (Honestly, a screenshot could possibly answer most of these questions and a whole lot more.)

    [It doesn’t look like anything. There’s no screenshot because there’s nothing to screenshot.]







  • IMO, yes. Docker (or at least OCI containers) aren’t going anywhere. Though one big warning to start with, as a sysadmin, you’re going to be absolutely aghast at the security practices that most docker tutorials suggest. Just know that it’s really not that hard to do things right (for the most part[1]).

    I personally suggest using rootless podman with docker-compose via the podman-system-service.

    Podman re-implements the docker cli using the system namespacing (etc.) features directly instead of through a daemon that runs as root. (You can run the docker daemon rootless, but it clearly wasn’t designed for it and it just creates way more headaches.) The Podman System Service re-implements the docker daemon’s UDS API which allows real Docker Compose to run without the docker-daemon.


    1. If anyone can tell me how to set SELinux labels such that both a container and a samba server can have access, I could fix my last remaining major headache. ↩︎






  • As far as I’m aware something like that isn’t really possible.

    • it would prevent one person from making multiple fake accounts

    How do you define ‘a person’ and how do you ensure that they only have one account? Short of government control of accounts, I don’t think you can really guarantee this and even then there’s still fraud that gets past the current government systems.

    Then, how do you verify that the review is coming from the person that the account is for?

    IMO, we’d all be better off going back to smaller scale social interactions, think ‘social media towns’ you trust a smaller number of people and over time develop trust in some. Then you can scale this out to more people than you can directly know with some sort of web-of-trust model. You know you trust Alice, and you know Alice trusts Bob, so therefore you can trust Bob, but not necessarily quite as much as you trust Alice. Then you have this web of trust relationships that decay a bit with each hop away from you.

    It’s a rather thorny problem to solve especially since for that to work optimally you’d want to know how much Alice trusts bob, but that amounts to everyone documenting how much they trust each of their friends, which seems socially… well… difficult.

    Though the rest is actually easy™:

    • reviews wouldn’t be suppressed or promoted by paid algorithms
    • the algorithm WOULD help connect people to items they are interested in. But maybe the workings of it would be open source, so it can be audited for bad acting.

    You do what the fediverse does, you have all the information available to everyone, then you run your own ‘algorithm’ that you wrote/audited/trust. The hard part is getting others to give away access to all ‘their’ data.






  • Yeah I had the exact same thought - “huh, transparent case and charging led” - but I hear they’re going to come out with an update to adjust the intensity of it, so that may help that.

    Oh, nice. I’m also wondering if I can’t paint part of the light pipe so it doesn’t shine outward (as much?). Or print some sort of replacement with opaque sides. We’ll see if I ever decide I’m bothered enough by it to actually do that.

    I also upgraded from OG 512 - personally love the OLED so far. Screen is really nice, battery life will be great to have on my business trips, and the clickiness of the Steam and … buttons is a definite improvement. Do you need any of these things? No… but they are really nice things.

    Yep, totally agreed. Though, I finally started one of my 4 HDR games (Death Stranding) and if I knew it was going to make this much difference, I might have been clamoring for it sooner. Though, I don’t know if DS is hamming it up/designed more for HDR at the expense of the quality without it.


  • I upgraded to an OLED from an OG 512. I definitely don’t think it was a “must have” upgrade, but I was never really bothered by the LCD.

    The only thing I have approaching a complaint, which is more of a “huh I didn’t actually think about that”, is that on the LE the charging LED shows through the transparent case from the front. I think I can probably come up with some way to fix that (or at least make it much dimmer from the front).