m4m4m4m4

But it wasn't "win XP mode", and if you take a look, it doesn't look like it at all - it was an attempt from RedHat to provide a consistent look to both GNOME and KDE. There were Windows ports of Bluecurve.

(TIL Bluecurve caused a domino effect that made a developer quit RedHat)

For what it's worth, yesterday this thing was mentioned here.

Gentoo

I still can't use it :( It compiles now, but when trying to set it all I get is this:

Yeah, no. Pretty bad argument.

When you buy a phone you know it will have calls and SMS - it's what you bought the phone in the first place. You bought them because of that. RCS is still just a fancy alternative.

Barring that, the EU's DMA is forcing the most important chat apps to interoperate at the very least, though full support (including calling and such) isn't mandatory until somewhere in 2027.

And you're missing the point again - a company doing a multi IM service app, like Beeper Mini, is not the same that a group of volunteers doing a multi service IM app, like Pidgin. They're still going to be closed source and they will not guarantee to give support for platforms people need. Beeper mini on desktop? Beeper mini on Linux/BSD? Forget it.

I think they mean it more as it's not only gonna be Google but Apple who are going to be shoving RCS down their throats of people wether they want it or not by shipping it as default.

On the other hand, the era when corporations cared even the tiniest bit for open standards in instant messaging was gone long ago. Now all instant messaging is a complete mess, we users have to deal with a myriad of apps and protocols that in the end are doing the same thing for the sake of "privacy", and RCS will not fix that. Nor Signal, truth be told.

I yearn the glory days of multi-protocol IM apps like Pidgin and Trident on Android (though +IM seems to still be a thing) - when you could use whatever you wanted without "missing features" or risking to be banned.

I got a HP Elitedesk 800 G4. This thing came with an integrated Intel card and a AMD one. With the Intel one it works fantastic. With the AMD one, bleh. I disabled in on the BIOS as I use this with a thunderbolt display, so it's been like two years since I tried it.

Download it, cd to its directory, and do the standard procedure to compile a Cmake project:

mkdir build && cd build
cmake ..
make
sudo/doas make install

You're right, thank you

If you're using Arch and it's in the AUR, I'd look into that. Otherwise you'd need to compile it by yourself.

If you don't feel like compiling stuff, you'd want to file a bug against your distro so there's someone willing to step up as a package mantainer to prepare a package for it and make it available for your distro.

Afaik the "original" Lightly was born as a fork of Breeze, which in turn was born a fork of KDE4's Oxygen. So all of them are written in pure C++.

Now, I heard Luwx/Lightly was stalled so they forked it in boehs/Lightly, merged some pending patches and even did a new branch to port it to Qt6 - but last time I tried to compile it, it failed. Not sure if they're still working on it, though. (From my part never liked Breeze but found about Brise, which I found much more torerable).

If I were you I'd try to get in touch with the mantainers of boehs/Lightly. If that doesn't work, I'd go to ask the KDE VDG (I guess they should be reachable at discuss.kde.org); at least they should redirect you to someone versed in Qt C++ styling - which is very complicated, at least for me, 'cause C++ is no easy thing and it seems there's almost no documentation at all about the subject. Pinheiro himself struggled to find someone with enough knowledge of C++ to help him with his O^2 theme.

If that doesn't work either for whatever reason, which I doubt ever happens, I'd try asking Carl Schwan as a last resort, the guy that came up with Brise. He helped me with a stupid patch for it - of course he knows his thing and seems to be very cool.

It worked! Thank you so much!