So essentially, federation of posts should slowly become less of an issue over time, but comments may possibly remain just as poor as ever because an instance might not be aware of certain users on other instances?
If this is federation implemented correctly, federation is dumb.
I've subscribed to the .zip backup, and my (virtual) bags are packed and at the door.
I did notice that @Neon_Carnivore's comment on the .zip announcement doesn't appear from lemmy.ml though, 8 hours later. Are we sure that instance is federating any better than kbin.social is, or is lemmy.ml the issue here?
I made this kbin alt just to browse because the delay federating with lemmy got so bad, so maybe it's a partially both kinda fault.
"No thanks, I've already played Assassins Creed: Black Flag like 10 years ago"
I've already scrapped the whole thing already anyway. It's an interesting concept, but it just didn't work for me. It makes sense if I was distributing a specific build to loads of machines, but for my own PC, its completely overkill.
If youâre rebasing on new commits then you set it up wrong. Consult the new instructions, there a lot more clear.
I had to rebase at the time because they completely reworked the bling stuff and scrapped Yafti, so my previously working builds were failing from that point onward, and I just thought it better to return to Arch.
This is just the Universal Blue template, but split out into it's own thing, right?
I was messing around with my own Fedora Silverblue build based on the older template, but it was a lot more annoying messing with the build pipeline and having to rebase onto new commits and stuff than it was to just set up everything I wanted in Arch and call it a day.
As much as I love NJPW, that sub is just too embarrassing to browse half the time.
Claiming TK stole everyone just because unlike Bushiroad he's actually willing to open up his chequebook during contract negotiations.
I typed a whole big thing about this and then kbin ate it on me.
TLDR:
- I'm happy for Rocky
- r/NJPW melting down
...well that commentary call from Michael Cole is going straight into Botchamania anyway. Accidentally naming someone not in the match yet... oof.
Someone smarter than me can probably explain this way better...
As far as Wayland goes, If I remember correctly, it's mainly just a protocol, and Gnome/KDE do all the actual work of making stuff happen, so both need to support it to have it work correctly. Like if Wayland was a language like French, Gnome and KDE need to know the French words for something before they can have conversations about it, and Gnome hasn't been as studious with it's dictionary in regards to VRR. X11 just has an ancient code-base, and adding support for anything involves a lot of effort to make sure something else isn't broken by the addition.
Gnome hasn't officially merged support for VRR yet, but there is a merge request to add support, and a patched version built on that code available if you want to try it (mutter-vrr, gnome-control-center-vrr) at least on Arch Linux's AUR.
I would like to think about various things later.
Me too, Kota. Me too.
The madman even put in the Alex Coughlin table spot from WK18 at the very end, the video might not be staying up for long!
I personally use an Nvidia card, so someone more knowledgeable can correct me.
For the open source drivers, Its a combination of both an AMDGPU (newer cards) or ATI (older cards) kernel module, alongside the mesa package, which provides 3D acceleration and OpenGL support. There is a separate package for Vulkan support too, either vulkan-radeon or amdvlk. For hardware video decoding, there is libva-mesa for VA-API, and mesa-vdpau for VDPAU support.
So yeah, Windows has one monolithic drivers .exe, and Linux has it all split out into separate chunks. How quickly you get updates depends on your choice of linux distro.