

vim, awesomewm, mbsync (isync),
As for recent discoveries: dwl — I was surprised on how robust it is, and how well it works.
A geek, who no longer likes tech


vim, awesomewm, mbsync (isync),
As for recent discoveries: dwl — I was surprised on how robust it is, and how well it works.
I’ve been running ministral on CPU on a home-server: works pretty nicely, not very performant for everyday tasks and the savings were not sufficient for it to make sense. It still was cheaper and faster to just use Mistral API and get better models.


EpicGames, huh? I did not expect that!


IMO, the only way the switch will actually happen is not the RAM or GPU, but if more manufacturers will start selling new/refurbished devices with Linux on it. Reason being: most people treat computers exactly the same way as I treat my car. I won’t bother replacing firmware, engine, transmission, or even tires on my car if there is no good reason for it. Same goes for people: they won’t be replacing OS, CPU, RAM, disk, etc, except there will be a really good reason for it.
Though, one thing to be mentioned: I generally see the trend that Linux is becoming more popular as more and more popular people adopt it (and are vocal that they have better time with it than with the alternative): PewDiePie, Linus Sebastian, etc. I think the trend might potentially accelerate, as more and more people are really unhappy with how well Windows works these days, and not everyone is ready to buy Mac (though the most recent Neo release success is a great indicator of how bad situation on the market is overall)


I presume that their employers just had terms that essentially gave the whole IP to the employer. And GPL is conflicting that, especially if they were producing the code using employers equipment, which essentially makes all the code to belong to employer. At the same time, GPL maintains the IP on the author of the code.
Not a lawyer, though I heard that some far-eastern companies have copied the US policymaking, which allows full separation of IP from the author.
There are folks form KDE who are trying to implement the Plasma Bigscreen solution: https://plasma-bigscreen.org/. Seems promising to me :)
Though, I’d still recommend to use an external device to avoid breaking the TV OS up ;)
The web ui with integration of email ecosystem for all those things are one of core selling points of https://sr.ht/
I’ve been following the software forge federation some time ago, and didn’t feel to pick up even when it was discusssed initially. It is a neat idea on high-level, though it requires forges to implement it, which has a risk of not picking up (just look at how much iterations of social media federation protocols was there, until ActivityPub arose).
On the other hand, all of the forges are based on a distributed technology out of the box: git. Most of the “modern days” comforts there are, are just built on top, and there are different ways to approach it.
As an example, you can send patches directly to the author in email. Is heavily implemented and suggested by https://sr.ht/ (1) — a software forge, which focuses on building a federated workflow by using email for communication (which is federated by design). This way, you can create “Pull Requests” without having account on the forge — all you need to do is just submit a patch. Author is very vocal about supporting it (2), and provides quite useful guides to learn (3), (4)
Generally, I’d say that e-mail is the only federative implementation you can get so far :)
What I can see clearly is that nation overall supports the warfare, and the annexation of neighbouring country — either silently, or loudly. This sentiment was there for even pre-full-scale invastion time period, even in anti-putinists circles (the “Crimea is not a sandwich” statement supporting that1).
There is an extreme minority that is against war, though they are against war in principle, and make no action to support the warfare to any side.
Removed by mod
Russian text in the video makes me very suspicious…


But on macOS it just uses Apple’s own WebKit fork, so it is very expected: WebKit is very optimised towards Apple hardware on macOS and iOS.


Each time I see anything like that, I just disengage with the content
I was going a long way, until I built a perfect AwesomeWM configuration for myself, and have not changed it for a while now. I am willing to switch to Wayland-based solution now, as it seems to be a bit more performant, but I just can’t make myself to do it: my config is really cozy and working
Neither am I. It’s just sad…


RCS is a really nice thing in principle, because SMS/MMS infrastructure is just awfully outdated from security standpoint.
Though, replacing SMS/MMS infrastructure which is internetless yet cross-carrier by making it a internet-first and tied to a single meta-carrier under the hood kind of defeats the purpose overall. There was an attempt to build an independent carrier-deployable implementation of RCS, yet it turned out to be bought off by Google :(
They have been for a while now. It’s just that now it kind of becomes obvious


I like systemd overall. The ease of use, uniform interface and nice documentation is awesome.
Though each time I try to run it on outdated hardware (say, my Thinkpad X100e, which is, well, a life choice xD) — it makes whole system much slower. IMO, openrc is not as bad, and in some ways it gives some capabiilties of systemd these days.
Wow, thanks for suggestion of Tdarr — that project indeed looks very nice. What is. your experience using it? Any quirks?
I share his vision. For this exact same reason I get angry, when people start rambling about software engineers being needed no more. It’s exactly the same abstraction layer extension, as compilers were, albeit the one that grants even less control over execution flow.