m0xEE @m0xee@librem.one

@ParadeGrotesque
Yeah, I doubt it's a night and day difference, but it's something worth keeping in mind. My machine also hosts a Pleroma instance, having PostgreSQL DB obviously leads to heavy disk I/O too. In my case storage becomes a bottleneck, I might sacrifice 4.0's lower CPU usage for having a more balanced system.

@splitshockvirus
Good, keep it up!
Give SAMe a try too. There aren't enough clinical studies, but it could be good for joint health. I've been taking it regularly a few years ago for different reasons — liver health, but my joints felt much healthier at the time. Could be a mere coincidence, could be that I'm getting older and being less physically active nowadays, or… It could indeed be good for joints.
It's more expensive than most vitamins, but not too expensive, check it out.

@ParadeGrotesque
I can neither confirm, not deny it yet, as when I build 3.0 with the same set of libraries and with the same gcc, it results in a segfaulting binary — seems peculiar, but not uncommon as support for 32-bit PowerPC in compilers and tooling is spotty nowadays, lots of bugs!
In any case, this seems worth investigating.

@ParadeGrotesque
Ha-ha-ha-ha! Yes, those are different, names libtorrent and libtorrent-rasterbar are often used to distinguish the two.
Another thing that might be of interest: I've seen opinions on Transmission's issue tracker that while 4.0 branch might be lighter on CPU and RAM usage, it could be heavier on disk I/O and indeed, on old PowerPC MacMini with "spinning rust" storage that hosts transmission-daemon for me, I often observe low CPU load, but system being in "waiting for I/O" state.

@neauoire @prahou
I agree, intent is the key!

@condret
It gets so bad: you can buy a book on some technology/library/programming language published just 2 years ago and it's already part-irrelevant. If security updates would keep getting abused to push features, I expect people to stop updating and we get botnets again.
Providing updates for 2-3 major versions was a good practice — free software devs of course don't have the luxury to do it, but distros can and IMO should!

@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
"We've changed the APIs so you can no longer use older version of the client, but we've also revamped the UI and you have to learn using our software again — we've also removed a couple of features you might've used while we we're at it, tehe😊"
This being stuck in a permanent feature update loop is the single thing I absolutely loathe about modern tech. Instead of using the software you have to start servicing it.

@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
And the justification was: there is this new serialiser in JS that I'd like to use, so you guys have to update FF — WTF?! 🤯
They have backtracked on it, but only because this case got a bad publicity.
Software indeed got stable, but feature creep got so much worse, and it's not about free software only — proprietary paid-for software became like that too!
@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
Don't get me wrong, I'm not defending Debian in particular, like I said, there are exceptions: there are online APIs, there are lazy package maintainers… But I still find the approach of following upstream's footsteps closely fundamentally flawed. For every lazy maintainer there is an out-of-his-mind developer. Remember that time when Element Web got broken in Firefox ESR?

@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@neauoire @prahou
I was always wondering about the etymology: the relation between UI customisation and rice is as far from obvious as it can possibly be, and as a non-American I wasn't aware of that. The etymology is indeed… questionable, but is it still racist when it got adopted in an unrelated field by wider audience, not used in a derogatory manner and not targeted at particular ethnicity? 🤔

@get
How is making my point worse than the usual exchange of such original opinions as:
— Ubuntu bad
— It's only bad if you're unemployed and have all the time in the world on your hands

If notifications annoy you, I can unmention you, but you can fix this yourself as well — by muting the thread 🤷

@Forestofenchantment @Suiseiseki @nyanide @sysrq @enigmatico @condret

@condret
Entrusting the upstream developer with security fixes is a horrible idea: you update the package to get a fix for the new exploit only to find out that UI has changed, or config file format — because it was a good idea that happened to coincide with the security fix, and now you have to waste time on fixing your configs — no, thank you! There are exceptions, but in general… Fuck this! It's like building on quicksand.

@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
Free software devs are not "licensing out" their stuff — they shouldn't have control over how others use it, nor they should provide support for binaries built with modifications.
End user reports the issue to the package maintainer, who in turn checks if it's a problem with their modifications/configuration or an upstream bug, and acts accordingly — that is how it used to be and I don't see what was wrong with that.

@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
> distros should pack our stuff without modifications
No, just no! I probably won't be able to use half of the stuff I use with such an approach: systemd dependency, musl incompatibilities and so on — all of this has to be patched to work well with the distro's base system.
And there is nothing wrong with back-porting security patches — because I don't want those coming bundled with 5 new bugs or incompatibilities.

@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
"Hello, I'd like to report a problem: I have this binary that someone else has built for me and it does not work",— WTF is this shit? They won't even be able to tell you how to reproduce the problem even if they tried really hard: they simply don't know what flags the software was built with.
@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@condret
That's what you should always be doing, not for Debian, but in general, end users should never report problems upstream, that's what they have their distro's maintainers for — if they decide that it's indeed a problem with software and not their build of it, they report it further upstream 🤷
@Forestofenchantment @get @Suiseiseki @nyanide @sysrq @enigmatico

@newt @j3rn @prahou @ammoniumperchlorate
> wasn't enough to run Slack
But that is exactly the product of developers like that — who need 36 gigabytes or RAM to be productive 🤣
We've come full circle here, the system is reproducing itself.

@Hyolobrika @strypey
Oh, it was a quote post, I don't see those from this instance 😬
Considering there WAS some context, my reply might seem inappropriate, sorry.