Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SC
Posts
11
Comments
1,437
Joined
1 yr. ago

  • It was prominent in smaller businesses that wanted or needed a Unix but weren't going to pay what sun or IBM or HP and friends wanted for their hardware+software.

    It ate the proprietary Unix market awfully quickly and I don't think anyone really misses it.

    For me, educational stuff was all windows with a small amount of macs and I don't think I ever saw a Linux system in actual use anywhere.

    I used it on the desktop but that was super rare because hardware support was nowhere as good as now - even getting X up was a challenge (go read up on mode lines if you want some entertainment).

  • Oh that's nice. Hadn't seen their stuff before but that looks like a MUCH better option than Matrix, if you want a shiny gui app and that kind of experience. And can't argue with the pricing if you're running an open-source project with it, though I suppose you can make a comment that it's still got a vendor lock-in problem.

    And 100% agree that email is the gold standard, still, and yeah, nobody has really come up with an amazing web UI for searching list archives.

  • Sat down and made a pretty blinky drive access light for one of my retro Macs.

    Super happy with how it came out. though finding an appropriately amber LED proved super problematic - they're all "orange" now instead, but eh, close enough.

    (If you're bored, blinkenlights video at https://tube.uncomfortable.business/w/8JanGKAYjAmcySy1U3sMG8 )

  • As someone with recent platforms from both Intel and AMD, man, I do not like my 7700x's platform.

    It's just sporadically unreliable: sometimes it posts, sometimes it doesn't, sometimes the memory decides it needs to reset back to jedc standards instead of the expo settings, sometimes it doesn't. Even a successful POST can take upwards of a minute sometimes, and the system may or may not reset in the middle of it, resulting in two extended delays.

    Perfectly stable once the OS gets booted (memtest is fine, prime95 is fine and it boosts like crazy up to about 5.5ghz all-core), but getting there is such a pain on occasion.

    I realize more than a little of this is probably attributable to the motherboard manufacturer/efi settings, but the last few AMD platforms I've had are just wonky and less than 100% reliable compared to the last several Intel ones, which have typically just worked, correctly, every time.

  • I don't agree with the whole list, but the CLA requirement and corpo projects pinky-promising they'd never do a bad thing and then going to do a bad thing as soon as their investors demand returns is certainly a major risk and harm. I've started self-hosting everything for my personal use, and if it's not AGPL, then I assume at some point I'm going to get fucked and shouldn't rely on it.

    Also, the endless stupidity around everyone using Discord as their primary means of communication, discussion, issue reporting and whatnot. Politely, fuck Discord, and fuck anyone who thinks Discord is the right way to make anything accessible to the public.

    There's lots of other alternatives, including ye olde IRC and forums and even simple mailing lists - and no, I don't mean 'sign up for our newsletter!' nonsense, but an actual real mailing list. And, if you want something a little more modern, there's always Matrix which is probably feature-complete enough to compete with whatever you'd want to use Discord for anyways.

  • Yeah, exactly: if you know how it works, then you know how to fix it. I don't think you need a comprehensive knowledge about how everything you run works, but you should at least have good enough notes somewhere to explain HOW you deployed it the first time, if you had to make any changes as well as anything you ran into that required you to go figure out what the blocking issue was.

    And then you should make sure that documentation is visible in a form that doesn't require ANYTHING to actually be working, which is why I just put pages of notes in the compose file: docker doesn't care, and darn near any computer on earth made in the last 40 years can read a plan text file.

    I don't really think there's any better/worse reverse proxy for simple configurations, but I'm most familiar with nginx, which means I've spent too long fixing busted shit on it so it's the choice primarily because, well, when I break it, I already probably know how to fix what's wrong.

  • I'm a grumpy linux greybeard type, so I went with... plain text files.

    Everything is deployed via docker, so I've got a docker-compose.yml for each stack, and any notes or configuration things specific to that app is a comment in the compose file. Those are all backed up in a couple of places, since all I need to do is drop them on a filesystem, and bam, complete restoration.

    Reverse proxy is nginx, because it's reliable, tested, proven, works, and while it might not have all those fancy auto-config options other things have, it also doesn't automatically configure itself into a way that I'd prefer it didn't, either.

    I don't use any tools like portainer or dockge or nginx proxy manager at this point, because dealing with what's just a couple of config files on the filesystem is faster (for me) and less complicated (again, for me) than adding another layer of software on top (and it keeps your attack surface small).

    My one concession to gui shit for the docker is an install of dozzle because it certainly makes dealing with docker logs simple, and it simplifies managing the ~40 stacks and ~85 containers that I've got setup at the moment.

  • That's a fair assessment. I'll admit to having a severe case of doomerism when it comes to tech lately, and the levels of shit tech bros will go to to monetize shit has me skeptical there's any sort of protocol or technology that could be made bro-resistant for more than a short period of time.

    EEE is pretty prevalent and has been a very standard practice with these tech companies for a long time. See: Meta and Threads for a recent example.

  • Oh sorry; my goal here was for individual metering. I've got an Enphase solar system, so the Envoy is already doing whole-house monitoring.

    I'd like to be able to identify and ultimately be able to lower my load to stay under what the solar panels are generating, but that needs data I mostly don't have, and specific equipment to actually turn things on and off.

  • Gemini protocol

    IDK, but I don't think that the problem is that any particular application protocol is bad so much as it is capitalists going to capitalist, and they've shit all over everything in the Quest to Make a Buck.

    It's not like a new protocol, if it becomes as widely adopted, won't see the same vultures swoop in and strip mine any value they can find there, too.

  • I could have been a little more clear: I don't think the whole must-compete-or-forget-it mindset makes any damn sense.

    I'm more than happy to use software that does what I want/need (which, more and more, is simply just not fucking spying on, trying to sell things to, or otherwise annoying me) even if it's not like, the most bestest version of whatever.

  • I think it's less that it's "impossible" but rather that it's expensive.

    Honestly we've in general shoved too much shit into the browser that's not strictly related to just browsing web sites.

    And you "have to" support all the layers and layers and layers of added stuff, or you can't "compete".

    But, at the same time, the goals of making a good-enough browser that mostly works and isn't completely enshittified and captured by corpo big tech interests is a very worthy project and 100% support what they're doing.