🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆.
𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍
- Posts
- 19
- Comments
- 1389
- Joined
- 4 yr. ago
- Posts
- 19
- Comments
- 1389
- Joined
- 4 yr. ago
I've never had to reboot the server; I had to restart Synapse because if Memory leaks.
Are you using any bridges?
Anyway, it got too expensive to run my own, so I went back to Matrix.org. Now I'm mostly back on IRC except for a couple of rooms. IRC stinks, but Matrix has been nothing but a decade of pain.
This is a really good way of saying it!
I'll give concrete examples. With Arch:
- you either upgrade frequently, or risk a painful upgrade. I find I can reliably go a month between upgrades, usually with no problems, which doesn't seem too bad... unless you're used to upgrading once a year.
- frequent upgrades mean you often have to reboot, because the kernel changes frequently. This means rebooting at least once a month, sometimes more frequently.
- the previous is exacerbated because Arch expects that, if you "update" your repos metadata, you must upgrade all packages. You can install new packages if you don't update, but you can't selectively upgrade individual packages - at least, it's considered unsupported and a bad practice (
pacman -Sy <package>is bad). So if you want to upgrade to Inkscape to a new version, you may find yourself having to install a new kernel which might force a reboot. - you can pin packages, but it's not exactly a user friendly process. To do this, you have to edit a file in
/etc, and then keep track; and if you do want to upgrade a pinned package it's a bit of a PITA. You can easily get yourself into a bad state by pinning packages, and it's easy to forget about pinned packages. - if you simply don't update the repos metadata, software frequently becomes uninstallable because upstream sources disappear. This happens to me far more frequently than I'd expect; like, in a matter of days between updates.
- Arch's package config (
/etc) management is primitive. It just dumps new versions of config files in the filesystem, and it's up to you to notice, find, and merge them. There are third party tools to help, but they're basically dev-level diff/merge tools. You have to realize this is going on, go find a tool, install it; and because of the previous points, it means if you want to upgrade Inkscape, you may find yourself being forced to merge a grub config. - news sucks. Arch regularly (more frequently than other distros) pushes out breaking changes - things that will screw up your system. You are warned about these not when you try to upgrade, but only in Arch news, which you're expected to go and read any time you install software. This means that upgrading Inkscape can break your system, if you don't first go and read the Arch news; and Arch news readers are not installed by default, so you have to manually install and remember to run this every time you run
pacman. You may be lucky, but it you aren't and it bites you, you'll be told by the Arch community it's your own dammed fault for not checking news first.
Despite all of these terrible, fixable aspects of Arch, I run it everywhere. Why? Because, unlike Debian, I don't have to wait two years to get package updates, because the Arch package repository is simply vast and comprehensive, and because if you get in the habit of navigating the Arch maintenance minefield, it is the least breaky of distros, and the easiest to fix if it does get broken. I've had Debian installs get so fucked up, the package db so broken, that the only fix is to re-install. I've had Arch get borked, but never to an unrecoverable state.
Yup! Someone else pointed that out to me; I thought you were talking about the puppets and missed that you were talking about Jabber.
My bad!
Developers are really using AI as authorized admins?
I guess since you can document that it wasn't your fault - and as long as you weren't the dumb fuck who argued to bring the technology in-host - it's all good. You still pull a paycheck.
This generation of devs must have a lot less self-respect, tho. Cleaning up AI fuck-ups all day doesn't sound fun to me; I think I'd be bouncing to a different job.
Oh. I did misread that. Thanks for pointing it out!
running your own server is super lightweight.
Not IME. Are you running Synapse? Gigabytes of disk usage and memory leaks requiring restarts.
I can use IRC
The fact that many Discord and IRC channels (servers?) block Matrix connections has drastically reduced its usefulness for me. When I was running my own Matrix server, I could have gotten around it by using a puppet, but Synapse is such a hog I had to shut it down, and most of the IRC rooms I want to use don't allow Matrix proxies.
I wanted to visualize this, so:
┌────────────────────────────────────────┐ 6 │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡜⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡜⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡜⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠜⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⠊⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣀⡠⠤⠒⠊⠉⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ │⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⡠⠤⠔⠒⠉⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 1 │⠀⠀⣀⣀⠤⠔⠒⠊⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ └────────────────────────────────────────┘ 2010 2030It's not precise; I took the text
After getting to 1% in approximately 2011, it took about a decade to double that to 2%. The jump from 2% to 3% took just over two years, and 3% to 4% took less than a year
and converted it to:
csv
2011,1 2021,2 2023,3 2024,4 2025,6Since my mobile client renders the terminal output poorly,
Proof that Linux use is rising asymptotically, and there will be infinity Linux users by 2030.
Edit I just discovered something nasty about Lemmy, at least in how the instance I'm on is configured. Lemmy rewrites comments to proxy image requests of external sources through the Lemmy server, but the proxy doesn't work for some reason, so it fucks up the image; therefore, you can't see it. Not cool, Lemmy. Not cool.
It's not a dependency, though. I mean, it could be, but you can just ssd easily rewrite or copy/paste; his repos is basically a single for with a half dozen functions. It's a hundred LOC, or something. Copy the file, change the package. A little copying.
I usually just re-implement the asserts as I need them, but copying this one for over into your project introduces no dependencies. If you import testify, you now have dependencies on
- testify
- github.com/davecgh/go-spew
- github.com/pmezard/go-difflib
- github.com/stretchr/objx
- gopkg.in/yaml.v3
because that's what testify imports.
It's not the same, at all.
Ah. I read you backwards, by bad.
Modern microkernel designs have largely addressed the performance issues. L4Linux claims to suffer a mere 5% maximum throughout penalty:
For L4Linux, the AIM benchmarks report a maximum throughput which is only 5% lower than that of native Linux TU Dresden
It's not going to win benchmark competitions, but it's also probably going to not have a substantial impact on average workloads.
I get that you're saying that µ-kernels would compound the performance challenges of current RISC-V implementations (it's an extremely young architecture), and I'm not suggesting that it would have a performance benefit. If the tradeoff is easier support of the permutations of the RISC-V feature set and fewer bugs in simpler code, it may be worth it.
Homeopathy often dilutes by taking far less than half of a solution and diluting it in a large amount of fresh solvent. One process repeatability empties the entire container and refills it with solvent.
If you were diluting something by replacing only half with solvent, you'd have to do many more steps to get as pure solvent as homeopathy produces.
Homeopathy is a tremendously wasteful way of washing a container. It's hugely wasteful, and being a homeopathic environmentalist is oxymoronic.
Remember:
Promote a Kim,And the future is grim.
You mean less steps. True homeopathy dilutes until there's no measurable amount of the substance left; it's just pure sugar/water/alcohol. You're supposedly getting benefits from "the vibrations."
Of all the pseudo-science quackery, homeopathy is one of the most idiot-prone.
On the linked product page:
To be clear: that says nothing about 25.10, but there's a lot of into on that site and the answer is probably find-able from there. It looks as if there's fairly broad support; they claim a range of compatability with a wide variety of software.
You're underestimating just how brave astronauts need to be. A second reason there's less padding there: to make room.
Did someone mention Russia?
All hail our new Zeppelin overlords!
Yes. Let's give credit to Infinity War which did not end with the heroes winning. Despite clearly being a 2-parter that the heroes would eventually win, it was a complete story arc and if you were one of the 16 million Americans who died in the 5 year gap between the releases of Infinity War and Endgame, you'd have died knowing only that the heroes lost.
Endgame was pretty effective, if heavy-handed, at manipulating my emotions, so it's hard for me to count it as a pure win, but that's just me.
However, yes: Infinity War is an exception that proves the rule.
They snuck a 7 8 9 joke in there.